U.S. Direct as a Source

July 20, 2026

Summary

U.S. Direct is a supplier source supporting inventory, order, and invoice operations. The connection uses three credentials — an API Token, a Reseller Token (required for Get Invoices), and a Feed URL (request from support@flxpoint.com) — shared across all five operations: Get Inventory (Primary and Secondary), Send Fulfillment Requests, Get Shipments, and Get Invoices. Get Invoices matches by the Flx PO Number stored as the Channel Order Number, using a Source Invoice Mapping Template configured under Settings → Mapping Templates.

What this integration does

Get Inventory (Primary)

Imports U.S. Direct's full catalog, pricing, and quantity daily.

Get Inventory (Secondary)

A lighter, more frequent refresh of pricing and quantity only.

Send Fulfillment Requests

Sends orders (Fulfillment Requests) to U.S. Direct for fulfillment.

Get Shipments

Pulls U.S. Direct shipment tracking and carrier details into Flxpoint.

Get Invoices

Retrieves invoice data using the Reseller Token and Flx PO Number.

How to connect - credentials you need

U.S. Direct connects via API. Add a U.S. Direct source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter your API Token, Reseller Token (if you plan to use Get Invoices), and Feed URL, then Test Connection → Save Connection. The Feed URL is not available in your U.S. Direct account — request it from support@flxpoint.com.

API TokenRequired

Your U.S. Direct API Token, used to authenticate the connection.

Reseller TokenOptional

A separate credential used exclusively by Get Invoices. Required if you plan to use Get Invoices; leave blank otherwise.

Feed URLRequired

The U.S. Direct feed location used for Get Inventory. Not available in your U.S. Direct account — request it from support@flxpoint.com.

Get Invoices requires a Source Invoice Mapping Template under Settings → Mapping Templates, mapping at minimum the Flx PO / Order Number, Invoice Number, and Invoice Total. Get Invoices matches by the Flx PO Number stored as the Channel Order Number — confirm the order exists in Order Manager with that reference before running it.

Important - read before configuring

Reseller Token is required for Get Invoice — it lives on the same connection card

The Reseller Token is a separate credential field on the U.S. Direct connection card, used exclusively by the Get Invoice operation. It does not replace the API Token — both are required when configuring the connection if you plan to use Get Invoice. If the Reseller Token is missing or blank, Get Invoice will fail to retrieve invoice data even when other operations work correctly.

Feed URL is not self-service — request it from Flxpoint Support

The Feed URL used by U.S. Direct is not available in your U.S. Direct account dashboard. You must request it from support@flxpoint.com. Do not attempt to use a generic URL or your U.S. Direct login URL in this field. Without the correct Feed URL, GIP and GIS will fail to retrieve inventory data.

Get Invoice uses the Flx PO Number, not the channel order number

When orders are imported from U.S. Direct into Order Manager, the Flx PO Number is stored as the Channel Order Number. Get Invoice fetches invoice details using this Flx PO / Order Number — not the original channel order reference. Confirm the order exists in Order Manager with the Flx PO Number stored as Channel Order Number before running Get Invoice.

Send FR required fields: PO Number, Ship To Address Line 1, and Item Number

Send Fulfillment Requests to U.S. Direct requires at minimum: Fulfillment Request Number → PO Number, Shipping Address Line 1 → Ship To Address1, and Item SKU → Item Number. Missing any of these will cause the order to fail submission. Run a single manual order first to verify the mapping before enabling automatic order sending.

Operations - fields to know

Get Inventory (Primary)Get Inventory (Secondary)Send Fulfillment RequestsGet ShipmentsGet Invoices

Field mapping for this operation is configured with Flxpoint Support.

Common issues

Connection failing — API Token incorrect or expired

If Test Connection fails, the API Token may be incorrect, expired, or rotated by U.S. Direct. Re-enter the API Token from your U.S. Direct account (check Account Dashboard or API Access section). If credentials worked previously but now fail, contact U.S. Direct at support@gousdirect.com to confirm your account's API access is still active. Credentials that expire silently are a common cause of sudden connection failures on integrations that were previously working.

Get Invoice not pulling — Reseller Token missing or invoice not matching

Two common causes: (1) the Reseller Token is not configured on the U.S. Direct connection card — open the connection and confirm it is populated; (2) the order's Flx PO / Order Number is not stored as the Channel Order Number in Order Manager — Get Invoice fetches by this reference. Verify the order exists in Order Manager with the correct Flx PO Number. Also confirm a Source Invoice Mapping Template is selected under Settings → Mapping Templates with the required fields mapped.

Send FR failing — order not submitting to U.S. Direct

Confirm: (1) the U.S. Direct connection passes Test Connection; (2) all three required fields are mapped and non-empty: Fulfillment Request Number → PO Number, Ship To Address Line 1, and Item SKU → Item Number; (3) check the integration job log for the specific error from U.S. Direct's API. The most common rejection reasons are a missing required address field or an item number that does not match U.S. Direct's catalog. Run a single manual order first before enabling automatic sending.

Inventory not syncing or fields missing from import

If GIP or GIS runs without error but data is missing: (1) check the mapping template for field mismatches — confirm SKU and Quantity are mapped; (2) verify the Feed URL is correct — if you entered a URL yourself instead of requesting it from Flxpoint Support, the URL may be invalid; (3) check whether the sync schedule is configured and active; (4) confirm U.S. Direct's feed is publishing current data by checking the last update time in the feed. If the issue persists after these checks, contact Flxpoint Support with the job log.

FAQs

How do I set up the Source Invoice Mapping Template for Get Invoice?▸

Go to Settings → Mapping Templates and create or select a Source Invoice template. Map at minimum: Flx PO / Order Number → Channel Order Number (identifies which order the invoice belongs to), Invoice Number → Flxpoint Invoice Number, and Invoice Total → Flxpoint Invoice Total. After saving the template, return to the U.S. Direct source → Get Invoice settings and confirm the template is selected. Get Invoice will not link invoice data to orders without this template correctly configured.

What shipping codes does U.S. Direct use in Get Shipments?▸

Get Shipments returns carrier and shipping codes that can be mapped in your template. Example formats: UPS Ground → carrier code UPS-GND; FedEx Express → FEDEX-EXP; USPS Priority → USPS-PRIORITY. Map these in the Get Shipments template using a Mapping Set to standardize carrier names across your Flxpoint account. Also map Tracking Number, Shipment Status, and Shipping Date fields for full shipment visibility.

Does U.S. Direct support all five operations (GIP, GIS, Send FR, Get Shipments, Get Invoice)?▸

Yes. U.S. Direct supports Get Inventory Primary (full catalog + stock sync), Get Inventory Secondary (delta updates), Send Fulfillment Requests (order submission), Get Shipments (tracking retrieval), and Get Invoice (invoice data retrieval using Reseller Token). All operations use the same connection card. Configure them individually based on your business needs — you do not need to enable all five if your workflow only requires some of them.

Back to General Supplier Integrations