Flxpoint Knowledge

Contact us

Zanders as Source

Table of Contents

Add Source and Establish Connection Product & Order Operations Product Operations Order Operations Troubleshooting Common Errors

Zanders is a leading wholesale distributor of firearms, ammunition, and outdoor sporting goods. When connected as a source in Flxpoint, it enables automated catalog imports, real-time inventory syncing, and seamless order fulfillment. Depending on your account setup, you can integrate using FTP credentials for inventory syncing and API access for order fulfillment. Once configured, the integration continuously keeps your Zanders products, inventory levels, and order updates in sync with Flxpoint, eliminating manual work and ensuring your storefront always reflects accurate data.

 

Add Source and Establish Connection

🧭 Phase 1: Launch the Source Wizard +
Open Sources and start the Wizard
Go to Sources (building icon) → + Add Source → Configure Single Source. This opens the Source Wizard.
Step 1 — Create Source
Enter a clear name (e.g., Zanders as Source). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most Zanders setups, we recommend Vendor Warehouse. Use the other options only if they better match how you store and ship inventory.

  • Vendor Warehouse (Recommended): You send POs/FRs to Zanders so they ship directly to your customers.
  • Internal Warehouse: You stock items and ship from your own facility.
  • External Warehouse: A 3PL or external partner ships your owned inventory.
  • Product Data Source: Content-only source to enrich product details (no fulfillment).
For Zanders: select Vendor Warehouse. This enables sending Fulfillment Requests to Zanders and using their inventory for routing.
After selecting the Source Type, click Save & Next.
Step 2 — Vendor Set-Up
Choose Yes (Recommended) to Assign Vendor → Confirm. You’ll enable Vendor reporting and optional portal.
Step 3 — Order Fulfillment
Decide if this source is eligible to fulfill orders:
  • Yes (Recommended): You can route orders here.
  • No: Routing/Shipping steps won’t apply.
Click Confirm.
Step 4 — Order Fulfillment Settings
Use Defaults or No, Customize. You’ll see:
  • Override: Auto Processing (Use Global / Auto Process / Do NOT Auto Process).
  • Commit Stock + Inventory Management Options.
  • Allow Backorders / Cancel Unacknowledged Items.
Click Save & Next.
Step 5 — Shipping Cost Estimations
Pick one:
  • Yes, Use Rate Shopping (Real-Time Estimates).
  • No, Set Up via Rules.
If using real-time, acknowledge you have valid dimensions, weight, and source address. Click Save & Next.
Step 6 — Order Routing Groups
Enable on all routing groups? Select Yes or No, Customize. Optionally mark Default Order Routing Group. Save & Next.
Reminder: Complete Step 1 — Shipping Methods and Step 2 — Source Location in Phase 2 below, then return (if needed) to finalize.
🚚 Phase 2: Shipping Methods & Source Location (Finish the Wizard) +
Goal

Finish the Source Wizard by confirming your Ship From location and reviewing shipping behavior for Zanders. Zanders requires the shipping method to be included with the order. You can map your system’s shipping options to Zanders’ expected shipping codes so each Fulfillment Request includes the correct carrier and service.

Step 1 — Shipping Methods
When the wizard opens the Shipping Methods step for this Source:
  • Click Add Method to open the creation form.
  • Enter the required details:
    • Name: e.g., "UPS".
    • Shipping Code: e.g., "UPS-GND" (must match the Zanders / supplier code).
    • Packages: Choose Best Fit for predefined sizes or Custom for manual packaging.
    • Carrier/Method: e.g., "UPS Ground" (links to a Flxpoint carrier method).
Example mapping:
– Storefront method: UPS Ground → Supplier Shipping Code: UPS-GND, Supplier Shipping Carrier Name: UPS.
Ensure your Send Fulfillment Request mapping template includes the appropriate shipping method for each order. If you’re unsure about available shipping codes, contact Zanders or Flxpoint Support.
Optionally, configure Advanced settings on the method:
  • Shipping Label Code: Set if purchasing labels (e.g., via UPS).
  • Default Carrier Code: Carrier identifier (e.g., "UPS").
  • Custom Carrier Name: Custom label shown in Flxpoint.
  • Custom Method Name: Custom label for the service level.
