US AutoForce is an automotive part and tire distributor, providing a wide range of products to retailers and service shops across the United States. Connecting your US AutoForce account in Flxpoint allows you to import product data, manage inventory, and route orders directly through your existing workflows. This guide will walk you through the setup process, ensuring your integration is properly configured for smooth operations.
📋 Phase 1: Create Source & Open the Wizard
+
Open Fulfillment Sources
Go to Connections > Fulfillment Sources and click + Add Source.
Name the Source
Set the name to US AutoForce, choose the source type, then click Save.
Launch Integrations
Open the source, select Integrations, and click Get Started to begin setup.
🔌 Phase 2: Supplier Directory & Master SKU
+
Select US AutoForce
Choose FLX Supplier Directory, search US AutoForce, click Select, then continue.
Set Master SKU
Pick the field to serve as your Master SKU. Recommended:
- Field: Inventory SKU → becomes Master SKU → maps to Listing SKU on channels.
- Optionally enable Set a SKU prefix to avoid cross-supplier collisions.
⚙️ Phase 3: Configure Pricing/Quantity, Send Orders & Get Shipments
+
Pricing & Quantity (Warehouses)
Keep Automatically Pricing & Quantity enabled. Choose All Warehouse or select specific branches (e.g., Appleton, West Allis, Madison, Kansas City, Omaha, etc.).
Available Quantity is the sum across the branches you select.
Tip: Limiting to nearby branches often reduces split shipments and transit time.
Send Orders (separate connection required)
Create the Send Orders connection and complete:
- UserName — provided by US AutoForce
- Password — provided by US AutoForce
- Environment — Sandbox (test) or Production (live)
- Revision — API/service version (e.g., 1.0)
- Account Number — your US AutoForce account
- Transaction Id — unique request identifier
- Branch — branch to fulfill the order (if required)
Advanced: Leave Disable Branch Sending off unless US AutoForce instructs otherwise.
Get Shipments (can reuse credentials)
Create the Get Shipments connection. You can check Use same connection as Send Orders to reuse credentials or create a separate one.
Adjust FR Lookback Period (default 3 Months) if you need a longer retrieval window for shipment updates.
Finalize & Verify
Test each connection and save. Click Continue / Save and Complete. Then:
- Run an inventory task to confirm quantities populate for the selected branches.
- Place a small test order (Sandbox if available) and verify shipment updates flow back.
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 and Pricing & Quantity
Supported | US AutoForce — Get Inventory and Pricing & Quantity
Overview
One integration that pulls recent CSVs from the US AutoForce FTP to build products and keep pricing + quantity fresh. Quantities are summed across the branches you select.
Files & default lookbacks
-
Products:
USAutoForceProduct_*.csv— last 14 days. -
Inventory:
USAutoForceInventory_*.csv— per-part quantities. -
Pricing:
Baseline_PricingData_*— most recent in last 7 days.
Not included in feed: categories, images, weights/dimensions, variations/options.
- Authentication: none required (per UI banner).
- Master SKU: Inventory SKU → Master SKU → Listing SKU (prefix optional). Changes apply after the next run; existing links remain.
- Pricing & Quantity: toggle Automatically Pricing & Quantity ON and pick All Warehouse or specific branches (sum of selected).
- Advanced: “Allow Create Variant” typically OFF here.
- 1 Open the US AutoForce source → Get Inventory and Pricing & Quantity.
- 2 Confirm Authentication shows “doesn’t require any authentication details”.
- 3 Set Master SKU as above.
- 4 Under Pricing & Quantity, enable automatic updates and choose branches (Appleton, West Allis, Madison, Kansas City, Omaha, etc.).
- 5 Open Mapping Template and map fields (complete list below). Save.
- 6 Click Run. Verify products, costs/MAP/MSRP, and summed quantities.
- 7 Schedule: Inventory daily; Pricing & Quantity hourly (business hours).
| Capability | Status | Notes |
|---|---|---|
| Client Pricing (& Currency) | Supported | From latest Baseline_PricingData_*
|
| Quantity | Supported | Single value; sum of selected branches |
| Multiple Warehouses | Not Supported | No per-warehouse codes in feed; totals only |
| Generic Pricing | Not Supported | Client-specific pricing only |
| Custom Fields / Variations | Not Supported | Variants/options not exposed |
| Weights & Dimensions | Not Supported | Absent from feed |
| Images / Categories | Not Supported | Absent from feed |
| Delta vs Full | Limited/Delta | Products limited; pricing/qty supports delta |
| Archive Support | Supported | Archived FTP files processed |
A) Product & Identifier Fields (from
USAutoForceProduct_*.csv)| US AutoForce Field (Dropdown) | Maps To | Purpose / Notes | Req? |
|---|---|---|---|
| Part Number | Inventory Variant: SKU | Primary identifier used for all updates/links | Required |
| Total Available Quantity | Inventory Variant: Quantity | Total units; summed across selected branches in UI | Enabled |
| Cost | Inventory Variant: Cost | Base cost used in pricing rules | Optional |
| Wholesale Cost | Inventory Variant: Cost (alt) | Some accounts expose Wholesale Cost; map if preferred | Optional |
| Map | Inventory Variant: MAP Price | Minimum advertised price | Optional |
| Retail Price | Inventory Variant: MSRP | General suggested retail price | Optional |
| GM Retail Price | Inventory Variant: MSRP (brand-specific) | Use when GM MSRP is needed | Optional |
| Toyota Retail Price | Inventory Variant: MSRP (brand-specific) | Use when Toyota MSRP is needed | Optional |
| Ford Retail Price | Inventory Variant: MSRP (brand-specific) | Use when Ford MSRP is needed | Optional |
Tip: If you only want one reference price, map Retail Price → MSRP. If your catalog needs automaker-specific MSRP, map the GM/Toyota/Ford rows to a custom field (if available) or choose one as MSRP and keep the others unmapped.
B) Pricing & Quantity Fields (from
USAutoForceInventory_*.csv + Baseline_PricingData_*)| US AutoForce Field | Maps To | Purpose / Notes | Req? |
|---|---|---|---|
| Part Number | Inventory Variant: SKU | Key to link price/qty to the right variant | Required |
| Total Available Quantity | Inventory Variant: Quantity | Summed total available (branches you selected) | Enabled |
| Cost | Inventory Variant: Cost | Base cost from latest pricing file | Optional |
| Wholesale Cost | Inventory Variant: Cost (alt) | Map if your pricing uses wholesale cost | Optional |
| Map | Inventory Variant: MAP Price | MAP from pricing file | Optional |
| Retail Price | Inventory Variant: MSRP | Reference MSRP | Optional |
| GM Retail Price | Inventory Variant: MSRP (brand-specific) | Optional brand MSRP | Optional |
| Toyota Retail Price | Inventory Variant: MSRP (brand-specific) | Optional brand MSRP | Optional |
| Ford Retail Price | Inventory Variant: MSRP (brand-specific) | Optional brand MSRP | Optional |
Remember: Categories, images, weights/dimensions aren’t provided in this integration, so those fields won’t appear in the US AutoForce mapping dropdowns.
- No product updates: Ensure a mapping template is saved and SKU ← Part Number is mapped (required).
- Quantity seems off: Check which branches are selected—quantity = sum of those branches.
-
Pricing empty: Verify a recent
Baseline_PricingData_*exists (≤7 days) on FTP and rerun.
Finalize
After verifying a first run, schedule: Inventory daily; Pricing & Quantity hourly during business hours.
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 Orders
Supported | US AutoForce — Send Orders
Overview
Sends Fulfillment Requests (purchase orders) to the US AutoForce Order endpoint. Requires a
warehouse (branch) number to fulfill the order
US AutoForce Warehouses.xlsx.
Response returns an
orderNumber, which Flxpoint stores as the confirmation number.
- We create an order request on the US AutoForce Order endpoint.
- Branch (warehouse) number must be supplied (see spreadsheet above).
- On success, supplier returns
orderNumber→ saved as the order confirmation in DB. - Validation: State must be a 2-letter abbreviation; ZIP must be a valid postal code.
Advanced Option — Disable Branch Sending: When enabled, branch is sent as null (warehouse optional).
Important: Merchant must contact US AutoForce to enable this behavior on their account before using it.
Separate connection required (cannot reuse Inventory/Shipments)
- UserName (required)
- Password (required)
- Environment — Sandbox / Production
- Revision — API revision (e.g., 1.0)
- Account Number — your US AutoForce account
- Transaction Id — unique request identifier
- Branch — warehouse number to fulfill from (lookup here)
Shipping Selection: Supported — the source shipping method code is sent (e.g.,
USAF-TRK, Pick-Up, FedEx-Grou).
Billing Address
| Flxpoint Field | US AutoForce Field | Notes |
|---|---|---|
| Address Line 1 | Billing Address : Address1 | |
| Address Line 2 | Billing Address : Address2 | |
| City | Billing Address : City | |
| Country | Billing Address : Country | |
| Full Name | Billing Address : Customer Name | |
| Postal Code | Billing Address : Zip | ZIP must be valid |
| State Code | Billing Address : State | Use 2-letter state abbreviation |
| Bill To Code (Account #) | Billing Address : Bill To Code | USAF account number |
Purchase Order (Header)
| Flxpoint Field | US AutoForce Field | Notes |
|---|---|---|
| Fill Flag | Purchase Order : Fill Flag | Values: Backord / Ship complete / Cancelline / Cancel Order |
| Delivery Method | Purchase Order : Delivery Method | Maps to carrier code (see Shipping Selection) |
| Order Reference | Purchase Order : Order Reference | |
| PO Number | Purchase Order : PO Number | |
| Ship Label | Purchase Order : Ship Label | Optional |
Purchase Order Item (Lines)
| Flxpoint Field | US AutoForce Field | Notes |
|---|---|---|
| SKU | Purchase Order Item : Part Number | Required; FR Item Association = Supported |
| Quantity | Purchase Order Item : Quantity Requested | |
| Cost | Purchase Order Item : Cost | |
| List | Purchase Order Item : List | Optional MSRP/list |
| Bin Location | Purchase Order Item : Line Code | Deprecated in mapping — now handled in backend via Variant Reference Identifier (see Release Note below). |
Shipping Address
| Flxpoint Field | US AutoForce Field | Notes |
|---|---|---|
| Address Line 1 | Shipping Address : Address1 | |
| Address Line 2 | Shipping Address : Address2 | |
| City | Shipping Address : City | |
| Country | Shipping Address : Country | |
| Full Name | Shipping Address : Customer Name | |
| Postal Code | Shipping Address : Zip | ZIP must be valid |
| State Code | Shipping Address : State | 2-letter state abbreviation |
| Bill To Code (Account #) | Shipping Address : Bill To Code | USAF account number |
Comment
| Flxpoint Field | US AutoForce Field | Notes |
|---|---|---|
| Note | Comment : Text | Custom fields can be sent as comments |
| Type | Comment : Type |
Release Notes: Line Code was removed from the mapping template and is now handled in code.
GIS saves the line code as the Variant Reference Identifier in Flxpoint and sends it with the PO automatically.
| Capability | Status | Notes |
|---|---|---|
| Fulfillment Request Number | Supported | Mappable via template |
| Customer Association | Not Supported | |
| FR Item Association | Supported | SKU is sent on order |
| Auto Acknowledgements | Supported |
orderNumber returned on success |
| Shipping Selection | Supported | Uses source shipping method code (e.g., USAF-TRK, Pick-Up, FedEx-Grou) |
| Custom Fields | Supported | Can be sent as Comments |
| Attachments | Not Supported | |
| Limitations | — | State must be 2-letter; ZIP must be valid |
- 401/403: Recheck Username/Password, Environment, Revision, Account Number.
- Branch errors: Confirm Branch number from the spreadsheet and that your account allows that branch. If using “Disable Branch Sending”, verify USAF enabled it for your account.
- Validation failures: Ensure 2-letter state (e.g., FL) and valid ZIP (5 or ZIP+4).
-
No confirmation saved: Inspect logs; successful responses include
orderNumber. - Shipping method rejected: Verify your policy maps to a valid USAF method code.
Go to ⋯ → View Logs on the integration card to see the exact request/response for each PO.
Ready to send
After configuring and mapping, run Send Orders from the integration menu or schedule it. Keep the warehouses sheet handy for Branch numbers.
Get Shipments
Supported | US AutoForce — Get Shipments
Overview
Retrieves tracking for orders previously sent to US AutoForce. Uses the
orderNumber saved during Send Orders to query shipment status.
- Calls OrderStatusDetail endpoint to fetch tracking.
- Looks up the orderNumber that was stored as the PO confirmation during Send Orders.
- If the response indicates success, a Shipment is saved in Flxpoint.
- Tracking is order-level (not per line). Only shipping method is returned for carrier/method.
Connection: Requires its own connection for “Get Shipments,” but you can select Use same connection as Send Orders if the credentials are identical.
Lookback: FR Lookback Period defaults to 3 months (90 days); adjust in Advanced Settings.
- Separate Connection Required (as indicated in UI). Optionally check Use same connection as Send Orders.
- Advanced: FR Lookback Period for eligibility (default 3 months).
Shipment (Order-level)
| US AutoForce Field | Maps To | Notes |
|---|---|---|
| Tracking Number | Shipment : Tracking Number | |
| Ship Method | Shipment : Carrier | Carrier derived from method text |
| Ship Method | Shipment : Method | Only the shipping method is available |
| PO Number | Shipment : Fulfillment Request Number | Matches the PO |
| Order Date | Shipment : Shipped At | |
| Comment | Shipment : Note |
Shipment Item (Line-level)
| US AutoForce Field | Maps To | Notes |
|---|---|---|
| Part Number | Shipment Item : Sku | Shipment Item Association: Supported (by SKU) |
| Quantity Shipped | Shipment Item : Quantity | |
| UPC | Shipment Item : Upc | Optional |
| Description | Shipment Item : Description | Optional |
| List Price | Shipment Item : List Price | Optional |
| Cost | Shipment Item : Cost | Optional |
| Retail Price | Shipment Item : Retail Price | Optional |
Note: Tracking is returned at order level; item fields (e.g., Quantity Shipped, SKU) are associated for reference and reconciliation.
| Capability | Status | Notes |
|---|---|---|
| Carrier & Methods | Supported | Only shipping method available in response |
| Shipment Item Association | Supported | By SKU |
| Partial Shipments | Not Supported | |
| Invoice Information | Not Supported | |
| Custom Fields (CFs) | Not Supported | |
| Limitation | — | Tracking available only at order level |
-
No shipments found: Confirm the PO has a saved
orderNumber(created by Send Orders). - Auth/connection errors: Verify the Get Shipments connection or select “Use same connection as Send Orders.”
- Old POs not returning: Increase the FR Lookback Period (Advanced Settings).
- Carrier blank: Only method is returned; ensure your display derives carrier from method where needed.
Use the integration menu ⋯ → View Logs to inspect the OrderStatusDetail request/response per PO.
Done
Enable Automatically Get Shipments, set the lookback window, and (optionally) reuse your Send Orders connection. You’re set to pull tracking from US AutoForce.