An order that doesn’t fall through

Orders and invoices sent over WhatsApp kept falling through — and every lost order hurt the reputation.

The 30-second read

Orders and invoices scattered across WhatsApp chats were getting lost, and the cost reached customers and reputation.
Ahmed built ORDERS between the branches and the factory: every order has a visible status, every department a clear responsibility.
The app works, and it has become the basis of daily work between the branches and the factory.

02 / Before

An order in a chat — that might never arrive

When an order lives inside a chat, nobody clearly owns it. It gets read, forgotten, or buried under newer messages.

03 / The workflow

In ORDERS an order is not sent — it is logged. From that moment its status is visible to the branch, the factory and management alike.

Logged by the branchEach branch signs in with its own account and logs the order directly.
Awaiting preparationThe order appears on the factory board with its deadline.
In preparationThe responsible department is working on it, and everyone can see that.
Shipped · Ready for deliveryThe order closes with a clear status and stays in the log.

Daily stockBranch restocking orders, each with a shipping slot. Every branch knows what was shipped to it, and when.
Special ordersCustomer orders on a weekly calendar by delivery date — and any delay flags itself.
ReturnsEvery return gets a numbered voucher and its own confirmation track, separate from production and delivery.

04 / Where it stands

The app works, and it has become the basis of daily work between the branches and the factory.
Ahmed reviews orders during the day, at its end and again the next morning.
A factory board, separate access for branches and management, sound alerts, and a log that keeps every order.

Each order became a trackable workflow, with clear responsibilities for every department.