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

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.