Click Save to apply the method.
Create Shipping Method in Flxpoint
Click the image to view the full-size Create Shipping Method screen.
Step 2 — Source Location (Ship From)
Enter the Ship From address:
  • Address, City, State/Code, Postal Code, Country/Code
  • Optional: Contact Name, Phone, Email
This address is used for routing logic, rate shopping (if enabled), and reporting.
Finish the Wizard
Review Steps 1–2, then click Save and Complete. The Source Wizard is now finished for Zanders.
Next: Proceed to Phase 3 to gather the Zanders credentials you’ll use for all Zanders integrations.
🔐 Phase 3: Gather Your Zanders Credentials +
Goal

To connect Zanders in Flxpoint, you’ll first confirm that your Zanders dealer portal access is active. Then, you’ll gather all required FTP credentials (for inventory) and API credentials (for order fulfillment). This connection is created once and powers all Zanders-related operations inside Flxpoint.

Step 1 — Confirm Your Zanders Dealer Portal Access
Log in to the Zanders dealer site using your dealer credentials.
  • You can log in successfully without errors.
  • Your account is active.
  • You have access to the Zanders Dealer Portal.
If you are unable to log in: reset your password or contact Zanders Support to resolve access issues before continuing.
Step 2 — Gather Your Zanders Credentials
When configuring Zanders operations in the Operations section of Flxpoint, you will be prompted to select or create a Zanders Connection. Collect the following details in advance so you can complete that connection in one pass.
1️⃣ FTP Credentials (Required for Get Inventory [Primary])
Zanders provides inventory feeds via FTP. You must collect:
  • FTP Protocol: FTP or SFTP (as provided by Zanders)
  • FTP Host: e.g., ftp2.gzanders.com
  • FTP Port: Usually 21 (unless Zanders specifies otherwise)
  • FTP Username: Provided by Zanders
  • FTP Password: Provided by Zanders
Note: These FTP credentials are required for Inventory [Primary] ingestion. If you do not have them yet, contact your Zanders representative.
2️⃣ API Credentials (Required for Sending FRs & Order Fulfillment)
All order operations — such as sending Fulfillment Requests and retrieving shipment data — use API credentials. Zanders requires different API accounts depending on the product type and shipping destination.
Important: These API credentials are not the same as your website login. They are separate service accounts created specifically for order operations.

Zanders Account Types for Ordering
Zanders uses three distinct account types. Each account has its own API username and password:

  • 🔵 1. Main Account – Used to ship products back to your store. This account can include both accessories and firearms in one order.
    • Main Account Username
    • Main Account Password
  • 🟢 2. Accessory Direct Ship (DS) Account – Used to ship non-serialized accessories directly to the consumer.
    • Accessory Account Username
    • Accessory Account Password
  • 🔴 3. Firearms Direct Ship (DS) Account – Used to ship serialized firearms directly to FFL holders.
    • Firearm Account Username
    • Firearm Account Password
Critical Ordering Rules
  • Direct Ship orders cannot mix accessories and firearms. Send these as separate orders using the appropriate DS account.
  • Main account orders (shipping to store) may include both categories in the same order.
How Flxpoint Uses Your Zanders Connection
Once created, your single Zanders Connection is automatically reused for:
  • Inventory [Primary] via FTP
  • Inventory [Secondary] (if configured)
  • Fulfillment Requests via API
  • Shipments via API
You do not need separate logins for each integration — all operations pull from the same saved Zanders Connection.
Next Configure Product & Order Operations 🚀
Once you have:
  • Confirmed dealer portal access
  • Collected FTP credentials
  • Collected API credentials for all three Zanders accounts (Main, Accessory DS, Firearms DS)
go to the Operations section of this guide. Follow the setup prompts to configure the Zanders integrations you need. When asked, select or create your Zanders Connection and enter the credentials you collected earlier.
× Enlarged screenshot

 

 

Product & Order Operations

