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.

Step 1 — Shipping Methods
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 supplier’s code).
    • Packages: Choose Best Fit for predefined sizes or Custom for manual packaging.
    • Carrier/Method: e.g., "UPS Ground" (links to a Flxpoint carrier).
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:
  • Shipping Label Code: Set if purchasing labels (e.g., via UPS).
  • Default Carrier Code: Carrier identifier (e.g., "UPS").
  • Custom Carrier Name: Custom label for the carrier.
  • 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 used to map your methods to Zanders shipping codes.
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
1️⃣ FTP Credentials (Required for Get Inventory [Primary])
Zanders provides inventory feeds via FTP. You must collect:
Credential Description
FTP Protocol FTP or SFTP (as provided by Zanders)
FTP Host Example: ftp2.gzanders.com
FTP Port Usually 21 (unless specified 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:

Account Type Used For Credentials to Collect
🔵 Main Account Ship products back to your store. This account can include both accessories and firearms in a single order.
Main Account Username
Main Account Password
🟢 Accessory Direct Ship (DS) Ship non-serialized accessories directly to the consumer (Direct Ship).
Accessory Account Username
Accessory Account Password
🔴 Firearms Direct Ship (DS) Ship serialized firearms directly to FFL holders (Direct Ship).
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 Zanders has four integrations available in Flxpoint: two for products and two for orders. Get Inventory [Primary] (GIP) and Get Inventory [Secondary] (GIS) keep your Zanders stock and pricing updated, while Send Fulfillment Requests and Get Shipments handle sending orders to Zanders and pulling back shipment/tracking data. All four use the same Zanders 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 Review the mapping template, which is pre-configured for most Zanders workflows.
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 setting up your connection, you’re ready to use your Zanders integration without needing to manually map fields.

Flxpoint has already pre-configured default mapping templates for you, so no mapping is required unless your specific workflow or business rules require customization.

If your unique use case needs adjustments, you can edit the default templates to apply changes.

  • No action needed for most accounts: the default templates are ready to use as-is.
  • Customize only if needed: update the template when your business rules require a different mapping.
Good news: For most users, the default configuration works out of the box — no manual field mapping needed.
Activate and Verify

Complete the setup by clicking Save and Complete. Your Zanders integration is now active and will run based on your settings.

Next Steps: The initial inventory sync may take some time to complete. You can monitor the progress in the Integrations section of your Flxpoint dashboard.
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]

Introduction

The Zanders – Get Inventory [Secondary] integration retrieves a lighter, inventory-focused 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 need reliable ongoing inventory and price refreshes for products that already exist in your catalog.

On this section
Setup Overview

Setting up Zanders – Get Inventory [Secondary] follows the same guided three-step flow as the primary inventory wizard, with a focus on Variant-level inventory and pricing updates:

  • 1 Establish the FTP connection to Zanders using the credentials they provide.
  • 2 Configure settings that control how this secondary feed updates inventory.
  • 3 Define your mapping template for SKU, pricing, and quantities at the Variant level.
Step 1 — Establish Connection to Zanders’ FTP Server

In Step 1, connect Flxpoint to Zanders’ FTP server using the credentials and folder path they provide for the secondary inventory feed:

  • Connection Name: e.g., Zanders Inventory Secondary.
  • FTP Protocol: Choose FTP or SFTP as specified by Zanders.
  • FTP Host: The server address (for example, ftp.zanders.com).
  • FTP Port: Usually 21 (FTP) or 22 (SFTP).
  • FTP User: Your Zanders-provided username.
  • FTP Password: Your Zanders-provided password.
  • Inbound Remote File Folder: The folder where Zanders drops the secondary inventory file (for example, /zanders-inventory-secondary).

Important: Zanders provides these credentials and folder paths when your account is enabled. If you don’t have them, contact your Zanders representative.

Click Advanced Settings if you need to adjust behavior for large files:

  • File Transfer Mode: Use Binary for most inventory files (recommended).
  • Maintain Constant Connection: Turn ON for large files to reduce FTP timeouts.
Tip: Use Test Connection before saving to confirm access to the secondary folder.
Step 2 — Configure Settings

Step 2 defines how Flxpoint should treat incoming inventory from the secondary feed. If you use both primary and secondary inventory integrations for the same Zanders source, make sure these settings are not duplicated across both.

Archive / Un-Archive Inventory (If Available)

When enabled, this setting can help keep your catalog clean by automatically:

  • Archiving SKUs not found in the latest feed by setting their quantity to 0.
  • Un-archiving SKUs that reappear in future feeds.
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 only one integration (typically the primary feed).
Step 3 — Define a Mapping Template

After your FTP connection and settings are saved, define how Zanders’ secondary inventory fields map into your Flxpoint Variant-level fields.

  • Select or create a mapping template specifically for the secondary feed.
  • Map essential Variant fields like SKU, Cost, MAP, MSRP, and Quantity as needed.
  • Use rules to control edge cases (for example, forcing Quantity to 0 when an availability flag indicates no stock).
