| Error text contains | Meaning | Fix |
|---|---|---|
| "no Sprint warehouse mapping" | order's Odoo warehouse is not mapped on the instance | add the warehouse mapping, retry |
| "has no Internal Reference (SKU)" | product cannot be identified to the 3PL | set the Internal Reference, retry |
| "unmapped carrier" on a despatch | 3PL shipped with a service you have not mapped | add the carrier mapping (or enable Auto-create Delivery Methods), retry |
| "reported no batch numbers for lot-tracked product" | 3PL despatch feed lacks batch data | have the 3PL supply batches, or enable Allow Un-batched Despatches |
| "only holds N un-batched unit(s)" | un-batched fallback lacks stock to relabel | investigate the stock discrepancy - hard failure by design |
| "credentials missing" / HTTP 401 | wrong or expired credentials | re-key on the Connection tab, Test Connection |
| "endpoint may not be enabled for your account" | request was valid but the 3PL refused the operation | contact the 3PL - the Email Support button exists for exactly this |
| HTTP 400 with the 3PL's own message | the 3PL rejected the payload; their reason is quoted in the entry title | read the redacted request in the entry, correct the data, retry |
Nothing is being sent - why? Check, in order: the instance is Active (not Connected/Paused); Sync Orders is on; Send Orders Automatically is on (off means orders wait for manual sends - look at the To Send card); the orders are eligible (confirmed, mapped warehouse, delivery method set if required).
An order shows despatched at the 3PL but not in Odoo. Run Check Statuses for the instance; open the order's Sync Log entries. The usual causes are an unmapped carrier (fix the mapping and retry the despatch entry) or missing batch data on a lot-tracked line (see above).
Stock looks wrong. Open the latest Inventory Sync report - it lists, per batch, what Odoo had, what the 3PL reported, and what was done. If the instance runs Odoo-as-master, look at the discrepancy lines; nothing was changed by design.
Does pausing an instance lose anything? No. Pausing stops the scheduler; polls resume against current remote state and the eligible backlog sends on the next push.
Who did that? Every manual action - runs, sends, setting changes, acknowledgements - is attributed in the instance/order/RMA chatter.
How long are logs kept? Per instance: Keep Logs (days), default 90. Set 0 to keep forever. Chatter is kept forever regardless.