Not a POS

This comes up early for most restaurant owners evaluating mozo, so it’s worth stating plainly: mozo is not a point-of-sale system. It doesn’t process payment, close out a register, or manage inventory — and none of that is on the roadmap. Where mozo does grow, occasionally, is small conveniences around the ordering and service experience itself (see the receipt-printing note below) — never into the transaction and accounting layer a POS actually owns.

What a POS does that mozo doesn’t

A point-of-sale system is the restaurant’s system of record for transactions: it processes payment, closes out registers, integrates with accounting, and often handles inventory. mozo does none of that. It doesn’t take payment from the guest, it doesn’t touch your till, and it has no concept of stock levels or cost of goods. (Mozo does track tax per product, so receipts and reports reflect it correctly — it just doesn’t export that to your accounting system yet.)

What mozo actually does

mozo sits in front of the ordering step. A guest scans a code, sees a menu, and places an order. That order shows up on your staff’s screen the same way an order called out from a table would, just faster and with zero chance of being misheard. Staff still ring it up, still take payment, still run the floor the way they always have.

The one exception: printing a receipt

mozo can optionally print a guest’s itemized bill on a thermal receipt printer, on request. It’s off by default, and a restaurant has to turn it on. This is as close as mozo gets to POS territory, so it’s worth being direct about why it doesn’t cross the line: it prints what’s already visible on the order, nothing more. No payment touches it, it doesn’t close anything out, and it doesn’t replace whatever your kitchen printer or till already does. It’s a physical copy of information mozo already has, not a new financial function.

Why not replace the POS too

Restaurants that already run a POS have usually invested years into getting it right: staff training, integrations, reporting habits. Asking a restaurant to rip that out to adopt mozo would be a much bigger ask than the problem mozo actually solves. Keeping mozo narrowly scoped means it can sit alongside whatever a restaurant already uses, old-fashioned paper tickets included.

The practical result

Setup takes minutes, not weeks, because there’s nothing to migrate. A restaurant’s existing till, kitchen printer, and payment terminal all keep working exactly as before. mozo adds a faster front door to ordering; it doesn’t ask you to rebuild the house behind it.