Flxpoint Help Center
All DocsContact support

Ingram Micro US/CA as a Source

July 17, 2026

Summary

Ingram Micro US/CA is a pre-built IT hardware and consumer electronics distributor integration in Flxpoint, with separate connectors for the US and Canadian markets. It connects via FTP for inventory (Get Inventory Primary and Secondary) and via a separate OAuth API connection for order operations (Send Fulfillment Requests, Get Shipments, and Get Invoices). Select the Ingram Micro US or Ingram Micro Canada connector that matches your account — see the separate Ingram Micro US/CA with Etilize article if you have an Etilize enrichment agreement.

Get Inventory (Primary)
Imports Ingram Micro's full electronics catalog — run once daily.
Get Inventory (Secondary)
Lighter, more frequent refresh of cost and quantity only.
Send Fulfillment Requests
Sends orders (Fulfillment Requests) to Ingram Micro for dropship fulfillment.
Get Shipments
Pulls Ingram Micro shipment tracking and carrier info back into Flxpoint.
Get Invoices
Pulls Ingram Micro invoice detail — pricing and tax — for shipped orders.

Ingram Micro US/CA uses two connection types depending on the operation: an FTP connection for inventory, and a separate OAuth API connection for order operations. Add an Ingram Micro source (choosing the US or Canada connector for your account), start configuring an operation, and when Flxpoint prompts you click + New Connection, enter the values, then Test ConnectionSave Connection.

FTP (Ingram Micro US or Canada)
HostRequired
The Ingram Micro FTP server hostname for your account, provided by Ingram Micro. Select the connector — Ingram Micro US or Ingram Micro Canada — that matches your account.
FTP UserRequired
Your Ingram Micro FTP username, provided by Ingram Micro (separate from your Ingram Micro account/website login).
FTP PasswordRequired
Your Ingram Micro FTP password, provided by Ingram Micro.
OAuth API (fulfillment operations)
Client IDRequired
Your Ingram Micro OAuth Client ID, from Ingram Micro's developer/API portal (separate from your account login).
Client SecretRequired
Your Ingram Micro OAuth Client Secret, provided alongside the Client ID.
Customer NumberRequired
Your Ingram Micro account (Customer) Number, used to authenticate order operations.
EnvironmentRequired
Toggles Sandbox vs Production for order operations. Use Sandbox for initial testing, then switch to Production before go-live.
Choose the connector — Ingram Micro US or Ingram Micro Canada — that matches your account when adding the source; each requires its own credentials. Get Inventory (Primary and Secondary) uses the FTP connection above; Send Fulfillment Requests, Get Shipments, and Get Invoices use the separate OAuth API connection. See the Ingram Micro US/CA with Etilize article if you have an Etilize enrichment agreement. For extended operation setup and field mapping beyond connection, contact support@flxpoint.com.

Two separate connection types — FTP for inventory, OAuth API for fulfillment

Inventory feeds use FTP credentials (FTP Host, FTP User, FTP Password). Fulfillment operations (Send Fulfillment Requests and related order ops) use OAuth credentials: Client ID, Client Secret, and Customer Number. The Customer Number is your Ingram Micro account number. Configure each connection type separately for the operations you need.

Get Inventory (Secondary) supports both API and FTP connection methods

Using the direct connection method, Get Inventory (Secondary) can be synced through either the API or the FTP connection — you can use whichever of the two connection methods you prefer to sync the inventory data.

Separate connectors for US and Canada — select the correct one for your market

Ingram Micro US and Ingram Micro Canada are separate integrations in Flxpoint. When adding the source integration, select the connector that matches your Ingram Micro account region. If you operate in both markets, configure two separate sources — one for US and one for Canada — each with their respective credentials.

Environment toggle (Production / Sandbox) applies to API-based operations

The OAuth API connection includes an Environment selector. Use Sandbox for initial testing of order operations and Production for live order submission. This toggle applies to fulfillment operations only — FTP inventory feeds do not have a sandbox mode.

For extended operation details and feed configuration, contact Flxpoint Support

The publicly available Ingram Micro US/CA help documentation covers connection setup only. For guidance on which operations are available for your account, FTP folder paths, inventory feed filenames, or mapping template recommendations, email support@flxpoint.com. Also see the Ingram Micro US/CA with Etilize article if you have an Etilize enrichment agreement.


