Flxpoint Help Center
All DocsContact support

Zanders as a Source

July 2, 2026

Summary

Zanders is a firearms and accessories distributor. Inventory is delivered over FTP, while orders go out through a separate Zanders ordering API that uses up to three distinct account types — Main (ship-to-store), Accessory Direct Ship, and Firearm Direct Ship — because accessories and serialized firearms can never be combined in the same order.

Get Inventory (Primary)
Retrieves full product data, pricing and quantity from the product file on the Zanders FTP
Get Inventory (Secondary)
Pulls just pricing and quantity from liveinv.csv to keep Cost, MAP, MSRP and Quantity fresh
Send Orders
Submits Fulfillment Requests through the matching Zanders account (Main, Accessory DS or Firearm DS)
Get Shipments
Pulls tracking back into Flxpoint at the Fulfillment Request level

Zanders uses two connections: a Zander FTP connection for inventory (Get Inventory jobs) and a Zander Integration order connection for Send Orders and Get Shipments. Add a source, start the relevant job, click + New Connection, enter the values, then Test ConnectionSave Connection.

FTP HostRequired
The Zanders FTP server that hosts your inventory files. Entered on the Zander FTP connection.
Zanders FTP host is ftp2.gzanders.com.
FTP PortRequired
The port for the FTP connection.
Port 21.
FTP ProtocolRequired
The transfer protocol used for the FTP connection.
Confirm the protocol with Zanders.
FTP UserRequired
Your FTP username for the Zanders inventory server.
Provided by Zanders.
FTP PasswordRequired
The password paired with your FTP user.
Provided by Zanders.
EnvironmentSetting
On the Zander Integration (order) connection, choose Sandbox or Production. Sandbox orders are accepted but never actually processed.
Always select Production for live order fulfillment.
Zanders order account credentialsRequired
Each Zanders order account type — Main Account Username, Main Account Password, Accessory Account Username, Accessory Account Password, Firearm Account Username, Firearm Account Password — is a separate order connection using its own dedicated API credentials from Zanders.
These API credentials are separate from your Zanders dealer website login — request the correct set for each account type from your Zanders rep.
Only configure the account types your business actually uses — if you only dropship accessories, you only need the Accessory Direct Ship account. If the FTP connection fails despite correct credentials, Zanders may need to whitelist Flxpoint's outbound IP addresses on their server. Flxpoint's outbound IP addresses are 52.44.101.151 and 52.1.186.211 — give these to Zanders directly so you don't need to request them separately.

Three separate API accounts — never mix accessories and firearms in one order

Zanders provides three distinct API credential sets for ordering, each with its own purpose and restriction: Main (ships to your store, accessories + firearms together), Accessory Direct Ship (non-serialized accessories to consumers), and Firearm Direct Ship (serialized firearms to FFL holders). Direct Ship accessories and firearms must be placed on separate accounts using separate Fulfillment Requests — mixing serialized firearms and non-serialized accessories in one Direct Ship order will be rejected.

Set the Custom Inventory Directory if Zanders uses a dealer-specific subfolder

Zanders may place your inventory files in a dealer-specific subfolder (e.g. Inventory/YourStoreName). If so, enter the relative path (no leading slash) in the Custom Inventory Directory setting in Get Inventory Primary. Without it, Flxpoint looks in the root FTP directory and finds no files. Primary reads zandersinv.csv and liveinv.csv from the subfolder; Secondary reads only liveinv.csv. Confirm with Zanders whether your account uses a subdirectory.

Select Production — not Sandbox — on the order connection

The Zanders order connection includes an environment selector. Sandbox orders are accepted without being processed. If orders submit successfully in Flxpoint but never appear in the Zanders dealer portal, confirm the connection is set to Production.

API credentials are not your Zanders website login

The three Zanders API accounts (Main, Accessory DS, Firearm DS) use dedicated API credentials issued by Zanders — these are separate from your Zanders dealer website username and password. Contact your Zanders account rep for the correct API credentials for each account type you need to activate.