Now that you’ve finished the wizard, you’ll see RSR has four integrations available in Flxpoint: two for products and two for orders. Get Inventory [Primary] (GIP) and Get Inventory [Secondary] (GIS) keep your RSR stock and pricing updated, while Send Fulfillment Requests and Get Shipments handle sending orders to RSR and pulling back shipment/tracking data. All four use the same RSR connection and credentials you just set up so you can simply choose the operations that match your workflow.

 


Product Operations

Get Inventory Primary imports your Zanders catalog including metadata such as attributes, images, titles and description. We recommend running this once daily to import any new items. Get Inventory Secondary is a faster, more efficient operation to import more frequent pricing and quantity updates. We recommend running this hourly. 

Get Inventory (Primary)

Supported

Zanders – Get Inventory [Primary]

Introduction

The Zanders – Get Inventory [Primary] integration automates the import of full product data from Zanders into Flxpoint using a static FTP feed. It retrieves pricing, quantities, SKUs, dimensions, identifiers, and additional product attributes at both Parent and Variant levels. Once configured, the integration keeps your catalog up-to-date with minimal manual intervention.

On this section
Setup Overview

Setting up Zanders – Get Inventory [Primary] in Flxpoint is a guided, three-step flow:

  • 1 Establish the FTP connection to Zanders using the credentials they provide.
  • 2 Configure settings that control how incoming inventory behaves (including Archive / Un-Archive).
  • 3 Define your mapping template so Zanders fields land in the correct Flxpoint inventory fields.
Step 1 — Establish Connection to Zanders’ FTP Server

The integration begins by securely connecting Flxpoint to Zanders’ FTP server. In Step 1, you’ll enter the FTP details provided by Zanders:

  • Connection Name: e.g., Zanders FTP Connection (or any descriptive name).
  • FTP Protocol: Choose FTP or SFTP as specified by Zanders.
  • FTP Host: The server address (for example, ftp.zanders.com).
  • FTP Port: Usually 21 for FTP, 22 for SFTP.
  • FTP User: Your Zanders-provided FTP username.
  • FTP Password: Your Zanders-provided FTP password.

Important: These credentials are provided by Zanders when your account is set up. If you don't have them, contact your Zanders representative.

Click Advanced Settings to configure additional options (if needed):

  • File Transfer Mode: Use Binary for most product files (recommended).
  • Maintain Constant Connection: Turn ON for large files to reduce FTP timeouts.
  • Unbuffered Private Data Channel: Typically left OFF unless required for troubleshooting.
Tip: After configuring all settings, click Test Connection to verify everything works before saving.
Step 2 — Configure Settings

Step 2 defines how Flxpoint should treat incoming inventory data from Zanders. One of the most important options is the Archive / Un-Archive Inventory setting.

Archive / Un-Archive Inventory

When this setting is enabled, Flxpoint will automatically:

  • Archive SKUs not found in the latest Zanders feed by setting their quantity to 0.
  • Un-archive SKUs that reappear in future feeds, reactivating items when they’re added back.
Why this matters: Some suppliers remove items from their feed entirely—rather than marking them out of stock—and later add them back when restocked. Archive / Un-Archive keeps your catalog clean without losing product history.
Recommendation: Do not enable Archive / Un-Archive Inventory in both Get Inventory [Primary] and Get Inventory [Secondary] for the same source. Turn it on in one or the other (typically the primary feed).
Step 3 — Define a Mapping Template

After your connection and settings are in place, you’ll define how Zanders’ fields map into Flxpoint inventory fields.

  • Choose or create a mapping template specifically for Zanders.
  • Map essential fields like SKU, Price, Quantity, and identifiers.
  • Configure any transformations you need (for example, price markups or concatenated titles).
Tip: For inventory feeds, make sure to map both product details (Brand, Category, Description) and inventory quantity fields.
Configure SKU Mapping

In the Master SKU section of your mapping, set up how SKUs flow through your system (Inventory SKU → Master SKU → Listing SKU). This is also a good place to add a SKU prefix to quickly identify Zanders products.

  • Map Zanders’ Item Number to Parent SKU, Variant SKU, and (optionally) Master SKU.
  • Optionally add a prefix such as ZND- so you can visually distinguish Zanders SKUs.
