Share of orders by shipping status. The operations team’s read on how cleanly orders are getting out the door.
At a glance
A donut breakdown of Salesforce Commerce Cloud (SFCC, formerly Demandware) orders by shipping status, not shipped, part shipped, shipped, over the period, pooled across every site in the realm. SFCC tracks fulfilment on each order through its shipping objects and a shipping status, and this card rolls those into a share view. It is the operations team’s read on how cleanly orders are moving from confirmed to out-the-door, and a fast way to spot a fulfilment or warehouse stall.
Calculation
Calculated automatically from your Salesforce Commerce 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 Fortune-500 fashion retailer running on Salesforce Commerce Cloud B2C, four DTC sites and one B2B portal, fulfilling DTC from two regional warehouses and B2B from a dedicated trade DC. The 30-day window covers 14 Mar 26 to 12 Apr 26. Shipping statuses derived from order shipping objects, confirmed in Business Manager.
Three things to notice:
- The 7.6% not-shipped slice is the normal in-flight pipeline, until it grows. At any moment a healthy realm has orders confirmed but not yet dispatched, sitting inside the fulfilment SLA. The slice existing is fine. The signal is the slice growing while order volume stays flat, which means dispatch has slowed at a warehouse or a downstream export stalled. Read it together with Pending Orders (created/new/open): if both climb with flat orders, the drain has stopped.
- Part-shipped (4.0%) is mostly split and multi-warehouse orders. When a basket draws from two warehouses, or one line is in stock and another is on back-order, SFCC dispatches what it can and the order reads part-shipped until the rest follows. A brand fulfilling from multiple DCs always carries a structural part-shipped slice. A sudden jump points at a stock problem on specific SKUs, cross-check Low Stock Products and Out-of-Stock Products.
- B2B skews part-shipped and slow not-shipped, by design. Trade orders ship on scheduled releases against contractual lead times, so the B2B portal naturally carries a larger and slower-moving not-shipped and part-shipped share than DTC. Filter out the B2B
siteIdfor a clean read on DTC dispatch speed, which is the number that matters for customer-facing delivery promises. - No alert is configured on this card, and that is deliberate. The “right” shipping mix is contextual: it depends on warehouse count, split-shipment policy, and how much B2B scheduled volume the realm carries. A fixed threshold would fire constantly on a multi-DC realm. Operations reads the shape and its period-over-period drift, and leans on the Order Processing Backlog alert for the acute stall signal. Pair with Total Orders to read slices as absolute counts.
Sibling cards merchants should reference together
Reconciling against Salesforce Commerce Cloud
Where to look in Business Manager: SFCC’s admin tool is Business Manager, reached at a per-realm URL likehttps://<realm>.business.demandware.net. To verify this card, go to Merchant Tools, Ordering, Order Search and use the shipping-status filters, or open individual orders and inspect their Shipments detail, which shows each shipping object, its line items, and its dispatch state. For a reporting view, Merchant Tools, Site, Reports & Dashboards, Operations breaks orders down by fulfilment state.
Other Business Manager views that look like the same number but aren’t:
- Order status (
OPEN,COMPLETED, etc.): the order lifecycle, a different axis from shipping status. An order can beOPENand not shipped, orCOMPLETEDand shipped. - Reports & Dashboards, Sales: revenue, not a fulfilment-state count.
- Carrier / 3PL tracking dashboards: the downstream view of in-transit parcels, useful for delivery SLA but on the carrier’s data, not SFCC’s shipping objects.
Known limitations / merchant FAQs
What shipping statuses does SFCC track and how are they grouped here? SFCC derives an order’s shipping status from its shipping objects and their dispatch state. The raw values vary by API version and by how fulfilment integrations write back, so this card groups them into three readable buckets: not shipped (nothing dispatched), part shipped (some dispatched), and shipped (all dispatched). Open an order’s Shipments detail in Business Manager to see the per-shipment state. Is a large not-shipped slice a problem? Not on its own. A healthy realm always has confirmed orders in the in-flight pipeline awaiting dispatch within the fulfilment SLA. The concern is the slice growing while order volume stays flat, which means dispatch has slowed at a warehouse or a downstream write-back stalled. Read it with Pending Orders (created/new/open) and lean on the Order Processing Backlog alert. Why do I have so many part-shipped orders? Almost always split and multi-warehouse fulfilment. When a basket draws from two DCs, or one line is in stock and another is back-ordered, SFCC dispatches what it can and the order reads part-shipped until the rest follows. A brand fulfilling from multiple warehouses carries a structural part-shipped slice. A sudden jump points at a stock problem on specific SKUs, cross-check Out-of-Stock Products. Why does B2B skew the distribution? B2B trade orders ship on scheduled releases against contractual lead times, so they sit not-shipped or part-shipped far longer than DTC by design. A realm with a B2B portal carries a structurally slower shipping mix. Filter out the B2BsiteId for a clean read on DTC dispatch speed, which is what drives customer-facing delivery promises.
Why is there no alert on this card?
Because the “right” shipping mix is contextual: it depends on warehouse count, split-shipment policy, and how much B2B scheduled volume the realm carries. A fixed threshold would fire constantly on a multi-DC realm. Operations reads the shape and its drift, and uses the Order Processing Backlog alert for the acute stall signal. You can add a per-card alert on the not-shipped slice if your fulfilment model makes that meaningful.
My number does not match Business Manager. Why?
Usually write-back timing or grouping. (1) Write-back lag, the shipped slice depends on when your OMS / WMS or carrier integration writes dispatch back to SFCC; a lag inflates the not-shipped slice. (2) Grouping, this card buckets raw statuses into three; a Business Manager raw read is finer-grained. (3) Site-scope, Business Manager defaults to one site, the card pools the realm. Confirm all three before treating a gap as an error.
Does this measure delivery, or just dispatch?
Dispatch. SFCC’s shipping status reflects whether shipments have left the warehouse, not whether the parcel has arrived. For in-transit and delivery SLA, reconcile against your carrier / 3PL tracking dashboards, which carry the downstream delivery events. This card is the right tool for “are we getting orders out the door”, not “have they arrived”.