FieldMaps To — Notes
SKUProduct / Variant → SKU. Required. Primary identifier for the catalog item.
ManufacturerManufacturer. Brand name for the item.
DescriptionTitle. Product title, taken from Ingram Micro's description field.
Description 2Additional Description. Secondary description line, when provided.
Manufacturer Part NumberIdentifiers → MPN. Manufacturer's item reference.
UPCIdentifiers → UPC. Product UPC/barcode.
CostPricing → Cost. Your Ingram Micro dealer cost.
MSRPPricing → MSRP. Manufacturer's suggested retail price, when provided.
Weight / Length / Width / HeightDimensions & Weight. Package dimensions and weight from Ingram Micro's product feed.
Category CodesCategory / Subcategory. Resolved to Ingram Micro's readable category names.
QuantityInventory → Quantity. Available units from Ingram Micro's daily quantity feed.
Alternate Part NumberIdentifiers → Alternate Part Number. Additional part reference Ingram Micro provides for some items.
FieldMaps To — Notes
SKU (Ingram Part Number)Inventory Variant → SKU. Required. Primary identifier.
QuantityInventory → Quantity. Current available units for your account's selected warehouse(s).
Cost / PricePricing → Cost. Updated wholesale cost.
Full catalog fieldsNot included in Secondary — title, category, dimensions and images come from Get Inventory Primary. Run Primary daily for the full catalog and Secondary more frequently to keep Cost and Quantity current.
Source FieldMaps To (Ingram Micro) — Notes
Shipping address → NameShip To Name. Required. Customer name for the shipment.
Shipping address → Address Line 1 / Line 2Ship To Address. Required (Address Line 1).
Shipping address → City / State / Postal Code / CountryShip To City / State / Postal / Country. Required.
Ship-to contact, phone, emailShip To Contact. Contact details for the shipment.
Fulfillment Request line → SKU / QuantityOrder Line. Required. Sent to Ingram Micro per line item (Ingram Part Number + Quantity).
Source Shipping MethodShip Method / Instructions. Carrier and any special shipping instructions sent with the order.
End customer / reseller infoEnd User & Reseller Info. Optional end-customer and reseller details Ingram Micro uses for drop-ship compliance.
FieldMaps To — Notes
Tracking NumberShipment → Tracking Number. Required. Package tracking number.
Carrier Name / CodeShipment → Ship Method. Carrier returned by Ingram Micro.
Item (Ingram Part Number)Shipment Item → SKU. Required. Associates the shipped line to your catalog.
Quantity Confirmed / Ordered / Back OrderedShipment Item → Quantity. Required. Units shipped, ordered and back-ordered for the line.
Serial NumbersShipment Item → Custom Fields. Serial numbers returned by Ingram Micro, added as numbered custom fields.
Freight ChargesShipment → Freight Charges. Freight amount Ingram Micro charged for the shipment, when provided.
FieldMaps To — Notes
Invoice NumberInvoice → Invoice Number. Required. Ingram Micro's invoice identifier.
Invoice DateInvoice → Invoice Date.
Ingram Part Number / Product DescriptionInvoice Item → SKU / Description. Required (SKU).
Quantity / Unit Price / Extended PriceInvoice Item → Quantity, Unit Price, Extended Price.
Tax Amount / Tax PercentageInvoice Item → Tax. Tax amount charged for the line.
Serial NumbersInvoice Item → Custom Fields. Serial numbers returned by Ingram Micro, added as numbered custom fields.

FTP Test Connection failing
Verify the FTP Host matches the value Ingram Micro provided for your account, and that your FTP User and Password match what Ingram Micro provided. Ingram Micro FTP credentials are different from your Ingram Micro website login — they are issued separately for API/FTP access. If credentials appear correct and the test still fails, contact your Ingram Micro account representative to confirm FTP access is enabled for your account and that the credentials have not expired.
OAuth API Test Connection failing for fulfillment operations
Check: (1) Client ID and Client Secret are entered correctly — these come from Ingram Micro's developer portal, not your account login; (2) Customer Number matches your Ingram Micro account number exactly; (3) the correct Environment is selected (Sandbox vs Production); (4) your Ingram Micro account has API access enabled — not all accounts have OAuth credentials by default. Contact Ingram Micro to confirm API access is active for your account type and region.

What credentials do I need and where do I get them?
For FTP (inventory feeds): FTP Host, FTP User, and FTP Password — obtained from your Ingram Micro account representative or dealer portal. For OAuth API (fulfillment): Client ID, Client Secret (from Ingram Micro's developer/API portal), and Customer Number (your Ingram Micro account number). If you don't have API credentials, contact your Ingram Micro account representative to request OAuth access for your account.
Does Ingram Micro have a separate Etilize-enriched version?
Yes. Ingram Micro US/CA with Etilize is a separate integration available for accounts with an Etilize content agreement. It provides enriched product content (detailed specifications, marketing copy, images) layered on top of the standard Ingram Micro inventory feed. If you have an Etilize agreement with Ingram Micro, use the "with Etilize" connector instead of the standard one. See the Ingram Micro US/CA with Etilize help doc for configuration details.
© 2026 Flxpoint. All rights reserved.