A pharmacy chain: hub, allocation and per-supplier ordering
The first network where the platform came together end to end: from reading a 1C export to an order that reaches a specific supplier, on their weekday, in their format.
- locations
- several dozen
- export
- nightly
- supplier orders
- on schedule
How it was before
- Orders were assembled in a spreadsheet from data several days old.
- Hub allocation happened by phone call and from memory.
- Part of the catalogue silently dropped out of the calculation.
What runs now
Sales, balances, movements and receipts are pulled overnight and checked for completeness before they reach any calculation.
Scarce stock is split by coverage — to whoever runs out first. What is left over becomes a purchase order.
Own file, own day, own format. Own-brand items and lines that are never bought externally are handled separately.
Footfall, average basket, cash and card split — collected from 1C receipts and delivered to the owner in a messenger each morning.
What we found on the way
A cut-off threshold was quietly eating the assortment
Slow-moving lines never entered the calculation: cosmetics and orthopaedics vanished from the report while sitting on the shelf. Removing the threshold nearly doubled the number of items covered.
An empty file is its own kind of outage
An order once went out to a supplier as an empty file: nothing was delivered, yet the system considered the send successful. Every send is now re-checked three hours later, and a calculation with an empty warehouse is refused outright.
What is still open
- Payables and treasury are only partly computed: the client's accounting simply does not hold that data.
- Items introduced after the first full import need a separate step — automatic creation is switched off for this network.
Show us one critical process. We will show how it runs here.
We look at your cycle: how an order is assembled today, who decides, where time leaks and what the system takes over.