These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Meal Prep / Subscription Box
- Features
- Meal orders
Meal orders
Keep each purchased meal line, customer, payment state and delivery state on one order.
OverviewOrders awaiting fulfillment×
Meal Prep / Subscription Box · Meal orders
New
Orders awaiting fulfillment
Start waits for the warehouse operator
| Record number | Placed at | Fulfillment status | Shipping method | Shipping address | |
|---|---|---|---|---|---|
| MO-28380 | 26 Oct | Unfulfilled | SM-5745 | SL-150 | |
| MO-33358 | 24 Oct | In progress | SM-1041 | SL-140 | |
| MO-58077 | 24 Oct | Partially fulfilled | SM-2229 | SL-140 | |
| MO-52462 | 15 Oct | Unfulfilled | SM-3733 | SL-140 | |
| MO-22854 | 19 Oct | In progress | SM-5972 | SL-130 |
6 of 6 records
SM-5745Meal orders · MO-28380
UnfulfilledPlaced at26 Oct
Shipping addressSL-150
What you can do
Work from the order record
Meal Orders is the operating center for a purchase. The order identifies the customer or guest email, storefront catalog, chosen shipping method and addresses. Meal Lines retain the purchased SKU, menu item, portions, unit price and discount. Customer Service Rep can answer what was ordered without reconstructing a basket from a current product listing. Warehouse Operator can see which lines require shipping and how many portions remain to be served or refunded.
The Meal Orders page brings order filters, a distribution by subscriber, record detail and a paginated list together. Staff can use that screen to find a specific order, inspect its detail and open the native record form. A customer asking about a delayed box should be identified by the order number before the team changes any status or starts a refund.
How the work is organized
- Purchase. meal orders ties the subscriber, catalog, shipping choice, addresses and order totals together.
- Contents. meal lines retains each purchased menu item and its portion, price and shipping details.
- History. operation receipts records order events, and related payment and fulfillment records add their own evidence.
What to agree during setup
Merchant Owner and Customer Service Rep agree which statuses mean an order is ready for warehouse action. Financial status, fraud status, fulfillment status and overall status answer different questions; one should not be used as a substitute for another. For example, an order may be open while payment is pending. Warehouse Operator needs a clear rule for when stock may be allocated and when a flagged payment should pause release.
The team should set a record-number convention and a routine for correcting customer addresses. A shipping address belongs to a service location; the team should confirm the chosen address before producing a label. Customer Service Rep needs a way to preserve the reason for cancellation and to follow the operation receipts when a customer disputes a change.
Check the handoff on an actual case
A subscriber orders a family meal and a side dish. The cart has two variant choices. After order placement, Customer Service Rep opens the order and checks its two meal lines, portion counts, catalog and shipping address. Finance Manager checks the payment evidence and financial status. Warehouse Operator sees the same order when preparing fulfillment and records the actual shipping step. A later customer question can be answered from the order, its lines and events rather than from a new copy of the catalog.
Run the same check for a guest order. The guest email remains available even without a subscriber reference. Staff should keep the order number as the anchor for support and avoid attaching the wrong subscriber history simply because an email looks familiar.
What your team sees
- Meal Orders workspace — Filtered orders with subscriber context and a detail panel for the selected record.
- Orders awaiting fulfillment — Purchases still needing warehouse work.
- Open meal orders board — Overall order state for customer care and ownership checks.
Follow the work through
Read order intake, payment and release and customer resolution for the full order path.
What it keeps track of
Data model- Meal orders
- Represents one customer order for meal boxes, used to track payment, fulfillment, and status.
- Meal lines
- Represents one menu item within an order, including portions and price, used to fulfill and bill it.
- Operation receipts
- Logs one event or action taken on an order, used to audit what happened and when.
- Subscribers
- Represents a customer who shops or subscribes, holding their contact info and order history.
- Service locations
- Represents a shipping or billing address, used to deliver orders and bill customers correctly.
- Carts
- Represents an in-progress shopping cart, used to hold items a customer hasn't checked out yet.
- Payment evidence
- Records one payment attempt or transaction detail, used to verify and audit payments on an order.
- Fulfillment events
- Logs a shipping step for one order—label, tracking, delivery—used to trace where a package is.
Who uses it
Permissions- Customer Service Rep
- Follows the buyer's case.
- Warehouse Operator
- Works delivery.
- Finance Manager
- Checks payment or refund evidence.
- Merchant Owner
- Owns the release policy and exceptions.
Set up Meal Prep / Subscription Box your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.