TD Synnex US/CA as a Source
Summary
TD Synnex is one of the largest IT distributors in the world, offering hardware, software, cloud solutions, and cybersecurity products. Two connection types are available: FTP (Basic Auth) for file-based feeds, and TDSynnex API Token (Customer Number + Environment + User Name + Password) for direct pricing and quantity access. One connection powers all five operations — Get Inventory (Primary), Get Inventory (Secondary), Send Fulfillment Requests, Get Shipments, and Get Invoices. The standard quantity FTP feed is quantity-only — costs require a separate customer-specific pricing FTP or API credentials. Run GIP daily and GIS hourly. TD Synnex selects the shipping carrier; do not map a shipping method unless your TD Synnex rep confirms it. Bundle SKUs have special handling for tracking — see Important Notes below.
TD Synnex supports two connection types. Use the one your TD Synnex representative provisioned for your account. Add a TD Synnex source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test Connection → Save Connection.
support@flxpoint.com.Costs empty? The quantity-only FTP feed doesn't include pricing — request pricing FTP or use API
TD Synnex often provides two separate data sources. The standard quantity FTP (quantity-only) does not include cost or MSRP. To import pricing: (1) request a customer-specific pricing FTP from TD Synnex (filename varies per customer) — map column CI → Cost and column AF → MSRP; or (2) use the TDSynnex API Token connection (Customer Number, Environment, User ID, Password) which returns both price and quantity directly. Without one of these, Cost and MSRP will import as empty.
Send FR requires ShipNode.ShipNode as exactly two digits — no DC prefix
Send FR uploads XML to TD Synnex. ShipNode.ShipNode is mandatory and must be exactly two digits (e.g., 01, 31). Do not prefix with DC — DC 01 is invalid and will be rejected. This applies even when using Source Complete "C." Also required: Ship To Account in settings or mapped in the template — if neither provides a value, the Send FR job fails.
Bundle SKUs: tracking comes from component lines — bundle header line never has tracking
When TD Synnex ships a bundle (multi-pack or kit), TD Synnex returns both the bundle SKU and each component. The bundle header line never carries tracking data — only the component lines do. Flxpoint automatically reads tracking from component lines and assigns it to the bundle SKU shipment. Component lines do not appear as separate shipment records. If a bundle shipment is missing tracking, confirm with TD Synnex that all component lines have shipped — tracking is only attached once each component has shipped.
TD Synnex selects shipping carrier — do not map shipping method unless your rep confirms it
For most TD Synnex accounts, you do not send a shipping method or carrier code with orders. TD Synnex automatically selects the carrier based on your account preferences and order details. Leaving shipping method unmapped will not cause order failures. Only map carrier/service codes if your TD Synnex representative has explicitly confirmed your account is configured to receive them.
| Field | Maps To — Notes |
|---|---|
| synnexSkuNumber | → Product / Variant → SKU. Required. Primary identifier for the catalog item. |
| manufacturerPartNumber | → Identifiers → Manufacturer Part Number (MPN). Manufacturer part reference. |
| upcCode | → Identifiers → UPC. Universal product code, when provided. |
| partDescription | → Product → Title / Description. Item description as returned by TD Synnex. |
| manufacturerName | → Product → Manufacturer / Brand. |
| category1 / category2 | → Product → Category / Subcategory. |
| contractPrice | → Pricing → Cost. Populated only when a pricing FTP or the TDSynnex API Token connection is configured — the standard quantity-only FTP does not return cost. |
| msrp | → Pricing → MSRP. Same pricing-feed dependency as Cost. |
| Per-warehouse quantity fields | → Inventory → Per-warehouse quantity. TD Synnex returns quantity per named U.S./Canada warehouse (e.g. Atlanta, Dallas, Los Angeles, Chicago, New York); selecting "ALL" in the warehouse picker aggregates all selected warehouses into a single total. |
| Field | Maps To — Notes |
|---|---|
| synnexSkuNumber | → Inventory Variant → SKU. Required. Primary identifier. |
| Per-warehouse quantity fields | → Inventory → Quantity. Current available units, summed across selected warehouses. |
| contractPrice / customerPrice | → Pricing → Cost. Requires a pricing FTP or the TDSynnex API Token connection — the standard quantity feed does not return cost. |
| msrp | → Pricing → MSRP. Same pricing-feed dependency as Cost. |
| Full catalog fields | Not included in Secondary — descriptions, categories and identifiers come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary hourly to keep Cost and Quantity current. |
| Source Field | Maps To (TD Synnex) — Notes |
|---|---|
| Fulfillment Request line → Quantity | → Order Item Quantity. Required. Units requested. |
| Shipping address | → Ship To. Required. End-customer shipping address. |
| Ship-to contact | → Ship To Contact. Contact name, phone and email for the shipment. |
| ShipNode.ShipNode (template field) | → Ship Node. Required. Must be exactly two digits (e.g. 01, 31) — do not prefix with DC. Required even when using Source Complete "C." |
| Ship To Account (settings or template) | → Ship To Account. Required. Must be set in either integration settings or the mapping template — the job fails if neither provides a value. |
| Billing address | → Bill To. Billing address for the order. |
| Source Shipping Method | → Ship Method. Only map this if your TD Synnex representative confirms your account is configured to receive shipping method/carrier codes — otherwise leave unmapped and TD Synnex selects the carrier automatically. |
The order item SKU is not mapped on this operation — Flxpoint sends the line identifier itself. Map the quantity per line item.
| Field | Maps To — Notes |
|---|---|
| Item SKU | → Shipment Item → SKU. Required. Associates the shipped line to your catalog. |
| Shipped Quantity | → Shipment Item → Quantity. Required. Units shipped for the line. |
| Tracking Number | → Shipment Item → Tracking Number. Primary tracking reference; blank on the bundle header line (see Important Notes). |
| Carton ID / BOL | → Shipment references. Used in place of Tracking Number when Tracking Number is blank — common for LTL shipments. |
| Carrier | → Shipment → Carrier. |
| Shipping Method | → Shipment → Ship Method. |
| Ship Date Time | → Shipment → Shipped At. |
| Field | Maps To — Notes |
|---|---|
| InvoiceNumber | → Invoice → Invoice Number. Required. |
| InvoiceDate | → Invoice → Invoice Date. |
| Item/Sku | → Invoice Item → SKU. Required. Associates the invoice line to your catalog. |
| Shipped Quantity | → Invoice Item → Quantity. |
| FreightCost / Handling Cost / Tax Cost / Other Cost | → Invoice → Line items. Header-level costs save as separate invoice line items; if multiple rows repeat the same header cost, the last value per invoice wins. |
ShipNode.ShipNode is wrong — must be exactly two digits, no DC prefix. Valid: 01, 31. Invalid: DC 01, 1. Even with Source Complete "C," this field is still required and must be present. (2) Ship To Account is not configured in either the mapping template or the integration settings — if neither provides a value, the job fails. Check both locations. After fixing, test with a single order before re-enabling automatic sends.What warehouses does TD Synnex support and how does multi-warehouse quantity work?▸
What does Get Shipments retrieve and how are bundle items handled?▸
How does Get Invoices work for TD Synnex?▸
inv_*.xml) and Inbound Remote File Folder to match where TD Synnex deposits invoice files. FR Lookback Period defaults to 30 days — increase this if invoices post much later than shipments. TD Synnex invoices are typically finalized hours after shipment, not in real-time. Key mappings: Invoice Number (InvoiceNumber), Invoice Date (InvoiceDate), Freight Cost (FreightCost), Handling Cost, Tax Cost, Other Cost, item SKU (Item/Sku), and Shipped Quantity. Header costs (Freight, Handling, Tax, Other) save as separate invoice line items — last value per invoice wins if multiple rows carry the same header cost.