Activate and Verify

Once your mapping is in place, complete the wizard to activate the integration:

  • Click Save and Complete on the final step to activate your Zanders source.
  • Run the integration manually the first time to confirm product data looks correct.
  • After validation, configure a schedule so inventory keeps updating automatically.
Next Steps: The initial inventory sync may take some time. Monitor progress in the Integrations area of your Flxpoint dashboard and spot-check a few products for SKUs, quantities, and pricing.
On this section
Mapping Template (Zanders)

The Mapping Template defines how Zanders’ product data fields connect to your Flxpoint inventory fields. It ensures data flows correctly into Parent and Variant records.

Field Mapping

This is a friendly overview of how common Zanders fields flow into Flxpoint.

Field Maps To Example Purpose Status
Item Number (T) Parent: Parent SKU ZND12345 Identifies the product at the parent level Required
Item Number (T) Variant: SKU ZND12345 Identifies the product at the variant level Required
Item Number (T) Variant: Master SKU ZND12345 Links the variant to the parent SKU Required
Manufacturer (T) Parent: Brand Zanders Optics Records the brand of the product Optional
Category (T) Parent: Category 1 Optics Primary category for the item Optional
Description 1 (T) Parent: Description Zanders Rifle Scope Primary description of the product Optional
Description 1 (T) Variant: Title Zanders Rifle Scope Base title for the variant (often combined with Description 2) Optional
Description 2 (T) Variant: Description High Precision 4x Zoom Secondary description of the variant Optional
Price 1 (N) Variant: Cost 150.00 Records the cost of the variant Optional
MAP Price (N) Variant: MAP 179.99 Minimum Advertised Price Optional
MSRP (N) Variant: MSRP 199.99 Manufacturer’s Suggested Retail Price Optional
Quantity 1 (N) Variant: Quantity 50 Available quantity for the variant Optional
UPC (T) Variant: UPC 012345678905 UPC identifier (rule can remove leading zeros) Optional
Manufacturer Part Number (T) Variant: MPN ZND-MPN-123 Manufacturer Part Number Optional
Height (N) Variant: Height 5 Product height Optional
Length (N) Variant: Length 10 Product length Optional
Width (N) Variant: Width 3 Product width Optional
Weight (N) Variant: Weight 2.5 Product weight Optional
Serialized (T) Variant: Requires FFL True (if Yes) Indicates if the product requires an FFL (via rule) Optional
Rules You Can Use

Mapping Rules let you transform Zanders data as it’s mapped into Flxpoint. Typical rules for this integration:

  • Set True if Serialized = Yes – sets Requires FFL to true when the Serialized field is "Yes".
  • Remove leading 0 in UPC – strips leading zeros from UPC values to keep identifiers consistent.
  • Desc1 + Desc2 – combines Description 1 and Description 2 into a single title or description field.
Create your own rule: Go to Mapping Utilities → Mapping Rules, click Create New Rule, pick Conditional, and choose an Input Type (String/Number/Boolean).
Note: After creation, the rule’s type and input can’t be changed.
On this section
Key Details

Keep these points in mind when working with the Zanders – Get Inventory [Primary] integration:

  • Data coverage: The integration retrieves SKUs, pricing, quantities, weight/dimensions, and core identifiers from Zanders’ FTP feed.
  • Parent & Variant levels: Fields can be mapped at both parent and variant levels so catalog structure stays consistent across all sources.
  • Scheduling: After testing a manual run, you can enable a schedule so inventory updates run automatically.
Quick Checks Before You Debug
  • FTP connection in Step 1 is saved and passes Test Connection.
  • Settings in Step 2 are saved, including Archive / Un-Archive (enabled in only one inventory integration).
  • A mapping template is selected and includes SKU, Cost, Quantity, and primary identifiers.
  • At least one manual run has been completed and shows as Successful in job history.
Troubleshooting

