Iron Valley is a wholesale supplier of firearms, ammunition, and outdoor gear. Flxpoint integration supports automated inventory and fulfillment.
How to Connect
Step 1: Log into your Flxpoint account and navigate to the Sources tab.
Step 2: Click on + Add Source (or Configure Single Source) to begin creating a new source.
Step 3: Fill in your source details (e.g., vendor name, fulfillment preferences) and click Save.
Step 4: After saving, navigate to Get Inventory under Integrations in the left menu. If you see No integrations have been configured for this process yet, click Start Creating Integrations.
Step 5: From the list of Custom Integrations or Standard Integrations, locate and select Iron Valley to open the connection setup screen.
Step 6: In the New Iron Valley Connection form, enter your:
FFL‑Order Details (new):
Advanced Settings:
Connection Name
FTP Protocol (SFTP, FTP, or FTPS)
FTP Host (e.g., ironvalleysupply.goanywhere.cloud)
FTP Port (22 for SFTP)
FTP User and FTP Password
FFL‑Order Details (new):
Only enabled when
FFLRequired = true on your Iron Valley source.CSV Naming:
cust#‑YYYY‑MM‑DD‑hhmmss.csv (e.g., 10100‑2025‑03‑20‑152526.csv).PDF Naming:
FFL#.pdf (e.g., 1‑63‑073‑08‑7D‑10006.pdf).Hard‑coded SFTP creds for FFL:
user: FlxpointFFL, pw: Flxp3248915@.If PDF not uploaded when required, a warning prompts the user to attach it.
Advanced Settings:
Maintain Constant Connection – keeps a live FTP session.
Use Unbuffered Private Data Channel – for secure FTPS SSL issues.
Step 7: Click Test Connection to verify your credentials, then click Save Connection.
Step 8: On the Configure Settings screen, enter your:
Then enter:
Inbound Remote File Folder
Outbound Remote File Folder (if applicable)
Then enter:
Our Sender/Receiver Qualifier and Our Sender/Receiver ID
Their Sender/Receiver Qualifier and Their Sender/Receiver ID
Click Save and Proceed.
Step 9: Under Define a Mapping Template, select or create a mapping template to align Iron Valley’s inventory fields (e.g., SKU, Quantity) with Flxpoint’s corresponding fields. Once mapped, click Save and Complete.
Step 10: Your Iron Valley integration is now active. Flxpoint will begin retrieving inventory from your Iron Valley feed based on your scheduled settings.
Product Operations
The primary operation handles the bulk of your inventory management needs, while the secondary operation allows for more detailed control, such as focusing on specific products or updates.
Get Inventory (Primary)
What You Get:
The Iron Valley integration helps you effortlessly retrieve inventory data using a secure FTP or SFTP connection. It pulls product details from the Catalog.csv file and maps them to your system, making inventory management a breeze. Here’s how it works:
Get Inventory Mappings:
These fields map the Catalog.csv data to your internal fields (based on supported data):
The Iron Valley integration helps you effortlessly retrieve inventory data using a secure FTP or SFTP connection. It pulls product details from the Catalog.csv file and maps them to your system, making inventory management a breeze. Here’s how it works:
- Get Inventory [Primary]: Fetches inventory data from Iron Valley’s Catalog.csv file.
How It Connects:
This integration uses FTP or SFTP to connect to Iron Valley’s server. You’ll need to provide your SFTP credentials and configure the connection. The process retrieves the Catalog.csv file from the default location: `/Catalog.csv`. Here’s what to set up:
- FTP/SFTP Protocol: Choose SFTP, FTP, or FTPS.
- FTP Host: The server address (e.g., `ironvalleysupply.goanywhere.cloud`).
- FTP Port: Defaults to `22` for SFTP.
- FTP User & Password: Your login credentials provided by Iron Valley.
Note: Test your connection to ensure it works before saving.
Default Settings:
Customize your inventory retrieval with these options:
- Inbound Remote File Folder: Specify where to retrieve the Catalog.csv file (default: `/Catalog.csv`).
- Remote Filename Pattern: Optional pattern for file names (if needed).
- Archive Old Inventory: Option to archive inventory data not in the latest feed.
Your Customization Dashboard:
The dashboard lets you map Iron Valley’s inventory fields to your system with easy controls. Here’s what you can set up:Get Inventory Mappings:
These fields map the Catalog.csv data to your internal fields (based on supported data):
- Custom Fields: Supported (e.g., Closeout, Serialized, Cal/GA, Allocated (Y/N)).
- Generic Pricing (& Currency): Supported.
- Quantity: Supported (pulled from Catalog.csv).
- Images: Supported (direct copy from the feed).
- Categories: Supported.
- Archive Support: Supported (products not in the feed can be archived if enabled).
- Variations/Options: Not supported.
- Client Pricing (& Currency): Unknown support.
- Multiple Warehouses: Not supported.
- Weights & Dimensions (& Units): Not supported.
- Delta Feed vs Full Feed: Full feed every time.
Note: You can adjust mappings to match your needs, with unsupported fields exposed for custom mapping if required.
Automation Options:
Once set up, your integration will be Connected, Configured, and Mapped. You can:
- Run it manually with the Run Integration button.
- Automate it by enabling a schedule (notifications sent for each run, using UTC time).
This setup ensures your inventory from Iron Valley is updated seamlessly, tailored to your workflow!
Get Inventory (Secondary)
What You Get:
The Iron Valley Get Inventory [Secondary] integration streamlines your inventory updates by retrieving pricing and quantity data from the PriceQty.csv file via a secure FTP connection. It’s designed to work alongside your primary inventory process, ensuring your product variants stay up-to-date. Here’s how it works:
Get Inventory [Secondary] Mappings:
These fields map the PriceQty.csv data to your variant fields (required fields are active):
The Iron Valley Get Inventory [Secondary] integration streamlines your inventory updates by retrieving pricing and quantity data from the PriceQty.csv file via a secure FTP connection. It’s designed to work alongside your primary inventory process, ensuring your product variants stay up-to-date. Here’s how it works:
- Get Inventory [Secondary]: Fetches and updates pricing and quantity data from PriceQty.csv.
How It Connects:
This integration retrieves the PriceQty.csv file from the default FTP location: /PriceQty.csv. It iterates through each SKU to update the appropriate variant data. You’ll need to ensure the connection is properly set up:
- Connection: Use your existing Iron Valley FTP connection (e.g., "zvvs - Iron Valley FTP").
Note: Mapping either quantity or price is mandatory; if neither is mapped, the integration will fail.
Default Settings:
Customize your secondary inventory retrieval with these options:
- Inbound Remote File Folder: Default is
/ (adjust if needed).
- Remote File Name Pattern: Set to
PriceQty.csv (can be modified if overridden).
- Archive/Un-Archive Inventory: Option to archive inventory not in the feed or un-archive it when added back (use cautiously).
- Allow Create Variant: Option to create variants during the process.
Note: Avoid enabling Archive/Un-Archive if it’s already enabled for Get Inventory [Secondary] on this source.
Your Customization Dashboard:
The dashboard lets you map Iron Valley’s PriceQty.csv fields to your variant fields with easy controls. Here’s what you can set up:Get Inventory [Secondary] Mappings:
These fields map the PriceQty.csv data to your variant fields (required fields are active):
- Cost: Maps to Iron Valley Product : Price (Enabled, Required)
- Quantity: Maps to Iron Valley Product : Quantity Available (Enabled, Required)
- SKU: Maps to Iron Valley Product : Iron Valley Prd (Enabled)
- UPC: Maps to Iron Valley Product : UPC/EAN/GTIN14 (Enabled)
- MAP: Not mapped by default (Disabled)
Note: At least one of Price or Quantity must be mapped; failure to map either will cause the integration to fail.
Troubleshooting:
If you encounter issues, here’s how to resolve them:
- Failed to download 'PriceQty.csv' file: Check the "Iron Valley Remote File Name" in settings. If overridden, ensure it matches the FTP server file name.
Automation Options:
Once set up, the integration will be Connected, Configured, and Mapped. You can:- Run it manually with the Run Integration button.
- Automate it by enabling a schedule (notifications sent for each run, using UTC time).
This setup keeps your secondary inventory running smoothly, tailored to your needs!
Order Operations
It submits orders to vendors for fulfillment and subsequently imports the shipment details, ensuring an integration between order processing and shipment tracking.
Send Fulfillment Requests
Supported | Iron Valley – Send Fulfillment Requests
Introduction to Iron Valley Send Fulfillment Requests Integration
This guide walks you through sending purchase orders (fulfillment requests) to Iron Valley via their API. We’ll cover connection setup, configuration options, mapping your order data, handling FFL‑required orders, and troubleshooting common errors—so you can automate PO submission confidently.
Purpose of This Integration
The Iron Valley Send Fulfillment Requests integration enables you to:
• Automate sending POs to Iron Valley for order processing.
• Include FFL license details and attachments when required.
• Control timing (hold for review, business‑hours only).
• Map your platform’s order fields to Iron Valley’s API schema.
How It Works
1. Connect: Select Iron Valley under “Send Fulfillment Requests.”
2. Configure: Enter FTP/API credentials, schedule, and FFL options.
3. Map: Define how your order data (SKU, qty, addresses, FFL#) maps to Iron Valley’s fields.
4. Run: Execute manually or on a schedule; PO + CSV + PDF (if FFL) go to Iron Valley automatically.
Configuration Options
Customer ID: Must end with your Iron Valley account number (e.g.
0001000000010100).
Hold for X Hours: Delay sending POs for review (default: 0).
Business‑Hours Only: Send only during specified hours.
FFL Required: Toggle to prompt for FFL PDF when needed.
FTP Credentials: Hard‑coded for FFL:
FlxpointFFL / Flxp3248915@.Setup Instructions
Step 1 – Select Integration: In “Send Fulfillment Requests,” choose Iron Valley and click “Save & Proceed.”
Step 2 – Enter Credentials:
– API Username & Password
– FTP Host: ironvalleysupply.goanywhere.cloud, Port: 22
– FTP User/Pass for FFL file delivery
Step 3 – Scheduling: Set a manual run or an automated schedule (e.g. daily at 6 AM UTC).
Step 4 – FFL Handling: If “FFL Required” is on and your PO includes FFL items, upload the PDF when prompted.
Step 5 – Save & Test: Click “Test Connection,” then “Save Integration.”
Request Example
Use only the required header + one line item:
{
"request": {
"t-inputheaderdata": [{
"customerid":"0001000000010100",
"ponumber":"4165619-3",
"shiptonumber":"66435456",
"ordertype":"O"
}],
"t-inputlinedata":[{ "itemnumber":"ABC-1234","orderqty":2 }]
}
}
We omit defaults (unitOfMeasure, carrierCode, etc.)—Flxpoint fills them automatically.
Mapping Template Overview
Use mapping to align your order fields with Iron Valley’s:
Purchase Order Header: ponumber, shiptonumber, webtransactiontype, ordertype
Line Items: itemnumber (SKU), orderqty, unitofmeasure, warehouseid
FFL Logic: If FFLRequired, map FFL# → shiptonumber (first 3 + last 5 digits).
Address Fields: Map shipping_address.address1, city, country, zip, name, phone.
Required Fields
•
ponumber, customerid, shiptonumber
• At least one line in
t-inputlinedata with itemnumber & orderqty
• If FFLRequired, FFL PDF must be attached before sending.
Troubleshooting
Error: “No Order Created|Customer Ship To Record No Longer Available” → invalid ship‑to. Update mapping or hold and retry.
Error: “400 Bad Request: Product Restriction Found: FFL” → missing FFL PDF. Attach PDF and reprocess.
Conclusion
You’re all set! With connection, mapping, and FFL handling in place, your POs and FFL attachments will flow seamlessly to Iron Valley. For further help, contact support or your Iron Valley rep.
Get Shipments
Supported | Iron Valley – Get Shipments
Introduction to Get Shipments
Retrieve shipment tracking details for POs you’ve sent to Iron Valley. Generate an API token, call the tracking endpoint with your order number, then map the response into your system’s shipment fields.
How It Works
1. Authenticate: POST credentials to the token endpoint.
2. Request Tracking: Send your saved PO confirmation number.
3. Parse & Map: Extract
trackerno, shipviaty, etc.Endpoints
Prod:
.../sxapisfgettrackingnum
Staging:
.../sxapisfgettrackingnum
Request Example
{
"request": {
"companyNumber": 1,
"operatorInit": "FLXP",
"operatorPassword": "FLXP",
"orderNumber": 4165619
}
}
Response Example
{
"response": {
"t-trackernum": [
{
"whse": "BHM1",
"orderno": 4165619,
"trackerno": "1Z338897A890926553",
"shipviaty": "UPSG"
}
]
}
}
• Array of tracker records; map each to your shipment entity.
Mapping Template
Map these response fields:
Carrier:
shipviaty
Tracking #:
trackerno
Warehouse:
whse (optional)
Order #:
orderno
Troubleshooting
401 Unauthorized: token invalid—regenerate.
No Data: order not shipped yet—retry later.
Automation Options
• Run manually via “Run Integration.”
• Schedule periodic runs (e.g. every 2 hrs).