Flxpoint Help Center
All DocsContact support

Tech Data as a Source

July 20, 2026

Summary

Tech Data (now TD SYNNEX) is a pre-built electronics and IT distributor source in Flxpoint. It requires your Tech Data Account Number and shop portal login, plus separate FTP or XML credentials requested from Tech Data depending on which operation you're configuring. The integration runs Get Inventory (Primary) for the full catalog and Get Inventory (Secondary) for frequent pricing/quantity refreshes; for extended setup guidance contact support@flxpoint.com.

Get Inventory (Primary)
Imports Tech Data's full catalog.
Get Inventory (Secondary)
Refreshes Tech Data pricing and quantity via XML between full pulls.

Tech Data requires your Account Number and Tech Data shop portal login, plus either FTP or XML credentials — these differ from each other and are both requested separately from Tech Data. Add a Tech Data source, start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test ConnectionSave Connection.

Account & Shop Login (required for all connections)
User IDRequired
Your Tech Data user ID - the only identifier needed for GIP and GIS.
PasswordRequired
Your Tech Data password.
The Get Inventory Secondary XML feed is capped by Tech Data at 10,000 SKUs per hour — Flxpoint blocks queueing above that limit. For access to the FTP or XML credentials, or for extended operation setup, contact support@flxpoint.com.

XML is recommended over FTP

The FTP feed updates only once daily, while XML is near-real-time. The XML and FTP credentials are separate and both must be requested from Tech Data.

10,000 SKU per hour XML limit

Tech Data caps XML at 10,000 SKUs per hour. Flxpoint blocks queueing more than that, because exceeding the limit risks losing access to Tech Data's XML.

Two ways to get inventory

Get Inventory Primary can use the prebuilt connector (Account Number plus your Tech Data shop portal ECID and password, pulling your PartSmart catalog) or Etilize enhanced product data.

Orders run through the Flxpoint API

Send Fulfillment Requests and Get Shipments are only available via the Flxpoint API. Contact support to configure them.


FieldMaps To — Notes
SkuProduct / Variant → SKU. Required. Primary identifier matched against the quantity and price files.
QtyInventory → Quantity. Available quantity for the SKU.
PricePricing → Cost. Tech Data's dealer price, saved as Cost.
Remaining catalog fields (title, category, etc.)Product / Variant. Mapped from the PartSmart (or Etilize, if enabled) catalog feed per your field-mapping template.
FieldMaps To — Notes
WhseInfo → Qty (per selected warehouse)Inventory → Quantity. Summed across the warehouse codes configured on the connection.
Sku / Mpn (reference ID)Product / Variant → SKU. Required. Uses SKU or manufacturer part number as the match key, based on your field mapping.

What format does the SKU monitoring file need?
A single column with the header SKU. The export used for Get Inventory Secondary should contain only that one column.
A product shows as archived after the GIS job. Why?
Selecting warehouses only imports products from those warehouses. If a product archives after the job, it does not exist at the selected warehouse.
Why does a digital product (like a warranty) always show quantity 100?
The Vendor Drop-ship/Software Licensing warehouse sometimes does not provide quantity for digital products, so the quantity stays at 100.
© 2026 Flxpoint. All rights reserved.