Built for a real shop, in front of real customers
OrderAgent did not start as a product idea. It started because a flour and spice distributor was running an entire business out of a WhatsApp group, and every part of it that hurt was a part a computer could do.
Why it exists
The software existed. It just did not fit.
Order management is a solved problem — for businesses whose customers will log into a portal. Distribution is not that business.
A wholesale customer orders three times a week from the same short list. They are not going to install an app, remember a password, or browse a catalogue. They are going to send a message, because they already have their phone in their hand and they already know what they want.
So the choice was never between WhatsApp and a proper system. It was between WhatsApp with a notebook beside it, and WhatsApp with a system behind it.
What the group chat actually cost
- Every order typed twice — once by the customer, once into a book.
- Stock promised twice because two chats moved four minutes apart.
- Receipts judged by eye, with no way to spot the same screenshot twice.
- Invoices written in the evening, if there was an evening left.
- One phone that had to be in the room for anything to happen.
How it is built
Shipped in vertical slices, against live traffic
Each capability went out end to end and was used by a real shop with real customers before the next one started.
Nothing ships unproven
Every capability on this site has run against live WhatsApp traffic with real orders and real money. Where something is built but not yet observed in production, the documentation says so.
Failures are recorded, not smoothed over
A message WhatsApp rejected is shown as not delivered. A receipt you rejected stays in the order's history. The record is what happened, not what was supposed to.
The model is kept on a short leash
It classifies and it reads images. It never supplies a value that reaches a customer. That boundary is the single most important design decision in the product.
Locale is designed, not patched
Time zone, currency, postcode shape and payment vocabulary come from a country registry. Adding a country is an entry in it, not a change to how existing shops behave.
History is immutable
Prices, currencies and invoice contents are snapshotted where they are used. Changing a setting today cannot restate what a record from last month means.
Small on purpose
One shop's real workflow, understood properly, beats ten shops' assumed requirements. The customer list grows when the product deserves it.
Where we are
Early, and honest about it
OrderAgent runs a real distribution business today and has done for months. It is not a prototype, and the order, payment, invoice and delivery paths have all been walked end to end on live handsets.
It is also not a mature platform with a thousand customers. Onboarding is hands-on because it genuinely involves provisioning a WhatsApp number and loading a catalogue with you, and we would rather say that than build a signup form that implies otherwise.
If your shop looks like the one this was built for, the fit will be obvious within one conversation — and if it does not, we will say so.
Tell us about your shop
How orders reach you today, roughly how many a week, and which country. That is enough to know whether this is worth either of our time.