Document not appearing in the target system
Lesson 14 of 17 7 min read
The four checks to make when a Document should have reached your ERP, warehouse or other system but has not.
"It's in Supply Lens but not in the ERP" is the most common question Support hears. The answer is almost always one of four things. In this lesson you will work through those four checks in order, with a worked example for each.
The four checks
1. The Document's status
Open the Document from its list, for example Sales → Orders.
Ready: the Mapping is set to manual. Process the Document with the Mapping, or run the target Integration manually if target data is waiting.Failed: open the Logs to see why processing failed, fix the issue, then reprocess.Complete: carry on to check 2.
2. The target data
From the Document's links menu, check whether there is target data for the Integration you expect. Each piece of target data shows which Integration it was for.
- Present and sent: the data was sent. Look in the target system itself, for example whether an import rule or filter there is holding it back.
- Cancelled or missing: the Document may not have been processed to that Integration yet, or a previous attempt was cancelled. Remember the duplicate fail-safe.
- Failed or Pending: go to check 4.
3. The Mapping
On Settings → Integration setup → Mappings, make sure:
- a Mapping exists for this document type, from the correct source Integration to the correct target Integration
- it is Enabled
- Automatic is on, if you want it to run without manual steps
- any filters (Customer, Supplier, Ship to, Ship from, Tags) actually match this Document
Use the data path
On the Mappings page, pick the document type and source Integration to see every step that kind of Document goes through and which Mappings run. A missing step jumps out.
4. The target Integration
On Settings → Integration setup → Integrations, confirm the target Integration is Enabled and is not showing connection or authentication errors. If credentials have expired, fix them (the next-but-one lesson covers this) and try again.
Worked examples
Three tickets in one morning
Ticket 1. A grocery chain order is not in Unleashed. Status: Ready. The chain's Mapping is
manual and Priya was off yesterday. She reviews and processes it. Check 1.
Ticket 2. A Shopify order is Complete but not at Northgate. No target data for Northgate.
The Orders Mapping to Northgate was disabled during a stock-take last week and never turned back
on. Priya enables it and processes the order to the Northgate Mapping. Check 3.
Ticket 3. Several orders have target data for Northgate showing Failed. The logs mention
authentication. Northgate rotated their API key on Friday. Priya updates the credential on the
Northgate Integration, then reprocesses the affected orders (the fail-safe protects against
duplicates). Check 4.
If it is still missing
Contact the Support Team with the Document ID and the Integration ID, and say which of the four checks you have already made.
Recap
- Check in order: Document status, target data, Mapping, target Integration.
Readymeans process it;Failedmeans logs, fix, reprocess.- No target data usually means a missing, disabled or over-filtered Mapping.
- Failed target data often points to the target Integration's connection or credentials.
- Send Support the Document ID and Integration ID if the four checks do not solve it.
Quick guides for this topic
Your progress is saved in this browser. Create a free account to keep it everywhere, take quizzes and earn certificates.