At 17:05 someone pays for a set that must be ready at 19:30: California swapped for spicy tuna, sauce in a separate cup, chopsticks for three. Packing is still finishing lunch boxes. If that ticket hits the board now, the fish sits too long. If it stays only in someone’s head, 19:25 is a panic. A POS system for sushi restaurants is tested on that delay and that swap, not on whether it has a button labelled “roll.”
An omakase counter is a different shop that happens to use similar ingredients. Sequence, a seat, and a comment to the chef matter more than a promised pickup time. A generic till usually fits one of those rhythms, not both.
Timed collection versus a seat at the counter
Name which Friday you actually run before you compare screens. Delivery and pickup inflate the card with lunch boxes and repeating exceptions: no cucumber, extra ginger, collect at 19:30. Omakase wants a short card and personal notes tied to a seat. If you run both, the software has to keep a dining-room ticket off the same board as a box that should wait in the fridge.
On-screen categories should follow the conversation: sets, rolls, nigiri, sides, drinks. Common items first. A set should show its contents and what staff are allowed to swap. Not every bar needs unlimited configuration of every box. A stable menu prefers simpler rules. A room where guests regularly ask for substitutions needs a controlled way to record them, not a comments field for everything.
Someone must be able to kill a seasonal item for the evening without a workaround at every station. Sales, menu, and later handling are mapped on OrderNow features. That map is not a substitute for a test on your card.
A 19:30 pickup that should not hit the board at 17:00
For collections, “accepted” is too thin. The team has to separate what to roll now from what must be ready at a stated time. Otherwise a lunch set sits warm for an hour, or someone notices at 19:25 that the box still does not exist.
Walk one order from phone or till to the hatch. Where is the time stored? Who sees it on the board and at packing? When does the item even enter prep? If you mix tables, phone, and an owned channel, look at the whole path, not only checkout. How the order flow works is a useful frame. Direct online is not in every plan. If pickups are meant to come from your own site, check scope before you promise guests a channel.
In a small counter shop where the same person rings and rolls, a separate kitchen screen can wait. It earns its keep when tickets pass through till, board, packing, and collection, and status dies between those zones.
A swap inside a set that packing cannot invent
The guest takes set B, drops the spicy roll, adds California, wants sauce separate and chopsticks for three. If the server remembers one version, the screen shows a second, and packing builds a third, the error exists before fish leaves the board.
Recurring changes need one place to live: no spicy sauce, extra ginger, separate packing, an allowed swap inside a set. The aim is not every imaginable combination. The aim is that a normal request does not end on a sticky note by the rice cooker.
Use last weekend: a dine-in set, a set with a swap, a pickup in an hour, a table with several items, an order with packing notes. For each: can staff enter it without a workaround, does the kitchen see the full version, can the person at the hatch tell whose box is whose.
A POS will not fix unclear names on the card or a missing rule for who confirms collection. Set those rules, then add modules. A heavy configuration slows a tiny pickup window. A cramped till cracks when pickups and extra hands arrive. Venue types, including sushi, are on industry solutions.
OrderNow is worth considering when sales, menu, and the next stages should share one path instead of a pad beside the board. One shop needs clearer sets and swaps. Another needs a kitchen queue or an owned ordering channel. You do not have to switch everything on the first day. Name one jam: a lost pickup time, or a lost substitution. If you are leaving another system, plan the menu and the team first: switching systems.
To match that to your card, see features or book a demo on sets and pickup times, not on a single sample roll.
Related articles:
- Restaurant POS system: choosing without overpaying
- Restaurant POS prices: what makes up the cost
- How to change a restaurant POS system without chaos