Inventory and fulfillment

Inventory records stock by product variant and warehouse. Quantity on hand, reserved quantity and reorder point give Warehouse Operator a practical starting position for each SKU. A meal line identifies the variant and portion count purchased. Comparing the order line with the stock record helps the team decide whether a box can be prepared or needs an exception. Catalog Manager should know when a listed item approaches its reorder point so promotion choices reflect available stock.

Fulfillment Events records the shipping steps for an order, with carrier, label, tracking and event type. The order separately tracks fulfillment status. These records let the team distinguish a label from a picked package and a shipped package from a delivered one. Customer Service Rep can give a customer the latest recorded event rather than assuming that fulfillment means arrival.

• Stock. Inventory keeps the warehouse position for each product variants record.
• Demand. meal orders and meal lines show which purchased variants and portions need work.
• Delivery. fulfillment events captures labels, packing, transit, delivery and exception events for an order.

Merchant Owner and Warehouse Operator agree which warehouse codes are in use, when a quantity is reserved, and who can correct an on-hand figure. The team should reconcile stock counts before opening a new catalog to orders. A negative or stale availability figure can turn a normal order into a service issue. Reorder points help prioritize checks, but they need a local replenishment practice outside the order record.

Shipping Methods defines the options offered to a buyer and may include a carrier, price and estimated transit days. Warehouse Operator should know which carrier service corresponds to each method before labels are produced. Customer Service Rep needs the tracking number and event time when answering delivery questions. The team should decide who updates an exception, returned package or failed label attempt.

A customer buys a dinner variant and a nonshippable add-on. Warehouse Operator checks the meal lines, shipping requirement and stock for the saleable variant. The operator records the appropriate fulfillment event and confirms that the order’s fulfillment status follows the physical work. Customer Service Rep then checks the carrier and tracking details before telling the buyer the package is in transit. If delivery fails, the exception event stays attached to the original order.

For a partially completed order, inspect the served portions on each meal line and the order’s partial fulfillment state. Do not mark the whole order delivered because one label was purchased. The remaining work should stay visible until the actual event history supports completion.

• Orders awaiting fulfillment — Orders with work still open, grouped by fulfillment state.
• Low stock variants — Warehouse positions near their reorder point.
• Meal Orders workspace — The selected order and its customer context during a delivery question.

Follow payment and release into delivery, then customer resolution when an exception or refund is needed.