POS Service Modes

What it does

A counter that also delivers runs three different businesses through one till, and Odoo's point of sale treats an eat-in ticket and a delivery exactly the same. So the delivery charge gets keyed in by hand, the address lives on a sticky note, the kitchen cannot tell one ticket from another, and at month end nobody can say how much of the trade was delivery.

POS Service Modes puts the service mode on the order record itself. Dine in, take away and delivery arrive ready to use, each naming the fee product used for its charge so delivery fees report against a real product rather than a manual line.

A delivery order that reaches the server without a delivery address is refused. A delivery with nowhere to send it cannot be fulfilled, so recording it only creates work for somebody later.

- Modes you define. Three ready to use, and add your own with any name and behaviour. - A fee product per mode. Charges post and report like everything else in the catalogue. - Enabled per register. A counter that does not deliver never sees the option. - Address enforced on delivery. Refused at the server, so it never lands in the kitchen incomplete. - Reporting filters. Filter the orders list by dine in, take away or delivery and see the split without exporting anything. - Fee product validated. A product the point of sale cannot load is rejected on save rather than silently never charging. - No Loyalty dependency. It needs Point of Sale and Inventory only, so installing it does not pull unrelated apps into your database.

Note that the fee is not yet inserted into the cart automatically at the till; each mode names the product used for the charge and the line is added normally. Automatic insertion is planned.

Who it's for

Restaurants, takeaways and cafés running eat-in and delivery through one till, and retailers who deliver alongside counter trade and want the split visible in reporting.