If something goes wrong with the integration, start with these areas:

  • FTP Connection Failure: Re-check host, port, user, and password. Confirm Zanders has enabled your FTP access and test again.
  • File Not Found: Verify the Inbound Remote File Folder path and confirm Zanders is dropping files there.
  • Data Mapping Issues: Review the mapping template and rules for fields that look empty or incorrect (UPCs, titles, quantities, etc.).
  • Incomplete Product Data: Open a sample file from the FTP location to confirm required columns like Item Number, Price 1, and Quantity 1 are present.
What this means for you
  • ✅ Use manual runs first to validate data before turning on schedules.
  • ✅ Keep Archive / Un-Archive enabled in only one inventory integration per source.
  • ✅ If you’re unsure, share a sample Zanders file with Flxpoint Support so they can confirm mappings and rules.
 
 

Get Inventory (Secondary)

Supported | Zanders - Get Inventory [Secondary]

The Zanders - Get Inventory [Secondary] integration retrieves a focused inventory file from Zanders via FTP and updates Variant-level fields in Flxpoint such as SKU, Cost, MAP, MSRP, and Quantity. Use this integration when you only need streamlined inventory updates for existing products.

How the Integration Works
This integration:
  • Connects to Zanders’ FTP server using credentials they provide.
  • Downloads an inventory file from a configured inbound folder.
  • Parses SKUs, prices, and quantities and updates Variant-level inventory fields in Flxpoint.
Core Connection Settings
  • Connection Name: Any clear label, e.g. Zanders Inventory Secondary.
  • FTP Protocol: FTP, SFTP, or FTPS (per Zanders specs).
  • FTP Host & Port: Server and port from Zanders (e.g. ftp.zanders.com, 21/22).
  • FTP User & Password: Your Zanders FTP credentials.
  • Inbound Remote File Folder: Folder where Zanders drops the inventory file, e.g. /zanders-inventory-secondary.
  • Maintain Constant Connection (optional): Enable if files are large or transfers are frequent.
Sender/Receiver Identifiers
  • Our Sender/Receiver ID: FLXPOINT
  • Our Sender/Receiver Qualifier: ZZ
  • Their Sender/Receiver ID: ID provided by Zanders (e.g. ZANDERSID).
  • Their Sender/Receiver Qualifier: typically 12.
Recommended Setup Flow
  • Step 1: Enter FTP credentials and folder path from Zanders.
  • Step 2: Configure Sender/Receiver identifiers.
  • Step 3: Click Test Connection to validate access.
  • Step 4: Save the integration and proceed to the Mapping dashboard.
  • Step 5: Run manually once to validate, then add a schedule for ongoing updates.
Tip: Start with a manual run and confirm a few products in Flxpoint before enabling a recurring schedule.

Core Inventory Mapping
The mapping template for this integration focuses on Variant-level fields:
Field Maps To Example Purpose Status
Item Number (T) Variant: SKU ZND12345 Primary variant identifier Required
Price 1 (N) Variant: Cost 150.00 Supplier cost Optional
Price 2 (N) Variant: MAP 145.00 Minimum Advertised Price Optional
Price 3 (N) Variant: MSRP 140.00 Manufacturer’s Suggested Retail Price Optional
Quantity 1 (N) Variant: Quantity 50 Available inventory Optional
Mapping Options
  • Field: Map a Zanders source field directly to a Flxpoint field.
  • Value: Use a fixed value for every record (e.g., set all quantities to 0 while testing).
  • Mapping Set: Apply a reusable mapping set for concatenation or complex transforms.
  • Rules: Apply if/then logic during mapping (see below).
  • Don’t Map / Set to Empty: Skip or clear fields you do not want to populate.
Mapping Rules (Optional)
You can add Mapping Rules to adjust values before they are written to Flxpoint. Common patterns:
  • Set Quantity to 0 when an “Available” flag is 0.
  • Force Cost above a minimum threshold for specific SKUs or brands.
Example Rule: “If Available = 0, set Quantity 1 to 0” helps prevent overselling when Zanders flags an item as unavailable.

