In daily use
PizzaMania B2B Platform
Custom operational platform, food production and delivery
Every order in the business moves through one system that six different roles use every day, from the customer who places it to the invoice at the end. Nobody phones anybody to ask where something is.
Who touches an order
B2B clientPlaces the order, follows its status
AdminCompany setup and commercial rules
ProductionWorks from confirmed demand
DistributionBatches and delivery documents
AccountingBilling context and references
System adminReleases and scheduled jobs
Six roles, one orderfrom the customer placing it to accounting closing it
Nothing retypeddelivery documents and invoices are generated, not copied by hand
Its own serverset up, hardened and operated by me
The real win
The phone stopped ringing about where things are
In a business that produces and delivers every day, most of the coordination used to be questions. Who ordered what. Whether it was made. Whether it went out. Whether it was invoiced. Each of those was a phone call to somebody who had to stop what they were doing in order to answer it. Now all four answers are on the same screen, and the person who needs one can simply look.
- A customer sees the status of their own order instead of calling to ask
- Production sees what has to be made without waiting for somebody to compile it
- Distribution prints what it needs from the order, rather than retyping it
- Accounting sees what has been delivered and what is still open, on the day rather than at the end of the month
Not my words
What the owner says
This is the part of the page I did not write. It is what the person who runs the business said afterwards.
Owner and Managing Director, food production and delivery
“The system significantly improved our processes, reduced manual effort and increased operational transparency.”
What disappears
Four things nobody does any more
The clearest way to describe what changed is not a feature list. It is the work that stopped existing.
- Nobody agrees a price from memory, because each client's commercial conditions are already in the system
- Nobody retypes an order into a delivery note
- Nobody reconstructs at the end of the month what was delivered and what was billed
- Nobody copies a file onto the live server in order to release a change
How an order travels
One order, six roles, one version of the truth
The same order is visible to the customer, to the office, to production, to distribution and to accounting. Each of them sees the part that is theirs, and none of them has to ask another one what happened to it. That sounds obvious until you have watched a business where everybody holds a different version of the same order.
- A new client is set up once, with their company data and their contract, and from then on they order for themselves
- An order is placed against real prices and real rules, so it does not need checking before it is accepted
- Its status is visible to everyone who needs it, at the same moment, without anybody being asked
- Production sees what has to be made, in the order it has to be made, without waiting for a list
- Delivery documents come out of the order itself, so what leaves matches what was ordered
B2B clientTheir own orders and status
AdminProducts, prices, contracts
ProductionConfirmed demand, by date
DistributionBatches and delivery notes
AccountingBilling tickets and values
System adminReleases and scheduled jobs
Commercial rules
Prices and conditions that apply themselves
Each client has their own prices, their own commercial conditions and their own contract. They are configured once, in one place, and after that they apply on every order without anybody having to remember them. The person taking an order stops being the last line of defence against a wrong figure.
- Each client's prices and conditions are set once and applied on every order after that
- Contracts are generated from the company data already in the system, rather than assembled by hand
- A change to a price takes effect where it should, and nowhere it should not
- A new customer can be onboarded without anybody rebuilding their commercial setup from an email thread
Money and paper
The month stops being a reconstruction
In a business that delivers daily, the end of the month used to be an archaeology exercise: what went out, what was invoiced, what is still open. All three are now on one screen, on the day, and the reports that used to be assembled by somebody arrive on their own.
- Billing visibility on the day, so what has been delivered and what is still open can be looked up rather than reconstructed
- Scheduled reports arrive without anybody remembering to produce them
- Operational notifications go out when something needs attention, rather than when somebody notices
How it changes safely
A change reaches the business only after somebody has used it
The platform runs on its own server, set up and hardened deliberately, with a development environment, a testing environment and production. A change is used before it is released, and a release that goes wrong can be undone. For a business that takes orders every day, that is not a technical detail. It is the difference between a bad afternoon and a bad week.
- Nothing reaches the live system that has not been used somewhere else first
- The server is operated rather than merely rented, so an update is somebody's job rather than an accident
Have something that should work like this?
Tell me what the work looks like now, and I will tell you whether software is the answer and what it would take.