- Revenue Gap vs Commerce. The dollar gap between commerce-platform total revenue (Shopify Plus, Salesforce Commerce Cloud, SAP Commerce Cloud / Hybris, Adobe Commerce, BigCommerce) and SAP S/4HANA Cloud GL-booked revenue, broken down by reason: Sales Documents stuck in approval, Billing Documents Pending (the Sales-Document-to-Billing-Document conversion delay, often 7 to 30 days for B2B Net-30 terms), Customer master record mismatches (a commerce customer with no SAP Business Partner record), Material Master gaps (a commerce SKU launched before its Material Master was created in SAP), and Company Code routing errors (an order routed to the wrong legal entity). At enterprise scale, a 3 to 8% gap on a 5B run-rate is 400M of trapped revenue the Finance team has not previously diagnosed at this granularity. The cross-stack visibility is the value: SAP knows what arrived; Vortex IQ knows what was placed and never arrived.
- Dead Stock with Active Ad Spend. The cross-channel kill shot. Materials sitting in SAP Inventory Management (transaction MMBE for Stock Overview) with zero 90-day Material consumption AND active monthly ad spend in Google Ads, Amazon Ads, or Meta Ads. For Fortune 500 retailers and consumer-goods manufacturers with 200K to $2M / year of recoverable spend. The SAP Material Master (transaction MM03 for display) is the source-of-truth for the inventory side; the ad platforms’ product feed maps to the Material Number for the spend side. Vortex IQ is the join layer.
- Margin Erosion at the Material level. Per-Material margin compression alerts where unit margin has dropped >20 percentage points relative quarter-over-quarter, ranked by annualised dollar impact. SAP’s Profitability Analysis (CO-PA) module is the closest in-SAP equivalent and is enormously powerful, but requires significant Functional Analyst configuration; the Vortex IQ card operates on the GL Detail (table BSEG joined to Material Master) plus standard cost (table MBEW), so it is available without CO-PA configuration. For enterprise merchants with deep CO-PA already in place, Vortex IQ adds the cross-channel ad-spend join that even a fully configured CO-PA cannot deliver natively.
| Card | Class | Tier | Category | Chart |
|---|---|---|---|---|
| Days Sales Outstanding (DSO) | 🦸 Hero | hero | Receivables & Cash | gauge |
| Dead Stock Value | 🦸 Hero | hero | Inventory & Items | kpi |
| Gross Margin Percentage | 🦸 Hero | hero | Margin & Cost Intelligence | gauge |
| Inventory Aging | 🦸 Hero | hero | Inventory & Items | bar |
| Margin Erosion Alerts | 🦸 Hero | hero | Margin & Cost Intelligence | alert_table |
| Open Sales Document Value | 🦸 Hero | hero | Executive Command Centre | kpi |
| Revenue Booked into GL | 🦸 Hero | hero | Executive Command Centre | kpi |
| Revenue Gap vs Commerce | 🦸 Hero | hero | Executive Command Centre | kpi |
| Sales Documents Blocked on Inventory or Credit | 🦸 Hero | hero | Executive Command Centre | alert_table |
| Total Inventory Value | 🦸 Hero | hero | Inventory & Items | kpi |
| Commerce Orders Without S/4HANA Cloud Sales Document | 🔗 Cross-Channel | - | Cross-Channel: Revenue Reconciliation | alert_table |
| Dead Stock with Active Ad Spend | 🔗 Cross-Channel | hero | Cross-Channel: Revenue Reconciliation | alert_table |
| Inventory Sync Drift | 🔗 Cross-Channel | - | Cross-Channel: Revenue Reconciliation | alert_table |
| OOS with Open Sales Document Demand | 🔗 Cross-Channel | hero | Cross-Channel: Revenue Reconciliation | alert_table |
| Revenue Gap, Detailed Breakdown | 🔗 Cross-Channel | hero | Cross-Channel: Revenue Reconciliation | table |
| A/R Aging Detail | Non-Hero | - | Receivables & Cash | bar |
| Active Customers | Non-Hero | - | Customers & B2B | kpi |
| Average Landed Cost per Unit | Non-Hero | - | Inventory & Items | kpi |
| Average Sales Document Value | Non-Hero | - | Revenue & Sales Performance | kpi |
| B2B Payment Terms Mix | Non-Hero | - | Customers & B2B | pie |
| Cash Application Rate | Non-Hero | - | Receivables & Cash | gauge |
| Cash Applied Today | Non-Hero | - | Executive Command Centre | kpi |
| Cash Collected | Non-Hero | - | Revenue & Sales Performance | kpi |
| Company Code Health Roll-up | Non-Hero | - | Multi-Entity Dashboard | table |
| Company Code Performance | Non-Hero | - | Multi-Entity & Multi-Currency | table |
| Consolidated Revenue Trend | Non-Hero | - | Multi-Entity Dashboard | area |
| Credit Hold Spike | Non-Hero | - | Alerts & Anomalies | alert_table |
| Credit Memo Value | Non-Hero | - | Order Operations | kpi |
| Customer Churn Signals | Non-Hero | - | Customers & B2B | alert_table |
| Customer Credit Utilisation | Non-Hero | - | Customers & B2B | gauge |
| Dead Stock Threshold Breach | Non-Hero | - | Alerts & Anomalies | alert_table |
| DSO Increase Alert | Non-Hero | - | Alerts & Anomalies | alert_table |
| FX Currency Exposure | Non-Hero | - | Multi-Entity & Multi-Currency | bar |
| High-Value Overdue Invoices | Non-Hero | - | Alerts & Anomalies | alert_table |
| Intercompany Balance | Non-Hero | - | Multi-Entity & Multi-Currency | kpi |
| Inventory Carrying Cost | Non-Hero | - | Inventory & Items | kpi |
| Inventory Turnover Ratio | Non-Hero | - | Inventory & Items | gauge |
| Invoice Aging Summary | Non-Hero | - | Executive Command Centre | bar |
| Invoiced Revenue | Non-Hero | - | Revenue & Sales Performance | kpi |
| Landed Cost Variance vs Standard | Non-Hero | - | Margin & Cost Intelligence | bar |
| Low Stock Alerts | Non-Hero | - | Inventory & Items | alert_table |
| Margin by SKU | Non-Hero | - | Margin & Cost Intelligence | bar_horizontal |
| Margin Compression | Non-Hero | - | Alerts & Anomalies | alert_table |
| Open Sales Documents | Non-Hero | - | Order Operations | kpi |
| Orders on Credit Hold | Non-Hero | - | Receivables & Cash | alert_table |
| Overdue Invoice Value | Non-Hero | - | Receivables & Cash | kpi |
| Returns Count | Non-Hero | - | Order Operations | kpi |
| Revenue Booked Over Time | Non-Hero | - | Revenue & Sales Performance | area |
| Revenue by Company Code | Non-Hero | - | Revenue & Sales Performance | bar |
| Revenue by Currency | Non-Hero | - | Revenue & Sales Performance | bar |
| Revenue by Segment | Non-Hero | - | Revenue & Sales Performance | bar |
| Revenue Gap Spike | Non-Hero | - | Alerts & Anomalies | alert_table |
| Sales Document State Breakdown | Non-Hero | - | Order Operations | pie |
| Sales Document to Invoice Lead Time | Non-Hero | - | Order Operations | gauge |
| Top B2B Accounts by Revenue | Non-Hero | - | Customers & B2B | bar_horizontal |
| Top Customers by Revenue | Non-Hero | - | Revenue & Sales Performance | bar_horizontal |
| Top Findings Across Company Codes | Non-Hero | - | Multi-Entity Dashboard | alert_table |
| Top SKUs by Inventory Value | Non-Hero | - | Inventory & Items | bar_horizontal |
| Total COGS | Non-Hero | - | Margin & Cost Intelligence | kpi |
| Unpaid Invoice Count | Non-Hero | - | Receivables & Cash | kpi |
API_SALES_ORDER_SRV, API_BILLING_DOCUMENT_SRV, API_MATERIAL_DOCUMENT_SRV, API_BUSINESS_PARTNER, API_GLACCOUNTLINEITEM) for transactional reads, with OAuth2 or SAP Cloud Identity authentication. Refresh cadence is 15 minutes for posted GL data on standard workspaces; real-time event subscription is available where the merchant has SAP Event Mesh enabled. The S/4HANA Cloud OData APIs are dimension-aware in the sense that every line carries Company Code, Plant, Profit Center, Cost Center, and the relevant master data references; queryable but with rate limits configured per pod. Vortex IQ honours per-pod rate limits with adaptive back-off, queueing bulk reads off-peak. Note that legacy SAP ECC on-premise customers running BAPI / RFC integration are supported on a custom-engagement basis, with different freshness characteristics.
SAP Analytics Cloud (SAC) complementarity. SAC is SAP’s native analytics layer, deeply integrated with S/4HANA Cloud subject areas via Live Connection. Use SAC for pre-built financial dashboards, period-close reports, group-reporting consolidation packs, and S/4-native KPI tiles. Use Vortex IQ for the cross-stack views SAC fundamentally cannot show because the underlying data lives outside SAP. Both layers running side-by-side is the typical Fortune 500 SAP pattern: SAC for in-SAP truth, Vortex IQ for whole-stack truth. SAC’s strength is that it speaks the SAP semantic model (Company Codes, Plants, Profit Centers, Material Groups) directly; Vortex IQ’s strength is that it joins those SAP semantics to commerce-platform and ad-platform data which SAC has no native bridge to.
FAQ-style notes:
- NetSuite vs SAP S/4HANA Cloud, when to choose which? NetSuite for 200M revenue, single ERP footprint, simpler operations, faster time-to-value (~6 to 9 months). S/4HANA Cloud for $500M+ revenue with complex manufacturing, deep supply-chain integration, multi-Company-Code statutory consolidation, and ASC 606 / IFRS 15 sophistication. The ERP migration motion from mid-market (NetSuite, Sage Intacct) to enterprise (S/4HANA Cloud, Oracle ERP Cloud) is well-trodden; Vortex IQ supports all four with the same KPI catalogue framing.
- S/4HANA Cloud vs S/4HANA on-premise, do they share the same Vortex IQ connector? Yes, the OData API surface is largely shared. S/4HANA Cloud is the strategic forward-looking deployment; on-premise is supported with the same connector subject to the merchant exposing the OData services through SAP Gateway.
- SAP ECC, do you support it? Yes, on a custom-engagement basis. ECC’s BAPI / RFC integration is structurally different from S/4HANA’s OData; the connector requires SAP NetWeaver RFC SDK access on the merchant side. The card catalogue is the same; the integration plumbing differs.
- Multi-Company-Code consolidation, how does it affect Vortex IQ cards? Each Company Code is treated as a separate scope. Top-level group consolidated views apply Group Reporting elimination journals; per-Company-Code views show raw inter-co revenue. The dashboard filter respects the chosen scope.
- Subledger Accounting (SLA) rule customisation in S/4HANA, what to watch for? Custom Account Determination tables can route revenue or COGS to non-standard GL accounts, affecting the standard 4xxxxx revenue / 5xxxxx COGS range assumptions. Confirm Chart of Accounts mapping with the Functional Analyst during onboarding.
- Profitability Analysis (CO-PA) complementarity? If your account has CO-PA configured, the Vortex IQ margin cards align with CO-PA’s Material-level margin reporting. The Vortex IQ value-add is the cross-channel ad-spend join, which CO-PA cannot deliver natively. Use CO-PA for in-SAP margin sophistication; use Vortex IQ for the cross-stack waste detection (Dead Stock with Active Ad Spend, Margin Erosion with Active Ad Spend).
- T-codes I should know to read these cards? VA01 / VA02 / VA03 (Sales Document create / change / display), VBAK / VBAP (Sales Document tables, header and item), VBRK / VBRP (Billing Document tables), MM03 (Material Master display), MMBE (Stock Overview), MIRO (Logistics Invoice Verification), FB60 (vendor invoice), F-43 (clear customer), KE30 (CO-PA report execution). Most cards in this catalogue map to data that the Functional Analyst would access through one of these T-codes; Vortex IQ exposes the same data via the OData APIs and joins it across the stack.
- SAP Commerce Cloud (Hybris) integration, is that the same as the SAP connector? No, separate connector. SAP Commerce Cloud is the commerce-platform product; the SAP connector in this catalogue is the financial-ERP product (S/4HANA Cloud). Most enterprise merchants run both; Vortex IQ joins them with the commerce-to-ERP cross-channel cards.
- SAP Group Reporting (S/4HANA Cloud Finance) complementarity? Group Reporting handles consolidation, eliminations, and group-level reporting on the consolidated entity. Vortex IQ reads the per-Company-Code data and surfaces the consolidated view via the dashboard filter. For audit-grade group-reporting figures, Group Reporting is the source of truth; Vortex IQ is the operational telemetry layer that keeps the day-to-day view current and joined to the rest of the stack.