Flxpoint Knowledge

Contact us

Iron Valley as Source

Table of Contents

How to Connect Product Operations Order Operations

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:
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:
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)

Supported | Iron Valley - Get Inventory [Primary]

Introduction to Iron Valley - Get Inventory [Primary] Integration
The Iron Valley - Get Inventory [Primary] integration helps you effortlessly retrieve inventory data from Iron Valley’s server using a secure FTP or SFTP connection. It pulls product details from the Catalog.csv file and maps them to your Flxpoint system, making inventory management seamless. This guide walks you through the setup process. Let’s get started!

The Iron Valley - Get Inventory [Primary] integration connects your Flxpoint system to Iron Valley to:
  • Retrieve inventory data from Iron Valley’s Catalog.csv file via FTP or SFTP.
  • Map Iron Valley’s inventory fields to your system for accurate inventory management.
  • Ensure seamless integration of product details into your Flxpoint system.

The integration follows a structured process to retrieve and map inventory data from Iron Valley:
  • FTP/SFTP Connection: Establishes a secure connection using your Iron Valley FTP or SFTP credentials (e.g., host: ironvalleysupply.goanywhere.cloud, port: 22).
  • File Retrieval: Pulls the Catalog.csv file from the default location /Catalog.csv (configurable via Inbound Remote File Folder).
  • Data Mapping: Uses the Mapping Dashboard ("Iron Valley - Get Inventory [Primary]") to map Iron Valley’s inventory fields to your system.
Note: Test your FTP/SFTP connection before saving to ensure it works properly.

Customize the integration to fit your needs:
  • FTP/SFTP Protocol: Choose SFTP, FTP, or FTPS for the connection.
  • FTP Host: Set the server address (e.g., ironvalleysupply.goanywhere.cloud).
  • FTP Port: Defaults to 22 for SFTP (adjustable if needed).
  • FTP User & Password: Provide your Iron Valley login credentials.
  • Inbound Remote File Folder: Specify the file location (default: /Catalog.csv).
  • Remote Filename Pattern: Optionally set a pattern for file names (if needed).
  • Archive Old Inventory: Enable to archive inventory data not in the latest feed.

Follow these steps to set up the Iron Valley - Get Inventory [Primary] integration:
  • 1 Configure FTP/SFTP Connection: Provide your Iron Valley credentials (FTP Host, Port, User, Password) and choose the protocol (SFTP, FTP, or FTPS).
  • 2 Set File Path: Specify the Inbound Remote File Folder (default: /Catalog.csv) and optionally set a Remote Filename Pattern.
  • 3 Enable Archive Option: Decide whether to archive old inventory data not in the latest feed.
  • 4 Create a Mapping Template: Use the Mapping Dashboard ("Iron Valley - Get Inventory [Primary]") to define how Iron Valley’s fields map to your inventory system (details below).
  • 5 Run the Integration: Run it manually with the "Run Integration" button or automate it by enabling a schedule (notifications sent for each run, using UTC time).

  • The mapping screen is labeled “Iron Valley - Get Inventory [Primary]” in the Mapping Dashboard.
  • Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
  • Sections include:
    • From Value: Iron Valley fields (e.g., Quantity, Images).
    • To Inventory Field: Flxpoint inventory fields (e.g., Stock Quantity, Product Images).
    • Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.

This section provides key details about the Iron Valley - Get Inventory [Primary] integration to help you understand the process:
  • Current Date and Time: As of 09:31 PM -04 on Thursday, May 15, 2025, this integration is fully operational for retrieving inventory data from Iron Valley.
  • Iron Valley Integration: Retrieves inventory data from the Catalog.csv file via FTP or SFTP, with a default path of /Catalog.csv.
  • Supported Features: Includes Custom Fields (e.g., Closeout, Serialized), Generic Pricing, Quantity, Images, Categories, and Archive Support.
  • Unsupported Features: Does not support Variations/Options, Multiple Warehouses, or Weights & Dimensions. Uses a full feed every time (no delta feed).
