Eleven days, told honestly. Delivered on day four, paid on day eleven, and that is a good ending here.
No card to start. Nothing is charged automatically, ever.
Delivery lands on the 16th. The money lands on the 23rd. A single status has to pick one of those two dates, which leaves it describing the other one wrongly for seven days. So we keep two.
| Track | Thu 12 | Fri 13 | Sat 14 | Sun 15 | Mon 16 | Tue 17 | Fri 20 | Mon 23 |
|---|---|---|---|---|---|---|---|---|
| Fulfilment | Ready | Dispatched | unchanged | unchanged | Delivered | unchanged | unchanged | unchanged |
| Payment | Unpaid | unchanged | unchanged | unchanged | unchanged | unchanged | Awaiting verification | Settled |
Illustrative, and completely unremarkable. One order in a small Beirut shop, in the order it actually happened. The gaps are not delays, they are the business.
Nadia orders two bowls. Nothing about the next four days is unusual.
A governorate, a district, an area and a landmark. There is no postal code field anywhere in this software, because a Lebanese address does not have one. And a form that asks for it is a form that was written somewhere else.
Your courier, your arrangement, your rate. He never signs in to anything and nothing here asks him to change how he works. From this moment the order is dispatched and unpaid, and the screen says exactly that instead of calling it complete.
Two columns, on every row, in a list of three hundred, on a phone. There is no view in this product where they are one.
For four days the money for this order is on somebody else’s scooter.
Out with the Hamra run since 09:14, four parcels on the same trip, one of them yours. You can see where it is without phoning him. And the software will not call any of it revenue while it is out there.
Refusal at the door is not an exception here. It is one of six ordinary outcomes, in the middle of the page, where it belongs.
A refusal here is an outcome, not an error. Software that files it under exceptions is software that will eventually have you counting stock you do not own.
A refusal puts the bowls back on your shelf and the count says so before the parcel is even unwrapped. A breakage puts nothing back and records a loss that keeps this order’s number. One button with two labels is how a tired person holding a parcel gets it wrong.
Bowl, ceramic · on shelf 12 → 14. Sellable this afternoon.
Bowl, ceramic · on shelf 12. Nothing restored; a loss recorded against #10476.
Same parcel, same doorway, two different truths about your shelf. Collapsing them is how a shop overstates what it owns.
“Delivered is not paid, and nothing here will call this order finished until somebody has handed you the money.”
A rule this software operates under. Not a promise we are making.Cash, days late, partly in the other currency, handed over by a courier who has never opened this app. Built for exactly that.
Sometimes in the other currency. You record what actually arrived rather than what should have, and the difference keeps the name of whoever it came through. Here, Rami’s Friday run.
An order with one shipment delivered and one still outstanding never reads as done, however much you would like it to. Nothing in this product can be talked into calling it done either.
Verified against the count on Monday morning. Only now is this order closed, and only now is any of it yours. Illustrative figures.
Not one of these is called revenue anywhere in this product. Three of them are not your money yet, which is exactly why they are never added together.
What customers asked for.
Real, and unspendable.
Counted, not yet checked.
In your hand.
Illustrative. A sample month for a shop this size.
Eleven days, two tracks, and no moment where a screen said something that was not true. Take your own first order this afternoon and watch it happen with your own names on it.
Nadia has the bowls. You have nothing yet. Both are true, and one badge cannot say both.