Auto-Processing
A job queue entry fetches the state of the orders at Ingram. It asks about every order that still waits for something and writes back what Ingram reports. Business Central SaaS gives an extension no publicly reachable endpoint — the status is therefore polled, not delivered.
The file imports (price list, availability), the catalog subscriptions and the stock refresh run separately through the Hub's import jobs — see Setup.
The Job
| Property | Value |
|---|---|
| Description | Ingram Micro - Auto Sync Orders |
| Codeunit | ALN MCIM Job Runner |
| Interval | Sync Interval (Minutes), default 60 |
| Time window | Monday to Friday, 06:00 to 20:00 |
| Retries | 3 attempts, 60 seconds apart |
After installation the job is On Hold. It starts when you enable Auto Sync in the setup wizard and finish, or on the setup page with Enable Auto Sync and Create/Update Job Queue. It only runs while the connector is enabled and licensed.
What a Run Does
- Find orders placed elsewhere (see below).
- Ask about open orders — status Submitted, Processing or Backordered, regardless of age.
- Ask about shipped orders with work left — while something is still missing within the follow-up window.
- Read invoices for shipped and completed orders of the last 90 days.
- Match invoices, then timestamp, log and — if set up — the e-mail to the Notification Email.
Every order is refreshed in a transaction of its own — completely or not at all. If the refresh fails, the Ingram order and the purchase order stay as they were before the attempt; a half-applied price or quantity correction does not remain. The same holds for the document automation after an invoice. The run then moves on to the next order. Simulated orders are never asked about.
What a Sync Writes
Onto the Ingram order: Ingram order number, status and Ingram's status text, order total, currency, and per line the confirmed, backordered and shipped quantity, price, delivery date, tracking, delivery note and invoice number. When nothing is open any more, Follow-up Complete is set.
Onto the purchase order — depending on the switches on the setup page:
- Vendor Order No. and Vendor Shipment No., if still empty
- corrected direct unit costs and quantities
- promised receipt date
- serial numbers
- with Auto Post Receipt: the goods receipt for the reported quantities, exact to the piece — every partial delivery becomes a receipt of its own, posted on the reported shipping date
- with Auto Post Invoice: the purchase invoice, once the invoice matching succeeds
Onto the sales order of a drop shipment: delivery date, serial numbers and tracking.
To the Hub: every status change in Ingram's own wording, every tracking number with the shipping agent recognised from the number, and every invoice read.
Errors and Logs
If the order status refresh, the invoice import or the document automation after the invoice fails for an order, the connector records the reason in two places:
- On the order, in the Last Error Message field of the Ingram order. The status stays unchanged. A later successful sync clears the message again — unless the order is in status Error, because then the message explains why it never got through.
- In the Hub's activity log as Order Sync, with purchase order, Ingram order number, step and the full error text. The dashboard counts its Sync errors (24 h) from these entries.
For the order status refresh this also applies when you start Refresh All Open Orders by hand.
In addition, every run of the job writes an Order Sync row into the Hub's Supplier Import Log — next to the import runs — with Orders Synced and Orders Failed.
Rate Limit and Retries
Ingram allows 60 API calls per minute. The connector therefore sends at most one call per second — in every run and for every action.
If Ingram answers with HTTP 429 (too many requests) or a server error (5xx), the connector repeats the call with a growing wait. After five failed attempts in a row, calls pause for one minute; during that time every call reports "Ingram Micro answered several calls in a row with an error, so calls are paused for a minute. Try again shortly."
Placing an order is never repeated automatically — see Transmitting an Order.
Follow-up Window
Ingram often reports the status before the shipment details, and a partial delivery reports its remainder days later. A shipped order is therefore asked about while something is missing — an open quantity, the invoice, its surcharges or serial numbers — and at most Follow-up Window (Days) after shipment (default 60). The window counts from the first run that sees the order as shipped, not from the order date. 0 switches the limit off: the order is then asked about until nothing is waiting any more.
Finding Orders Placed Elsewhere
Every run looks within the Discovery Window (Days) (default 90) for purchase orders to the Ingram vendor that have no Ingram order — for example because they were ordered by e-mail or in Ingram's portal. It searches by Vendor Order No., Vendor Invoice No. and your purchase order number. Only certain hits are linked; uncertain ones appear in the log so you can check them by hand with Link Existing Ingram Micro Order. 0 switches the search off.
Unconfirmed Orders
Ingram assigns the order number asynchronously, usually within minutes. If Ingram still knows no order under your purchase order number after 48 hours, the run sets the Ingram order to Error and writes the reason into Last Error Message. A search that got no answer changes nothing — only Ingram's explicit "no order under this number" counts. See Troubleshooting.
Notification
With a Notification Email and Send Process Notification, every run that did something sends a summary: refreshed orders, invoices read, errors and the run's log.