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 File Transfer Details:
Advanced Settings:
Connection Name
FTP Protocol (SFTP, FTP, or FTPS)
FTP Host (e.g., ironvalleysupply.goanywhere.cloud)
FTP Port (defaults to 22 for SFTP)
FTP User and FTP Password
FFL File Transfer Details:
Ensure the connection supports sending FFL details via email with attachments or via SFTP.
Please contact your Iron Valley representative for the specific FTP credentials for FFL file transfers.
CSV File Naming Format: cust#-datetimestamp.csv (e.g., 10100-2025-01-09-080115.csv). The CSV must include a header row with the required FFL details (FFL# and ship-to information).
PDF File Naming Format: FFL#.pdf (e.g., 1-59-115-01-7H-59074.pdf). If applicable, enable customer uploads for the PDF attachment.
Advanced Settings:
Maintain Constant Connection – keeps an active FTP session throughout the process.
Use Unbuffered Private Data Channel – useful for secure FTPS connections encountering SSL errors.
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
What You Get:
The Iron Valley integration allows you to send purchase order (PO) fulfillment requests seamlessly using the Iron Valley API. This process involves generating an access token, configuring settings, defining a mapping template, and automating the workflow. Here’s how it works:
Once the token is generated, use the following endpoints to send POs:
For Purchase Order:
For Purchase Order Item:
Special Rules:
The Iron Valley integration allows you to send purchase order (PO) fulfillment requests seamlessly using the Iron Valley API. This process involves generating an access token, configuring settings, defining a mapping template, and automating the workflow. Here’s how it works:
- Send Purchase Orders: Sends PO data to Iron Valley for fulfillment processing.
How It Connects:
To use the Iron Valley API, you need to generate a token for authentication. The token generation requires the following fields in the body:- grant_type
- username
- password
- client_id
- client_secret
Once the token is generated, use the following endpoints to send POs:
- Prod:
https://mingle-ionapi.inforcloudsuite.com/BANGERSUSA_PRD
- Staging:
https://mingle-ionapi.inforcloudsuite.com/BANGERSUSA_TST/SX/web/sxapirestservice/sxapisfoeordertotloadv4
Warning: Current authentication status: Prod Auth - Error, Staging Auth - Error. Please resolve authentication issues before proceeding.
Request Example:
Below is an example of the request sent to the Iron Valley API to initiate a fulfillment request:{
"request": {
"companyNumber": 1,
"operatorInit": "FLXP",
"operatorPassword": "FLXP",
"tInputheaderdata": {
"t-inputheaderdata": [
{
"customerid": "0001000000010100",
"ponumber": "4165619-3",
"carriercode": "BWSHP",
"shiptonumber": "66435456",
"webtransactiontype": "LSF",
"ordertype": "0"
}
]
},
"tInputlinedata": {
"t-inputlinedata": [
{
"itemnumber": "Test-1234",
"orderqty": 1,
"unitofmeasure": "EA",
"warehouseid": "BHM1",
"lineitemtype": "I",
"seqno": 1
}
]
}
}
}
Note: The response order number is set as the PO confirmation number for tracking in subsequent processes.
Default Settings:
Configure the integration settings to tailor the PO sending process:
- Customer ID: Must be in the format where the last 5 digits are the Iron Valley customer number (e.g.,
0001000000010100). This is set in the integration config.
- Hold for X Hours: Option to delay sending POs for review (useful if you don’t want to process orders older than X hours).
- Send During Business Hours: Option to restrict PO sending to business hours only.
Your Customization Dashboard:
Define a mapping template to map your data to Iron Valley PO fields. The following fields are exposed:For Purchase Order:
- Purchase Order Number: Maps to the PO number in the request (e.g.,
ponumber).- Ship To Number: Can be dynamically set based on rules (e.g.,
shiptonumber).- Use FFL License Number as Ship To Number: If true, the "Ship-to" number is derived as the first 3 digits + last 5 digits of the FFL# (e.g., FFL#
6-64-027-07-7D-35456 → 66435456).For Purchase Order Item:
- Item Description: Suggested to include the end-customer name for dropship orders.
- Item Number: Maps to the SKU or MPN (e.g.,
itemnumber).- Order Qty: Quantity of the item to be ordered (e.g.,
orderqty).Special Rules:
- If any PO item uses the following brands, override the 'Ship To Number' with value
1:
- Browning
- Glock
- FN
- IWI US
- Outdoor Edge
- Ruger
- Smith & Wesson
- Springfield Armory
- Walther
- Winchester
Troubleshooting:
- Common Error #1: "No Order Created|Customer Ship To Record No Longer Available" indicates the 'Ship To Number' is invalid. Set 'Ship To Number' to 'Hold' and reprocess the order.
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 ensures your POs are sent to Iron Valley efficiently, with customizable mappings and robust error handling!
Get Shipments
What You Get:
The Iron Valley integration allows you to retrieve shipment tracking information using the Iron Valley API. This process involves generating an access token, configuring the integration, and defining a mapping template to map the API response to shipment fields. Here’s how it works:
Current authentication status:
Once the token is generated, use the following endpoints to get shipments:
Request:
Response:
The Iron Valley integration allows you to retrieve shipment tracking information using the Iron Valley API. This process involves generating an access token, configuring the integration, and defining a mapping template to map the API response to shipment fields. Here’s how it works:
- Get Shipments: Retrieves tracking details for purchase orders using the order number (confirmation number saved from the Send PO process).
How It Connects:
To use the Iron Valley API, you need to generate a token for authentication. The token generation requires the following fields in the body:- grant_type
- username
- password
- client_id
- client_secret
Current authentication status:
- Prod Auth: Error
- Staging Auth: Error
Note: Please resolve authentication issues before proceeding.
Once the token is generated, use the following endpoints to get shipments:
- Prod: https://mingle-ionapi.inforcloudsuite.com/BANGERSUSA_PRD/SX/web/sxapirestservice/sxapisfgettrackingnum
- Staging: https://mingle-ionapi.inforcloudsuite.com/BANGERSUSA_TST/SX/web/sxapirestservice/sxapisfgettrackingnum
Request and Response:
The shipment is retrieved by passing the order number (saved as the PO confirmation number) in the request body.Request:
{
"request": {
"companyNumber": 1,
"operatorInit": "FLXP",
"operatorPassword": "FLXP",
"orderNumber": 4165619
}
}
Response:
{
"response": {
"cErrorMessage": "",
"tTrackernum": {
"t-trackernum": [
{
"whse": "BHM1",
"orderno": 4165619,
"ordersuf": 0,
"trackerno": "1Z338897A890926553",
"shipviaty": "UPSG"
}
]
}
}
}
Troubleshooting:
- 401 Unauthorized: Occurs if an incorrect token is passed in the request header. Regenerate and use the correct token.
- Empty Response: Occurs if the order number provided does not have tracking information. Verify the order number and ensure it has been processed.
Your Customization Dashboard (Mapping Template):
Define a mapping template to map the API response fields to shipment fields. The following fields are available:
- Carrier: Maps to "shipviaty" (e.g., "UPSG") from the response.
- Method: Maps to "shipviaty" (e.g., "UPSG") from the response.
- Tracking Number: Maps to "trackerno" (e.g., "1Z338897A890926553") from the response.
- Note: Not mapped by default (optional field).
Note: Use the dropdowns in the mapping interface to select and map these fields appropriately.
Automation Options:
Once configured and mapped, the integration can be automated. 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 you can efficiently retrieve shipment tracking information from Iron Valley!