> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Commerce Orders Without Oracle ERP Cloud Sales Order, Oracle ERP Cloud > Commerce orders that never created a Oracle ERP Cloud Sales Order. Each row is a revenue-leak investigation. How to read it, why it matters, and how to act... **Metrics type:** [Cross-Platform Metrics](/nerve-centre/overview#metrics-types-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > Commerce orders that never created a Oracle ERP Cloud Sales Order. Each row is a revenue-leak investigation. ## At a glance > Commerce-platform orders that have not produced a corresponding Oracle ERP Cloud Sales Order. Each row is a potential revenue-leak investigation. The Unmapped Customer subset of the [revenue gap breakdown](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-detailed-breakdown), promoted to its own card because it is the most actionable bucket. | | | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Commerce orders in the window where the integration did not produce an Oracle Sales Order, broken down by failure reason: Unmapped Customer (most common), Unmapped Item, Tax Calculation Failed, Pricing Lookup Failed, Currency Mapping Missing, Other Validation Error. | | **Tax treatment** | n/a (integration-error universe). | | **Currency** | Order amount in transaction currency. | | **Time window** | Real-time snapshot. | | **Alert trigger** | `>0 unmapped orders` (every unmapped order is real revenue at risk) | | **Roles** | owner, finance, operations | ## Calculation Calculated automatically from your Oracle ERP Cloud 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 Fortune 500 industrial distributor on Oracle ERP Cloud with Salesforce Commerce Cloud B2B and Adobe Commerce. Snapshot 14 Apr 26. | Failure reason | Order count | Total \$ at risk | | ------------------------ | ----------- | ---------------- | | Unmapped Customer | 22 | \$384,000 | | Unmapped Item | 14 | \$128,400 | | Tax Calculation Failed | 8 | \$48,200 | | Pricing Lookup Failed | 6 | \$24,800 | | Currency Mapping Missing | 2 | \$14,200 | | Other Validation Error | 4 | \$18,400 | | **Total Unmapped** | **56** | **\$618,000** | Five things to notice: 1. **22 Unmapped Customer rows = \$384K stuck.** Top priority: send the Customer Hub team the customer-key list. Each customer is a 1 to 3 day mapping job; if the team has bandwidth they could clear all 22 in 5 to 10 working days. 2. **14 Unmapped Item rows.** A new product line launched on Adobe Commerce was not yet synced into Oracle Item Master. Operations needs to set up the items in Oracle (cost, lead time, BU assignment) before the SO can import. 3. **Tax Calculation Failed (8 orders).** The E-Business Tax engine could not find a rule for the customer's shipping jurisdiction. Often a new state / country where the merchant has not yet registered. Either suspend new orders to that jurisdiction or update the tax registration + rule set. 4. **Pricing Lookup Failed (6 orders).** Custom contract pricing on the customer's account expired or has not been renewed. Pricing Operations to renew the contract. 5. \*\*The $618K is real revenue at risk.** Without intervention, these orders will not become Oracle SOs, will not AutoInvoice, will not become GL revenue, and may eventually expire from the integration's retry queue. At Fortune 500 scale, $618K per snapshot translates to \$1M+ per quarter if unaddressed. ## Sibling cards merchants should reference together | Card | Why pair it with Commerce Orders Without Oracle SO | | ---------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- | | [Revenue Gap vs Commerce](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-vs-commerce) | This card is the Unmapped Customer / Unmapped Item subset. | | [Revenue Gap, Detailed Breakdown](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-detailed-breakdown) | Per-row drill-down across all gap reasons. | | [Open Sales Order Value](/nerve-centre/kpi-cards/oracle-erp/oerp-open-so-value) | The forward book that this card threatens to undermine. | | Commerce-platform total order count cards | The numerator of the gap. | ## Reconciling against the vendor's own dashboard **Where to look in Oracle ERP Cloud:** > **Order Management → Process Order Import** (failed-import log) > **Oracle Integration Cloud (OIC) → Monitoring → Failed Instances** (if OIC orchestrates the inbound) > **OTBI → Order Management Real Time** with custom filter on Order Source = the connected commerce platform AND Status = 'Error' The Process Order Import error log shows each failed inbound, but stops at "what failed in Oracle". This card adds "what was the originating commerce order" so the merchant can act. **Why our number may legitimately differ:** | Reason | Direction | Why | | ------------------------ | --------- | --------------------------------------------------------------------------------------------------------- | | **Retry queue cadence** | Either | OIC retries failures on a configurable schedule. Card snapshot may include items currently being retried. | | **Test order exclusion** | Either | Configurable; default excludes commerce-platform test flag. | **Cross-connector reconciliation:** | Card | Direction | Notes | | ---------------------------------------------------------------------------------------------------- | --------- | --------------------------------------- | | Commerce-platform order count | Numerator | Card is the integration-failure subset. | | [Revenue Gap, Detailed Breakdown](/nerve-centre/kpi-cards/oracle-erp/revenue-gap-detailed-breakdown) | Same | Drill-down for context. | ## Known limitations / merchant FAQs **Why is Unmapped Customer the most common reason?** Because customer onboarding is a separate, often-manual workflow in Fortune 500 governance. Sales adds a B2B customer in the commerce platform; the Customer Hub team has to mirror that customer in Oracle (with required-field validation, credit-limit setup, terms assignment). The lag is structural. **Can the integration auto-create customers?** Yes if configured, but most Fortune 500 implementations deliberately disable auto-create for governance reasons. Customer master data is a controlled object in finance. **Unmapped Item, when does this happen?** New product launches that were created in commerce but not yet in Oracle Item Master. Reverse direction is rare (Oracle Item Master is usually source of truth). **Tax Calculation Failed, what to do?** Either update the E-Business Tax rule set to cover the new jurisdiction, or block customers from new jurisdictions until tax registration is complete. Working with legal / tax counsel. **OIC vs Vortex IQ for resolving these?** OIC orchestrates the integration and exposes raw error logs. Vortex IQ reads both sides (commerce + Oracle) and surfaces in Controller-readable language with action owners. Complementary. **How does this differ from Oracle's own failed-import log?** Oracle's log shows the failure event; this card shows the business impact (which customer, which order, what dollar amount). Same facts, different framing. *** ### Tracked live in Vortex IQ Nerve Centre *Commerce Orders Without Oracle ERP Cloud Sales Order* is one of hundreds of KPI pulses Vortex IQ tracks across Oracle ERP Cloud 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](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.