Tip: Secondary inventory feeds are best used for fast pricing/quantity refreshes once your core catalog is already established.
Activate and Verify

Complete the wizard to activate the integration:

  • Click Save and Complete to activate your secondary inventory integration.
  • Run the integration manually the first time to confirm inventory updates look correct.
  • After validation, configure a schedule for ongoing refreshes.
Next Steps: Spot-check a handful of SKUs for Cost, MAP/MSRP, and Quantity after the first successful run.
On this section
Mapping Template (Zanders Secondary)

The secondary Mapping Template is designed for faster Variant-level inventory and pricing refreshes. It typically does not need the full parent-level product structure used in the primary feed.

Field Mapping

This overview reflects the most common Variant-level mappings for the secondary inventory file.

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
Rules You Can Use

Mapping Rules let you refine how secondary inventory values update your catalog. Common patterns include:

  • Inventory guardrails: Set Quantity to 0 when an “Available” or similar flag equals 0.
  • Price protection: Prevent Cost from dropping below a minimum threshold for specific SKUs or brands.
Example rule: “If Available = 0, set Quantity 1 to 0” helps prevent overselling when items are flagged unavailable.
On this section
Key Details

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

  • Data focus: This feed prioritizes Variant-level SKU, pricing, and quantity updates.
  • No new product creation: It expects SKUs that already exist in your catalog.
  • Speed: Secondary feeds are ideal for more frequent refreshes after your primary catalog is established.
Quick Checks Before You Debug
  • FTP connection in Step 1 is saved and passes Test Connection.
  • Inbound folder path is correct for the secondary feed.
  • Archive / Un-Archive is enabled in only one inventory integration (if used).
  • A mapping template is selected and includes at least SKU and Quantity.
  • At least one manual run has completed successfully in job history.
Troubleshooting

If something goes wrong with the integration, start here:

  • FTP Connection Failure: Re-check host, port, user, and password. Confirm Zanders has enabled your FTP access.
  • File Not Found: Verify the Inbound Remote File Folder for the secondary feed and confirm Zanders is dropping files there.
  • Inventory Not Updating: Confirm Item Number is mapped to Variant: SKU and that the integration job completed successfully.
  • Unexpected quantities: Review mapping rules that may be overriding Quantity logic.
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 needed, download a sample Zanders secondary file and compare a few SKUs to your Flxpoint results.
 
 
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

Introduction

The Zanders – Send Fulfillment Requests integration converts Flxpoint Fulfillment Requests (FRs) into Zanders purchase orders (POs) and submits them via API. This integration supports all three Zanders order channels:

  • Main Account → Ship-to-store (mixed firearms + accessories allowed)
  • Accessory Direct Ship (DS) → Non-serialized items shipped to consumers
  • Firearm Direct Ship (DS) → Serialized items shipped to FFL holders

After configuring the Zanders API Connection, the Send FR workflow requires completing three operational steps: connect an integration, configure settings, and define a mapping template. These steps ensure FRs flow correctly from Flxpoint to Zanders.

On this section
Overview of the Send FR Workflow

The Send Fulfillment Requests workflow depends on a valid Zanders API Connection. Once your API connection is saved, you will complete three operational steps inside the Send FR setup to ensure Flxpoint can generate and submit POs using the appropriate Zanders account (Main, Accessory DS, or Firearm DS).

Step 1 — Connect an Integration

Follow the steps below in sequence to create your Zanders API Connection and connect it to the Send Fulfillment Requests workflow.

Connection Name: A descriptive label used to identify this Zanders connection in Flxpoint.
Example suggestions:
  • Zanders API Connection
  • Zanders Fulfillment Integration
Fill in Required API Credentials

Flxpoint will use your saved Zanders API Connection to submit POs using the appropriate Zanders account. These are API credentials, not the Zanders website login.

Enter Main Account credentials
Used for ship-to-store orders and orders containing both firearms and accessories.
  • Main Account Username
  • Main Account Password
✅ Good to know: Main Account supports mixed firearm + accessory orders.
Enter Accessory Direct Ship (DS) credentials
Used for direct ship accessory orders (non-serialized items) shipped to consumers.
  • Accessory Account Username
  • Accessory Account Password
⚠️ Important: Accessory DS orders cannot include firearms.
Enter Firearm Direct Ship (DS) credentials
Used for direct ship firearm orders (serialized items) shipped to FFL holders.
  • Firearm Account Username
  • Firearm Account Password
❗ Critical rule: Firearm DS orders cannot include accessories. Use the Main Account for mixed items.
Select the Environment

Choose the environment that matches your testing or live operation stage.

  • Sandbox → For testing and validation
  • Production → For live operations
Recommended: Always begin in Sandbox until Zanders confirms correct formatting.
Test the Connection

Click Test Connection to validate all credentials. This checks authentication for the Main Account, Accessory DS Account, and Firearm DS Account.

  • Credentials are correct
  • API access is functioning
  • All three accounts authenticate successfully