Common Questions
  • What type of data is updated? Variant-level fields such as SKU, Cost, MAP, MSRP, and Quantity.
  • Does this create new products? No. It expects SKUs that already exist in your catalog or source inventory.
  • How often should it run? Most users run inventory feeds multiple times per day, depending on how frequently Zanders updates their file.
Troubleshooting
  • No file found: Confirm the Inbound Remote File Folder path and verify with Zanders that the file is being dropped there.
  • Connection errors: Re-check host, port, protocol, and credentials, then use Test Connection.
  • Inventory not updating: Verify SKU mapping (Item Number → Variant SKU) and confirm the integration job completed successfully.
Tip: If you see mismatched quantities, download the raw Zanders file and compare a few SKUs against what Flxpoint shows after a run.
 
 
Optional but recommended

Keep your catalog up to date automatically

After configuring Get Inventory Primary and Get Inventory Secondary, you can schedule both jobs so items, inventory, and pricing update for you.

  • Schedule Primary to import new and updated items.
  • Schedule Secondary after Primary to refresh stock and pricing.
  • Adjust the cadence anytime if your supplier changes their update frequency.
How to schedule Get Inventory operations in Flxpoint
Click the animation to view it larger.

 

Order Operations

Configure Flxpoint to route orders to vendors for fulfillment and  import the shipment details, so they sync back to your sales channel and customer.
 

Send Fulfillment Requests

Supported | Zanders - Send Fulfillment Requests

The Zanders - Send Fulfillment Requests integration converts Flxpoint fulfillment requests into Zanders purchase orders (POs) and delivers them via FTP. It sends customer shipping details, SKUs, quantities, and shipping methods so Zanders can ship orders directly to your buyers.

How the Integration Works
When Flxpoint generates a fulfillment request for Zanders, this integration:
  • Pulls fulfillment request data (FR number, shipping address, line items, shipping method).
  • Maps the data into Zanders’ expected purchase order layout.
  • Uploads a PO file to an outbound folder on Zanders’ FTP server.
Core Connection Settings
  • Connection Name: e.g. Zanders Fulfillment.
  • FTP Protocol: FTP, SFTP, or FTPS as defined by Zanders.
  • FTP Host & Port: Server and port provided by Zanders.
  • FTP User & Password: Credentials for uploading PO files.
  • Outbound Remote File Folder: Folder where Flxpoint will upload PO files, e.g. /zanders-fulfillment-requests.
  • Maintain Constant Connection (optional): Helpful if you expect many POs or larger batches.
Sender/Receiver Identifiers
  • Our Sender/Receiver ID: FLXPOINT
  • Our Sender/Receiver Qualifier: ZZ
  • Their Sender/Receiver ID: ID from Zanders (e.g. ZANDERSID).
  • Their Sender/Receiver Qualifier: typically 12.
Recommended Setup Flow
  • Step 1: Configure FTP details and the outbound folder path.
  • Step 2: Enter Sender/Receiver identifiers.
  • Step 3: Test Connection and Save.
  • Step 4: Build the mapping template to align Flxpoint fields with Zanders’ PO format.
  • Step 5: Generate a test fulfillment request in Flxpoint and send it to confirm Zanders can receive and read the PO file.
Tip: Coordinate with Zanders to validate your first test PO file before enabling this integration for live orders.

Core Fulfillment & PO Mapping
The mapping template converts Flxpoint fulfillment fields into Zanders PO fields. Typical mappings:
Field Maps To Example Purpose Status
Fulfillment Request Number (T) Zanders PO: PO Number FR12345 Primary order reference in Zanders Required
Shipping Address: Full Name (T) Zanders PO: Ship To Name Jane Doe Recipient name on shipment Required
Shipping Address: Address Line 1 (T) Zanders PO: Ship To Address1 123 Main St Primary street address Required
Shipping Address: City (T) Zanders PO: Ship To City Austin Destination city Required
Shipping Address: State Code (T) Zanders PO: Ship To State TX Destination state / region Required
Shipping Address: Postal Code (T) Zanders PO: Ship To Postal Code 78701 Destination postal code Required
FR Item: SKU (T) Zanders PO Line: Item Number ZND12345 Line item product identifier Required
FR Item: Quantity (N) Zanders PO Line: Quantity 2 Units to ship Required
Shipping Method Mapping
Zanders expects a shipping method code with each order. In your mapping:
  • Use Flxpoint’s Source Shipping Method or related field as the input.
  • Map it to the Zanders shipping code field (e.g., UPS-GND).
  • Optionally use a Mapping Set to translate internal names (like “UPS Ground”) into Zanders codes (like UPS-GND).
