At a glance
| What it counts | Computed by the connector engine from the upstream data feed; see the worked example for a representative reading. |
| VAT / tax treatment | Inclusive of tax by default; ex-tax variant available where the connector exposes it. |
| Shipping | Per merchant configuration; check connector settings for current treatment. |
| Discounts | Already deducted from order totals; gross-discount metrics are tracked separately. |
| Refunds | Excluded from period totals; refund rate is tracked separately. |
| Cancelled / voided orders | Excluded from period totals. |
| Currency | Aligned to merchant primary currency, FX-converted at order time for multi-currency stores. |
| Channels / sources | All channels included by default; channel-specific filtering is configurable per profile. |
| Time window | 30D |
| Alert trigger | - |
| Roles | owner, finance |
Calculation
Calculated automatically from your SAP 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 representative reading of this metric for a typical merchant. The card reports the current period value alongside a comparison against the previous period. Cross-reference the siblings below to triangulate cause when the value moves outside expected range.Sibling cards merchants should reference together
Sibling cards live in the same connector hub. Browse the connector index for related metrics in the same category.Reconciling against the vendor’s own dashboard
Where to look in SAP’s own dashboard: The SAP platform dashboard surfaces this metric (or its components) under the relevant report section. Confirm period boundaries and filter settings match the Vortex IQ profile to reconcile cleanly. Why our number may legitimately differ from the vendor’s: The Vortex IQ figure may differ from the vendor dashboard because of period boundary differences (Vortex IQ uses 30-day rolling by default), time-zone alignment, or filter scope. Match those settings to reconcile. Cross-connector reconciliation: If this card has counterparts on other connectors, add them to the field map’sper_card.<card_id> block under one of: same_metric_on (definitional twins on other platforms), reconciles_with (real reconciliation when same merchant has both connected), or internal_identity (mathematical identity within this connector). Then regenerate.