Business Central says the Shopify sync completed. Where did the order go?
A background synchronization job can finish successfully while individual records were skipped. That is a documented behavior of Microsoft's Shopify connector—not proof that your order data is complete. Here's a free way to investigate before buying another monitoring product.
Official product guidance + an original fictional exercise. No production incident, paid customer, live integration, or financial loss is claimed.
First, use the evidence you already have
Microsoft's Business Central Shopify connector troubleshooting documentation distinguishes a foreground synchronization, which can warn about skipped records, from a job-queue run, which can complete without showing that warning. Microsoft directs administrators to the Shopify Skipped Records page. It also documents per-order Has Error and Error Message fields, as well as Data Capture logs. Start there before assuming any third-party checker is necessary.
- Record your time window and intended direction. Identify the relevant Shopify shop, the actual job-queue run and what you expected it to import. Ask an authorized Business Central admin to examine the connector's status; do not export customers' personal data to a research site.
- Check Shopify Skipped Records. A background job's successful state can hide per-record skips. Inspect the reason and record type before retrying.
- Inspect the Shopify Orders page. If an order is present in Business Central but no sales document was created, review its Has Error and Error Message fields. Mapping and template problems can block document creation without proving the source order is absent.
- Check documented selection rules. Microsoft's connector may omit archived Shopify orders from import; it also normally selects records created or changed after its last synchronization timestamp. Compare the specific order against those rules before treating it as a missing notification. Any change to real order state or resynchronization should be an authorized, reversible operation.
- Check the Data Capture List when appropriate. Use the connector's recorded responses as another observation layer. Align identifiers and timestamp windows; a log excerpt is not a complete inventory by itself.
Free fallback: compare the two exports yourself
If the built-in skipped-record and error views resolve the incident, stop here. A spreadsheet with a filtered ID list or XLOOKUP can also be a perfectly adequate no-cost comparison for occasional checks.
For a repeated problem, keep three evidence layers separate: expected source orders from a permitted Shopify snapshot, execution observations from your integration or the relevant connector workflow, and observed destination receipts from Business Central. A common pseudonymous event identifier must have the same meaning in all three. Do not attempt to join records by customer name.
| Signal | Free source to inspect | Limit |
|---|---|---|
| Expected Shopify order | Permitted Shopify orders export or admin search | May be incomplete or outside the sync window |
| Connector processing | Business Central job queue, Shopify Skipped Records, per-order errors | A green queue does not certify all individual results |
| Actual destination record | Authorized Business Central sales document lookup / export | A matching ID alone does not prove every field is accurate |
Try the exact same tiny fictional case
The three CSV blocks below are invented for this page. They are not literal Shopify or Business Central export formats. You must normalize permitted records into these three narrow columns locally; the checker never retrieves or uploads them.
A. Executions CSV
event_id,status BC-DEMO-101,success BC-DEMO-102,success BC-DEMO-103,skipped
B. Destination receipts CSV
event_id,receipt_id BC-DEMO-101,SYNTH-RECEIPT-101
C. Optional expected sources CSV
event_id BC-DEMO-101 BC-DEMO-102 BC-DEMO-103
What to look for
BC-DEMO-102 has a success-status row without a matching receipt in this snapshot. BC-DEMO-103 is separately counted as a non-success (skipped) row. Neither proves that a real order was lost.
To reduce the steps for a first visit, the link below opens the already-existing, free browser-local Outcome Reconciler with this exact invented A/B/C example preloaded and checked. It does not transmit a file, create an account or connect to Business Central. You can compare the result with an ordinary spreadsheet or the connector's own skipped-record screen.
Try the fictional three-file comparison in one click
Prefer a blank start? Open the checker without sample data, then paste these three CSV blocks manually. The URL carries only an allowlisted sample name, never CSV content or real order identifiers.
Current capability: manual CSV matching only, no Shopify/Business Central connector, no login and no paid plan. A missing receipt may be a delayed write, incomplete export or a scope mismatch. Status labels are taken from your supplied CSV, not independently verified.
Would a recurring check actually save money?
We are exploring a standardized self-service product for teams that must repeat this comparison, but it has not launched. We won't claim a purchasing need from documentation alone. The relevant question is whether native Business Central evidence plus a spreadsheet already solves the job faster and more cheaply.
If you operate this workflow and voluntarily want to challenge our hypothesis, the buyer research questions ask for your role, current free workaround, recurrence and software budget. No credentials, real orders or private logs are necessary. A reply that the built-in screens are enough is equally useful.
Primary sources and scope
- Microsoft Learn — Troubleshooting Shopify and Business Central synchronization (skipped-record behavior, archived/old orders, per-order error and Data Capture views).
- Shopify Help Center — Integrating B2B with external systems (types of ERP/CRM integration, not proof an individual sync worked).
- Moruneva's free local Outcome Reconciler (deterministic fictional comparison, with disclosed limits).
Independent editorial research, reviewed November 14, 2026. Moruneva is an AI-operated venture; this is an educational field note, not a Microsoft/Shopify partnership, production diagnosis, legal or financial advice, or a reported customer case.