Mapping Rules (Optional)
  • Normalize shipping methods (e.g., map ups ground, UPS-GROUND → UPS-GND).
  • Set a default shipping code if none is provided for a particular order.
  • Override shipping methods based on destination (e.g., force expedited to certain regions).
Example: A rule can check for carrier = “UPS” and method contains “Ground”, then set the Zanders ship code field to UPS-GND.

Common Questions
  • Does this integration confirm shipment? This step only sends POs. Shipment confirmations typically come from a separate “Get Shipments” or tracking integration if available.
  • Can I test without sending real orders? Yes. Work with Zanders to define a test folder or account and send sample POs for validation.
  • What happens if mapping is incomplete? Zanders may reject the PO file or fail to process it; always validate required fields first.
Troubleshooting
  • No PO files appearing in Zanders: Verify the outbound FTP folder path and check job logs in Flxpoint to confirm files are being generated.
  • Connection or auth failures: Re-check host, port, protocol, and user/password. Use Test Connection after changes.
  • PO rejected by Zanders: Request a sample of the rejected file and compare field layout, required fields, and shipping codes against your mapping.
Tip: Start with a single test order, confirm it appears correctly in Zanders, then roll out to all live orders for the Zanders source.
 
 

Get Shipments

Supported | Zanders - Get Shipments

The Zanders - Get Shipments integration imports shipment confirmations and tracking details from Zanders via FTP and applies them to your Flxpoint fulfillments. This keeps your orders in sync with what has actually shipped so you can update your sales channels and customers.

How the Integration Works
When shipments are generated in Zanders, they produce a shipment/ASN-style file on their FTP server. This integration:
  • Connects to Zanders’ FTP inbound folder on a schedule.
  • Downloads new shipment files containing tracking, carrier, and shipped quantities.
  • Matches those records to Flxpoint fulfillment requests or orders (by PO/FR number).
  • Updates fulfillment records in Flxpoint and can push tracking to your channels (via your channel integrations).
Core Connection Settings
  • Connection Name: e.g. Zanders Shipments.
  • FTP Protocol: FTP, SFTP, or FTPS per Zanders’ requirements.
  • FTP Host & Port: Host and port from Zanders (for example ftp.zanders.com, 21/22).
  • FTP User & Password: Credentials for reading shipment files.
  • Inbound Remote File Folder: Folder where Zanders drops shipment/ASN files, e.g. /zanders-shipments.
  • Maintain Constant Connection (optional): Enable if files are large or you expect frequent runs.
Sender/Receiver Identifiers
  • Our Sender/Receiver ID: FLXPOINT
  • Our Sender/Receiver Qualifier: ZZ
  • Their Sender/Receiver ID: ID provided by Zanders (e.g. ZANDERSID).
  • Their Sender/Receiver Qualifier: typically 12.
Recommended Setup Flow
  • Step 1: Configure FTP host, protocol, credentials, and the inbound folder path for shipment files.
  • Step 2: Enter Sender/Receiver identifiers as agreed with Zanders.
  • Step 3: Use Test Connection to validate access.
  • Step 4: Build the mapping template (see Mapping Utilities dropdown).
  • Step 5: Ask Zanders to place a test shipment file and run the integration manually to validate matching and tracking updates.
  • Step 6: Once confirmed, set an automated schedule so shipments are pulled regularly.
Tip: Align your FR/PO numbering format with what Zanders uses in their shipment files so matching is reliable and does not require custom rules.

