Iron Valley as Source

Table of Contents

How to Connect Product Operations Order Operations

In this guide, you'll learn how to set up Iron Valley as a source in Flxpoint — create the source wizard, connect via FTP for inventory and via API for orders, and configure FFL handling for firearm dropship orders. Iron Valley uses an updated API as of Q2 2026; existing connections continue to work without setup changes.

Add Source and Establish Connection

Heads-up — Iron Valley API update: Iron Valley has upgraded their API. Flxpoint already uses the new version, so existing connections continue to work without setup changes. New connections include a Staging / Production environment toggle — pick Production for live orders. If Iron Valley issues you a replacement API Username or API Password during this transition, update them in this connection and click Test 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., Iron Valley). Then choose the Source Type that best fits how this Source will be used.

Choose the right Source Type

For most Iron Valley 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 Iron Valley 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 Iron Valley: select Vendor Warehouse. This enables sending Fulfillment Requests to Iron Valley 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 Iron Valley.

Step 1 — Shipping Methods

When the wizard opens the Shipping Methods step for this Source:

Skip if you do not need to configure shipping methods at this time.
Or Add Method to configure shipping methods if required for your setup.

Click Save & Next to continue.

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 wizard is now finished.

Next: Proceed to Phase 3 to create your Iron Valley connections for inventory and order operations.

🔑 Phase 3: Create Your Iron Valley Connections +

Goal

Iron Valley uses two connection types — an FTP connection for inventory feeds and an API connection for order operations. You will create one or both depending on which integrations you need. The FTP connection powers Get Inventory Primary and Get Inventory Secondary. The API connection powers Send Fulfillment Requests and Get Shipments.

Step 1 — Open Get Inventory [Primary] and start

Inside your Iron Valley source, open Integrations → Get Inventory [Primary] and click Start Creating Integrations. In the connector gallery, choose Iron Valley.

Step 2 — Choose your Connection Type

In New Iron Valley Connection, select one of:

FTP (Basic Auth) — for inventory file pickup. Used by Get Inventory Primary and Get Inventory Secondary.
Iron Valley API — for order operations. Used by Send Fulfillment Requests and Get Shipments.

Note: You may need both connection types if you plan to use both inventory and order operations. Create them one at a time.

Step 3a — If you choose FTP (Basic Auth)

Fill the form with the credentials provided by Iron Valley:

Connection Name (required) — a friendly label for this connection
FTP Protocol (SFTP, FTP, or FTPS)
FTP Host (required) — the host provided by Iron Valley
FTP Port (typically 22 for SFTP)
FTP User and FTP Password (required)

Optional Advanced Settings:

Maintain Constant Connection — keeps a live FTP session.
Use Unbuffered Private Data Channel — for FTPS SSL issues.

Click Test Connection → Save Connection.

Step 3b — If you choose Iron Valley API

Enter:

Connection Name (required) — a friendly label for this connection
Environment (required) — choose Production for live orders or Staging for testing. The authentication token is generated by Flxpoint behind the scenes for the environment you pick.
API Username (required) — provided by Iron Valley
API Password (required) — provided by Iron Valley
Customer Number (required) — your Iron Valley account number

Then Test Connection and Save Connection.

Important: Orders submitted while the connection is in Staging are NOT fulfilled by Iron Valley. Switch to Production only after your test order has been approved.

Step 4 — Configure FFL handling (firearm orders only)

If you process FFL-required firearm orders, turn on FFL Required in your Send Fulfillment Requests integration settings. When enabled, you'll be prompted to attach an FFL PDF to each FFL order before submission. Flxpoint automatically delivers the FFL documentation to Iron Valley alongside the order.

Tip: Non-firearm dropship orders skip the FFL upload step. Replenishment orders to your own warehouse do not require FFL documentation.

Step 5 — How Flxpoint uses these connections

Important: Iron Valley uses two separate connections for different operation types:

FTP (Basic Auth) connection → powers Get Inventory [Primary] and Get Inventory [Secondary]
Iron Valley API connection → powers Send Fulfillment Requests and Get Shipments

