At a glance
Distribution of orders by financial status (statusfield). Adobe Commerce uses configurable status labels layered on top of thestatemachine; merchants commonly extend the default list with custom statuses (e.g. “Awaiting Wire Transfer”, “Net-30 Pending”, “Sales Approved”). The card surfaces the active distribution so finance and operations can audit the workflow.
Calculation
Worked example
A B2B-heavy industrial supply distributor on Adobe Commerce 2.4.6. Custom statuses configured per the merchant’s workflow. 30-day window ending Monday 4 May 26. Status distribution:
What this is telling operations and finance:
- Custom workflow visibility. This merchant has 7 active status labels mapped onto 5 canonical states. The card surfaces both, so operations can audit which custom labels are in use.
- 31% of revenue is in “Sales Approved” but not yet shipped. This is the operational pipeline; warehouse should prioritise.
- 12.4% in “Awaiting Wire Transfer” + 18.6% in “Net-30 Pending” = 31% of revenue waiting on payment. For B2B distribution this is normal (net-30 invoicing); the merchant’s cash-flow forecasts depend on aging this pipeline.
- 4.4% “Holded for Credit Check” ($44k) is the credit-review queue. A back-office task; operations should ensure this doesn’t accumulate.
- 1.2% “Canceled” is in the healthy range; cross-check Cancellation Rate for the trend.
- Cross-checking Order State Distribution which shows canonical states only: the same data appears as 4 buckets there (
processing,pending_payment,complete/closedcombined,canceled,holded). The 7-status custom view here is more useful for operations workflow tracking; the canonical view is more useful for cross-platform comparison.
Sibling cards merchants should reference together
Reconciling against the vendor’s own dashboard
Where to look in Adobe Commerce Admin:Sales > Orders with the Status filter shows per-status counts. The grid total updates as filters apply.
Stores > Configuration > Sales > Sales > Order Status lists all configured statuses and their state mappings.
Reports > Sales > Orders with date range and grouping by status (Adobe Commerce 2.4.4+).For workflow audit:
Stores > Order Status lists every status, custom label, and which state it maps to.Why our number may legitimately differ from Admin:
Cross-connector reconciliation (when these connectors are connected for this merchant):
Known limitations / merchant FAQs
What’s the difference between status and state in Adobe Commerce?state is the canonical 8-value lifecycle (new, pending_payment, processing, complete, closed, canceled, holded, payment_review). status is a configurable label that maps to a state. A merchant can have 20 custom statuses (“Sales Approved”, “Awaiting Wire”, “Pick Started”, “Quality Check”) all mapped to state = processing. The card surfaces both.
Adobe Commerce vs Magento Open Source: difference?
Both editions have configurable status. Open Source merchants typically have fewer custom statuses (no built-in B2B workflows); Adobe Commerce paid edition’s B2B Companies module may add approval-flow statuses (Awaiting Approval, Approved, Rejected).
My status names look weird, why?
The card preserves whatever the merchant has configured in Stores > Configuration > Sales > Order Status. Custom names persist; abbreviations and historical labels appear here.
Why are pending_payment orders worth tracking?
On B2B-heavy stores they represent net-30 PO pipeline (genuine future revenue). On consumer stores they may indicate gateway issues. The financial_status card lets you distinguish: a B2B-tagged custom status like “Net-30 Pending” is healthy pipeline; a status like “Stripe Failed” sitting in pending_payment is a gateway problem.
My multi-store, can statuses differ per Store View?
Adobe Commerce statuses are global, not per-Store-View. A status defined for the consumer Store View applies on all. For per-Store-View routing, use Customer Group filtering on rules instead.
A custom status was renamed; do historical records update?
Adobe Commerce status changes apply going forward. Historical orders keep the label they had at order time. The card sees current labels, so a rename creates a brief “two labels for the same state” period. Most stabilises within 7-14 days.
Why do complete and closed look similar?
complete = order shipped and invoiced; closed = the merchant has closed the order (typically because it’s fully refunded or no further action expected). On many stores they look similar; on stores using Adobe RMA module, closed may dominate post-RMA.
Why does the card include cancelled orders in the distribution but other cards exclude?
This card is auditing the workflow distribution; cancellations are part of that. Other cards (Total Revenue, AOV) exclude cancellations because they’re not real revenue.