- Record exact devices and connections
- Test ordinary and interrupted work
- Document recovery responsibilities
Compatibility belongs to a tested configuration, not merely to a device category or connector shape.
Illustrative decision process, not a product screenshot or customer result.Before choosing a restaurant POS, test the equipment and connection arrangement you intend to use. A supplier’s dashboard running on a demonstration laptop does not prove that your printer, counter device or local network will work the same way. Hardware assumptions can become operating problems at the busiest moment of the shift.
This checklist is for evaluating a proposed setup. It does not claim support for any particular Restrova device, printer, offline mode or third-party integration unless that combination has been verified separately.
Record the exact proposed configuration
Write down the device model, operating system, browser or application version, printer model and connection type where relevant. Identify whether printing happens through the browser, a local service, an application or another supported route.
Also record the network arrangement and who maintains it. Two printers with similar names may use different drivers or protocols. A USB or network connector alone does not establish compatibility with the proposed software.
Test a representative kitchen ticket
Use long item names, multiple quantities, required modifiers and a customer instruction that staff must interpret. Check readability, line wrapping and how the order reference appears. Ask the kitchen team to read the ticket without looking at the cashier’s screen.
If the restaurant uses several preparation stations, ask the supplier to demonstrate the intended routing. Do not assume separate printers or displays can be added simply because the product supports one printing arrangement.
Use an equipment acceptance record
| Check | What to record | Passing evidence |
|---|---|---|
| Device access | Model, system and supported application | Staff can perform the agreed tasks |
| Printer output | Exact model and connection | Representative ticket prints legibly |
| Quantity and modifiers | Known sample basket | Printed instruction matches accepted order |
| Reprint | Authorised repeat request | Staff can identify it as a repeat where required |
| Interruption | Agreed safe test condition | Team understands what was and was not completed |
| Recovery | Named person and procedure | Work can be reconciled without guessing |
Attach the result to the exact configuration. If the hardware or software version changes later, decide which checks need to be repeated.
Distinguish internet loss from power loss
These interruptions create different problems. A network outage may affect synchronisation while devices remain powered. A power outage may stop the device or printer itself. Ask the supplier what the proposed system can actually do in each case.
Do not infer offline operation from the fact that a page remains visible after a connection drops. Test whether a new order can be accepted, where it is stored and how the team reconciles it when the connection returns. If offline behaviour is not verified, document the agreed operating fallback.
Test an uncertain print outcome
In a controlled demonstration, ask how staff determine whether an order printed when the response is unclear. Reprinting without checking can create duplicate preparation. Conversely, assuming that an unprinted order reached the kitchen can leave work unattended.
The acceptance goal is a clear record and responsibility, not a promise that every device interruption can be prevented. Ask what support information the restaurant should collect, such as the order reference and device state, without exposing unnecessary customer details.
Review physical use at the counter
Check screen readability from the staff position, reach to common controls and whether the printer can be accessed without disrupting service. Make sure cabling and placement are handled by the appropriate responsible people. The software demonstration should include the practical environment in which staff will work.
Avoid purchasing replacement equipment based only on a general recommendation in a blog. Obtain confirmation of the exact supported arrangement and a clear understanding of who installs, maintains and replaces it.
Ask Restrova to verify your setup
Start with Restrova’s compatibility checklist and POS service. The related dashboard video demonstrates administration context, not a universal hardware certification. Bring the device and printer details to a demo discussion.
Combine the equipment checks with the rush-hour rehearsal and shift-closing review. A suitable proposal should identify verified equipment, unresolved dependencies and the support responsibilities for each.
Hardware questions
Can I keep my existing printer?
Possibly, but confirm the exact model, connection and supported workflow. This guide does not establish compatibility for a particular printer.
Does cloud software always stop working without internet?
Products differ. Ask for a demonstration of the proposed configuration’s supported behaviour and recovery process rather than relying on the label “cloud”.
Should I test only a basic receipt?
No. Include the long names, modifiers, quantities and routing requirements your kitchen actually uses.
Related Restrova demonstration
This dashboard introduction provides context for discussing restaurant order records and reporting. It does not demonstrate every report, correction, permission or commercial requirement in this guide.
Restrova Restaurant Dashboard Demo
The Restrova dashboard walkthrough introduces order statistics, recent orders and a sales overview, alongside access to restaurant management tools.
Watch this demonstration on YouTube · Published
Written overview, not a transcript. Use a live demonstration to verify the specific requirements in this guide.