If the test fails:
  • Recheck usernames/passwords
  • Verify case sensitivity
  • Confirm Sandbox vs Production selection
  • Contact Zanders if credentials appear inactive
Save the Connection

When the connection test succeeds, click Save Connection. Your Zanders API integration is now active inside Flxpoint.

New Zanders Connection screen showing Main, Accessory DS, Firearm DS credentials and environment

Step 2 — Configure Settings

In this step, you define when and how Fulfillment Requests should be sent to Zanders. These options help you control timing based on your operational needs.

  • Hold for X Hours
    Delay sending an FR for a set number of hours after it is created. This is useful for merchants who expect rapid order changes or cancellations.
  • Send During Business Hours Only
    Enable this option to ensure FRs are only sent during standard business hours. This helps avoid sending FRs at night or during warehouse downtime.

Click Save and Proceed to continue.

Step 3 — Define a Mapping Template

The mapping template determines how Flxpoint fields translate into Zanders' required PO structure. This is where you confirm that all required order, line item, and shipping details are aligned to Zanders expectations.

  • SKU mapping
  • Quantity fields
  • Shipping method mapping
  • Address and contact fields
  • Any custom fields Zanders requires

Once the mapping is completed and validated, the step will show Mapped. At that point, your integration is fully configured to generate and submit FR → PO data through the Zanders API.

Submit a Test Fulfillment Request

Send a test FR to validate correct account selection, proper PO formatting, and successful receipt and processing by Zanders.

Best practice: Share your first test PO with Zanders Support to verify formatting and routing before enabling Production mode.
On this section
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.
On this section
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 process and send sample POs for validation.
  • What happens if mapping is incomplete? Zanders may reject the PO or fail to process it; always validate required fields first.
Troubleshooting
  • Connection or auth failures: Re-check usernames/passwords for all accounts and confirm the correct environment. Use Test Connection after changes.
  • PO rejected by Zanders: Request a sample of the rejected payload and compare required fields and shipping codes against your mapping.
  • Account selection issues: Confirm product mix rules: Accessory DS cannot include firearms, and Firearm DS cannot include accessories. Use the Main Account for mixed items.
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

Introduction

The Zanders – Get Shipments integration retrieves shipment confirmations and tracking details directly from Zanders via API and applies them to your Flxpoint fulfillments. This ensures your orders remain up-to-date with Zanders’ actual shipment activity, allowing you to keep your sales channels and customers accurately informed.

The setup flow follows the same three-step structure as Send Fulfillment Requests: Connect an Integration, Configure Settings, and Define a Mapping Template.

On this section
Step 1 — Connect an Integration

Select Zanders as your Get Shipments integration. Flxpoint will use your saved Zanders API Connection to retrieve tracking and shipment updates.

This step confirms the integration is connected and ready.
Step 2 — Configure Settings

This step controls how far back Flxpoint should look for Fulfillment Requests (FRs) when retrieving shipment updates.

FR Lookback Period for Get Shipments

This defines the maximum age of Fulfillment Requests that should be considered when pulling shipments.

  • Example: 3 Months
  • Only FRs created within this timeframe are eligible for shipment retrieval.
  • Default is 90 days.
What this setting does: Flxpoint will only attempt to pull tracking/shipment updates for FRs created within the lookback window you specify.
Tip: If you routinely handle long fulfillment cycles, increase the window (e.g., 6 months). If most orders ship quickly, shorter windows improve efficiency.

Click Save and Proceed to continue.

Step 3 — Define a Mapping Template

Map the shipment data coming from Zanders into Flxpoint standard fields, including:

  • Tracking numbers
  • Carrier names
  • Shipment dates
  • Line item shipment details
  • Other relevant shipment attributes

Once mapping is complete, this step will show as Mapped.

Setup Complete: Your Zanders Get Shipments integration is now configured to retrieve real-time shipment updates via API.
On this section
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 attribute directly to a Flxpoint shipment or fulfillment field.
  • Value: Use fixed values (for example, force status = SHIPPED if implied by the data).
  • Mapping Set: Normalize carrier/service codes (e.g., 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.
On this section
Common Questions
  • Does this integration close fulfillments automatically? Yes, if the shipment data 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 Zanders provides line-level quantities, Flxpoint can update shipped quantities while leaving remaining units open.
  • How often should it run? Most merchants schedule shipment retrieval to run multiple times per day to keep tracking current across channels.
  • What if we ship after long cycles? Increase the FR Lookback Period beyond the default 90 days to ensure older FRs remain eligible for updates.
Troubleshooting
  • No shipments imported: Confirm your Zanders API Connection is valid and review job logs for authentication or retrieval errors.
  • Shipments not matching orders: Check that the PO/Order Number returned by Zanders 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.
  • Older FRs missing updates: Increase the FR Lookback Period if your fulfillment timelines commonly exceed the default window.
Tip: During onboarding, validate your mapping with a small test set of fulfillments before relying on automated schedules 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...