Iron Valley as a Source
July 17, 2026
Summary
Iron Valley is a wholesale distributor of firearms, ammunition, and outdoor gear. Get Inventory (Primary) and Get Inventory (Secondary) connect over a pre-configured FTP that Flxpoint manages — no setup required; Send Fulfillment Requests and Get Shipments connect through the Iron Valley API, which only needs an Environment selection (Staging or Production) plus a Customer ID for sending orders. Firearm dropship orders can require FFL documentation, and Iron Valley automatically classifies each order as Replenishment or Dropship based on brand and routing.
What this integration does
Get Inventory (Primary)
Imports Iron Valley's full product catalog via pre-configured FTP.
Get Inventory (Secondary)
Refreshes price, quantity and UPC via the same FTP feed.
Send Fulfillment Requests
Sends dropship orders to Iron Valley, with FFL support.
Get Shipments
Pulls tracking numbers and carrier info from Iron Valley.
How to connect - credentials you need
Iron Valley uses two independent connections. Get Inventory (Primary) and Get Inventory (Secondary) need no connection setup — Flxpoint's FTP credentials are pre-configured. For Send Fulfillment Requests and Get Shipments, add the source, open the Iron Valley API connection, select the correct Environment (Staging or Production), then Test Connection → Save Connection. Send Fulfillment Requests also needs a Customer ID entered in that operation's integration settings.
Get Inventory (Primary) & Get Inventory (Secondary) — No Setup Needed
Pre-Configured FTP ConnectionAutomatic
Flxpoint connects automatically to Iron Valley's FTP using credentials Flxpoint maintains — you do not enter any host, port, username, or password. Just add Iron Valley as the source and proceed directly to configuring Get Inventory (Primary) and Get Inventory (Secondary).
Send Fulfillment Requests & Get Shipments — Iron Valley API
EnvironmentRequired
Staging or Production toggle for the Iron Valley API connection. Staging accepts requests but does not forward orders to Iron Valley for fulfillment — confirm Production is selected before enabling automatic order sending.
Customer IDRequired for Send FR
Your Iron Valley customer number, entered in Send Fulfillment Requests' integration settings (not on the connection itself). Get Shipments does not use this field. The last 5 digits of your account number are the Iron Valley customer number for the account placing the order.
The Iron Valley API connection uses Flxpoint-managed authentication per environment — there is no separate API username or password to enter. Get Shipments uses the same Environment setting as Send Fulfillment Requests; Customer ID applies only to Send Fulfillment Requests. For extended setup or field mapping guidance, contact
support@flxpoint.com.Important - read before configuring
Two separate connections — FTP for inventory, API for orders. Do not mix them.
GIP and GIS use the FTP (Basic Auth) connection. Send FR and Get Shipments use the Iron Valley API connection. When configuring each operation, select the correct connection type. Applying the API connection to GIP or the FTP connection to Send FR will fail. You may need to create both connections if you use all four operations.
Staging environment accepts orders without fulfilling them — use Production for live orders
The Iron Valley API connection has a Staging / Production environment toggle. Staging returns success responses but does not forward orders to Iron Valley for fulfillment. Always confirm the connection is set to Production before enabling automatic order sending. If test orders appear accepted in Flxpoint but don't arrive at Iron Valley, check the environment setting first.
Replenishment vs Dropship classification is automatic — mixed-brand POs cause issues
Iron Valley automatically classifies each PO as Replenishment (to your warehouse) or Dropship (to your customer) based on brand and routing destination. If a single PO contains both replenishment and dropship brands, Iron Valley may misclassify it. Split mixed-brand POs into separate FRs to ensure correct routing. You do not need to set classification manually in Flxpoint.
Operations - fields to know
| Field | Maps To — Notes |
|---|---|
| Iron Valley Prd# (Catalog.csv) | → Product / Variant → SKU. Required. Primary identifier for the catalog item. |
| Description | → Product → Title. |
| Extended Descritpion | → Product → Description. |
| Brand | → Product → Manufacturer. |
| Manufacturer Product# | → Identifiers → MPN. Manufacturer part reference. |
| UPC/EAN/GTIN-14 | → Identifiers → UPC / EAN / GTIN-14. |
| Category | → Product → Category. |
| SubCat | → Product → Sub Category. |
| Price | → Pricing → Cost. |
| Quantity Available | → Inventory → Quantity. |
| Image URL | → Product / Variant → Images. |
| Cal/GA, Closeout, Serialized, Allocated (Y/N) | → Custom fields. Caliber/gauge, closeout status, serialized-item flag, and allocation status passed through as-is. |
| Field | Maps To — Notes |
|---|---|
| Iron Valley Prd# (PriceQty.csv) | → Inventory Variant → SKU. Required. Matched against the existing catalog item. |
| Price | → Pricing → Cost. |
| Quantity Available | → Inventory → Quantity. |
| UPC | → Identifiers → UPC. Only set when present in this feed. |
| Full catalog fields | Not included in Secondary — title, description, category, brand, and images come from Get Inventory (Primary). Run Primary daily for the full catalog and Secondary more frequently to keep Cost and Quantity current. |
| Source Field | Maps To (Iron Valley) — Notes |
|---|---|
| Fulfillment Request Item → SKU | → PO Line Items#. Required. Sent per line item. |
| Fulfillment Request Item → Quantity | → Order Quantity. Required. Units requested. |
| Fulfillment Request Number | → PO Number. Iron Valley's order confirmation number is written back to this field once accepted. |
| Customer ID (Send FR integration settings) | → Customer Number. Required. Set once in Send Fulfillment Requests' settings — not mapped per order; the job fails if it is blank. |
| FFL license info (order-level, FFL-required orders only) | → Ship To Number override + a separate FFL file upload. When FFL Required is enabled, Flxpoint derives part of the Ship To Number from the FFL license number and sends the FFL details as a separate file alongside the order — not part of the main order submission. |
| Field | Maps To — Notes |
|---|---|
| Order Number (matched to your Fulfillment Request confirmation number) | → Lookup key. Used to request shipment records for that order — not itself a mapped field. |
| Whse | → Shipment → Warehouse. |
| Trackerno | → Shipment → Tracking Number. Required. |
| Shipviaty | → Shipment → Ship Method / Carrier. |
| Shipment Item SKU / Quantity | → Shipment Item → SKU / Quantity. Required. Taken from your original Fulfillment Request line items, not returned per-line by Iron Valley. |
Common issues
Send FR error — "Customer Ship To Record No Longer Available"
Iron Valley could not match the ship-to address on the order. This error usually means the shipping address fields are incorrect, incomplete, or formatted in a way that Iron Valley cannot validate. Re-check all Ship To mapping fields: Address Line 1, City, State, Postal Code, Country. Ensure Country is mapped as a 2-letter code (e.g.,
US). Hold the FR and retry after correcting the address mapping.Send FR error — "Product Restriction Found: FFL"
A firearm item on the order requires FFL documentation but no FFL PDF is attached. Open the Iron Valley source → Send Fulfillment Requests settings and confirm FFL Required is toggled ON. For each pending FFL order, attach a current, legible FFL PDF before reprocessing. The FFL PDF must be attached to the individual FR in Flxpoint before it can be submitted. If FFL Required was previously off and you have queued firearm dropship orders, you must manually attach FFL documents to each before resubmitting.
Get Shipments returning 401 authentication error
A 401 error means the Iron Valley API auth token has expired or is invalid. Flxpoint regenerates the auth token automatically — click Test Connection on the Iron Valley API connection to trigger token regeneration. If the error persists after clicking Test Connection, re-enter the API Username, API Password, and Customer Number and test again. A 401 on Get Shipments will cause the job to return no data without an obvious error in some cases — if shipments stopped importing unexpectedly, checking the connection token is the first step.
GIP not importing product data — FTP feed missing
If GIP runs but imports nothing: (1) verify FTP credentials by clicking Test Connection on the FTP (Basic Auth) connection; (2) confirm the Inbound Remote File Folder matches the directory where Iron Valley delivers your catalog file; (3) if a Remote Filename Pattern is set, confirm it matches the actual filename Iron Valley is using; (4) run GIP manually and check the job log for file retrieval errors. If the feed file is simply not yet available (Iron Valley hasn't published the latest file), wait and re-run. Contact Iron Valley to confirm the feed schedule if the file is consistently missing.
FAQs
What fields does GIP import from Iron Valley's FTP feed?▸
GIP reads Iron Valley's product feed via FTP and imports: SKU (and Parent SKU for variants), Title, Description, Long Description, Manufacturer, MPN, UPC, Cost, MSRP, Quantity, Weight (with unit — pound, ounce, gram, kilogram), Dimensions (Height, Length, Width), Images (via FTP download or Source Image Grabber), Primary Category, Sub Category, Country of Origin, and flags like Hazardous and Restricted. Option Name/Value fields (1–10) support variant attributes. Up to 100 Custom Fields and 10 Custom Aggregate Fields are available.
How should I configure GIS for Iron Valley?▸
GIS reuses the same FTP (Basic Auth) connection from GIP — no separate connection is needed. Configure the Inbound Remote File Folder to point to the correct secondary feed folder on Iron Valley's FTP, and set the Remote Filename Pattern to match the secondary feed file. GIS focuses on variant-level fields: SKU (required), Cost, MSRP, MAP, Quantity, Dimensions, Weight, Shipping Cost, Source List Price, UPC, and GTIN. Run GIS more frequently than GIP to keep pricing and quantity current between full catalog syncs.
What are the required fields for Send Fulfillment Requests to Iron Valley?▸
Required: Fulfillment Request Number → PO Number, SKU → PO Line Items#, Quantity → Order Quantity, Full Name → Ship To Name, Address Line 1 → Ship To Address 1, City → Ship To City, State → Ship To State, Postal Code → Ship To Zip, Country Code → Ship To Country. For FFL firearm orders: FFL Number → FFL Reference. Optional: Address Line 2, Phone, Notes. The Customer Number, PO Number, and order type classification are handled automatically by the Iron Valley API connection settings.
Does Iron Valley support partial shipments in Get Shipments?▸
Partial shipments are supported only on Flxpoint V2 — V1 does not support partial shipments for Iron Valley Get Shipments. On V2, Get Shipments retrieves shipment records from Iron Valley via API and supports partial fulfillment — multiple shipment responses can incrementally complete a single FR. Each response includes Carrier, Tracking Number, Order Number (to link to the FR), Warehouse, and Ship Date. Map Order Number carefully — it must point to the FR Number so Flxpoint can match the shipment to the original order. Item-level shipped quantities are inferred from matched FR items, not returned explicitly per shipment line.