Tip: When configuring each operation later, select the correct connection type for that operation. Inventory operations need the FTP connection; order operations need the API connection.

Next Configure Product & Order Operations 🚀

Now that your Iron Valley connections are saved, go to the Operations section of this doc to set up the Iron Valley integrations you need (Inventory and Order operations). Each operation will let you select the appropriate Iron Valley Connection (FTP for inventory, API for orders).

Product Operations

Get Inventory (Primary)

Iron Valley integration: Supported

Introduction

Iron Valley is a wholesale supplier of firearms, ammunition, and outdoor gear. The Get Inventory (Primary) job imports Iron Valley product data and quantities into your Global Inventory Pool via FTP.

Use GIP to keep Iron Valley inventory current in Flxpoint: import the full product catalog with core details (titles, descriptions, categories, images, weight, dimensions), keep quantities and pricing up to date, and identify discontinued stock.

The sections below walk through each step of the setup and configuration process.

        Note: GIP is the import process. After each
        run, products and quantities live in the
        Global Inventory Pool and can be mapped to downstream channels.
      

Each run follows this workflow:

1Select Connection — Choose FTP (Basic Auth) when creating your Iron Valley connection.
2Fetch Data — Flxpoint reads the Iron Valley product feed file from the configured FTP folder. The feed includes the full catalog with stock levels, pricing, attributes, and image URLs.
3Map Fields — Incoming data is matched to your Mapping Template.
4Save to Global Inventory Pool — The pool is updated; changes flow to channels after your next push.

Follow these steps in your Iron Valley source → Get Inventory (Primary):

Step 1: Connect an Integration

Choose Iron Valley and create or select an FTP (Basic Auth) connection.

Fields: Connection Name, FTP Protocol, FTP Host, FTP Port, FTP User, FTP Password.
Tip: Use to validate your credentials before saving.

Step 2: Configure Settings

Inbound Remote File Folder — Specify the folder on the Iron Valley FTP server where your catalog file is delivered.
Remote Filename Pattern (optional) — Restrict pickup to a specific filename pattern.
Image Handling — Choose between FTP download or Source Image Grabber depending on your setup.

Step 3: Define a Mapping Template

Use the recommended fields from the Mapping Utilities section below, then adjust for your catalog.

Step 4: Save & Schedule

Run manually or enable a schedule (jobs run in UTC). The status page will show Connected, Configured, and Mapped with the template once complete.

Recommended Mapping (Iron Valley GIP)

Starter field mapping for Iron Valley (adjust per your template):

Flxpoint Field	Iron Valley Field	Example	Purpose	Status
SKU (T)	Inventory: SKU	IV12345	Product identifier	Required
Title (T)	Inventory: Title	Tactical Backpack	Display title	Required
Description (T)	Inventory: Description	Durable tactical backpack	Short description	Optional
Long Description (T)	Inventory: Long Description	High-capacity tactical pack with...	Detailed description	Optional
Manufacturer (T)	Inventory: Manufacturer	Iron Valley	Manufacturer	Optional
MPN (T)	Inventory: MPN	BPK-12345	Manufacturer Part Number	Optional
UPC (T)	Inventory: UPC	012345678905	Barcode	Optional
Cost (N)	Inventory: Cost	15.00	Cost price	Optional
MSRP (N)	Inventory: MSRP	29.99	Retail price	Optional
Quantity (N)	Inventory: Quantity	100	Stock quantity	Optional
Weight (N)	Inventory: Weight	2.5	Product weight	Optional
Weight Unit (T)	Inventory: Weight Unit	pound	Unit of weight	Optional
Height (N)	Inventory: Height	10	Height	Optional
Length (N)	Inventory: Length	15	Length	Optional
Width (N)	Inventory: Width	12	Width	Optional
Image (T)	Inventory: Image	https://...	Product image URL	Optional
Primary Category (T)	Inventory: Primary Category	Tactical	Main category	Optional
Sub Category (T)	Inventory: Sub Category	Backpacks	Subcategory	Optional
Parent SKU (T)	Inventory: Parent SKU	IV-PARENT	Parent SKU for variants	Optional
Country of Origin (T)	Inventory: Country of Origin	USA	Country of origin	Optional

