Building order-printing software, the thing that surprised me most is that every way this fails is silent paper, a sleeping Bluetooth printer, a killed background app, a revoked email password. All of them look exactly like a quiet night. Curious how people running shops actually catch it.
Hi Product Hunt 👋
I built this because a restaurant I'm close to kept missing online orders. They
arrive as email, and during service nobody is looking at an inbox. An order
would sit unnoticed until the customer rang to ask where their food was.
Every existing fix felt disproportionate. A cloud receipt printer costs more
than the till it sits next to. A PC left running in the corner is one Windows
update away from a silent morning. Both need looking after.
So OrderPrint uses the phone already in your drawer. It reads the order email
and prints a kitchen ticket — no computer, no cloud service, no plugin.
The part I care most about is failure handling. Every system like this fails
silently: paper runs out, a Bluetooth printer sleeps, Android kills a
background app, an email password gets revoked — and all of them look exactly
like a quiet night. So the status card is never green unless orders are
actually printing, and a ticket that doesn't come out raises an alert.
Happy to answer anything, especially the technical bits. Parsing order emails
across platforms was harder than expected, and cheap Bluetooth thermal
printers have strong opinions about being rushed.
Free for 100 orders a month if you want to try it — an old Android phone and
a £20 printer is the whole setup.