Orders and jobs are linked but distinct. An order is a transaction — what the customer bought, what they paid, where it ships. A job is a production unit — what the press makes, on what substrate, with what finishing, on what schedule.
PrintIntegrator handles both ends and connects them. When a customer pays, the order generates one or more jobs depending on product type and configuration. Each job carries the print-ready file, substrate selection, finishing requirements, and deadline.
Order lifecycle
- Cart → Payment → Order
- Order → Job(s) created in production queue
- Job → Preflight (auto, runs in seconds)
- Job → Press scheduling (operator-assigned or rule-based)
- Job → Printing → Finishing → Packing → Ship
- Order → Tracking number → Customer notification
Job status visibility
Customers see the order status: paid, in production, shipped, delivered. They don't see the production sub-states unless you choose to show them.
Internally, operators see every sub-state. Reports show where jobs stall (waiting at preflight, sitting at plate, finished but not packed) and which sub-states are bottlenecks.
Splitting and combining jobs
Single orders sometimes split across jobs (different finishing requirements; one item ships from warehouse A and one ships from warehouse B). Multiple orders sometimes combine into one job (gang-up runs for label rolls). The job manager handles both with operator overrides.
Customer reorder flow
When an order completes, the customer can reorder it as-is with one click. This is the killer flow for stationery, packaging, and any reorder-heavy category. The new order opens with all original specs; the customer adjusts quantity or modifies the design and submits.