Skip to main content
Metrics type: Cross-Platform Metrics • Category: Ecommerce Platform
Commerce orders that never created a Business Central Sales Order. Each row is a revenue-leak investigation.

​
At a glance

Commerce orders that exist on the commerce platform but have no matching BC Sales Order or Posted Sales Invoice. Each row is a revenue leak: the customer paid (or committed to pay) but BC has no record. Until mapped, it never hits the GL.

​
Calculation

Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​
Worked example

A US wholesale distributor on BC + BigCommerce B2B + Adobe Commerce. 30-day window 14 Mar 26 to 12 Apr 26. Five things to notice:
  1. Wholesale-X has $28K stuck across two orders. Same root cause: customer record never created in BC. The BC Functional Consultant creates the Customer once and both orders re-sync automatically. Vortex IQ groups same-customer rows in the export.
  2. Wholesale-X is 21 days old. That is 3 weeks of revenue invisible to the GL. The customer has likely received the goods (BigCommerce shipment confirmed) and may even be late-paying without anyone noticing because there is no Customer Ledger Entry to age.
  3. Connector Error on Acme Tech is a VAT Posting Group misconfiguration. Customer was migrated from another ERP without the VAT Posting Group field. The AL Extension fails the SO creation. Fix: complete the Customer Card.
  4. Mapping Conflict on Distrib-Z is a multi-Company issue. Customer exists in both UK and US BC Companies; the AL connector cannot determine which to use. Fix: workspace setting to either default to a Company or explicit per-customer mapping.
  5. The DTC Shopify case ($284) is auto-resolvable. BC’s standard DTC sync flow auto-creates a Customer record from the commerce order; this row exists because the order is < 24 hours old and the next AL connector run will pick it up. Vortex IQ does not alert at < 24hr age to suppress this noise.

​
Sibling cards merchants should reference together

​
Reconciling against the vendor’s own dashboard

Where to look in Business Central:
AL Extension Connector Logs (varies by connector vendor: Insight Works, Sana Commerce, dynamicweb, etc.) Sales > Sales Orders filtered to External Document No. IS BLANK (no commerce ID, possibly manually created) Customer List filtered to last sync errors
There is no native BC tile that surfaces “commerce orders we could not map”. The card automates the comparison. Why our list may legitimately differ from a manual export: Cross-connector reconciliation: This card IS the cross-connector reconciliation for the Unmapped subset of the Revenue Gap headline. Other connectors do not see this dimension because they do not query the BC side.

​
Known limitations / merchant FAQs

A new commerce customer placed their first order. Will it always be unmapped? For B2B: yes briefly, until a BC Customer record is created. Most B2B AL connectors require manual customer onboarding (KYC, VAT validation, credit limit). The order sits unmapped until the customer is created. For DTC: most connectors auto-create a BC Customer record with default settings. Can Vortex IQ auto-create the BC Customer for me? Not yet. The AI OS Action Engine roadmap includes safe auto-mapping for low-risk DTC cases. B2B always requires human review. Why is the same customer’s order unmapped multiple times? Because the customer record is missing. Once created, all that customer’s orders sync; until then, every new order from them adds another row. Multi-Company: which Company should the order go to? The field map can specify. Default rules: by ship-to country (UK shipments to UK Company, US to US Company), by commerce platform tag (Shopify Plus → DTC Company), or by customer-specific override. Connector Error rows: what is the most common cause? VAT Posting Group missing on the Customer (especially on EU customers migrated without full setup). Customer Posting Group missing. Currency Code mismatch. Item No. on the order line not in BC’s Item table. How long should an order stay in this card? < 24 hours: normal sync delay. 1-3 days: BC Functional Consultant queue. > 3 days: escalate. > 7 days: revenue at material risk; alert fires daily. Mapping Conflict resolution: what does Vortex IQ recommend? Workspace setting + BC Functional Consultant action. Vortex IQ flags but does not write back to BC. Does this card show CSV export? Yes, sorted by age descending. The export is the BC Functional Consultant’s daily worklist.

​
Tracked live in Vortex IQ Nerve Centre

Commerce Orders Without Business Central Sales Order is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.