Tip: Ensure all required fields (e.g., Quantity) are properly mapped to avoid missing inventory data in Flxpoint.

Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, as in the dashboard):
Iron Valley - Get Inventory [Primary] Mappings
Field Maps To Example Purpose Status
Closeout (T) Inventory: Custom Field - Closeout Yes Indicates if the product is a closeout item Optional
Serialized (T) Inventory: Custom Field - Serialized No Indicates if the product is serialized Optional
Cal/GA (T) Inventory: Custom Field - Cal/GA Compliant Records California/Georgia compliance status Optional
Allocated (T) Inventory: Custom Field - Allocated Y Indicates if the product is allocated (Y/N) Optional
Generic Pricing (N) Inventory: Price 29.99 Records the product’s price (supports currency) Required
Quantity (N) Inventory: Quantity 100 Records the stock quantity available Required
Images (T) Inventory: Images https://example.com/image.jpg Sets the URLs for product images (direct copy) Optional
Categories (T) Inventory: Category Firearms Records the product category Optional

Available Source Fields
Iron Valley provides fields from the Catalog.csv file, including:
  • Custom Fields: Closeout (T), Serialized (T), Cal/GA (T), Allocated (T).
  • Product Data: Generic Pricing (N), Quantity (N), Images (T), Categories (T).

Mapping Options
You can choose from the following options for each field:
  • Field: Link an Iron Valley field (e.g., Quantity) to a Flxpoint inventory field.
  • Value: Choose a fixed value for the field.
  • Mapping Set: Use preset tools to adjust data (e.g., combine fields).
  • Rules: Add "if-then" logic (e.g., only map if quantity > 0).
  • Don’t Map: Ignore the field entirely.
  • Set to Empty: Clear the field in the Flxpoint inventory, removing existing data.

If the integration encounters an issue, try these steps:
  • Data Not Importing: Verify your FTP/SFTP credentials and ensure the file path (/Catalog.csv) is correct.
  • Fields Not Mapping: Ensure required fields like Quantity and Generic Pricing are mapped correctly in the Mapping Dashboard.
  • Connection Issues: Test your FTP/SFTP connection to confirm it’s active and accessible.

Conclusion
With the Iron Valley - Get Inventory [Primary] integration, you can efficiently retrieve and map inventory data from Iron Valley into your Flxpoint system. Flexible mapping options, a user-friendly Mapping Dashboard, and automation features ensure your inventory management is accurate and tailored to your workflow.
 
 

Get Inventory (Secondary)

Supported | Iron Valley - Get Inventory [Secondary]

Introduction to Iron Valley - Get Inventory [Secondary] Integration
The Iron Valley - Get Inventory [Secondary] integration streamlines your inventory updates by retrieving pricing and quantity data from Iron Valley’s PriceQty.csv file via a secure FTP connection. Designed to work alongside your primary inventory process, it ensures your product variants stay up-to-date. This guide walks you through the setup process. Let’s get started!

The Iron Valley - Get Inventory [Secondary] integration connects your Flxpoint system to Iron Valley to:
  • Retrieve pricing and quantity data from Iron Valley’s PriceQty.csv file via FTP.
  • Update variant data by mapping Iron Valley’s fields to your inventory system.
  • Ensure seamless integration of variant updates alongside your primary inventory process.

The integration follows a structured process to retrieve and map secondary inventory data from Iron Valley:
  • FTP Connection: Uses your existing Iron Valley FTP connection (e.g., "zvvs - Iron Valley FTP") to access the server.
  • File Retrieval: Pulls the PriceQty.csv file from the default location /PriceQty.csv (configurable via Inbound Remote File Folder).
  • Data Mapping: Iterates through each SKU in the PriceQty.csv file and updates the corresponding variant data in your system using the Mapping Dashboard ("Iron Valley - Get Inventory [Secondary]").
Note: Mapping either quantity or price is mandatory; if neither is mapped, the integration will fail.

Customize the integration to fit your needs:
  • Inbound Remote File Folder: Specify the file location (default: /).
  • Remote File Name Pattern: Set to PriceQty.csv (can be modified if overridden).
  • Archive/Un-Archive Inventory: Enable to archive inventory not in the feed or un-archive when added back (use cautiously).
  • Allow Create Variant: Enable to create variants during the process.
Note: Avoid enabling Archive/Un-Archive if it’s already enabled for Get Inventory [Secondary] on this source.

