- Create two distinct branch cases
- Trace each order and staff role
- Reconcile the results separately
A multi-branch label is useful only when the differences between your locations are handled correctly.
Illustrative decision process, not a product screenshot or customer result.A growing restaurant considering an Indolj alternative needs to test differences between branches, not merely count the branch names visible in a dashboard. The useful questions concern order destination, menu exceptions, staff responsibilities and reporting boundaries.
This trial is an original buying exercise from Restrova. It can be used with your existing supplier and any proposed alternative. It does not claim that Indolj or Restrova passes a particular test until the behaviour is demonstrated in the agreed configuration.
Choose two deliberately different branches
Use an illustrative setup: Branch A offers lunch pickup and Branch B offers evening delivery. Give one item a different agreed price and make another item unavailable at only one branch. Assign different staff roles to each location.
These differences are intentional. Two identical demo branches can hide the very configuration questions a growing business needs answered. Keep the sample small enough that the owner can independently verify every expected result.
Make destination visible to the customer
Ask how the customer selects a branch and how that choice appears before submission. Test similar branch names and a change of fulfilment method. Determine whether the menu and payable total are rechecked when the branch changes.
Follow the accepted order into the restaurant’s queue. The responsible branch should be clear to staff without someone manually forwarding a screenshot. If a manual process is proposed, document its owner and its limitations rather than treating it as automatic routing.
Record six branch acceptance checks
| Check | Branch A | Branch B |
|---|---|---|
| Opening arrangement | Lunch pickup example | Evening delivery example |
| Item exception | Item remains available | Same item unavailable |
| Price exception | Agreed sample price | Different agreed sample price |
| Order destination | Correct local queue | Correct local queue |
| Staff boundary | Local role sees permitted work | Separate role sees permitted work |
| Closing review | Branch total can be explained | Branch total can be explained |
The table describes the trial conditions, not either supplier’s confirmed functionality. Ask the supplier to complete a result column with demonstrated evidence and outstanding limitations.
Test central control and local responsibility
Decide which menu decisions belong to the central team and which can be made during a branch’s service. Ask how an authorised person changes a local availability state and how a central menu correction reaches the intended locations.
Also test an action that a local staff member should not perform. Access boundaries are easiest to discuss using a concrete role and task. A shared administrator login may be convenient for a demonstration, but it does not prove the role structure your business needs.
Reconcile reports by branch and period
Use a small known set of sample orders. Ask the supplier to explain the reporting period, branch filter and treatment of corrections. The owner should be able to trace the displayed result back to the sample records.
For illustration, if Branch A has three accepted orders and Branch B has two, ask which report counts accepted work and which represents completed or paid work. Those totals need not always be identical. The important requirement is a clear definition, not a forced match between different measures.
Compare scope and growth terms fairly
Indolj’s official website lists branch-management capabilities. Restrova’s multi-branch guidance also describes branch-oriented operating requirements. Neither public description substitutes for a written proposal covering your specific locations, roles and menu rules.
Ask each supplier how additional branches affect the commercial arrangement, onboarding and support process. Do not assume a branch is free or separately charged without checking. Restrova’s published software formula is explained on the pricing page; confirm the agreed branch scope alongside it.
Turn the trial into a decision
Mark the essential outcomes before the demonstration. Wrong branch routing, unexplained branch totals or unacceptable staff access should remain visible blockers. Record any agreed manual workaround, the staff effort it requires and whether it is appropriate during a busy shift.
The related Restrova dashboard video gives reporting and administration context. Request the two-branch exercise in a live demo and compare it with the supplier evaluation guide. If you choose to move, use the handover checklist.
Branch questions
Does multi-branch always mean every branch shares one menu?
No assumption should be made. Ask how shared information and local exceptions work in the proposed configuration.
Can a public customer example prove my branch rules will work?
It can show that an implementation exists, but your exact roles, menu differences and routing rules still require verification.
What should happen if one test fails?
Record the failure, its operational consequence and the proposed resolution. Repeat the test before marking the requirement accepted.
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.


