Five stores and half a thousand suppliers in a messenger
The network where the supplier layer was proven: not whether an order can be calculated, but whether it reaches a live person and whether that person answers.
- stores
- 5
- suppliers connected
- 535
- orders in 30 days
- 835
How it was before
- Each store ordered on its own, from its own suppliers, with no shared view.
- Written-off goods landed in the sales statistics and inflated the next order.
What runs now
Each supplier has a day and an hour. The order is assembled, checked and delivered to the supplier's chat with no human in the middle — unless the owner has required confirmation.
Buttons for accept, partial and out-of-stock, plus a free-text note. The reply is visible to the owner in the web app and lands in the order history.
Narrow groups — a single product line at a single supplier — get their own channel, with their own schedule and recipient.
What we found on the way
A write-off counted as a sale
A write-off document was being counted as demand, so the system kept reordering what had just been discarded. After the fix, ordering in two stores fell 16% and 7% at the same availability level.
Sent is not delivered
Some channels had been “working” for months while the link to the supplier's chat was dead. It is now visible how many suppliers an order actually reaches a person at — and how many it does not.
What is still open
- Some suppliers are not yet invited to a chat — the invitation is sent by the network owner by hand.
- Receiving is not yet fed back for every supplier.
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.