Zanders FieldMaps To – Notes
Item NumberParent SKU, Variant SKU and Master SKU. Primary product identifier / linking key.
SerializedThere is no direct field for Serialized. First map Requires FFL to True or False, then set a rule for serialized products — for example: IF Zanders Product Serialized equals Yes, Then Incoming Value Set to True (mapping and rule can also go the other way).
UPCUse a rule to remove the leading zero — Zanders includes a leading zero that causes UPC mismatch issues on channels.
Description1 + Description2Combine via a rule for the product title / description.
Firearm identificationNo such field is available from Zanders. Flxpoint adds this as a custom field at the variant level using Direct Copy.
Bulk pricingSupported, but must be mapped to the Price 2 or Price 3 fields.
CategoryOnly single-level categories are supported.
Reads product data, pricing and quantity from zandersinv.csv (with liveinv.csv) on the FTP.
Only refreshes pricing and quantity — reads variant-level SKU, Cost, MAP, MSRP and Quantity from Zanders's liveinv.csv. Pre-configured default mapping templates are available for Zanders Secondary. Run it on a more frequent schedule than Primary (hourly if possible) to keep pricing and quantity current.
Submits Fulfillment Requests (FRs). Required fields: PO Number, Ship To Name, Ship To Address, Ship To City, Ship To State, Ship To Zip, Item Number, Quantity. The itemNumber sent on the FR is default-mapped to SKU. Shipping method is mapped with a code such as UPS-GND — confirm valid codes with Zanders. Place accessory and firearm orders through their matching account (Accessory DS vs Firearm DS); they cannot share one FR. Flxpoint shows an error message if an FR cannot be processed.
Returns tracking at the Fulfillment Request level, not per item. Partial shipments from Zanders are not supported. The FR Lookback Period defaults to 90 days — increase it in Advanced Settings to retrieve shipments for older FRs.

Send FR fails with a null UseShipToResponse.getReturn() error
Zanders's API could not validate the ship-to address — typically on a Firearm Direct Ship order whose ship-to does not match a valid FFL holder on file, or where FFL information is missing/incorrect. Verify the FFL holder's address matches exactly what Zanders has on file, and confirm FFL status with Zanders before resubmitting.
FTP connection failing despite correct credentials
Zanders may need to whitelist Flxpoint's outbound IP addresses on their FTP server. Contact Zanders support and provide Flxpoint's IP range (contact Flxpoint Support for current outbound IPs). This is a common first-time setup issue.
Orders selling out of stock, or items no longer in the Zanders feed
Usually Get Inventory Secondary has not run recently enough to reflect current quantities — Zanders's liveinv.csv updates frequently, so schedule Secondary hourly if possible. For items no longer in the feed (discontinued), confirm Archive is enabled on Primary or Secondary so removed items are deactivated in Flxpoint.
Products missing from the Zanders feed / inventory not loading
Check the Custom Inventory Directory setting. If Zanders uses a dealer-specific subdirectory and this field is empty, Get Inventory Primary looks in the root FTP directory and finds no files. Confirm the correct relative path with Zanders, verify Test Connection passes, and check that zandersinv.csv and liveinv.csv are present in the expected directory.

What are the three Zanders API account types and when do I use each?
Main Account ships to your store/account address and allows accessories and firearms in the same order, but is not for direct-to-consumer shipments. Accessory Direct Ship (DS) ships to the consumer and allows non-serialized accessories only — no firearms or serialized items. Firearm Direct Ship (DS) ships to an FFL holder and allows serialized firearms only — no accessories, and the ship-to must be a valid FFL. Each type requires separate API credentials from Zanders; only configure the account types relevant to your business.
What is the Custom Inventory Directory and how do I configure it?
If Zanders stores your inventory files in a dealer-specific subfolder (for example Inventory/YourStoreName), enter the relative path in the Custom Inventory Directory field in the Get Inventory Primary settings — do not include a leading slash. Primary will read both zandersinv.csv and liveinv.csv from that subfolder; Secondary reads only liveinv.csv from the same path. If Zanders does not use a subdirectory for your account, leave this field empty.
What fields does Get Inventory Secondary return from Zanders?
Secondary returns variant-level fields from Zanders's liveinv.csv: variant-level SKU, Cost, MAP, MSRP and Quantity. Pre-configured default mapping templates are available for Zanders Secondary. Run it on a more frequent schedule than Primary to keep pricing and quantity current.
What fields are required for Send Orders (Fulfillment Requests) to Zanders?
Required fields: PO Number, Ship To Name, Ship To Address, Ship To City, Ship To State, Ship To Zip, Item Number and Quantity. Shipping method is mapped using a value such as UPS-GND — check your Zanders account documentation for valid shipping method codes. The FR Lookback Period defaults to 90 days; adjust it in Advanced Settings if you need to retrieve shipments for older FRs.
What are the Get Inventory Primary mapping notes for Zanders product data?
Key notes: (1) Item Number maps to Parent SKU, Variant SKU and Master SKU; (2) there is no direct field for Serialized — first map Requires FFL to True or False, then set a rule for serialized products (for example: IF Zanders Product Serialized equals Yes, Then Incoming Value Set to True; mapping and rule can also go the other way); (3) use a rule to remove the leading zero from UPC values, since Zanders includes one that can cause UPC mismatches on channels; (4) combine Description1 + Description2 via a rule for the product title/description. Bulk pricing must map to Price 2 or Price 3, and only single-level categories are supported.
© 2026 Flxpoint. All rights reserved.