Troubleshooting
The "Ingram Micro" group is missing on the purchase order
The order is not addressed to the vendor entered on the Supplier Card INGRAM-MICRO — or no vendor is entered there. Since version 1.16 the vendor is kept there only, no longer in Ingram Micro Setup.
A message asks for the vendor on the merchantCENTRAL supplier card
Enter the Vendor No. on the Supplier Card INGRAM-MICRO, or in the setup wizard. Since version 1.16 the vendor is kept there only.
"The connector is not active"
Module INGRAM-MICRO has no license or running demo, or the supplier INGRAM-MICRO is not Enabled in the Supplier List. Both apply in a sandbox too — a sandbox is only not billed. See Licensing.
A line has no Ingram part number
The item has neither Ingram supplier data nor an entry in the item vendor catalog of the Ingram vendor, and the purchase line has no Vendor Item No. Import the price list for the manufacturer, or enter the Ingram part number in the item vendor catalog.
A message names the Client ID or the Client Secret
The credentials are missing. The message leads to Ingram Micro Setup; enter them there and check with Test Connection.
The connection fails although the credentials are right
- Are Customer Number and Country Code right? Ingram checks both on every request.
- Were the credentials issued for live or for the sandbox? Set Use Sandbox accordingly.
- Are the credentials entered in this company? They apply per company — see Authentication.
- A new Client ID or Client Secret discards the stored token by itself. If in doubt, discard it with Clear Access Token; the next call requests a new one.
"Ingram Micro answered several calls in a row with an error …"
Several attempts in a row failed, usually because Ingram was overloaded (HTTP 429), answered with a server error or not at all. So that the connector does not keep loading a disturbed API, calls pause for one minute. Try again afterwards; the scheduled sync catches up on its next run with whatever was missed. See Rate Limit and Retries.
"Execute Import" reports a missing "Active import definition"
None of the connector's four import definitions is active. Activate price list and availability in the import definitions, and the definitions INGRAM-CATALOG and INGRAM-STOCK in the Hub's Supplier Setup.
An order shows a Last Error Message but is not in status "Error"
A sync of this order failed — the refresh, the invoice import or the document automation after the invoice — or the transmission got no answer (see below). The status stays unchanged; the full text is in the Hub's activity log. The next successful sync clears the message. See Errors and Logs.
A user cannot create or run catalog subscriptions
The permission set Ingram Micro User may only read catalog subscriptions; running catalog imports is admin work. Assign Ingram Micro Admin — see Permissions.
The order stays "Submitted" for a long time
Ingram assigns the order number asynchronously, usually within minutes. If Ingram still knows no order under your purchase order number after 48 hours, the sync sets the Ingram order to Error and writes the reason into Last Error Message — Ingram has then most likely turned the order down.
Check in the Ingram portal before transmitting the purchase order again. The new transmission asks Ingram for an existing order first anyway and links it if there is one after all.
"Ingram Micro could not be asked whether it already holds an order for purchase order …"
Before every transmission the connector asks Ingram whether an order already exists under your purchase order number. When no answer came, it does not send - otherwise the goods could be ordered twice, and Ingram knows no cancellation. Transmit the purchase order again later.
"Purchase order … was sent, but Ingram Micro did not answer"
The order went out, the answer did not come back. Ingram may have taken it all the same. The Ingram order therefore stays Submitted without a confirmation number, with a note in Last Error Message, and is blocked against being sent again. The sync looks for it under your purchase order number; if Ingram still knows no such order after 48 hours, it goes to Error and may be transmitted again. Do not send it again until then.
"These Ingram Micro imports failed: …"
Execute Import runs every active import definition on its own. The ones named failed, the others ran. The reason is on each definition in the import definitions or in the hub's supplier setup.
"Ingram Micro already holds order … for purchase order …"
On transmission the connector found an existing Ingram order under your purchase order number and linked it instead of ordering twice — typically after a timeout where Ingram had taken the order anyway. The next sync reads the order data. Nothing to do.
The price list import reports "no article"
The file was empty or truncated. The run then counts as failed and nothing was set to draft. Check with Test Connection in the import definition and repeat the import once the file is complete in your Blob Storage again.
The availability import reports "no known article"
Availability only updates articles from the price list. Run the price list first and check the manufacturer selection.
Many articles show a stock of 10,000
Ingram reports this value as a ceiling, not as real stock. Set a Stock Quantity Cap if your shops should not show such high quantities.
An invoice is not posted automatically
See Invoices: the option is off by default, the matching found a deviation (often a missing item charge), it is a credit memo, or no goods receipt has been posted yet.
Can I change or cancel a transmitted order?
Not through the connector — the Xvantage API offers no endpoint for it. Settle it with Ingram; the next sync takes over the new quantities or the status Cancelled.
The sync job does not run
- Is Enable Auto Sync set and the job started with Create/Update Job Queue? After installation it is on hold.
- Is the time within the window Monday to Friday, 06:00 to 20:00?
- Is the connector enabled and licensed?