Statuses

Why statuses matter

Statuses drive routing, automation, and reporting.

Use them as decision signals: they should tell a user what can happen next, what is blocked, and whether the record still needs attention.

Shared patterns

Visual emphasis

Informational states use a calm information treatment. Warnings, overdue work, errors and operational failures use amber attention treatments, with stronger emphasis for the most urgent state and an explicit text label alongside colour. Red treatments are reserved for destructive actions and their confirmation surfaces.

Facts, states and actions

App pages distinguish ordinary facts from operational states:

• Channel identity is an unboxed wordmark or link. Its destination, external-link indicator and keyboard focus remain available; actual controls retain their button treatment. The public website uses the same borderless treatment. Amazon uses the supplied lowercase SVG wordmark with an orange smile; its lettering follows the surrounding theme surface. Accessible names still say Amazon. Discogs uses the supplied SVG wordmark, including its record detail, in theme-aware monochrome with its accessible name preserved. Shopify uses the supplied bag-and-wordmark SVG: the green bag and white S stay unchanged while its lettering follows the theme. WooCommerce uses the supplied purple Woo SVG mark; accessible names and product labels still say WooCommerce. Website uses a custom cut-paper SVG wordmark in the existing theme-aware plum colours, without a separate W icon. Its accessible name remains Website. POS uses a custom uppercase Counterform SVG wordmark in the existing theme-aware teal colours, retaining its accessible POS name. These visual changes do not change connection or built-in/manual order behaviour.
• SKUs, record IDs, stock links, category/type labels, permission summaries and routine counts use quieter text. On Listings, offer settings remain visible metadata rather than a second success badge. Unknown, disabled and failed verification still mean different things.
• List-row states and detail At a glance states use bold, theme-aware text without a pill border, fill or shadow. Warnings retain a decorative warning icon and urgent replies use stronger weight. Other detail-page badges are unchanged. Payment and fulfilment remain independent on orders; unread/reply cues, publishing/reconciliation warnings, stock shortages and blocked actions are not collapsed into one status.
• An attention-worthy metadata value, such as an unlinked listing, retains its explicit text and an amber warning indicator. Colour is never its only cue.
• Media previews, clean scans and successful Stock matches use quieter text. Processing, unknown scan results and failures use bold list-state text; warnings and failures retain their explicit labels and warning icons.

Messages list counts read 3 unread, not an unexplained number. Stock's Live · 2 Channels list link is underlined, retains keyboard focus and opens the same exact live-listings scope. Navigation counters, filter chips, buttons, selection controls and detail-page badges outside At a glance keep their existing treatment.

Mobile facts remain grouped without a second bordered card inside each row. Prices, totals and available quantities are emphasised; timestamps are smaller secondary information. At a glance summaries use open spacing rather than a box full of pills; themes may retain a borderless backdrop for readability over gradients. Filters, actionable links, counts and permission information remain accessible; these presentation changes do not change permissions or workflow rules.

Every At a glance summary names its facts with quiet labels beside the existing values. Stock separates Stock, Catalogue and Listings; sales orders separate Order (when shown), Payment and Fulfilment; conversations distinguish Type, Latest event, Cancellation, Messages and Reply when those facts apply. Listing detail distinguishes Format, Stock link, Listing and Offers, while listing drafts label their state Draft. Other summaries identify their Status, Type, Order or Connection as appropriate.

Channel wordmarks remain standalone. Each label stays grouped with its value when facts move onto another line; long values can still wrap on small screens. Optional facts hide their labels too, including hidden Stock warnings, listing offer signals and internal record IDs. Existing links, warning emphasis, reply timers and accessible descriptions are unchanged. Linked records and list rows are outside this summary-label treatment.

The internal data-cw-meta marker is opt-in presentation for a fact, not a state inferred from its colour. It survives controller class updates. It must not be applied to primary state, safety warnings or filter controls simply to make a page quieter.

The separate data-cw-list-state marker opts a list-row state into bold text. Detail forms use data-cw-summary-state only within At a glance, including the shared listing-draft summary. The two markers share the same presentation; neither belongs on buttons, filter controls or ordinary data-cw-meta facts. Stock catalogue state, readiness and listing state remain independent. The separate Linked records strip is unchanged. Tone classes retain their meaning; the text foreground is adjusted for an unfilled surface rather than reusing a filled badge's foreground. Saturated green theme surfaces use darker, near-neutral state text. State labels, reply timers, tooltips and accessible descriptions are preserved.

Transitional states

Short-lived processing states should auto-resolve.

Terminal states

Terminal states require explicit user or system action to exit.

Naming

Use explicit, business-readable terms and avoid overloaded labels.

Good status wording should:

• describe the business state, not the implementation
• avoid version or release wording
• stay consistent across list pages, detail pages, filters, and docs
• distinguish active work from historic or terminal records

Common status families

• Draft / Ready / Submitted / Live for listing preparation and publishing.
• Open / Partially delivered / Delivered for purchase-order receiving.
• In progress / Dispatched / Delivered / Cancelled for sales orders.
• Active / Inactive for master data such as stock items, suppliers, groups, locations, and policies.

Channel statuses

Channel connection and listing status meanings are documented in Listings & Channels → Statuses.

Inventory statuses

Inventory status and signal meanings are documented in Inventory → Statuses.

Sales statuses

Order and fulfilment status meanings are documented in Sales → Statuses.