Search articles

    All Gastrokompass articles →

    Details

    Reuse Existing Tablets and Order-Ticket Printers?

    Can you reuse existing tablets and order‑ticket printers for a BonZumo setup?

    Decide device‑by‑device after inventorying models, OS versions, connection types and placement. Test each tablet with your menu and peak workflows and each printer with real mixed orders and output routes. Check battery, power, network stability and environmental factors; replace only devices that fail under your expected service conditions.

    Decide device by device, not with a blanket yes or no

    Reuse is possible if your specific tablets and order-ticket printers are compatible with the intended connections, software versions and workflows. Have each device checked individually. What matters is the exact model, the software version, the network connection, and the place where the device is supposed to work in daily operations. A tablet that still works well at home can still be too slow for service. A printer that prints neatly in an office can cause trouble at the counter when orders need to reach the right kitchen or bar station quickly and reliably.

    For your switch, that means this: do not replace anything too early, but also do not rely on “it worked before.” When you contact BonZumo, list your existing devices, where you use them and the connections you need, so their suitability can be checked specifically. That helps you justify any new purchase properly. The software supports table service, fast counter sales, and printing routes for kitchen or bar stations, but that does not automatically mean every older device will fit without checking. That distinction matters if you want to avoid unnecessary costs.

    Start by documenting your full device inventory

    Before you ask whether something is compatible, you need a clean list. Write down every tablet with manufacturer, model name, screen size, operating system version, storage condition, and charging port. For each order-ticket printer, note the model, connection type, and current use: LAN, Wi-Fi, USB, or another connection. Also record where the device stands and what it is used for, for example table service, counter, kitchen, bar, or pickup station. Without that information, any answer stays too vague and usually ends in either unnecessary caution or false confidence.

    The condition under load matters too. An older tablet may look fine while idle, but show its limits during a lunch rush with many items, constant switching, and long operating hours. The same applies to printers that still produce a test ticket after sitting unused, but start delaying when many short orders come in one after another. If you do this inventory first, it becomes much easier to judge which devices will probably keep working and where replacement is more about reducing operational risk than adding comfort.

    Check tablets against real workflows, not only the spec sheet

    With a tablet, the basic technical question is only one part of the decision. What matters more is how it behaves in real hospitality work. BonZumo offers an interface for table service and a fast counter view with favorites. That immediately leads to the practical question: is the screen large enough for your item structure, the way your team taps through tasks, and the pace of service? At a counter with a few fast-moving items, a device may still be a good fit. In table service with many notes, areas, and active tables, the same tablet may feel too small, too slow, or too cluttered.

    So do not only ask, “Does the app open?” Ask instead, “Can my team work safely with it during peak hours?” Have your own menu structure shown on your device so you can see how favorites, item selection, and order taking actually feel. Your team is not looking at some abstract demo screen. They see the real work context: table or counter, selected items, notes on the order, and the next step in the process. If even a simple repeat order already requires zooming, searching, or extra tapping, that is not a cosmetic issue. It is a real time loss in every shift.

    Pay close attention to battery life, power supply, and hot spots

    Many plans to reuse old tablets fail not because of the interface, but because of power. An older tablet that only works reliably while plugged in may be fine at a fixed counter, but awkward or disruptive in table service. If devices constantly need recharging, power outlets are scarce, or charging ports are already loose, you create hidden daily effort. That is one of the most common reasons why a device is still technically usable, but no longer makes sense operationally.

    You should also check the actual location. Direct sun on a terrace, heat near the coffee station, or grease and steam close to the kitchen can change day-to-day usability a lot. A tablet that seems fine in the office can dim, overheat, or react slowly outdoors or near hot equipment. No POS interface solves that for you. That is why older devices should always be tested exactly where they will later be used. If you end up replacing a tablet only because of battery weakness or heat exposure, that is a much cleaner decision than replacing everything as a precaution.

    With order-ticket printers, the connection type decides the effort

    For an order-ticket printer, the first thing you need to understand is how it is connected today. An existing LAN printer is often easier to assess for a new setup than a device that only worked in a very specific older arrangement. The question is not only whether it can print, but whether printing arrives reliably in the right place. In hospitality, this is not about a single test ticket. It is about repeated, clear output at the kitchen, bar, or counter station.

    BonZumo can map printing rules and output routes to your operation. That is useful because not every order needs to appear everywhere. In the workflow, the team sees the relevant order context, and the setup can define which items or categories should go to which output point. That is exactly why printer testing is more than a technical check. It has to show whether a specific printer in its specific place can really handle the ticket output your business needs. A device may be able to print in principle and still be unsuitable for your routes if the connection or reaction time does not fit.

    Test printing rules with your real items and stations

    A meaningful test is not “does anything print?” but a set of typical orders. For example, simulate a table with drinks for the bar, food for the kitchen, and an extra item added later. If you also run counter sales, test quick sales with favorites as well. That shows whether output routes are cleanly separated and whether each printing point receives exactly what that station is supposed to work on. This matters much more than an abstract compatibility statement with no connection to your business.

    That makes one concrete decision much easier for your team: does everything need to print immediately, or is a different process enough at one station? Where do questions arise because tickets are unclear, too late, or duplicated? BonZumo is strong at structuring orders across service and kitchen or bar station workflows. If the printing routes fit your setup, the bar sees its relevant orders and the kitchen sees its own. If an older printer shows delays or dropouts in that test, the issue is no longer theoretical. Then you can say very clearly that not all hardware needs to be replaced, only this specific bottleneck.

    Without a stable network, even a good older device will not help much

    When problems appear, many operators first suspect an incompatible tablet or a weak printer, even though the real issue is the network. Order-ticket printers in the dining room, kitchen, or terrace depend heavily on how stable the connection actually is at that exact spot. If orders need to reach several output points, the network has to be assessed across the whole route. Otherwise, you may replace working devices even though the real cause sits in the environment around them.

    So always plan for an on-site look. Where is the router? Where are thick walls, cooling equipment, metal surfaces, or other sources of interference? How far away is the terrace? Is the same network also being used for guests, music, office tasks, and operations? Questions like these are often more important than the age of the device. When you first contact BonZumo, describe the planned workstations, devices and network connections so you can assess the specific setup together. For you, that means being organized: do not send only model numbers. Prepare a small sketch or photos of the work areas too. That makes the technical assessment much more useful.

    Separate minor limitations from real failure risks

    Not every older device has to be perfect to remain in use. What matters is whether a weakness only means slightly less comfort or whether it seriously threatens operations. A tablet with somewhat weaker battery life can still be fine at a fixed counter. A service tablet that needs recharging again and again during the evening is a risk. A printer that is a bit louder may not matter. A printer that occasionally delays orders affects the kitchen, the bar, and the guest experience directly.

    This distinction also helps in conversations with your provider or technician. Instead of asking generally whether older devices are supported, ask very specifically: is this tablet sufficient for the planned counter interface? Is this printer suitable for the intended output route? What limitation remains if we keep using it? Those are the answers you should get in writing, or at least documented clearly. That turns a vague gut feeling into a traceable decision with named remaining issues.

    Ask for each necessary replacement to be justified separately

    If new hardware is needed in the end, every replacement should have a concrete reason. Good reasons include an unsuitable connection type, an unstable connection at the place of use, too little performance reserve for the workflow, unreliable power supply, or an impractical screen size for your order structure. Weak reasons are broad statements like “that is just how it is done now” or “best to replace everything.” Especially when you already own working devices, it is worth insisting on a strict individual check for each workstation.

    This also makes economic sense. Maybe two tablets can stay in counter use, while only the service tablet has to be replaced. Maybe the existing LAN printer can remain in the kitchen, while a different output route makes more sense at the bar. BonZumo supports your workflows with table and counter interfaces as well as configurable printing routes, but the hardware decision remains an operational and technical decision for each individual case. The more precisely you have the benefit or weakness of each device described, the lower the risk of buying everything new unnecessarily.

    Get one test result for the full workflow, not only for individual parts

    In the end, you do not need a collection of partial answers. You need one overall picture. So do not have the tablet and printer judged separately only. Have a complete workflow checked: take an order, select items, add a note if needed, send it to the right output point, and continue processing it in the correct context. Only when that full process runs cleanly on your existing devices has reuse really been assessed in a meaningful way.

    To prepare for that check, a few simple materials are enough: your device list, photos of model labels, software versions, a rough sketch of the workstations, and two or three typical order scenarios from your daily business. A café, for example, can walk through counter sales with favorites, a table with an added order later, and separate output to bar and kitchen. That is what creates a reliable answer to your actual question. Whether you can reuse existing tablets and order-ticket printers depends on the checked compatibility of your specific devices. But you can only decide sensibly once model, place of use, and full workflow have been checked together.

    More insights

    Staff deployment planning tool: The practical checks I use before adoptionI do not test a staff deployment planning tool on a quiet day. I test it when someone calls in sick two hours before service and a group booking is due at the same time. In that moment, I need a clear view of tasks, available people, the published shift plan, and the final closing coverage. This is the practical checklist I use when I discuss Bonzumo with my team and decide which access rights, workflows, and review steps we actually need.How can I stand out positively during onboarding?You stand out in onboarding by learning reliably, asking well-timed questions, and following through cleanly—not by trying to look perfect too soon.Restaurant staff training: Practise around a busy serviceFit restaurant staff training into daily service with short learning windows, one clear case per session and a defined place for follow-up questions.When a More Expensive POS System Pays Off for Your RestaurantA more expensive POS system only makes sense once you can measure its value in your own restaurant: with full costs, a clean test, and real time savings.How Many Clicks Simple Admin Tasks Really NeedGood POS software needs as few steps as make sense for simple admin work, but not at the cost of mistakes. What matters is the full path to a checked, saved change.Hospitality training: Identify the real learning needNot every issue needs training right away. Check whether repeated pass questions come from missing knowledge, unclear tasks or missing information.Holiday rota: Checking agreed absences before releasing the weekly planA weekly plan can look complete and still fail the moment a confirmed absence comes back into view. I use the holiday rota as a fixed review step before I switch a rota from draft to published status. This keeps confirmed leave, open holiday requests, replacement cover, and later time questions in one practical workflow instead of turning release day into a scramble.Buying a restaurant POS system: plan the transition before the old workflow slows you downHow I review sales, kitchen, team, and daily close when changing tills so the switch does not surprise us during service.Excel hospitality staff rota: Agreeing the spreadsheet version before a busy weekBefore a packed week, several rota spreadsheets can circulate at once, each with a different holiday note or copied shift pattern. I describe what happens when the Saturday answer is unclear, why last week’s file causes avoidable staffing risk, and how I move from conflicting drafts to one published plan. Bonzumo fits into this as the team framework for shifts, absences, roles, permissions, and a clear draft and published status, without relying on any Excel connection.Managing Food Cost, Costing and Selling Prices TogetherYou keep food cost, recipe costing and selling prices in view together when purchasing units, recipe quantities and selling prices all rely on the same item data.Bar POS system: Organize service, kitchen, and shift handoffs during a rushHow I structure orders and open tasks as a bar operator so the counter stays clear at peak pace.How I Make Payment Guest-Friendly in My RestaurantGuest-friendly payment means short waits, clear totals, fair splits and a finish that guests and staff both understand immediately.Are You Paying for Features You Don’t Use in BonZumo?Not automatically. What matters is which tasks your business actually needs covered and how the scope, included areas, and necessary dependencies are agreed in the offer.POS system with table management: Plan the restaurant flow from guest to closeHow I review reservation, table assignment, order, kitchen, payment, and daily close as one operating sequence.Restaurant POS system: plan the service journey from greeting to closeHow I make typical restaurant workflows visible and build a shared process for service, kitchen, guests, and management.Which Features Are Available Today and What Is Only PlannedFor your decision, only count what can be shown to you in a real workflow today. Everything else should stay clearly separated as planned or still to be checked.How to Use POS System Comparison Guides WellA useful POS comparison guide sorts systems by your real service flow, payment situations, and handoffs, not by a long list of buzzwords.Restaurant inventory management: Organize stock and purchasing in kitchen operationsHow I structure stock movements, deliveries, and team ownership so shortages become visible earlier.Is Hospitality a Profession With a Future?Yes, if a restaurant offers growth, reliable structure, and real responsibility. What makes hospitality a future-proof profession in day-to-day operations.Working time recording: Seeing preparation and closing work clearlyWhen the dining room is empty, work is often still in full motion. From an operator’s perspective, this article shows how I separate sales time from real working time, discuss preparation, polishing, and handover with the team, and review time data in Bonzumo without reducing the conversation to the first booking or the last payment.Can I Open a Small Restaurant Without Much Experience?Yes, but only if you keep the concept deliberately small, learnable, and financially sober from day one.Burnout Prevention in Restaurants: What Really Helps at WorkBurnout prevention in restaurants starts with workable shifts, clear handovers, real breaks, and managers who stay reachable when pressure rises.What Belongs to Professional Restaurant Service?Professional service is more than friendliness: it combines preparation, timing, clarity, advice, calm problem-solving and a clean finish guests can trust.Understanding Labour Costs in a RestaurantRestaurant labour costs are more than hourly pay. Here is how I calculate them clearly, fairly, and in a way that actually helps decisions.Free vs paid POS systems: which is better for restaurants?Free can work at a very simple counter. Once service gets messy, the real comparison is workflow, follow-up work and operating risk, not just monthly fees.Are variable working hours legal in restaurants?Yes, but not without limits. In restaurants, variable hours can be lawful only when contract terms, planning, breaks, rest periods and fair organisation all fit together.Hospitality hygiene training template: Adapt it with expert helpA hygiene training template should match your own stations. Review it with qualified support and keep the source and date clearly documented.Time tracking and shift planning: Using clear differences to improve next week's rotaTwo Saturday services finish late, but they do not mean the same thing. In one case, recurring closing work is taking longer than the rota allows. In another, the shift likely ended on time and the final clock-out is missing. I use time tracking and shift planning together in our Bonzumo setup to compare planned shifts with personal time sessions, check plausibility before any correction, and make calmer decisions for next week’s rota.Pizzeria POS system: Coordinating dine-in, collection and the kitchenA pizzeria can have full tables, phone orders and collections arriving at once. Here is how Bonzumo can help organize the path from order to daily close.POS system for restaurants: stay on top of things with a small teamHow I structure shift start, a full dining room, and closing so our team does not have to search across scattered information.Delivery service POS system: Connecting order intake, kitchen work, and handoffA delivery service depends on reliable handoffs. I show how I organize the order queue, team responsibilities, and daily close as a restaurateur.Restaurant ordering system: Move orders through service without needless loopsHow I make the route from a guest's order to the kitchen reliable and assess a system against real restaurant work.Process-driven POS: Why connecting every step beats feature-hopping in your restaurantA modern POS's real strength is not a single flashy function but the way order-taking, kitchen, payments, tips, fiscalization and accounting flow as one traceable process. This article shows how to set up and run a process-driven system so your team spends less time fixing inconsistencies and more time serving guests.Best restaurant POS system: decide based on your restaurant’s real workThe “best” checkout system depends on the problems our operation actually needs to solve. I compare concrete workflows and confirmed scope, not promises alone.Best POS system for restaurants: Test service, corrections, and close in daily workHow I assess usability and operational fit from the restaurant team's perspective and test it across real shifts.Bar POS system: How I keep the counter under control during a rushA busy bar runs more smoothly when orders, open checks, team handovers and the daily close follow a clear routine. Here is how Bonzumo’s bar POS system can help.Restaurant inventory management system: Aligning stock, purchasing, and kitchen workAn inventory system for hospitality is useful only when data matches reality. I show how I organize stock, deliveries, menu availability, and team routines.

    Next step

    See how the workflow fits your operation.

    Contact