November 5, 2026English

From paper orders to one-click staging: how we rebuilt Kalia's order-to-delivery cycle with Kalia Flow

Kalia, a fast-growing apparel distributor, needed five days to turn an order into a delivery, mostly because of paper forms and manual staging. Kalia Flow, a mobile app plus an ERP built on one source of truth, gave back a day and a half to two days.

transformationoperationscase-study

Kalia is a women's apparel distributor in Egypt. It sells its brand to multi-brand retailers through a network of sales reps, and it is known for a wide product range, a large client base and steady year-over-year growth. But we felt its legacy system and its day-to-day operations were slowing that growth down, and in places halting it. From the moment a rep wrote an order to the moment the goods reached the shop, about five days went by.

Nobody was doing anything wrong. The process worked, and it had carried Kalia this far. But it was becoming outdated, and as the business grew, the gap between how Kalia operated and how fast it could grow kept widening.

What the old process looked like

A rep took the order on paper, working from a printed stock sheet. At some point the rep brought it to the office, where a data-entry clerk keyed it into a slow legacy system. The warehouse then staged the order. Excel sheets traveled back to the office for invoicing. Afterwards the rep collected installments against paper invoices and handed the cash over at the office.

Every handoff was a place where information could wait, get re-typed, or get lost. Two of them did most of the damage:

  1. Order submission was physical. An order didn't exist for the office until someone carried the paper in. Latency was measured in hours at best.
  2. Staging was heavy. The warehouse split limited stock across competing orders by hand, and that took a large part of the day, sometimes all of it. Stock allocation was also unpredictable: what a client received depended on who was staging and in what order.

The rest of the cycle, the invoicing and the cash collection, inherited the delay from those two steps.

What Kalia Flow is

Kalia Flow is a two-sided system on a single backend:

  • A mobile app for sales reps. Orders, clients, balances and installment collection all live in the rep's pocket. An order is submitted from the field and reaches the office through the API the second it is submitted.
  • A Django ERP, with an Unfold admin interface, for the office and the warehouse. Role-based views let the office confirm orders with accepted quantities, and let the warehouse stage against those confirmed quantities.

Under the hood, the order is a small state machine. It moves from submitted, to confirmed with accepted quantities, to staged, to invoiced, and every transition is timestamped. Installments follow the same logic: they show as pending until the cash actually reaches the office, and only then are they confirmed and deducted from both the client's balance and the order's remaining value. Every installment is linked to its order. The system also supports the payment plans Kalia already offered: one week, one month, two months and two and a half months.

The result is a single source of truth with a full audit trail, in place of five spreadsheets that each held part of it.

What changed in the numbers

The headline is time. Staging used to take hours, often most of a day. Now the warehouse stages an order with one click, in about five minutes. Orders arrive digitally, so the physical-submission delay is gone. Together, those two changes remove a day and a half to two days from a cycle that used to take five.

For a distributor, a shorter cycle is also a faster money cycle. Goods that are confirmed, staged and delivered sooner are invoiced sooner, and cash is collected sooner. Stock turns back into sales sooner. Reps get back to selling instead of waiting. The same sales force and the same warehouse can move more orders in the same month, which is how a growing business grows without growing its overhead at the same pace.

There are secondary effects that matter as much. Staging follows the quantities the office accepted, so the warehouse and the office stop disagreeing. Reps can see client balances before they take the next order. And because every step now carries a timestamp, Kalia has data on its own operation for the first time: how long an order waits for confirmation, which clients pay late, how cash comes in.

How we did it, and the calls we made along the way

We'd like to say it was linear. It wasn't, and three things shaped the build.

Unstructured data. The legacy system held years of clients, orders and payments in formats nobody had ever standardized. Migration was an ETL job with a lot of cleaning in the middle, and it took more effort than the application code.

No agreed requirements at the start. There was no specification to build against, so we didn't wait for one. We put a working prototype in front of the people who do the job, and the requirements surfaced from their reactions. The warehouse team told us in ten minutes what a document would have taken weeks to extract.

Integrate or renovate. The initial plan was to integrate Kalia Flow with the legacy inventory system. As we worked through it, both Kalia and our team agreed that a fully renovated system was the better solution, for three reasons. The legacy system was slow, and bridging it would have kept that latency in the middle of an otherwise real-time flow. It wasn't built to receive orders from a mobile app or to track the timestamped order-to-cash states that the new flow depends on. And an integration would have meant maintaining two systems plus a bridge between them, with the old system's unstructured data leaking through. So we renovated instead of patching. Kalia Flow went operational in August 2026, and the legacy system is now retired.

Why it worked

It's the same pattern behind most operational rebuilds that stick. The scope was one process, order to delivery. The people doing the work were in the room from week one. And success was defined by something measurable and visible: days in the cycle, minutes in staging.

None of the technology involved is exotic. A REST API, a relational database, a mobile client and an admin panel are a decade-old toolkit. What changed is that building them has become cheap enough that a mid-sized distributor no longer has to live with paper.

If your own operation still runs on paper forms and spreadsheets, the question to start with is the usual one: which single process, if it got three times faster tomorrow, would unblock everything else?

Ready to transform your business?

A 30-minute conversation is enough to know if we're a match. No cost, no commitment, no sales templates.

Who'll be on the call — no BDRs, no scripts
Gustavo Maryssael
Gustavo Maryssael
CEO · Founding Partner
José Antonio García
José Antonio García
CTO · Founding Partner