Card States

A Kanban card’s state shows where it sits in the replenishment lifecycle. Knowing card states lets you see at a glance what has been scanned, what is on order, and what has been received.

The 9 Operational States

State	Description	Typical Trigger
AVAILABLE	Card is on the shelf; item is in stock.	Item received and restocked.
REQUESTED	Card has been scanned; reorder signal sent.	Worker scans card at the reorder point.
READY	Order is prepared but not yet placed.	Manager reviews and approves.
INPROCESS	Order has been placed with supplier.	Purchase order sent.
FULFILLING	Supplier is actively fulfilling the order.	Supplier confirms shipment.
DELIVERED	Item has arrived at the facility.	Delivery confirmed.
RECEIVED	Item checked in and verified.	Worker confirms receipt.
SHELVED	Card returned to its storage location.	Item restocked; card back on shelf.
CANCELLED	Order was cancelled before completion.	Manager or system cancels.

Practical Flow for Most Operations

In streamlined workflows, some states are bypassed. The typical flow is:

AVAILABLE -> REQUESTED -> INPROCESS -> DELIVERED -> SHELVED

READY and FULFILLING are frequently skipped when orders go directly from REQUESTED to INPROCESS. They are reserved for future Kanban Loops functionality.

As a Shop Worker (Sam)

Your job is to scan cards when the reorder bin is empty. Scanning moves the card from AVAILABLE to REQUESTED. That is all you need to do — the Procurement Manager (David) takes it from there.

As the Procurement Manager (David)

You see all REQUESTED cards in the Order Queue. After placing an order with the supplier, cards move to INPROCESS. When goods arrive, the Receiving Clerk (Keisha) moves them to RECEIVED and then SHELVED.

Mapping to Domain Model States

The user-facing labels above correspond to canonical domain model states used by the Arda backend. This mapping resolves the terminology difference between what you see in the product and what the system tracks internally.

User-Facing Label	Domain Model State	Notes
(card just created)	`AVAILABLE`	Visible only while editing a new card for the first time, before it is saved.
REQUESTED	`REQUESTING`	Card has been scanned / added to the order queue; demand signal is in transit to the procurement station.
INPROCESS	`REQUESTED`	Procurement has accepted the request and is adding it to a supplier order.
INPROCESS	`IN_PROCESS`	Supplier order has been submitted; materials are expected from the supplier.
READY	`READY`	Materials have arrived at the procurement station but have not yet been sent to the requesting station. (Reserved for future Kanban Loops functionality.)
FULFILLING	`FULFILLING`	Materials are in transit from the procurement station to the requesting station. (Reserved for future Kanban Loops functionality.)
SHELVED	`FULFILLED`	Materials have been received at the requesting station and the card is back on the shelf.
CANCELLED	—	Order was cancelled before completion; no corresponding domain lifecycle state.

MVP note. In the current MVP0/MVP1 release, the READY and FULFILLING states are not surfaced in the UI. The procurement workflow moves cards directly from IN_PROCESS (or even REQUESTED) to FULFILLED when the user receives or completes an order. The DELIVERED and RECEIVED labels shown in some UI surfaces correspond to intermediate steps within this simplified path.

For the authoritative domain model definition of these states and their lifecycle transitions, see Kanban Cards — Domain Model.