Store dashboard and order statuses #

This page is for shop owners and administrators who run the built-in shop. The Store tab of the administration now opens a dashboard (shop/dashboard) that shows on one page what used to need a guide to piece together: how the shop is doing, which orders need attention and how checkout is configured. The same release adds an order status for every stage of an order's life.

Open it #

1. Sign in to the administration.
2. Click Store (the tab was called Webshop before 30 September 2026).
3. The dashboard is the first entry of the shop menu. The order list stays one click away in the same menu and is linked from the dashboard wherever orders are shown.

It needs the shop / administrate policy, like the order list and the statistics. Titles and texts are translated (German included).

What is on the page #

Every figure comes from a fixed set of about twenty aggregate statements whatever the size of the shop, written without LIMIT or engine-specific functions, so it runs the same on Oracle, MySQL, PostgreSQL and SQLite. Totals use the arithmetic of the order list, so the numbers agree with it.

Order statuses for the whole lifecycle #

An installation used to ship three statuses (Pending, Processing, Delivered), so a shop that takes payment, ships parcels or handles returns had to invent its own. Fourteen more now come with every new installation and with the 6.0.15 database update. They are internal statuses (identifier below 1000), so they cannot be removed by mistake. Custom statuses start at 1000.

Grouped by stage: payment (Awaiting payment, Paid, Payment failed), fulfilment (On hold, Backordered, Packed, Shipped, Ready for pickup), the end of an order (Completed, Cancelled) and after it (Return requested, Returned, Partially refunded, Refunded).

The three helper methods tell code and the dashboard what each status means:

eZOrderStatus::finishedStatusIDs();          // no longer an open order
eZOrderStatus::noRevenueStatusIDs();         // brought in no money
eZOrderStatus::waitingForCustomerStatusIDs();// the shorter "waiting too long" limit applies

On the dashboard an order is open until its status is finished (not only until Delivered), so a cancelled or refunded order no longer waits in the list of orders to handle. Failed, cancelled and refunded orders count as orders but not as revenue in the totals, the average, the daily chart and the top products. Orders waiting for the customer are highlighted after the shorter limit. The status table lists the statuses in lifecycle order, says what each means and colours each by what it stands for: new, waiting for the customer, in progress, done, stopped or custom.

Upgrading an existing shop #

The seed data of every engine carries the new statuses (MySQL, PostgreSQL, SQLite clean data and share/db_data.dba). The 6.0.15 database update scripts (update/database/<mysql|postgresql|sqlite>/6.0/dbupdate-6.0.0-6.0.15.sql) add each status only when no status already has that number and leave the row id to the database, so a custom status you created keeps its row. If you already used one of the numbers 4 to 17 for a custom status, check the shop's order status list after the update.

Related pages #

• Order receipts, order list sorting, shop basket view name
• Administration navigation: the top node and tabs (the Store tab)
• Installer logs and seed data
• Behaviour changes, 16 to 30 September 2026
• Changelog 6.0.15
• Chronicle, 16 to 30 September 2026