In this guide, you'll learn how to set up American Tire Distributors (ATD) as a source in Flxpoint — create the source, connect via your ATD API credentials, and configure inventory, dropship orders, and shipments. Integrating ATD as a source gives you access to a vast inventory of tires and helps you streamline your e-commerce operations.
Add Source and Establish Connection
Choose the right Source Type
For most ATD 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 Fulfillment Requests to ATD so they ship directly to your customers (dropship).
- 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).
Finish the Source Wizard by adding at least one Shipping Method and confirming your Ship From location.
Flxpoint securely authenticates with ATD using your API credentials. One connection covers inventory, dropship orders, and shipments.
Product Operations
Get Inventory (Primary)
American Tire Distributors (ATD) is a wholesale supplier of tires and related products. The Get Inventory (Primary) job imports your ATD catalog into Flxpoint — product data, variations (Size and Side Wall), pricing, quantity, weights and dimensions, images, and categories — and keeps it up to date.
Using this feature with Flxpoint allows you to seamlessly integrate your inventory data, ensuring that you have up-to-date product information. This integration helps streamline operations, reduces manual errors, and ensures that your inventory levels are always accurate. The sections below walk through each step of the setup and configuration process.
Each run follows this workflow:
- 1Select Connection — Choose your ATD connection (uses your ATD API credentials).
- 2Fetch Catalog — Flxpoint retrieves the ATD product feed, including product data, variations, pricing, quantity, weights and dimensions, images, and categories.
- 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.
Choose American Tire Distributors (ATD) and select your existing ATD connection (or create one — see How to Connect → Phase 3). Click Save and Proceed.
- Quantity Type — ATD provides three quantity options: Localplus, Nationwide, and Onhand. Quantity will be saved as selected in your mapping template.
- Archive / Un-Archive Inventory — When enabled, items absent from the latest feed are archived and re-activated automatically if they return. Enable in either Primary or Secondary — not both.
Click Save and Proceed.
Choose a mapping template (or build your own). Confirm your quantity type and category mapping, then click Save and Complete.
Run manually first to verify the import, then enable a schedule — daily is a good default for Primary (jobs run in UTC). The status page will show Connected, Configured, and Mapped with your template once complete.
- Custom Fields: Additional tire information is saved in variant custom fields. Up to 100 custom fields, 10 summary fields.
- Variations / Options: We use Size and Side Wall to create options.
- Generic Pricing (& Currency).
- Quantity: Three types of quantity option — Localplus, Nationwide, Onhand. Quantity will be saved as selected in the mapping template.
- Weights & Dimensions (& Units): Weight is available in pounds and dimensions are available in inches.
- Images: Available.
- Categories: Single-level category is available in the feed.
- Archive Support.
- Delta Feed vs Full Feed: This is the full product feed.
- Client Pricing (& Currency).
- Multiple Warehouses: We support a single warehouse per integration. To use more than one warehouse, create a separate integration for each warehouse.
A Catalog Type setting lets you choose where product data is retrieved from. By default, products are retrieved from the Ship To Store (STS) catalog. You can switch this to Ship To Home (STH) to retrieve products from the Ship To Home catalog instead.
This is useful when some items (for example, oversized tires) are not eligible for Ship To Home delivery, so you can select the catalog that matches how you intend to fulfill those products.
- 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.
- ATD connection is selected and the API credentials pass Test Connection.
- Quantity Type (Localplus, Nationwide, or Onhand) is selected in the mapping template.
- Catalog Type (Ship To Store or Ship To Home) is set to match how you intend to fulfill these products.
- Archive / Un-Archive is enabled in either Primary or Secondary — not both.
- Run once manually first, then enable a daily schedule once verified.
- Catalog not importing: Open the ATD connection and click Test Connection. If it fails, re-enter your ATD API credentials and retry.
- Unexpected or missing items: Confirm your Catalog Type is set correctly. Some items (e.g., oversized tires) are not eligible for Ship To Home, so they may not appear when the Ship To Home catalog is selected.
- Specifications look different after switching catalogs: Product specification details can differ between Ship To Store and Ship To Home. Review your variant specification and custom-field mappings.
| Feature | Availability | What to Expect |
|---|---|---|
| Custom Fields | Supported | Additional tire information saved in variant custom fields. |
| Variations / Options | Supported | Size and Side Wall are used to create options. |
| Quantity | Supported | Localplus, Nationwide, or Onhand — saved as selected in mapping. |
| Pricing | Supported | Generic Pricing (& Currency). Client Pricing is not supported. |
| Weights & Dimensions | Supported | Weight in pounds, dimensions in inches. |
| Images | Supported | Available. |
| Categories | Supported | Single-level category available in the feed. |
| Catalog Type | Supported | Ship To Store (default) or Ship To Home product retrieval. |
| Multiple Warehouses | Not Supported | Single warehouse per integration; create one integration per warehouse. |
Get Inventory (Secondary)
The Get Inventory (Secondary) operation is designed to provide more frequent updates to your product inventory, ensuring that your stock levels and pricing are as current as possible without running the full data import process.
Run it on a more frequent schedule (e.g., hourly) alongside Get Inventory (Primary) so quantity and pricing stay fresh between full feed runs.
Set up follows the same pattern as Primary:
- 1Connect an Integration — Select your ATD connection.
- 2Configure Settings — Choose the Quantity Type (Localplus, Nationwide, or Onhand) and enable Archive here only if it is not already enabled in Primary.
- 3Define a Mapping Template — Map quantity and pricing fields, then Save and Complete.
- 4Save & Schedule — Run on a frequent schedule to keep stock and pricing current.
- Generic Pricing (& Currency).
- Quantity: Three types of quantity option — Localplus, Nationwide, Onhand. Quantity will be saved as selected in the mapping template.
- Delta Feed vs Full Feed: Only quantity and pricing are available.
- Archive Support.
- Custom Fields (Variants Only).
- Client Pricing (& Currency).
- Multiple Warehouses: We support a single warehouse per integration. To use more than one warehouse, create a separate integration for each warehouse.
- Weights & Dimensions (& Units).
- ATD connection passes Test Connection.
- Quantity and pricing fields are mapped.
- Archive is enabled in either Primary or Secondary — not both.
- Quantities not updating: Confirm the correct Quantity Type is selected and that the secondary job is scheduled frequently.
- Pricing out of date: Verify the pricing field is mapped in the secondary template.
- Items disappearing unexpectedly: Check that Archive is not enabled in both Primary and Secondary at the same time.
Order Operations
Send Fulfillment Requests
Send Fulfillment Requests submits orders to ATD for fulfillment so they can ship directly to your customers (dropship). An order is created with ATD through your configured connection, and the integration tracks the response so you know it was accepted.
The sections below walk through the workflow, the supported order details, and common issues.
The operation works as follows:
- 1Connect an Integration — Select your ATD connection.
- 2Map Order Fields — Map the fulfillment request fields (see Mapping & Configuration).
- 3Submit & Acknowledge — Flxpoint sends the Fulfillment Request Number with the order; ATD returns an order ID on successful processing (auto-acknowledgement).
- Fulfillment Request Number: The Flxpoint FR# is sent in the order.
- FR Item Association: The Item ID received during Get Inventory (Primary) is sent. If the Item ID is blank in source inventory, FR processing will fail.
- Auto Acknowledgements: We receive an order ID in the response for successful order processing.
- Shipping Selection: The shipping method is selected per the logic mentioned in the operational flow.
- Customer Association.
- Custom Fields.
- Attachments.
- The ATD connection passes Test Connection.
- Your Sandbox test order was confirmed by ATD before going live.
- Item ID is present in source inventory for every line item.
- FR processing fails: Confirm the Item ID is not blank in source inventory — a missing Item ID will cause the request to fail.
- Live orders not accepted: Make sure you completed the Sandbox test order and that ATD confirmed it before you switched to Production.
- No acknowledgement returned: A successful order returns an order ID. If none is returned, check the job log for the ATD response and retry.
Get Shipments
The Get Shipments operation allows you to retrieve shipment tracking details and updates for your orders, ensuring that accurate delivery information is always available.
It imports shipment details after orders are submitted, giving you a seamless link between order processing and shipment tracking.
The operation works as follows:
- 1Connect an Integration — Select your ATD connection.
- 2Map Shipment Fields — Map shipping method and SKU (see Mapping & Configuration).
- 3Schedule — Run on a regular schedule so tracking flows back to your orders as ATD ships them.
- Carrier & Methods: Only the shipping method is available in the response.
- Shipment Item Association: SKU is available in the response.
- Partial Shipments.
- Invoice Information.
- Custom Fields (CFs).
- The ATD connection passes Test Connection.
- Shipping method and SKU are mapped in the template.
- The operation has an active schedule.
- No tracking yet: The order may not have shipped on ATD's side. Tracking appears once ATD reports a shipment.
- Carrier missing: Only the shipping method is returned; confirm the shipping method field is mapped.
- Partial orders: Expect more than one shipment per order when ATD ships items separately.
Troubleshooting
Common issues and solutions for the American Tire Distributors (ATD) integration. Expand each item to learn more.
What's happening
The ATD connection is not authenticating or Test Connection returns an error.
- The API credentials may be incorrect or expired.
- You may still be in Sandbox mode and haven't completed the test-order confirmation needed to switch to Production.
How to fix it
- Open the ATD connection and click Test Connection. If it fails, re-enter your ATD API credentials and retry.
- For new setups, place a test order in Sandbox, then contact ATD to confirm it before switching to Production.
What's happening
Get Inventory (Primary or Secondary) is not importing data, or quantities don't match what you expect.
- The ATD connection may not be passing Test Connection.
- The wrong Quantity Type (Localplus, Nationwide, or Onhand) may be selected.
- Archive may be enabled in both Primary and Secondary at the same time.
How to fix it
- Confirm the ATD connection passes Test Connection and that the correct mapping template is selected.
- Select the Quantity Type that matches your fulfillment model. Quantity is saved as selected in the mapping template.
- Make sure Archive is enabled in either Primary or Secondary, not both. Conflicting archive settings can cause items to disappear.
What's happening
After choosing or switching the Catalog Type, some items are missing or product specifications look different from what you saw before.
- Some items (for example, oversized tires) are not eligible for Ship To Home delivery, so they may not appear when the Ship To Home (STH) catalog is selected.
- Product specification details can differ between the Ship To Store (STS) and Ship To Home (STH) catalogs.
How to fix it
- Confirm Catalog Type is set to match how you intend to fulfill these products — Ship To Store (default) or Ship To Home.
- Remember that brand and style data still comes from the standard (Ship To Store) catalog, while product data can come from the Ship To Home catalog when that Catalog Type is selected.
- If specifications populate differently after switching, review your variant specification and custom-field mappings so the values come through as expected.
What's happening
Send Fulfillment Requests fails to submit a dropship order to ATD.
- The Item ID received during Get Inventory (Primary) is blank in source inventory — FR processing will fail without it.
- You may not have completed the Sandbox test order that ATD requires before live orders are allowed in Production.
How to fix it
- Confirm your Get Inventory (Primary) import is complete so every line item carries a valid Item ID.
- Make sure you placed a Sandbox test order and that ATD confirmed it before you switched to Production mode.
- A successful order returns an order ID (auto-acknowledgement). If none is returned, check the job log and retry.
What's happening
Recent orders show no tracking updates, or the shipping method / SKU is missing.
- The order may not have shipped yet on ATD's side.
- The shipping method or SKU may not be mapped in the template.
- The Get Shipments operation may not have an active schedule.
How to fix it
- Confirm shipping method and SKU are mapped — only the shipping method and SKU are available in ATD's shipment response.
- Confirm Get Shipments has an active schedule so tracking flows back as ATD ships orders.
- Expect partial shipments — a single order may return more than one shipment over time.
Still need help? If you're experiencing issues not covered here, contact ATD or your Flxpoint account manager.
Contact Support