Configurable Status Workflows

Give an example status lifecycle for Physical vs Service products.

The two types naturally differ. A Physical product might run Pending → Approved → Packed → Out for Delivery → Delivered — reflecting the pick-pack-ship reality of goods. A Service product might run Pending → Quoted → Scheduled → In Progress → Completed — reflecting that a service is booked, performed, and finished rather than shipped. Both are illustrative; each business…

The two types naturally differ. A Physical product might run Pending → Approved → Packed → Out for Delivery → Delivered — reflecting the pick-pack-ship reality of goods. A Service product might run Pending → Quoted → Scheduled → In Progress → Completed — reflecting that a service is booked, performed, and finished rather than shipped. Both are illustrative; each business defines its own status names and order per type. The point is that the same engine expresses two very different operational realities, because the statuses themselves are configured per product type rather than hard-coded.