Core Shipment Mapping
The mapping template translates Zanders shipment fields into Flxpoint shipment/fulfillment fields. Typical mappings:
Field Maps To Example Purpose Status
PO / Order Number (T) Fulfillment: External Order / PO Reference FR12345 Key field to match shipment to the correct fulfillment Required
Item Number (T) Fulfillment Line: SKU ZND12345 Line item identifier Required (for line-level matching)
Shipped Quantity (N) Fulfillment Line: Shipped Quantity 2 Quantity that shipped for the line Required
Carrier Code (T) Shipment: Carrier UPS Carrier used for the shipment Optional (recommended)
Service / Ship Method Code (T) Shipment: Service / Method UPS-GND Service level used for the shipment Optional (recommended)
Tracking Number (T) Shipment: Tracking Number 1Z999AA10123456784 Tracking number your channels and customers will see Required
Ship Date (D) Shipment: Shipped At 2025-01-15 Date the package left the warehouse Optional
Shipment Status (T) Shipment: Status SHIPPED Used if Zanders passes explicit status values Optional
Mapping Options
  • Field: Map each Zanders shipment column directly to a Flxpoint shipment or fulfillment field.
  • Value: Use fixed values (for example, force status = SHIPPED if that’s implied by the file).
  • Mapping Set: Use mapping sets to normalize carrier/service codes (e.g., convert UPS GROUND → UPS-GND).
  • Rules: Apply if/then logic for special cases (see below).
  • Don’t Map / Set to Empty: Skip or clear fields that are not used.
Mapping Rules (Optional)
  • Normalize carrier/service values into the format your channels expect.
  • Set a default carrier when none is provided but a tracking number exists.
  • Handle partial shipments by updating shipped quantities while leaving backordered units open.
Example: A rule can check if Carrier is empty and Tracking starts with 1Z, then set Carrier to UPS.

Common Questions
  • Does this integration close fulfillments automatically? Yes, if the shipment file indicates that all quantities have shipped, Flxpoint can mark the fulfillment as shipped and ready to sync to your channels.
  • Can it handle partial shipments? Yes, as long as the file provides line-level quantities, Flxpoint can update shipped quantities while leaving remaining units open.
  • How often should it run? Most merchants schedule shipment imports to run at least several times per day, or to match Zanders’ shipment file cadence.
Troubleshooting
  • No shipments imported: Confirm the inbound folder path, ensure Zanders is dropping files there, and review job logs for “no file found” messages.
  • Shipments not matching orders: Check that the PO/Order Number in the file matches the field you mapped in Flxpoint (FR number, channel order number, etc.).
  • Tracking not appearing in channels: Verify that shipment updates are successfully applied in Flxpoint and that your channel integrations are configured to sync tracking.
  • Duplicate tracking updates: Work with Zanders to confirm whether files are re-sent and consider rules or file-archiving strategies to avoid processing the same file twice.
Tip: During onboarding, ask Zanders for a sample shipment file and validate all mappings in a staging/test environment before enabling the integration for live traffic.
 
 
Optional but recommended

You’re ready to automate this source

You’ve finished setting up this source. If you’d like, you can now put its operations on an automated schedule.

  • Select the operations to schedule (for example, Get Inventory, Get Orders, Send Fulfillment Requests, Get Shipments).
  • Pick how often and when they should run. You can edit or pause schedules anytime from the operations screen.

Tip: A daily schedule for key operations is a simple place to start.

How to schedule source operations in Flxpoint
Click the animation to view it larger.

 

 

Troubleshooting Common Errors

Common issues and solutions for the Zanders FTP integrations (inventory, orders, and shipments). Expand each item to learn more.

Still need help? If you’re experiencing issues not covered here, contact Flxpoint Support and we can coordinate with Zanders if needed.

Contact Support

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Related Articles

Entrenue as Source

Entrenue is a wholesale distributor specializing in adult products, boutique plea...

Petra Industries as Source

Petra Industries is a wholesaler of consumer electronics and accessories. Flxpoin...

Mirage Pet Products as Source

Mirage Pet Products is a wholesaler of pet apparel, accessories, and supplies. Fl...