Available Source Fields

Product Data: Cost (N), Country of Origin (T), Description (T), Hazardous (T), Height (N), Length (N), Width (N), Image (T), Long Description (T), Manufacturer (T), MPN (T), MSRP (N), Option Name 1-10 (T), Option Value 1-10 (T), Parent SKU (T), Primary Category (T), Quantity (N), Restricted (T), SKU (T), Sub Category (T), Title (T), UPC (T), Weight (N), Weight Unit (T), Weight Unit (Abbreviated) (T).

Mapping Options

Match It — Directly map a source field to a Flxpoint field.
Set It — Set a fixed/static value for a field.
Transform It (Mapping Set) — Apply a transformation or mapping set to the value.
Smart Rules — Use conditional logic to determine the mapped value.
Skip It (Don't Map) — Ignore the field entirely.
Skip It (Set to Empty) — Clear the field value on each sync.

        
        Summary: Map the core fields above and verify your FTP
        connection to ensure product data, pricing, and quantity import
        correctly.
      

Quick Checks

Connection shows Connected and passes Test Connection.
Mapping template is selected and saved.
FTP credentials are confirmed with Iron Valley.
Image handling setting is configured (FTP download or Source Image Grabber).

Troubleshooting

Data Not Importing: Verify your Iron Valley FTP credentials and the configured Inbound Remote File Folder. Confirm the connection passes Test Connection.
Images Not Loading: Check image handling settings. Confirm whether you are using FTP download or Source Image Grabber and that the configuration matches your setup.
Fields Not Mapping: Ensure the desired fields are enabled in the Mapping Dashboard and that the mapping template is saved and selected.

Operation Details

Feature	Availability	What to Expect
Custom Fields	Supported	100 custom fields, 10 summary fields.
Variations / Options	Supported	Option Name/Value 1-10.
Quantity	Supported	From the FTP product feed.
Weights & Dimensions	Supported	Weight, Height, Length, Width.
Images	Supported	Via FTP or Source Image Grabber.
Categories	Supported	Two-level (Primary + Sub).
Weight Unit Options	Supported	pound, ounce, gram, kilogram (full name) or lb, oz (abbreviated).

        
        Tip: Run a manual sync first to verify field mapping
        before enabling a recurring schedule.

Get Inventory (Secondary)

Iron Valley integration: Supported

Introduction

The Iron Valley – Get Inventory (Secondary) integration retrieves variant-level inventory updates from Iron Valley's FTP feed — SKU, Cost, MSRP, MAP, Quantity, Weight, and Dimensions. This job uses the same FTP connection configured during primary inventory setup.

The sections below walk through each step of the setup and configuration process.

        Tip: This operation reuses the same FTP (Basic Auth)
        connection from Get Inventory (Primary). No separate connection is
        needed.
      

Use this job to:

Refresh variant-level cost, MSRP, and MAP for existing SKUs.
Update quantities and related inventory fields.
Sync dimensions and weight data for shipping calculations.

Each run follows this workflow:

1Connection — Uses the existing FTP (Basic Auth) connection to retrieve the secondary inventory feed from Iron Valley's FTP server.
2Parse & Map — Variant-level fields are matched to your Mapping Template (see Mapping Utilities below).
3Write — Updates variant data in the Global Inventory Pool.

Example: SKU IV12345 with cost 15.00, MSRP 29.99, MAP 25.00, and quantity 100 ⇒ Flxpoint updates the variant with all secondary fields.

Step 1: Select Existing Iron Valley FTP Connection

Choose Iron Valley and select the existing FTP (Basic Auth) connection configured during primary inventory setup.

Step 2: Configure Settings

Inbound Remote File Folder — The folder where the secondary feed is delivered.
Remote Filename Pattern — Restrict pickup to the secondary feed filename pattern.
File Action — Set to Read.

Step 3: Define a Mapping Template

Choose or create a mapping template named Iron Valley – Get Inventory [Secondary]. Use the recommended fields from the Mapping Utilities section below.

Step 4: Save & Schedule

Run manually or enable scheduling (jobs run in UTC). When ready, the status page will show Connected, Configured, and Mapped with your template.

Recommended Mapping (Secondary)

Map the variant-level fields below for secondary inventory updates.

Flxpoint Field	Iron Valley Field	Example	Purpose	Status
SKU (T)	Inventory Variant: SKU	`IV12345`	Variant identifier	Required
Cost (N)	Inventory Variant: Cost	`15.00`	Cost price	Optional
Dimension Unit (T)	Inventory Variant: Dimension Unit	`inch`	Dimension unit	Optional
GTIN (T)	Inventory Variant: GTIN	`012345678905`	Global Trade Item Number	Optional
Height (N)	Inventory Variant: Height	`10`	Height	Optional
Length (N)	Inventory Variant: Length	`15`	Length	Optional
MAP (N)	Inventory Variant: MAP	`25.00`	Min Advertised Price	Optional
MSRP (N)	Inventory Variant: MSRP	`29.99`	Retail price	Optional
Quantity (N)	Inventory Variant: Quantity	`100`	Stock quantity	Optional
Shipping Cost (N)	Inventory Variant: Shipping Cost	`5.00`	Shipping cost	Optional
Source List Price (N)	Inventory Variant: List Price	`30.00`	List price	Optional
UPC (T)	Inventory Variant: UPC	`012345678905`	Barcode	Optional
Weight (N)	Inventory Variant: Weight	`2.5`	Weight	Optional
Weight Unit (T)	Inventory Variant: Weight Unit	`pound`	Weight unit	Optional
Width (N)	Inventory Variant: Width	`12`	Width	Optional

Available Source Fields

Iron Valley Inventory Variant: Cost (N), Height (N), Length (N), MAP (N), MSRP (N), Quantity (N), SKU (T), Weight (N), Width (N).
Additional: Dimension Unit (T), GTIN (T), Shipping Cost (N), Source List Price (N), UPC (T), Weight Unit (T).

Mapping Options

Options include Field, Value, Mapping Set, Rules, Don't Map, Set to Empty.

        
        Summary: Secondary mapping focuses on variant-level
        fields including cost, quantity, dimensions, MAP, MSRP, and weight. Keep
        catalog-level fields (titles, images, descriptions) in the Primary job.
      

Quick Checks

Connection reuses the same FTP connection from Get Inventory (Primary) and shows Connected.
Mapping template is selected and saved.
File paths are configured correctly for secondary data.
Remote File Name Pattern and Inbound Folder are set correctly.

Troubleshooting

Data not importing? Verify FTP credentials and folder paths. Use Test Connection to confirm the connection is active.
Fields not mapping? Check the Mapping Dashboard to confirm all fields are mapped correctly in the template.
Missing quantities? Confirm the secondary data file is present in the configured folder and that the filename pattern matches.
Cost or MSRP not updating? Verify the mapping template includes Cost and MSRP and that the source file contains non-empty values.

Operation Details

Feature	Availability	What to Expect
Variant-Level Fields	Supported	SKU, Cost, MAP, MSRP, Quantity, Weight, Dimensions.
Connection	Shared	Reuses the same Iron Valley FTP connection from primary inventory setup.
Scheduling	Supported	Run on demand or via recurring schedule (UTC).
Catalog-Level Fields	Not Supported	Titles, images, and descriptions belong in the Primary job.

        
        Tip: Run Secondary on a more frequent schedule than
        Primary to keep cost, quantity, and pricing data fresh between full
        catalog syncs.
      

Optional but recommended

Keep your Iron Valley 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

Send Fulfillment Requests

Iron Valley integration: Supported

Introduction

The Iron Valley – Send Fulfillment Requests integration sends Flxpoint Fulfillment Requests (FRs) to Iron Valley as Purchase Orders. This uses the Iron Valley API connection (Environment, API Username, API Password, Customer Number).

Iron Valley automatically classifies each PO as either Replenishment (stocking your own warehouse) or Dropship (shipping directly to your customer) based on brand and routing. For dropship firearm orders, FFL documentation is sent alongside the PO when FFL Required is enabled on the source.

The sections below walk through each step of the setup and configuration process.

Send Fulfillment Requests submits Flxpoint FRs to Iron Valley as Purchase Orders. If the request is accepted, the FR is marked as processed.

The setup is completed in four steps.

Step 1: Select Iron Valley API Connection

Select Iron Valley and choose your existing API connection. This connection requires:

Environment — Production for live orders or Staging for testing.
API Username, API Password — provided by Iron Valley.
Customer Number — your Iron Valley account number.

Click Test Connection, then Save Connection once successful.

        
        Tip: Reuse the same Iron Valley API connection if one
        was already created for other operations.

Step 2: Configure Settings

FFL Required — Toggle ON if you process FFL-required firearm orders. When enabled, you'll be prompted to attach an FFL PDF to each FFL order before submission. Flxpoint automatically delivers the FFL documentation to Iron Valley alongside the order.
- FFL PDF: Attach a current, legible FFL PDF to the PO.
- If PDF is missing: A warning prompts you to attach it before the order can be sent.
Hold for X Hours — Optional. Delay sending POs to allow review (default: 0).
Only Send During Business Hours — Restrict sends to specified hours.

Click Save and Proceed.

        
        Important: Replenishment vs Dropship classification is
        automatic. POs containing firearm-only brands routed to your warehouse
        are sent as Replenishment; POs routed to a consumer address are sent as
        Dropship. Dropship firearm orders require FFL documentation when FFL
        Required is enabled.
      

Step 3: Define a Mapping Template

Choose or create a mapping template named Iron Valley – Send FRs. Click Save and Complete.

Step 4: Save & Schedule

Run on demand or enable scheduling. Schedules run in UTC. The status page will show Connected, Configured, and Mapped.

The Mapping Template defines how Flxpoint fulfillment request data maps to Iron Valley's Purchase Order format. Header fields and line items map from your order to Iron Valley's required format.

Recommended Mapping (Key Fields)

Flxpoint Field	Iron Valley Field	Example	Purpose	Status
Fulfillment Request Number (T)	PO Number	`FR12345`	Purchase order number sent to Iron Valley	Required
SKU (T)	Item Number	`IV12345`	Product SKU on the line item	Required
Quantity (N)	Order Quantity	`2`	Quantity ordered on the line item	Required
Full Name (T)	Ship To Name	`John Doe`	Recipient name	Required
Address Line 1 (T)	Ship To Address 1	`123 Main St`	Shipping address line 1	Required
Address Line 2 (T)	Ship To Address 2	`Apt 4B`	Shipping address line 2	Optional
City (T)	Ship To City	`Los Angeles`	Shipping city	Required
State (T)	Ship To State	`CA`	Shipping state	Required
Postal Code (T)	Ship To Zip	`90210`	Shipping postal code	Required
Country Code (T)	Ship To Country	`US`	Shipping country	Required
Phone (T)	Ship To Telephone	`555-123-4567`	Recipient phone	Optional
FFL Number (T)	FFL Reference	`(provided by FFL dealer)`	FFL dealer license number for firearm orders	Conditional (FFL orders only)
Notes (T)	Order Note	`Special handling`	Free-text order note	Optional

Available Source Fields

The following field categories are available from Flxpoint:

Fulfillment Request: FR Number, FR Notes, Custom Fields, Confirm To Email, Confirm To Name.
FR Item: SKU, Quantity, Unit Price, Custom Fields.
Shipping Address: Full Name, Address Line 1, Address Line 2, City, State, Postal Code, Country Code, Phone.
FFL Information: FFL Number, FFL Dealer Name, FFL Address fields (when FFL Required is enabled).

Let's Break It Down: Map shipping address fields, SKU, and quantity as required fields. Add FFL fields when FFL Required is enabled. The PO number, customer number, and order type are derived automatically from your Iron Valley source configuration — you do not need to map them.

        
        Summary: Map the key fields above for accurate FR
        submission to Iron Valley. Ship To fields, SKU, Quantity, and (for FFL
        orders) FFL fields are the most critical to verify.
      

Quick Checks

Connection shows Connected and passes Test Connection.
Environment is set to Production before sending live orders.
Mapping template is selected and saved.
Required Ship To fields, SKU, and Quantity are mapped.
FFL Required is toggled correctly for firearm dropship orders.

Troubleshooting

Request not sending? Verify API credentials (Environment, API Username, API Password, Customer Number) and confirm the connection passes Test Connection.
"Customer Ship To Record No Longer Available" error: Indicates Iron Valley could not match the ship-to address. Re-check the Ship To mapping or hold the FR and retry.
"Product Restriction Found: FFL" error: The FFL PDF is missing for an FFL-required item. Attach the FFL PDF and reprocess the request.
Mixed Brands in a Single PO: If a PO contains both replenishment and dropship brands, split it into separate POs to ensure correct classification.
Test orders going through to live fulfillment: Confirm your connection is set to Staging for testing. Switch to Production only after your test order has been approved.

Operation Workflow

FR is submitted to Iron Valley using the configured API connection.
Iron Valley automatically classifies the order as Replenishment or Dropship based on brand and routing.
For dropship firearm orders with FFL Required enabled, FFL documentation is sent alongside the PO.
If the request is accepted, the FR is marked as processed.

Operation Details

Feature	Availability	What to Expect
FR Number	Supported	FR Number is sent as the Iron Valley PO Number.
Ship To Address	Supported	Full address including Address Lines 1–2, City, State, Postal Code, Country.
FR Item Association	Supported	Line items include SKU and Quantity.
FFL Documentation	Supported	FFL PDF is automatically delivered for FFL-required firearm dropship orders.
Replenishment vs Dropship	Automatic	Classified by brand and routing destination.
Environment Toggle	Supported	Production or Staging selectable on the connection.
Auto Acknowledgements	Basic	FR is marked Acknowledged on a successful API response.
Custom Fields	Supported	FR and FR Item Custom Fields are mappable to Iron Valley order notes.

        
        Tip: Always test with a single order in
        Staging first to verify Ship To mapping, FFL handling, and
        connectivity before switching to Production and enabling
        automation.
      

Get Shipments

Iron Valley integration: Supported

Introduction

The Iron Valley – Get Shipments integration retrieves shipment data from Iron Valley via API, including carrier, tracking numbers, and warehouse. This operation uses the same Iron Valley API connection configured for Send Fulfillment Requests.

The sections below walk through each step of the setup and configuration process.

        Note: This operation retrieves shipment confirmations
        from Iron Valley via API and updates your orders with carrier and
        tracking information.
      

Use this job to:

Retrieve shipment data including carrier and tracking numbers from Iron Valley.
Update orders with shipment confirmations after fulfillment.
Associate shipped items by SKU and order number.

Each run follows this workflow:

1Connect — Uses the Iron Valley API connection (Environment, API Username, API Password, Customer Number) to query shipment data.
2Parse — Carrier, tracking number, warehouse, and order number are parsed into your mapping template.
3Save — Shipment data posts back to the order; partial shipments are supported across multiple runs.

Example: Iron Valley returns a shipment with Carrier=UPS Ground, Tracking=1Z999..., and order number matching your FR → the Flxpoint shipment is created and the order status is updated.

Step 1: Select Iron Valley API Connection

Choose Iron Valley and select your existing API connection. Reuse the same connection from Send Fulfillment Requests if one already exists.

Step 2: Create a Mapping Template

Choose or create a mapping template named Iron Valley – Get Shipments. Use the recommended fields from the Mapping Utilities section below.

Step 3: Save & Schedule

Run manually or schedule periodic runs (UTC) — for example, every 2 hours.

Mapping Template (Recommended Fields)

Map these Iron Valley shipment fields to your Flxpoint shipment object.

Flxpoint Field	Iron Valley Field	Example	Purpose	Status
Shipped Via (T)	Shipment: Carrier	`UPS`	Carrier name or code	Required
Tracking Numbers (T)	Shipment: Tracking Number	`1Z999...`	Tracking number	Required
Order Confirmation Number (T)	Shipment: Order Number	`FR12345`	Links the shipment to the original FR	Required
Warehouse (T)	Shipment: Warehouse	`(Iron Valley warehouse code)`	Records the originating warehouse	Optional
Shipment Date (D)	Shipment: Shipped At	`2026-05-01T20:59:00Z`	Ship date	Optional

Available Source Fields

The following fields are available from the Iron Valley shipment response:

Iron Valley Shipment: Carrier, Order Number, Tracking Number, Warehouse, Shipment Date.

Mapping Options

Options include Field, Value, Mapping Set, Rules, Don't Map, Set to Empty.

Operation Workflow

Shipment data is fetched via the Iron Valley API connection on each scheduled run.
Iron Valley returns one record per shipment, including carrier, tracking, and the linking order number.
Partial shipments are supported — multiple responses can incrementally complete fulfillment.

        
        Summary: Map carrier, tracking number, and order number
        to associate shipments with the correct FRs. Warehouse and ship date are
        optional but useful for reporting.
      

Quick Checks

Connection shows Connected and passes Test Connection.
Mapping template is selected and saved.
Order Number is mapped to associate shipments with the correct FRs.
Tracking Number and Carrier fields are mapped.

Troubleshooting

Authentication errors (401): The connection token has expired or credentials are invalid. Re-test the connection — Flxpoint regenerates the auth token automatically.
"No Data" responses: The order may not have shipped yet. Confirm shipment status with Iron Valley and retry later.
Mapping issues: Ensure required fields like Tracking Number and Carrier are mapped correctly in the Mapping Dashboard.
Shipments not linking to FRs: Confirm the Order Number mapping points to your FR Number so Flxpoint can match the shipment to the original FR.

Operation Details

Feature	Availability	What to Expect
Carrier & Tracking	Supported	Carrier and tracking number are returned per shipment.
Shipment to FR Association	Supported	By Order Number matching the original FR.
Partial Shipments	Supported	Multiple responses can incrementally complete fulfillment.
Warehouse Code	Supported	Records the originating warehouse on the shipment.
Item-Level Quantity	Limited	Iron Valley returns shipment headers; line-level shipped quantities are inferred from the matched FR items.
Invoice Information	Not Supported	Invoices are not part of this operation.

        
        Tip: Schedule this job to run frequently (e.g., every 2
        hours) to keep shipment status and tracking information up to date in
        Flxpoint.
      

Optional but recommended

You're ready to automate this source

You've finished setting up Iron Valley. If you'd like, you can now put its operations on an automated schedule.

Select the operations to schedule (Get Inventory Primary, Get Inventory Secondary, 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 inventory and a more frequent schedule (every 2 hours) for shipments 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 Iron Valley integration. Expand each item to learn more.

Connection failing or Test Connection errors

Inventory not syncing or product feed missing

Order submission failing or rejected by Iron Valley

FFL documentation not attaching to firearm orders

Shipments or tracking not importing

Still need help? If you're experiencing issues not covered here, contact Iron Valley or your Flxpoint account manager.

Contact Support

Flxpoint Knowledge

Iron Valley as Source

Add Source and Establish Connection

Choose the right Source Type

Product Operations

Get Inventory (Primary)

Get Inventory (Secondary)

Keep your Iron Valley catalog up to date automatically

Order Operations

Send Fulfillment Requests

Get Shipments

You're ready to automate this source

Troubleshooting Common Errors

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

Flxpoint Knowledge

Add Source and Establish Connection

Choose the right Source Type

Product Operations

Get Inventory (Primary)

Get Inventory (Secondary)

Keep your Iron Valley catalog up to date automatically

Order Operations

Send Fulfillment Requests

Get Shipments

You're ready to automate this source

Troubleshooting Common Errors

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

What's happening

How to fix it

Related Articles