Follow these steps to set up the Iron Valley - Get Inventory [Secondary] integration:
  • 1 Verify FTP Connection: Ensure your existing Iron Valley FTP connection (e.g., "zvvs - Iron Valley FTP") is active and accessible.
  • 2 Set File Path: Specify the Inbound Remote File Folder (default: /) and confirm the Remote File Name Pattern is set to PriceQty.csv.
  • 3 Configure Archive Options: Decide whether to enable Archive/Un-Archive Inventory and Allow Create Variant settings.
  • 4 Create a Mapping Template: Use the Mapping Dashboard ("Iron Valley - Get Inventory [Secondary]") to define how Iron Valley’s fields map to your variant fields (details below).
  • 5 Run the Integration: Run it manually with the "Run Integration" button or automate it by enabling a schedule (notifications sent for each run, using UTC time).

  • The mapping screen is labeled “Iron Valley - Get Inventory [Secondary]” in the Mapping Dashboard.
  • Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
  • Sections include:
    • From Value: Iron Valley fields (e.g., Price, Quantity Available).
    • To Variant Field: Flxpoint variant fields (e.g., Cost, Quantity).
    • Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.

This section provides key details about the Iron Valley - Get Inventory [Secondary] integration to help you understand the process:
  • Current Date and Time: As of 09:32 PM -04 on Thursday, May 15, 2025, this integration is fully operational for retrieving secondary inventory data from Iron Valley.
  • Iron Valley Integration: Retrieves pricing and quantity data from the PriceQty.csv file via FTP, with a default path of /PriceQty.csv.
  • Required Mapping: At least one of Price or Quantity must be mapped to avoid integration failure.
  • Archive Caution: Avoid enabling Archive/Un-Archive if already enabled for Get Inventory [Secondary] on this source to prevent conflicts.
Tip: Ensure Price and Quantity are mapped correctly to keep your variant data up-to-date.

Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, as in the dashboard):
Iron Valley - Get Inventory [Secondary] Mappings
Field Maps To Example Purpose Status
Price (N) Variant: Cost 29.99 Records the cost of the variant (required if Quantity is not mapped) Required
Quantity Available (N) Variant: Quantity 100 Records the available quantity for the variant (required if Price is not mapped) Required
Iron Valley Prd (T) Variant: SKU IV12345 Identifies the variant by SKU Enabled
UPC/EAN/GTIN14 (T) Variant: UPC 012345678905 Records the UPC/EAN/GTIN14 for the variant Enabled
MAP (N) Variant: MAP 25.00 Sets the Minimum Advertised Price for the variant Disabled

Available Source Fields
Iron Valley provides fields from the PriceQty.csv file, including:
  • Product Data: Price (N), Quantity Available (N), Iron Valley Prd (T), UPC/EAN/GTIN14 (T), MAP (N).

Mapping Options
You can choose from the following options for each field:
  • Field: Link an Iron Valley field (e.g., Quantity Available) to a Flxpoint variant field.
  • Value: Choose a fixed value for the field.
  • Mapping Set: Use preset tools to adjust data (e.g., combine fields).
  • Rules: Add "if-then" logic (e.g., only map if quantity > 0).
  • Don’t Map: Ignore the field entirely.
  • Set to Empty: Clear the field in the Flxpoint variant, removing existing data.

If the integration encounters an issue, try these steps:
  • 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.
  • Integration Failure: Ensure at least one of Price or Quantity is mapped in the Mapping Dashboard.
  • Connection Issues: Verify your FTP connection (e.g., "zvvs - Iron Valley FTP") is active and accessible.

Conclusion
With the Iron Valley - Get Inventory [Secondary] integration, you can efficiently retrieve and map pricing and quantity data from Iron Valley into your Flxpoint system, keeping your product variants up-to-date. Flexible mapping options, a user-friendly Mapping Dashboard, and automation features ensure your secondary inventory process runs 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.

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.

