American Tire Distributors as a Source
July 2, 2026
Summary
American Tire Distributors (ATD) is a wholesale supplier of tires and related products. Flxpoint connects to ATD over their API using credentials ATD provides, and one connection covers full catalog import, frequent quantity/price refreshes, dropship order submission, and shipment tracking. ATD requires a successful Sandbox test order — confirmed by ATD — before live orders are allowed in Production.
What this integration does
Get Inventory (Primary)
Imports the full ATD catalog – product data, Size and Side Wall variations, pricing, quantity, weights, dimensions, images and categories
Get Inventory (Secondary)
Lightweight refresh that updates quantity and pricing only, on a more frequent schedule between full feed runs
Send Fulfillment Requests
Submits dropship orders to ATD so ATD ships directly to your customer
Get Shipments
Pulls shipment tracking (shipping method and SKU) back into Flxpoint as ATD ships orders
How to connect - credentials you need
Complete the Source Wizard first (set Source Type to Vendor Warehouse), then open Integrations → Get Inventory [Primary], click Start Creating Integrations, choose American Tire Distributors (ATD) and enter the Location Number ATD provided. One connection covers inventory, orders and shipments.
Location NumberRequired
Your ATD dealer location number. This is how ATD identifies the dealer on record for order placement, and it authenticates the connection.
Provided by ATD.
Environment (Sandbox / Production)Setting
Start in Sandbox to place a required test order. Switch to Production only after ATD confirms your Sandbox test.
ATD refuses live orders until the Sandbox test is confirmed.
Test Connection failing? Re-enter your ATD Location Number exactly as provided. For new accounts, live traffic is refused until you place a Sandbox test order and ATD confirms it — that is an ATD requirement and cannot be bypassed in Flxpoint. If a Location Number that used to work starts failing, contact ATD to verify it is still active on your dealer account.
Important - read before configuring
Set Source Type to Vendor Warehouse — not Product Data Source
When adding ATD, choose Vendor Warehouse as the Source Type. This enables Send Fulfillment Requests and order routing to ATD. Product Data Source disables all order operations and is for content enrichment only — most "can't send orders to ATD" issues trace back to the wrong Source Type at creation.
ATD requires a confirmed Sandbox test order before live orders
New accounts must place a test order in ATD's Sandbox environment and contact ATD to confirm it before switching to Production. Until ATD confirms, Production will not accept orders regardless of Flxpoint configuration. This is required once per account.
Archive / Un-Archive can only be enabled on one inventory job at a time
Flxpoint already prevents Archive / Un-Archive from being enabled on both Get Inventory Primary and Secondary at the same time — turning it on for both is blocked, even if you try. Enable it on whichever job you want to own archival, typically Primary.
A blank Item ID from Get Inventory (Primary) will fail the order
Send Fulfillment Requests uses the Item ID captured during catalog import to identify each line item. If a product's Item ID is blank in source inventory — because Primary hasn't run, didn't map the field, or the item was added manually — the fulfillment request fails. Confirm a full Get Inventory (Primary) run completed for every product you intend to order.
Mapping - fields to know
| Setting / Feature | Notes |
|---|---|
| Quantity | Choose Localplus (local DC plus nearby network), Nationwide (all ATD DCs), or Onhand (your designated location). Saved as selected in the mapping template — use the same type in Primary and Secondary. |
| Catalog Type | Ship To Store (STS) is the default; switch to Ship To Home (STH) to fulfill via home delivery. Some items (e.g. oversized tires) aren't STH-eligible and won't appear in that catalog. Brand and style data always comes from the STS catalog; only product-level data follows the Catalog Type. |
| All Options | Size and Side Wall variant attributes are handled via Direct Copy — no manual option mapping is needed. |
| Parent All Custom Fields | Additional tire information is stored in parent-level custom fields via Direct Copy — up to 100 custom fields and 10 summary fields. There is no variant-level custom fields mapping for ATD. |
| Pricing | Generic Pricing (and currency) is supported. Client Pricing is not supported — all accounts get the same feed prices. |
| Weights & Dimensions | Weight is provided in pounds; dimensions in inches. |
| Images & Categories | Images are available. A single-level category is available in the feed. |
| Archive / Multiple Warehouses | Archive / Un-Archive is supported — enable on Primary or Secondary, not both. Only one warehouse per integration; create a separate integration for each additional ATD warehouse. |
A lightweight refresh that updates quantity and pricing only — it does not re-import product data, images, categories, weights/dimensions or custom fields (those come from Primary). Use the same Quantity Type as Primary for consistency. Run Primary daily (full feed) and Secondary hourly to keep stock and pricing fresh between full runs. Enable Archive here only if it is not already enabled in Primary.
This is Flxpoint's Send Fulfillment Requests operation — it submits dropship orders to ATD. The Flxpoint FR# is sent with the order, the Item ID captured during Get Inventory (Primary) identifies each line item, and ATD returns an order ID as an auto-acknowledgement of a successful order. The shipping method is selected per your routing logic. A blank Item ID fails the request, and ATD requires a confirmed Sandbox test order before live orders are accepted. Customer association, custom fields, and attachments are not supported.
Pulls tracking for orders ATD has shipped. Only Shipping Method and SKU are available in the response — carrier name and invoice information are not returned, so map only those two fields. Partial shipments are supported, so a single order can return more than one shipment record over time. Run on a regular schedule so tracking flows back to your orders automatically.
Common issues
Source set up as Product Data Source — cannot send orders to ATD
If Send Fulfillment Requests is unavailable or orders won't route to ATD, check the Source Type. If it is Product Data Source, that disables order operations — create a new ATD source with Vendor Warehouse selected, then delete the old source once the new one is configured and tested.
Connection failing or Test Connection returning an error
Usually an incorrect or inactive Location Number, or a new account still in Sandbox that hasn't completed ATD's test-order confirmation. Open the connection, click Test Connection, and re-enter your ATD Location Number exactly as provided. For new accounts, confirm you placed a Sandbox test order and that ATD confirmed it before switching to Production. If a previously-working Location Number fails, contact ATD to verify it is still active.
Send Fulfillment Request failing — Item ID is blank in source inventory
ATD requires the Item ID (received during Get Inventory Primary) on every line item. A blank Item ID fails the request immediately — this happens when Primary hasn't run, the Item ID field wasn't mapped in the GIP template, or the item was added manually. Confirm the GIP template maps Item ID and that a full Primary run completed, then retry the order.
Catalog not importing or items missing after Get Inventory (Primary)
First confirm the connection passes Test Connection. Then check Catalog Type — if it is Ship To Home and oversized tires or other large items are missing, those aren't STH-eligible; switch to Ship To Store (the default). Also confirm a Quantity Type is selected in the mapping template, or quantities may not populate even when the rest of the catalog imports.
Products unexpectedly disappearing or dropping to zero quantity
Almost always caused by Archive / Un-Archive being enabled in both Primary and Secondary — one job archives what the other restores. Enable Archive in only one operation (typically Primary) and disable it in the other. If items disappeared recently, re-run Get Inventory (Primary) with Archive enabled to restore them.
Get Shipments not returning tracking or shipping method missing
First confirm the order has actually shipped on ATD's side — tracking only appears once ATD reports a shipment. If it has shipped, verify Shipping Method and SKU are both mapped (the only two fields ATD returns) and that Get Shipments has an active schedule. For orders that ship in multiple packages, expect more than one shipment record per order.
FAQs
What Source Type should I select when adding ATD in Flxpoint?▸
Select Vendor Warehouse. It is the correct type for ATD dropship setups — it enables Send Fulfillment Requests and makes ATD eligible for order routing. Do not select Product Data Source, which disables order operations and is only for content-only integrations. If you set ATD up as a Product Data Source by mistake, create a new ATD source with the correct type.
What are the three Quantity Types and which should I use?▸
ATD provides three quantity options in their feed; you pick one in your mapping template and that value drives your inventory levels. Localplus = quantity at or near your local ATD distribution center plus nearby network locations. Nationwide = total quantity across all ATD distribution centers. Onhand = quantity physically on hand at your designated ATD location. Use the same Quantity Type in both Get Inventory Primary and Secondary so they stay consistent.
What is the Catalog Type setting and when should I change it?▸
Catalog Type controls which ATD catalog Get Inventory Primary pulls product data from. The default is Ship To Store (STS); switch to Ship To Home (STH) if you fulfill via home delivery. Some items — such as oversized tires — aren't STH-eligible and won't appear in the STH catalog. Brand and style data always comes from the standard STS catalog regardless of Catalog Type; only product-level data changes. After switching, review your variant specifications and custom-field mappings, since spec details can differ between the two catalogs.
What does Get Inventory Secondary update — and how often should I run it?▸
Secondary is a lightweight refresh that updates quantity and pricing only. It does not re-import full product data, images, categories, or custom fields — those come only through Get Inventory Primary. Run Primary daily for the full catalog and Secondary hourly to keep stock and pricing current between full runs. Use the same Quantity Type in both for consistency.
Can I use more than one ATD warehouse in a single source integration?▸
No. ATD supports a single warehouse per integration. To manage inventory from multiple ATD warehouses, create a separate Get Inventory integration for each warehouse within the same ATD source — each can have its own warehouse configuration and schedule.
What shipment data does Get Shipments return from ATD?▸
ATD's shipment response includes the shipping method and SKU — the only fields available for mapping in the Get Shipments template. Carrier name and invoice information are not included. Partial shipments are supported, so a single order can return more than one shipment event over time. Schedule Get Shipments to run regularly so tracking updates flow back as ATD ships.
Does ATD support client-specific pricing?▸
No. ATD's integration only supports generic pricing. Client Pricing is not available in either Get Inventory Primary or Secondary — all accounts receive the same price values from the ATD feed.