Four apps, and the back office they already had.
An ordering website, a phone app, a self-order screen in the shop and a rider panel, all from one system. All four are joined to PetPooja, which the client already used and did not want to give up. The hard part was joining the two together.
assets/screens/pizza-house-web.png
Do not make them throw away what already works
It is tempting on a job like this to replace everything, because software you wrote yourself is always easier to work with. It is also the wrong answer, because the client’s staff already know their current system and their accountant already knows those reports.
So PetPooja stayed, and it remained the one place holding the menu, what is in stock and the status of each order. All four apps read from it and write back to it. That join is where all the risk sits. Replies arrive half finished. An item went out of stock two minutes ago. And an order must never be created twice if a request is sent again.
The self-order screen was the hardest test. Nobody is watching it, so an out-of-date menu there means a queue of people ordering something the kitchen cannot make.
Replacing what the client already used would have been easier for us and worse for them.
- Four surfaces — ordering website, phone app, self-order screen, rider panel
- Menu, stock and order status all come from PetPooja
- Orders can never be created twice, so nobody is charged double
- One project, four apps, sharing the same cart and prices
Pending client approval.
Captures of a client's live deployment go up when they say yes, not before. These slots are wired and waiting.
assets/screens/pizza-house-web.png
assets/screens/pizza-house-kiosk.png
We build around what you have.
PetPooja, Petpooja-alikes, or something older with a CSV export — if it has an interface we can usually meet it rather than replace it.