Build or Buy a Restaurant POS in Indonesia: A Buyer's Guide

Should a restaurant group in Indonesia build or buy its point of sale? The question usually arrives at a specific moment: a second or third outlet is opening, the owner wants stock and food cost under control, or a delivery marketplace is taking a larger share of orders than is comfortable. The honest answer is that most restaurants should buy, a few should build, and many should do a little of both. This guide explains how to tell which group you are in.

What any restaurant POS in Indonesia must handle

Start with the requirements that do not depend on the route. The first is tax. In an explainer dated 19 May 2022, the Directorate General of Taxes stated that food and drink served by restaurants is not subject to PPN. It falls under a regional tax, Pajak Barang dan Jasa Tertentu (PBJT), introduced by Law 1/2022 on fiscal relations between central and regional governments, and collected by the regency or city government, or by the province in Jakarta's case. The rate is set by regional regulation at up to 10% of what the customer pays. The office called an 11% charge on a cafe receipt an error.

Two details matter for a system. A business counts as a restaurant if it provides at least tables, chairs or eating utensils, so a bakery with seating is covered even for takeaway. And, as DDTCNews reported on 18 July 2023, regional governments may set a turnover threshold below which sales are excluded, under Article 51 of the same law, with regional rules due to be aligned by 5 January 2024. A point of sale therefore needs a tax rate and rule set per outlet, not one national setting.

The second requirement is payments. Speaking at the Lampung Financial Festival, Bank Indonesia Deputy Governor Filianingsih Hendarta said QRIS had reached 15 billion transactions to July 2026, with about 45 million merchants and 67 million users, Katadata reported on 7 September 2026. The same report cites Bank Indonesia's June figure of 44.86 million merchants, 96.68% of them small businesses. A till that cannot take QRIS and reconcile it is not a serious candidate.

Option one: subscribe to a ready-made POS

A subscription product gives a restaurant a working till, kitchen tickets, table management, basic stock and reports within days, for a monthly fee per outlet or device. The supplier carries the cost of keeping up with tax rules, payment methods and devices.

• Right when: one to a handful of outlets, a standard service model, and no in-house technology team.
• Watch for: how the product behaves when the internet drops, whether stock and recipes go deep enough for food costing, and whether you can export all your data.
• The limit: you get the roadmap the supplier chooses. A feature only you need may never arrive.

Option two: an ERP suite with an implementation partner

Larger groups sometimes choose an enterprise resource planning suite with a restaurant module, configured by a systems integrator. Global consultancies and local integrators both offer this. The appeal is one ledger for purchasing, inventory, production, finance and sales across several legal entities.

• Right when: several companies or brands need consolidated accounts, central purchasing and formal approval chains.
• Watch for: licence costs per user, the cost of customisation and of re-testing it at every upgrade, and a till that was designed for retail before restaurants.
• The limit: implementations take months, and the floor staff experience is often the weakest part.

Option three: build your own

Building means commissioning software that belongs to the business. It is the most expensive route to start and the only one with no ceiling.

• Right when: the way you serve guests is your competitive edge, such as an unusual ordering flow, a membership programme at the centre of the brand, or a franchise model you intend to sell.
• Watch for: the unglamorous parts. Offline selling, printer and device support, tax changes, security and round-the-clock support all become your responsibility.
• The limit: you need an owner for the product for as long as it runs, not only until launch.

The hybrid most groups end up with

In our view the most practical pattern for a growing group is to buy the commodity and build the difference. The till, kitchen tickets, stock and accounting are similar in every restaurant, so a product does them well. The guest relationship is not. A branded website and ordering app, a loyalty programme, and the data they generate are worth owning, because orders taken there are not shared with a marketplace and the customer list stays with the restaurant. The two halves are joined through the product's interfaces, which is why integration belongs on the checklist below.

Questions to ask before you sign

• Offline: what exactly can the till do with no connection, and how are sales synchronised afterwards?
• Tax: can each outlet carry its own PBJT rate and service charge rule, and who updates them when a regional rule changes?
• Payments: which QRIS acquirers are supported, and how are settlements and fees reconciled to the bank?
• Data: can you export every sale, customer and stock movement at any time, in a usable format?
• Integration: is there a documented interface for your website, app, accounting or delivery channels?
• Cost: what is the total over three years, including devices, training, support and changes?
• Exit: what happens to your data and your service if you leave or the supplier stops trading?

How to decide

Write down the three things your restaurants do differently from the one next door. If the list is empty, buy, and spend the saving on training. If the differences are in the back office, such as central kitchens or several companies, look at an ERP or a product with strong inventory and production. If they are in how guests discover, order and return, keep a bought till and build the channels. Whatever the route, run a real service on the system before committing: one busy evening tells you more than any demonstration.