The rate list you turn around on the counter
Retailer OS is the customer's side of a small shop: your items and your prices, in large type, meant to be read at arm's length and upside down by somebody standing on the other side of the counter.
A shopkeeper asked what something costs either remembers, or hunts through a book, or guesses. A shop carrying three hundred lines — a pesticide dealer, a hardware counter, a medical store — cannot hold all of it in his head, and the guess is where an argument starts. This is the screen he turns around instead.
It shows prices and nothing else. What the goods cost him, what he makes on them, the day's takings, and what any customer still owes are never on this screen. That is not a matter of what the screen chooses to display: the server returns only names and prices to it, so there is nothing there to reveal even if somebody went looking.
It reads from the same list of items kept in Meri Dukan, so there is nothing separate to maintain. Change a price once, in Saaman, and the rate list a customer sees changes with it.
A shop with many lines gets a search box; a shop with a handful does not, because a search box above twelve items is a shop's whole stock made harder to read. Either way the customer finds a price in one action.
It is part of Meri Dukan, which is part of the Laisha subscription, and carries no separate price. The shop ledger and this screen open together.
What it is. The customer-facing half of Meri Dukan: a clean rate list of what the shop sells and what it costs, searchable, with nothing of the shopkeeper's business on it.
When to open it. Whenever a customer asks what you have and what it costs — across the counter, or sent ahead on WhatsApp.
Have ready.
Step by step.
What it will not do. It displays; it does not record. Sales, credit and costs all live in Meri Dukan, and this is deliberately the one screen you can hand to somebody else.
A customer asks what a particular item costs while three other people are waiting.
What goes in:
What comes out:
That absence is the feature. A rate list built from the same products the shopkeeper costs his margins with must not show those margins, and this one cannot: the customer view is constructed field by field from what is allowed, not by hiding what is not.
No. The customer view is built from a fixed list of fields that are allowed to appear — the name and the price — rather than by taking the full product and removing things. A field that is not explicitly permitted cannot leak, and there is a test that fails if cost price, margin or margin percentage ever reach this screen.
Open Retailer OS and hand the phone over. The products come from what you entered in Meri Dukan, so there is nothing separate to maintain, and the search box makes it usable in a shop with hundreds of lines.
No. There is one product list. Meri Dukan's Saaman is where you enter and price things; Retailer OS is the same list shown the way a customer should see it.