Yes, staff can scan packaged goods alongside prepared food without interrupting checkout if the POS, scanner, and item setup work together. The buying decision is whether your particular setup can handle a mixed order, recover from a bad scan, and let staff finish the sale without a complicated workaround.
Ask each vendor to demonstrate the same order using your sample items. Watch what happens on the cashier’s screen, not just whether the scanner beeps. A useful result shows the right item and price, allows a quantity correction, and gives the cashier a clear way to enter an item when scanning fails.
Build a small sample catalog
Choose fixed-price packaged items that resemble what you sell at the counter: a bottled drink, a bag of chips, and a wrapped cookie, for example. Include a prepared item such as a sandwich so the demonstration reflects a real mixed order. This comparison is for fixed packaged goods; items sold by weight need a separate evaluation.
Hypothetical sample: A café sells a sandwich for $8.00, bottled tea for $3.00, chips for $2.00, and a wrapped cookie for $2.50. The barcode strings in the worksheet below are sample identifiers, not customer data or verified retail barcodes. Ask the vendor how to create or substitute suitable demo codes for its system. Do not assume these strings will scan as printed.
Before the demo, agree on which sample code belongs to each packaged item and which price should appear. Use a separate code for an unknown item and, if the demo setup permits, create a duplicate assignment to see how the system handles it. Keep the expected item list separate from the POS screen so you can check the result rather than simply accepting what appears.
Include the people who will use or maintain the setup. A cashier can judge how many actions are needed at the counter. A manager can ask how item codes and prices are created or changed. Whoever handles equipment should check the proposed scanner and terminal. If different staff cover busy and quiet shifts, invite someone who knows the busiest checkout routine.
Start with a clean demo order. Add the sandwich in the normal way, then scan the tea and chips. The expected subtotal is $13.00: $8.00 + $3.00 + $2.00. This is a merchandise subtotal, not a payment or an all-in operating cost. It excludes tax, payment processing, equipment, software, and any exception-handling costs. The purpose is to check item and price handling, not to estimate the cost of running the POS.
Run the same scan tests in each demo
Use a demo or test environment that cannot charge a card, send a guest message, or dispatch a courier. Do not complete a live payment to prove that an item can be added. If the vendor cannot provide a safe simulation, ask it to demonstrate with an equivalent non-transactional setup and explain the limits.
Run the tests in the same order for each system. Record what the vendor shows, including any setup or staff action needed. A demonstration of one configuration is evidence for that configuration; it does not establish how every scanner or terminal will behave.
- Recognized item: Scan the tea after adding the sandwich. Check the item name and $3.00 price on the order. Then scan the chips and check the $13.00 subtotal.
- Unknown code: Scan a code that has no item assigned in the demo. Ask what the cashier sees and whether the existing order stays available. Try the agreed fallback entry for the intended item.
- Duplicate assignment: Where the demo allows it, assign one code to two items or ask the vendor to show how the system prevents that assignment. Record whether the cashier gets a choice, an error, or another result. Do not assume any particular behavior.
- Repeated scan: Scan the same packaged item twice. Check whether the order shows two units, a separate line, or another result. Then correct it to the intended quantity.
- Mixed-order correction: Remove or change a packaged item while leaving the prepared item on the order. Confirm the item names, quantities, and subtotal before ending the simulation.
A scanner beep alone is not a pass. The cashier needs visible confirmation of what was added. Likewise, an error message is useful only if staff can understand what to do next. Ask the vendor to show the actual fallback path: searching by name, selecting an on-screen item, or another method available in that setup.
Separate a demonstrated result from a promise about future setup. For example, “the demo added tea by scanning” is an observed result. “Every product in our catalog will work immediately” is a broader claim that needs a setup plan. Ask who enters the codes, how prices are checked, and what happens when a supplier changes a package code.
Check the hardware and fix an incorrect quantity
Bring a list of the equipment you intend to use: terminal or tablet model, operating system, scanner model and connection type. If you have not chosen a scanner, ask the vendor to name a compatible option and include it in the quote. Fleksa’s hardware page covers terminals and other restaurant equipment; ask for written confirmation for the specific scanner and device combination you want.
Do not assume an existing scanner or tablet will work because it connects physically. Ask whether the scanner needs a particular configuration, whether it can be shared between devices, and who will help set it up. If a counter uses more than one terminal, clarify which devices need scanners and whether each requires separate equipment or setup.
Then test a mistake a cashier could actually make. In the sample order, the cashier intends to sell one bag of chips but scans it twice. Before correction, the sandwich, tea, and two bags of chips total $15.00. After reducing chips to one, the subtotal should return to $13.00. Watch whether the cashier can identify the extra unit and correct it without rebuilding the order.
The answer may change the purchase decision. Suppose one demo lets the cashier correct the quantity on the order screen, while another requires a manager to intervene for the same correction. If cashiers often work alone and quick self-correction is a requirement, the second setup does not meet that requirement as demonstrated. Ask whether a configuration change can alter the workflow, then repeat the simulation before deciding.
Also compare the proposed fallback with your counter layout. A name search may be workable for a short list of packaged goods but slower if staff must sort through many similar names. Ask the vendor to demonstrate the fallback with names resembling yours and with the cashier starting from the mixed order, not from an empty screen.
Use a scan test sheet to make the decision
The worksheet records the expected result and a useful fallback for each sample. Add your observations beside it in your own notes: what appeared, how the cashier corrected it, and what the vendor had to configure. The barcode entries are hypothetical identifiers; replace them with demo codes the vendor can use.
| Sample item and input | Expected identity and price | Fallback or correction to check |
|---|---|---|
| Bottled tea; sample code 100001 | Tea, one unit, $3.00 | Find tea by name or use another demonstrated entry method. |
| Chips; sample code 100002 | Chips, one unit, $2.00 | If scanned twice, reduce to one and check the subtotal. |
| Wrapped cookie; sample code 100003 | Cookie, one unit, $2.50 | Find the cookie without removing other order lines. |
| Unknown code 100099 | No assigned item; observe the response. | Enter the intended item another way and check its price. |
| Duplicate code assignment | Observe whether setup is blocked or a selection is needed. | Ask how staff or a manager resolves the conflict. |
Use the same pass criteria for every demonstration. For recognized items, the displayed identity and price should match the sample catalog. For an unknown code, the cashier should be able to understand the next step and retain the rest of the order. For duplicate assignments and repeated scans, record the actual behavior and decide whether it fits your staffing. A vendor’s explanation is useful, but a shown correction is stronger evidence than an assumed one.
Before choosing, request a written configuration and quote: POS devices, scanner models, connections, setup work, software charges, and any ongoing support or replacement charges the vendor includes. Ask which costs are fixed, which vary, and which exceptions may create additional charges. Compare the quoted operational totals on the same scope; do not treat a processing fee alone as the full cost. Ask a qualified adviser about contract or tax treatment when needed.
For broader setup questions, review the POS questions and consider how the counter fits with your restaurant management software. Then request a restaurant POS demo using the sample scenario and ask the vendor to document the outcome, compatible equipment, and any unresolved steps.
Frequently asked questions
Can one order include scanned goods and prepared food?
That is the workflow to demonstrate. Add a prepared item, scan packaged goods, and verify each item and the subtotal on the same order before deciding.
What should happen when a barcode is not recognized?
Ask the vendor to show its actual response and a practical fallback. Staff should be able to find or enter the intended item, check its price, and keep the rest of the order intact.
Will an existing barcode scanner work with a new POS?
Not necessarily. Provide the scanner, terminal, connection, and operating system details, then ask for written compatibility confirmation and a demonstration of the intended setup.
