In most restaurants the check is built from what a guest ordered. In a revolving sushi restaurant it is built from what they took off a belt, and nobody wrote any of it down.

That one difference invalidates most of what a standard point of sale assumes. There is no ticket to price, the party grows and shrinks seat by seat, and the whole business model depends on turning a counter several times over a two hour lunch without anyone queueing to pay.

In this article

• Why a Belt Breaks a Standard POS Setup

• The Bill Is Assembled from Plates, Not from Orders

• All You Can Eat Changes What a Plate Costs

• The Seat Is the Ticket, Not the Table

• Made to Order Rides Alongside the Belt

• Checkout Is Where the Turn Is Won or Lost

• What Reporting Should Tell You About the Belt

• Where Peblla Fits a Revolving Sushi Restaurant, and Where It Does Not

Why a Belt Breaks a Standard POS Setup

A conveyor belt restaurant runs two service models at the same time. Guests take finished plates off the belt with no order attached, and they also order made-to-order items from a screen at the seat. Both have to land on the same check.

A general-purpose restaurant POS system can handle the second and has no concept of the first. Operators fill the gap with a paper tally, a clicker, or a server counting stacked plates by eye at the end of the meal.

That workaround is where the money goes. Miscounts run in both directions, and the disputed ones always resolve in the guest's favour because there is no record to point at. Accuracy is not a nice-to-have in this format, it is the margin.

The Bill Is Assembled from Plates, Not from Orders

The fix is to make the plate itself the record. Plates are priced by colour, and at the end of a meal the stack is scanned at the seat rather than counted, so the check assembles itself from what is physically in front of the guest.

Peblla supports this on a handheld POS, which is the only sensible place for it. The device goes to the counter, the scan happens where the plates are, and the total is on the screen before the guest has finished asking for the bill.

Two details separate a system that works from a demo that works. Whether the device can pick up the seat automatically instead of making a server select it first, and whether plates taken off the belt stay visually distinct on the check from items the guest ordered at the seat. Both come up within a week of opening.

All You Can Eat Changes What a Plate Costs

Many revolving sushi operations sell an all-you-can-eat tier alongside standard plate pricing, and the two run at the same counter at the same time.

The rule the system has to hold is specific. For a guest on a tier, plates inside that tier are not charged, and anything outside it prices normally on the same check. Get this wrong and you either give away premium items or charge a guest for something they were told was included.

This is worth testing directly during evaluation. Seat two guests, put one on a tier and one on standard pricing, run the same plates past both, and see whether the check comes out right without anyone doing mental arithmetic. Buffet and Korean BBQ operations hit the same rule from a different angle.

The Seat Is the Ticket, Not the Table

At a counter, parties do not map onto tables. Two people sit down at seats nine and ten, a solo diner takes seat eleven twenty minutes later, and a group of four splits across a corner because that is what was free.

Seat-level status is what keeps that legible. Occupied, dining, needs clearing, all visible on one screen so a host can seat the next guest without walking the length of the counter to check.

An ordering tablet at each seat makes the same structure work for ordering. The guest adds items themselves, the item lands on that seat's check, and a server is not walking the counter taking additions that could have been entered directly.

Made to Order Rides Alongside the Belt

The belt carries volume items. The margin sits in what guests order fresh, and those tickets have to reach the sushi counter in the order they were placed, not in the order someone gets round to reading them.

A kitchen display system at the pass keeps that queue honest, and it does something paper cannot in this format: it shows the seat number, so the runner delivers to a position rather than hunting for a party.

Plating rules matter more here than most operators expect. Two guests ordering the same item usually want two plates, not one shared plate, and if the system cannot express that the kitchen will guess. It is a small setting that produces a steady trickle of remakes when it is wrong.

Checkout Is Where the Turn Is Won or Lost

A revolving sushi restaurant lives on turns. Every minute a guest spends waiting to pay is a minute a seat is producing nothing, and at a forty seat counter that adds up faster than any menu change you could make.

Two things shorten it. Scanning the plates at the seat, so the total is ready when the guest stands up. And a self-ordering kiosk at the exit that also takes payment, so guests settle themselves on the way out instead of waiting for a server to bring a card machine.

Run the numbers on your own counter before dismissing this. Three minutes saved per party, across the number of parties a busy izakaya-style counter turns at lunch, is a whole extra service sitting inside the same opening hours.

What Reporting Should Tell You About the Belt

Belt reporting has a job no ordinary sales report has. It should tell you what to put on the belt tomorrow, and what to stop making.

Sales by item by hour shows what moved at noon and what was still circling at two. Splitting belt items from made-to-order items shows whether your margin is coming from volume or from the fresh side, which is the decision that sets your staffing on the sushi line.

Ask to see both on real data during an evaluation. A system that can only give you a daily total is asking you to keep guessing at the one number that drives your waste.

Where Peblla Fits a Revolving Sushi Restaurant, and Where It Does Not

Peblla fits a revolving sushi restaurant running the full format: plates priced by colour and scanned at the seat, tablets at each position, an all-you-can-eat tier alongside standard pricing, seat-level status, a display at the sushi counter, and self-checkout at the door. These are not separate products bolted together, which is why a plate scan, a tablet order and a kiosk payment end up on one check.

It is more system than a small sushi bar with no belt. If your guests order everything from a server and nothing circulates, the plate logic is dead weight and you should be reading about full-service restaurant setups instead.

It also will not tell you what to put on the belt. It will show you what sold, at what hour, from which side of the operation. Somebody still has to stand at the counter at ten in the morning and decide how much salmon that means.

Frequently Asked Questions

How does a POS price plates on a conveyor belt?

By colour. Each plate colour maps to a price, and instead of counting the stack by eye a server scans the plates at the seat, so the check assembles from what is physically there. That removes the tally sheet, and it removes the disputes that a tally sheet always loses.

Can all-you-can-eat and standard pricing run at the same counter?

Yes, and the rule has to be enforced per guest rather than per table. For a guest on a tier, plates inside that tier are not charged while anything outside it prices normally on the same check. Test it with two guests on different pricing before you sign anything.

Do guests order from a tablet or from a server?

Both, usually. An ordering tablet at each seat handles additions, which keeps servers off the counter walk, while staff still handle service and anything complicated. The important part is that tablet orders, belt plates and server-entered items all land on the same seat-level check.

How do you speed up checkout in a revolving sushi restaurant?

Scan the plates at the seat so the total is ready before the guest stands, and put a self-service kiosk near the exit so parties can pay on the way out. Turns are the entire economics of a belt counter, and waiting for a card machine is the most expensive minute in the meal.

Does the kitchen see which seat ordered what?

It should. A kitchen display at the sushi counter shows the seat number with each made-to-order item, so a runner delivers to a position instead of hunting for a party at a counter where groups are split across whatever seats were free. Plating rules should be configurable alongside it.

What reporting matters most for a belt operation?

Sales by item by hour, split between belt items and made-to-order items. The first tells you what to put out tomorrow and what to stop making. The second tells you whether your margin comes from volume or from the fresh side, which is what actually sets staffing on the sushi line.

If plate counts and the queue at the register are where your counter loses time, the useful next step is to walk your own service flow through with the Peblla team and see what scanning at the seat does to your turns.