Choosing a POS for a hotpot restaurant

Hotpot is structurally different

In most restaurants the flow is order, serve, settle, clear. Hotpot does not work that way. Guests sitting down is the start: over the next two or three hours they will keep adding to the order, and every addition is urgent, because the pot is already boiling.

That pattern magnifies every weakness in a POS. Ordering that is slightly slow costs a fast-food shop ten seconds; it costs a hotpot restaurant that same delay thirty times in an evening. One add-on recorded wrongly becomes an argument at the till. So for hotpot, the question is not whether the feature list is complete, but whether the handful of repeated actions are fast and accurate.

1. Soup bases: split pots, three-way pots, pricing

The soup base is the part of a hotpot menu most often modelled wrongly. A single base is trivial, but a split pot means choosing two, a three-way pot means three, and bases are often priced differently. If a guest picks two expensive ones, how is the total calculated: the higher price, an average, or each added?

Many systems only support picking one option from a group. To offer split pots you then create a product per combination: mala plus pork bone, mala plus tomato, pork bone plus tomato, and so on. Ten bases becomes forty-odd combinations. During a demo, have the vendor build a split pot in front of you and watch how they handle it.

• Can one option group allow multiple picks, and require exactly two?
• With bases at different prices, does the total calculate correctly?
• Are pot charges, burner charges and per-head charges kept separate?
• Can guests change base, add stock or top up, and is it priced?

2. Adding to an order: the action that matters most

A hotpot table adding to its order a dozen times in an evening is normal, so how smoothly that flows decides how many floor staff you need. Check three things: how many taps an addition takes, whether the kitchen can tell which round it is, and whether new items get confused with earlier ones.

The kitchen side matters most. If every addition prints a full ticket including everything ordered earlier, the kitchen has to work out what is new and what is already cooked. The correct behaviour is to print only the new items, marked with the table and the round.

3. QR ordering earns its keep here

If a hotpot restaurant invests in one thing, it should be QR self-ordering. The reasoning is direct: hotpot additions are frequent and small — two more plates of beef, a plate of fish balls — and guests tapping their own phones is far faster than finding a server, while staff stop circling the room collecting add-ons all night.

One practical caveat: hotpot tables produce steam and condensation, so table QR codes need to be waterproof or sleeved. It sounds trivial and it directly determines whether the code still scans by week three.

• Guests add to their order without waiting for a server
• Additions reach the kitchen with nobody relaying them
• Guests can see what they already ordered, reducing duplicates
• Table codes must be waterproof — steam destroys paper quickly

4. All-you-can-eat: timing and overtime

If you run a buffet or all-you-can-eat format, the POS needs a different set of logic: per-head pricing, a time limit, an overtime charge, and separate child and senior rates. Most general POS systems cannot do this, so staff track it on paper.

Tracking time by hand works at a few tables and fails reliably once the room is full. Ask specifically: does the system track each table’s start time and time remaining, does it alert the floor when time is up, and can the overtime surcharge be added to the bill as a line item?

5. Mixing per-head charges with à la carte

Most hotpot restaurants are a hybrid: the base priced per pot, a burner or tea charge per person, meat and seafood ordered à la carte, drinks separate. All of that has to appear on one bill and still be legible to the guest.

Test this: when an extra guest arrives mid-meal, does the system add another per-head charge automatically? How is a child at half price entered? These come up every single service.

6. Splitting the bill, because hotpot tables are large

Hotpot is usually eaten in a group, and splitting the bill or paying in several parts is routine. If your POS can only settle a bill in one go, the till ends up splitting it on a calculator and tracking who has paid on paper.

Confirm three things: can a bill be split evenly by headcount, can it be split by item so a guest pays only for what they ordered, and can each part be settled with a different payment method? Get those right and the queue at the till stops forming.

7. Sold-out items and seasonal stock

Much hotpot stock is bought daily and sells out. If marking something sold out requires going into a back office, the floor keeps taking orders for it and the kitchen keeps phoning out to say it is gone — several times a night.

Check whether the floor can mark an item sold out directly on the POS, whether it disappears from QR ordering immediately, and — if you run delivery — whether it syncs to Foodpanda and Keeta too.

8. Table time and turnover

Hotpot tables sit for a long time, so turnover and average table time directly determine an evening’s revenue. The POS should calculate this for you rather than leaving it to instinct.

The report to look for: average table duration, which time bands are busiest, and which tables turn fastest. With those numbers you can decide whether to impose a time limit or change your table mix — without them, you are guessing.