Ingram Micro US/CA as a Source
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.
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 Connection → Save Connection.
| Field | What to enter |
|---|---|
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. |
| Field | What to enter |
|---|---|
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. |
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.
Imports Ingram Micro's full electronics catalog: run once daily.
| Field | Maps To: Notes |
|---|---|
| SKU | → Product / Variant → SKU. Required. Primary identifier for the catalog item. |
| Manufacturer | → Manufacturer. Brand name for the item. |
| Description | → Title. Product title, taken from Ingram Micro's description field. |
| Description 2 | → Additional Description. Secondary description line, when provided. |
| Manufacturer Part Number | → Identifiers → MPN. Manufacturer's item reference. |
| UPC | → Identifiers → UPC. Product UPC/barcode. |
| Cost | → Pricing → Cost. Your Ingram Micro dealer cost. |
| MSRP | → Pricing → MSRP. Manufacturer's suggested retail price, when provided. |
| Weight / Length / Width / Height | → Dimensions & Weight. Package dimensions and weight from Ingram Micro's product feed. |
| Category Codes | → Category / Subcategory. Resolved to Ingram Micro's readable category names. |
| Quantity | → Inventory → Quantity. Available units from Ingram Micro's daily quantity feed. |
| Alternate Part Number | → Identifiers → Alternate Part Number. Additional part reference Ingram Micro provides for some items. |
Lighter, more frequent refresh of cost and quantity only.
| Field | Maps To: Notes |
|---|---|
| SKU (Ingram Part Number) | → Inventory Variant → SKU. Required. Primary identifier. |
| Quantity | → Inventory → Quantity. Current available units for your account's selected warehouse(s). |
| Cost / Price | → Pricing → Cost. Updated wholesale cost. |
| Full catalog fields | Not 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. |
Sends orders (Fulfillment Requests) to Ingram Micro for dropship fulfillment.
| Source Field | Maps To (Ingram Micro): Notes |
|---|---|
| Shipping address → Name | → Ship To Name. Required. Customer name for the shipment. |
| Shipping address → Address Line 1 / Line 2 | → Ship To Address. Required (Address Line 1). |
| Shipping address → City / State / Postal Code / Country | → Ship To City / State / Postal / Country. Required. |
| Ship-to contact, phone, email | → Ship To Contact. Contact details for the shipment. |
| Fulfillment Request line → SKU / Quantity | → Order Line. Required. Sent to Ingram Micro per line item (Ingram Part Number + Quantity). |
| Source Shipping Method | → Ship Method / Instructions. Carrier and any special shipping instructions sent with the order. |
| End customer / reseller info | → End User & Reseller Info. Optional end-customer and reseller details Ingram Micro uses for drop-ship compliance. |
Pulls Ingram Micro shipment tracking and carrier info back into Flxpoint.
| Field | Maps To: Notes |
|---|---|
| Tracking Number | → Shipment → Tracking Number. Required. Package tracking number. |
| Carrier Name / Code | → Shipment → 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 Ordered | → Shipment Item → Quantity. Required. Units shipped, ordered and back-ordered for the line. |
| Serial Numbers | → Shipment Item → Custom Fields. Serial numbers returned by Ingram Micro, added as numbered custom fields. |
| Freight Charges | → Shipment → Freight Charges. Freight amount Ingram Micro charged for the shipment, when provided. |
Pulls Ingram Micro invoice detail (pricing and tax) for shipped orders.
| Field | Maps To: Notes |
|---|---|
| Invoice Number | → Invoice → Invoice Number. Required. Ingram Micro's invoice identifier. |
| Invoice Date | → Invoice → Invoice Date. |
| Ingram Part Number / Product Description | → Invoice Item → SKU / Description. Required (SKU). |
| Quantity / Unit Price / Extended Price | → Invoice Item → Quantity, Unit Price, Extended Price. |
| Tax Amount / Tax Percentage | → Invoice Item → Tax. Tax amount charged for the line. |
| Serial Numbers | → Invoice Item → Custom Fields. Serial numbers returned by Ingram Micro, added as numbered custom fields. |
