Make submitted orders visible
Show new app, web and assisted orders as a queue the supplier team can review.
Use submitted, accepted, invoiced, paid, cancelled and pending-review context to keep customer orders visible without treating a status badge as the whole workflow.
Order submitted
Staff reviews status
Exceptions remain visible
Next action is clearer
Real Porosi product screens. Customers can order on iOS, Android or the web, and submitted orders appear in the supplier dashboard for review.
Wholesale teams need to know where each customer order sits, but status is only useful when the underlying product, price, quantity and note context is still easy to inspect.
Show new app, web and assisted orders as a queue the supplier team can review.
Accepted, invoiced, paid and cancelled labels must tell staff what has happened without burying the order detail.
Pending edits, unclear notes and exception-heavy orders must stay reviewable before the next team relies on them.
Status must help finance understand what is ready for invoice work while leaving staff judgement in place.
A buyer builds the order from the products, prices and history available to their account. When they press submit, submitted orders, accepted orders, invoiced orders and paid orders stay with the order, so the supplier can check it without retyping a call, email or message.
The supplier team receives one order record with submitted orders, accepted orders, invoiced orders and paid orders. Staff can check exceptions before picking, delivery or invoice preparation begins.
The label exists but staff still search for context.
The status sits beside customer, product, price and note detail.
Unclear orders look tidy because they have a label.
Pending edits and unusual detail stay available for staff checks.
Operations and finance ask whether the order is ready.
Status and context help staff decide what must happen next.
Use current customer orders at different states so the team can judge whether status visibility reduces follow-up and uncertainty.
Include submitted, accepted, invoiced, paid and cancelled examples where possible.
Check whether pending edits and notes remain visible beside status labels.
Ask what fulfilment and finance can trust from the status view.
Wholesale teams need to know where each customer order sits, but status is only useful when the underlying product, price, quantity and note context is still easy to inspect.
Confidence that submitted orders are received by the supplier. A clear route for repeat orders, notes and order history.
A visible queue of submitted, accepted, invoiced, paid and cancelled orders. Status filters that do not hide changed lines, notes or finance questions.
Use current customer orders at different states so the team can judge whether status visibility reduces follow-up and uncertainty.
Bring submitted, accepted, invoiced and changed orders so the demo shows whether status helps the team act.