The integration follows a structured process to send fulfillment requests to Iron Valley:
  • Connect: Select Iron Valley under “Send Fulfillment Requests.”
  • Configure: Enter FTP/API credentials, schedule, and FFL options.
  • Determine Order Type: The integration automatically classifies the order as either Dropship or Replenishment:
    • Replenishment Orders: Used for stocking products in your own warehouse. If any line item’s brand matches Browning, Glock, FN, IWI US, Outdoor Edge, Ruger, Smith & Wesson, Springfield Armory, Walther, or Winchester, the entire PO is sent as a replenishment order with shiptonumber = 1.
    • Dropship Orders: Used for shipping directly to your consumer. Applies to all other brands, omitting shiptonumber = 1. For dropship firearm orders, FFL documentation (PDF and CSV) is required and automatically uploaded to Iron Valley’s SFTP at sftp://ironvalleysupply.goanywhere.cloud/.
  • Map: Define how your order data (SKU, qty, addresses, FFL#) maps to Iron Valley’s fields. For dropship orders, the integration automatically sets warehouse = "BHM1" at both header and line-item levels.
  • Run: Execute manually or on a schedule; PO + CSV + PDF (if FFL) go to Iron Valley automatically via API and SFTP.
  • Example API Request: Below is an example of the API request sent to Iron Valley, showing the required header and a single 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.

Customize the integration to fit your needs:
  • 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 for dropship firearm orders. When enabled:
    • FFL PDF: Attach a clear, current FFL PDF to the PO.
    • FFL CSV: Upload a CSV with required fields (dealer name, license #, expiry date, address, city, state, ZIP) in the order specified in Iron Valley’s API guide.
  • FTP Credentials: Hard-coded for FFL: FlxpointFFL / Flxp3248915@. Files are automatically pushed to sftp://ironvalleysupply.goanywhere.cloud/ in the root folder (/) unless Iron Valley instructs otherwise.
  • Warehouse Code: For dropship orders, the integration automatically sets warehouse = "BHM1" at both header and line-item levels.

Follow these steps to set up the Iron Valley Send Fulfillment Requests integration:
  • 1 Select Integration: In “Send Fulfillment Requests,” choose Iron Valley and click “Save & Proceed.”
  • 2 Enter Credentials:
    • API Username & Password.
    • FTP Host: ironvalleysupply.goanywhere.cloud, Port: 22.
    • FTP User/Pass for FFL file delivery (e.g., FlxpointFFL / Flxp3248915@).
  • 3 Scheduling: Set a manual run or an automated schedule (e.g., daily at 6 AM UTC).
  • 4 FFL Handling: If “FFL Required” is on and your PO includes FFL items, upload the PDF and CSV when prompted. The integration will automatically deliver these files to Iron Valley’s SFTP.
  • 5 Save & Test: Click “Test Connection,” then “Save Integration.”

  • The mapping screen is labeled “Iron Valley – Send Fulfillment Requests” in the Mapping Dashboard.
  • Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
  • Sections include:
    • From Value: Flxpoint fields (e.g., Order: ponumber, Order Item: SKU).
    • To Iron Valley Field: Iron Valley fields (e.g., t-inputheaderdata: ponumber, t-inputlinedata: itemnumber).
    • Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.

This section provides key details about the Iron Valley Send Fulfillment Requests integration to help you understand the process:
  • Current Date and Time: As of 09:49 PM -04 on Thursday, May 15, 2025, this integration is fully operational for sending fulfillment requests to Iron Valley.
  • Iron Valley Integration: Sends purchase orders to Iron Valley via API, with FFL attachments delivered via FTP to sftp://ironvalleysupply.goanywhere.cloud/.
  • Dropship vs. Replenishment Orders:
    • Replenishment Orders: Used for stocking your warehouse. Automatically sets shiptonumber = 1 if any line item’s brand is Browning, Glock, FN, IWI US, Outdoor Edge, Ruger, Smith & Wesson, Springfield Armory, Walther, or Winchester.
    • Dropship Orders: Used for shipping directly to consumers. Omits shiptonumber = 1 for other brands. For firearm orders, requires FFL documentation (PDF and CSV) to be uploaded.
  • Special Requirements for Dropship Firearm Orders:
    • FFL Documentation: Attach a clear, current FFL PDF and a CSV with fields (dealer name, license #, expiry date, address, city, state, ZIP) in the specified order.
    • Delivery: Files are automatically pushed to Iron Valley’s SFTP at sftp://ironvalleysupply.goanywhere.cloud/.
    • Warehouse Code: Automatically set to BHM1 for dropship orders.
    • Accessories: Non-firearm dropship orders skip the FFL upload step.
  • Required Fields: ponumber, customerid, shiptonumber, and at least one line item with itemnumber and orderqty.
  • FFL Handling: If FFL Required is enabled, an FFL PDF and CSV must be attached before sending.
  • What Changed: The integration now supports both dropship and replenishment orders without separate manual workflows. Existing replenishment behavior is unchanged, but dropship orders omit shiptonumber = 1. Update any custom logic relying on this field for all orders.
Tip: If a single PO contains a mix of brands, split it into separate POs to ensure each order is properly classified as dropship or replenishment.
Need More Detail? For the full API field list, error handling rules, and sample payloads, see Iron Valley Supply – Order Upload API User Guide, April 2025, p. 26–34 (“Drop Ship Orders”).

Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, as in the dashboard):
Iron Valley – Send Fulfillment Requests Mappings
Field Maps To Example Purpose Status
ponumber (T) t-inputheaderdata: ponumber 4165619-3 Records the purchase order number Required
customerid (T) t-inputheaderdata: customerid 0001000000010100 Identifies the customer (must end with Iron Valley account number) Required
shiptonumber (T) t-inputheaderdata: shiptonumber 66435456 Records the ship-to number (for FFL, map FFL# as first 3 + last 5 digits; set to 1 for replenishment orders) Required
ordertype (T) t-inputheaderdata: ordertype O Specifies the order type Optional
itemnumber (T) t-inputlinedata: itemnumber ABC-1234 Identifies the product SKU in the line item Required
orderqty (N) t-inputlinedata: orderqty 2 Records the quantity ordered for the line item Required
address1 (T) Shipping Address: address1 123 Main St Records the first line of the shipping address Required
city (T) Shipping Address: city Los Angeles Records the city of the shipping address Required
country (T) Shipping Address: country US Records the country of the shipping address Required
zip (T) Shipping Address: zip 90210 Records the postal code of the shipping address Required
name (T) Shipping Address: name John Doe Records the name of the shipping recipient Required
phone (T) Shipping Address: phone 555-123-4567 Records the telephone number for the shipping contact Optional

Available Source Fields
Flxpoint provides fields under categories like:
  • Order: ponumber (T), customerid (T), shiptonumber (T), ordertype (T).
  • Order Item: itemnumber (T), orderqty (N), unitofmeasure (T), warehouseid (T).
  • Shipping Address: address1 (T), city (T), country (T), zip (T), name (T), phone (T).

Mapping Options
You can choose from the following options for each field:
  • Field: Link a Flxpoint field (e.g., SKU) to an Iron Valley field.
  • Value: Choose a fixed value for the field.
  • Mapping Set: Use preset tools to adjust data (e.g., combine fields).
  • Rules: Add "if-then" logic (e.g., only map if quantity > 0).
  • Don’t Map: Ignore the field entirely.
  • Set to Empty: Clear the field in the Iron Valley request, removing existing data.

If the integration encounters an issue, try these steps:
  • Error: “No Order Created|Customer Ship To Record No Longer Available”: Indicates an invalid ship-to number. Update the mapping for shiptonumber or hold and retry.
  • Error: “400 Bad Request: Product Restriction Found: FFL”: Missing FFL PDF or CSV. Attach both files and reprocess the request.
  • Connection Issues: Verify your API and FTP credentials, ensuring the FTP host (ironvalleysupply.goanywhere.cloud) and port (22) are accessible.
  • Mixed Brands in a Single PO: If a PO contains both replenishment and dropship brands, split it into separate POs to ensure correct classification.
  • Custom Logic Issues: If your custom logic relies on shiptonumber = 1 for all orders, update it to account for dropship orders where this field is omitted.

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 Iron Valley Get Shipments Integration
Retrieve shipment tracking details for purchase orders you’ve sent to Iron Valley. This integration allows you to generate an API token, call the tracking endpoint with your order number, and map the response into your Flxpoint system’s shipment fields for seamless tracking updates.

The Iron Valley Get Shipments integration enables you to:
  • Retrieve shipment tracking details for POs sent to Iron Valley via their API.
  • Map tracking data (e.g., carrier, tracking number) to your Flxpoint shipment fields.
  • Automate tracking updates for seamless order fulfillment monitoring.

The integration follows a structured process to retrieve and map shipment data from Iron Valley:
  • Authenticate: POST credentials to the token endpoint to generate an API token.
  • Request Tracking: Send your saved PO confirmation number to the tracking endpoint (.../sxapisfgettrackingnum).
  • Example API Request: Below is an example of the API request sent to Iron Valley to retrieve tracking details: 
    {
  "request": {
    "companyNumber": 1,
    "operatorInit": "FLXP",
    "operatorPassword": "FLXP",
    "orderNumber": 4165619
  }
}
  • Parse & Map: Extract fields like trackerno, shipviaty, etc., from the response and map them to your system.
  • Example API Response: Below is an example of the API response received from Iron Valley, containing tracking details: 
    {
  "response": {
    "t-trackernum": [
      {
        "whse":       "BHM1",
        "orderno":    4165619,
        "trackerno":  "1Z338897A890926553",
        "shipviaty":  "UPSG"
      }
    ]
  }
}
    Array of tracker records; map each to your shipment entity.

Configure the integration to fit your needs:
  • API Credentials: Provide your API username (e.g., "FLXP") and password (e.g., "FLXP") for authentication.
  • Endpoint: Use .../sxapisfgettrackingnum for both production and staging environments.

Follow these steps to set up the Iron Valley Get Shipments integration:
  • 1 Configure API Credentials: Provide your API username (e.g., "FLXP") and password (e.g., "FLXP") to authenticate with Iron Valley’s API.
  • 2 Set Up Endpoint: Use the tracking endpoint .../sxapisfgettrackingnum for both production and staging environments.
  • 3 Create a Mapping Template: Use the Mapping Dashboard ("Iron Valley – Get Shipments") to define how Iron Valley’s response fields map to your shipment fields (details below).
  • 4 Run the Integration: Run manually via the “Run Integration” button or schedule periodic runs (e.g., every 2 hours).

  • The mapping screen is labeled “Iron Valley – Get Shipments” in the Mapping Dashboard.
  • Buttons available: Delete to remove the template, Duplicate to copy it, and Save to save changes.
  • Sections include:
    • From Value: Iron Valley response fields (e.g., t-trackernum: trackerno, shipviaty).
    • To Shipment Field: Flxpoint shipment fields (e.g., Tracking Number, Carrier).
    • Mapping Options: Options like Field, Value, Mapping Set, and Rules for customization.

This section provides key details about the Iron Valley Get Shipments integration to help you understand the process:
  • Current Date and Time: As of 09:43 PM -04 on Thursday, May 15, 2025, this integration is fully operational for retrieving shipment data from Iron Valley.
  • Iron Valley Integration: Retrieves shipment tracking details using the API endpoint .../sxapisfgettrackingnum.
  • Response Structure: The API returns an array of tracker records; map each to your shipment entity.
Tip: Ensure your PO confirmation number is correct to avoid "No Data" responses from the API.

Mapping Fields
Below are the fields you can map, with examples and purposes (labeled as "T" for text, "N" for numbers, as in the dashboard):
Iron Valley – Get Shipments Mappings
Field Maps To Example Purpose Status
shipviaty (T) Shipment: Carrier UPSG Identifies the shipping carrier for the shipment Required
trackerno (T) Shipment: Tracking Number 1Z338897A890926553 Records the tracking number for the shipment Required
whse (T) Shipment: Warehouse BHM1 Records the warehouse from which the shipment originated Optional
orderno (N) Shipment: Order Number 4165619 Associates the shipment with the Flxpoint order Required

Available Source Fields
Iron Valley provides fields from the API response, including:
  • t-trackernum: whse (T), orderno (N), trackerno (T), shipviaty (T).

Mapping Options
You can choose from the following options for each field:
  • Field: Link an Iron Valley response field (e.g., trackerno) to a Flxpoint shipment field.
  • Value: Choose a fixed value for the field.
  • Mapping Set: Use preset tools to adjust data (e.g., combine fields).
  • Rules: Add "if-then" logic (e.g., only map if trackerno is present).
  • Don’t Map: Ignore the field entirely.
  • Set to Empty: Clear the field in the Flxpoint shipment, removing existing data.

You can automate the integration as follows:
  • Run manually via the “Run Integration” button.
  • Schedule periodic runs (e.g., every 2 hours).

If the integration encounters an issue, try these steps:
  • Error: “401 Unauthorized”: Token invalid—regenerate the API token and retry.
  • Error: “No Data”: Order not shipped yet—retry later after confirming with Iron Valley.
  • Mapping Issues: Ensure required fields like shipviaty and trackerno are mapped correctly in the Mapping Dashboard.

Conclusion
With the Iron Valley Get Shipments integration, you can efficiently retrieve and map shipment tracking details into your Flxpoint system. Automated runs and flexible mapping options ensure your order fulfillment tracking is seamless and up-to-date.
 
 

 

 

Related Articles

FragranceNet as Source

FragranceNet Specializes in fragrances, skincare, and beauty products. Flxpoint i...

Essential Pet Products as Source

Essential Pet Products is a distributor of pet supplies, including toys, food, an...

FragranceX as Source

FragranceX is a supplier of discounted fragrances and beauty products. Available ...