Order Lifecycle and Production (Kanban)

An accepted marketplace quote creates a platform order. A print shop can also manage its own jobs through a separate order workflow. Their screens can look similar, but their mutation authority, commercial terms and readiness checks differ.

Production Architecture (Mermaid Flow)

Each check can block progression and identify the next action. The production decision is re-evaluated using current transaction facts. A readiness decision or board movement is not itself a machine command.

Live Kanban Experience (Live Sandbox)

The following illustrative simulation demonstrates moving cards. Its sample jobs and permitted interactions do not establish live permissions, credit overrides, machine integration or marketplace stage admission.

Order Workstations (Statuses)

The print-shop board groups related statuses into nine visual columns:

Column	Typical grouped statuses
Pending	Pending / awaiting approval / quote pending
Confirmed	Confirmed / approved / processing
Prepress	Preflight / prepress / plate making / proofing
Printing	Printing / in production
Postpress	Binding / finishing / quality
On hold	Work paused
Ready	Ready / completed / ready for pickup
Shipping	Shipped / in transit / delivered
Cancelled	Cancelled

These are board groupings, not a universal sequence for every product. Buyer order screens use the simpler Received / Completed / Cancelled summary. A fallback completion percentage is derived from status and is not machine-measured progress. WIP warnings support operator planning; they do not enforce API capacity limits.

Marketplace Stage Control

Marketplace production progression uses the canonical platform event sequence. Before printing and later stages, the checks include the payment release condition, file readiness, applicable preflight/proof resolution, verified production PDF/imposition evidence and production-information handoff. A print shop’s own-order status controls do not bypass these marketplace gates.

Machine and Shipping Updates

Use the actual recorded event and configured integration evidence. Neither a JDF/PrintTalk-compatible record nor a Kanban status guarantees that a RIP, Edge Hub or machine is connected or has started work. Shipment details are manually recorded under the supplier’s carrier arrangement; verify carrier status separately.

Estimated Processing and Delivery Times (SLA)

Check the order-specific estimate, production capacity and unresolved actions. This guide does not set universal prepress, production or shipping durations. File-based deadline calculations wait for required file completion; that date calculation is distinct from payment and production-release checks. A displayed estimate is not a guaranteed carrier commitment.

Use due dates, priority and hold information to plan work. A priority label does not promise a flashing-red alert, automatic rescheduling or a machine intervention.

Frequently Asked Operational Questions

Can I cancel an order while it is in the Preflight stage? Use the governed cancellation request workflow and check the current production policy and payment boundary. Moving a card is not a refund or an approval. See Cancellation Policy.

What happens if the PDF needs correction? Review the actual finding and request. Depending on the decision, the next action may be a revised PDF, proof approval or specialist review. A reupload or proof request must exist for the corresponding buyer action to appear; not every order automatically sends a repair message.

Where is the shipping tracking code entered? Use the permitted shipment update flow and check the saved carrier reference. The simulation does not establish a live drag-triggered popup or carrier booking service.

Related Operations