A tour of the screens
Today, orders, customers, catalogue, bot health and the settings behind them.
The dashboard is built for a phone first. Everything below works on a 360px screen, in one hand, standing up.
Today
The screen you open in the morning and check between customers.
- The approval queue — receipts waiting for your decision, newest first. This is the money loop, so it is at the top.
- The pipeline — how many orders sit at each stage right now.
- Low stock — products at or below their threshold.
- Anything needing you — alerts that a person has to resolve.
Orders
Every order, filterable by status and searchable by reference, customer name or phone number.
Phone search strips non-digits before matching, because owners type
012-345 6789 and WhatsApp stores 60123456789.
An order screen shows:
- The lines as they were frozen when ordered, not as your catalogue reads now.
- The full payment history, including rejected receipts. That history is the audit trail.
- Notes the customer sent with the order.
- Fulfilment controls, and Extend / Cancel where they are legal.
- The invoice, with View, Resend and Rebuild.
- A link to the conversation.
The conversation view
The full message history with that customer, in order, read-only.
Read-only is deliberate. Replying from a dashboard means watching two inboxes and answering from the one the customer is not looking at. You already have WhatsApp.
Outbound messages WhatsApp rejected are marked not delivered rather than hidden, so a message that never arrived does not look identical to one that did.
Customers
Everyone who has ever messaged you — including people who have never ordered, because they messaged you and that is worth knowing.
Each customer shows their orders, their lifetime spend, their saved address and their opt-out state.
Lifetime spend is money you approved, never the sum of order totals.
The address editor writes through the same code the bot uses when a customer sends their address, so the two can never store it differently. A blank field stores as empty rather than as a blank string, because the run sheet groups by area.
Catalogue
Products as cards, with a full editor behind each one — price, unit, stock, threshold, aliases, order limits, active state.
Cards rather than a table: seven editable columns do not fit a phone, and this is a phone-first product.
Search matches names and aliases, because the question you actually have is "which product owns this word?"
Alerts
Everything the system could not resolve on its own. Sorted needs-you first, then newest. See alerts and bot health.
Bot health
How the bot's day went: how many conversations it handled alone, how many needed a person, how often it had to ask a clarifying question.
Packing lists and run sheets. See packing lists and run sheets.
Settings
Bank details, payment QR, invoice header details, quiet hours, and your shop's currency and country.