Codegres.org VS OrderPrint.app

OrderPrint.app's answer:

It started with a shop that kept missing online orders. They arrive as email, and during service nobody is watching an inbox — an order would sit there until the customer rang to ask where their food was.

The available answers all felt out of proportion. A cloud receipt printer cost more than the till it sat next to. A PC left running in the corner was one Windows update away from a silent morning. Both needed looking after.

The realisation was that the order was already arriving — as an email, on time, every time. Nothing needed integrating. Something just needed to read it and put it on paper. So that's what it does, using the old Android phone in a drawer.

OrderPrint.app's answer:

Three reasons, and one reason not to.

Cost: the hardware is a cheap thermal printer and an Android phone you probably already own, rather than a cloud-connected printer that costs more than the till it sits beside.

Nothing to keep running: no computer switched on all day, and no plugin on your site to maintain or to break at the next update.

Any platform: because it reads the order email, adding a second sales channel doesn't mean finding another printing solution.

The reason not to: if you need one system managing printers across several sites centrally, a print service running on a computer will suit you better than we will. We bill per phone, and we're honest about that being the wrong shape for a chain.

OrderPrint.app's answer:

Small independent food businesses, mainly — restaurants, takeaways, cafés, bakeries and dark kitchens taking online orders. Also small online shops that pack their own parcels and want a picking ticket.

Typically one to five people, one or two locations, selling through WooCommerce, Shopify or Wix, with no IT person and no appetite for a monthly bill that grows faster than the business does.

OrderPrint.app's answer:

It works from the order email rather than an integration. Your shop already emails you every order, so OrderPrint just reads that mailbox — nothing is installed on your website, and it doesn't care whether you sell on WooCommerce, Shopify, Wix or something nobody has heard of.

There is also no OrderPrint server. The phone reads the mailbox itself, so your email password and your customers' orders never leave the device.

And it assumes printing will eventually fail. The status card is never green unless orders are actually printing, and a ticket that doesn't come out raises an alert naming the printer and the order. Most tools in this space treat printing as the problem. The real problem is not noticing when it stops.

OrderPrint.app's answer:

Flutter and Dart, targeting Android.

Email is read over IMAP directly from the device. Receipts are composed as ESC/POS byte streams and sent either over Bluetooth Classic (RFCOMM) or to a network printer on TCP port 9100. Polling runs in an Android foreground service so it keeps working with the app in the background, and subscriptions go through Google Play Billing.

There is no backend at all — no server, no database, no API of ours in the middle. Everything happens on the phone.