2026-06-21 · TajerGo Guides

Rolling Out a New Branch: An Operations Checklist

Q: How do I set up staff access for a new branch correctly?

Create each staff account, assign the correct static role such as Cashier, Manager, or Auditor, and scope the account to this branch. Do not give broader access than the role requires. If an HQ manager needs to also operate the till at the new branch, use a branch-level role override rather than elevating their global permissions.

Quick answer: Rolling out a new restaurant branch requires replicating your menu, pricing, staff roles, and receipt setup from an existing outlet, so the new location is consistent from day one. The most common mistake is treating each new branch as a fresh build rather than a copy of what already works, which introduces configuration drift before the first customer walks in.

Opening a second branch is exciting and stressful in equal measure. The excitement is obvious. The stress comes from realising how much invisible setup holds the first branch together — menu structure, pricing logic, staff permissions, shift rules, receipt templates, VAT configuration — none of which documents itself. TajerGo, the UAE-built restaurant operating system that combines POS, inventory, purchasing, Khata, AI insights, and VAT compliance in one platform, makes branch provisioning a structured process rather than a memory exercise, so new outlets are consistent from their first sale, at AED 499 per branch.

What is branch provisioning?

Branch provisioning is the process of setting up a new outlet so it is fully configured and ready to trade. In a multi-branch group, good provisioning means the new branch inherits the proven setup of existing outlets rather than being rebuilt from scratch. Every element of the existing branch that should be the same — the menu, the pricing, the roles, the receipt template, the VAT settings — gets replicated, and only the genuinely local settings (hours, specific suppliers, local payment methods) are set fresh.

What are the most common provisioning mistakes?

Rebuilding the menu manually. Re-entering a full menu item by item is slow and introduces errors. Prices get transposed, variants get missed, tax profiles get applied inconsistently. A central catalog that propagates to new branches eliminates this.

Creating ad hoc roles. Without a defined role structure, branch managers invent access levels on the fly. The new cashier ends up with manager-level permissions "to make setup easier," and the configuration never gets corrected.

Skipping receipt configuration. The new branch receipt goes live with the wrong address, a missing VAT TRN, or no logo. FTA compliance fails from the first transaction.

Not assigning suppliers before launch. The branch opens and the purchasing team has no supplier list. The first reorder is chaos.

The complete branch launch checklist

Step 1 — Catalog and pricing

[ ] Central menu is current and complete before provisioning begins
[ ] All items have correct base prices, variants, and modifiers
[ ] Tax profiles are applied to all items (VAT-inclusive or exclusive, 5% standard or zero-rated)
[ ] Any branch-specific surcharges or local exceptions are defined and documented
[ ] Items not available at this branch are marked unavailable (not deleted)

Step 2 — Staff, roles, and access

[ ] All staff accounts are created with correct email/phone
[ ] Each account is assigned the correct role (Owner, Admin, Manager, Cashier, Accountant, Auditor)
[ ] Branch assignment is confirmed — each user is scoped to the correct branch(es)
[ ] Branch-level role overrides are applied where needed (an HQ manager who will also operate the till)
[ ] No one has permissions beyond what their job requires

Step 3 — Payment methods

[ ] Payment methods enabled at this branch are confirmed (Cash, Card, Wallet, Khata)
[ ] Any locally required wallet or payment gateway is integrated and tested
[ ] Khata (credit) settings are configured if credit sales will be offered at this branch
[ ] Split payment is tested end-to-end before launch

Step 4 — Receipt and invoice configuration

[ ] Branch name and address are correct on the receipt template
[ ] VAT TRN is applied (inherited from group or confirmed for this branch)
[ ] Logo and branding are uploaded
[ ] Receipt footer includes return policy and any required local text
[ ] Paper size is set to match the printer at this branch (58mm or 80mm)
[ ] A test receipt is printed and reviewed before service

Step 5 — Kitchen display system (KDS)

[ ] Kitchen stations are created and named for this branch's layout
[ ] Station PINs are set and the kitchen tablet link is shared securely
[ ] A test order is sent from the POS to the KDS and confirmed received
[ ] Two-way sync is confirmed (done status on KDS flows back to POS)

Step 6 — Inventory setup

[ ] Opening stock quantities are entered for all stocked items
[ ] Reorder points and safety stock levels are set per item for this branch
[ ] Costing method (FIFO or weighted average) is confirmed
[ ] Batch and expiry tracking is enabled for perishable items if required
[ ] Negative stock policy is set (allow or block)

Step 7 — Supplier assignments

[ ] All suppliers serving this branch are linked in the Admin portal
[ ] Per-supplier contacts and payment terms are confirmed for this location
[ ] The first reorder process is walked through with the branch manager before launch

Step 8 — Shift and cash settings

[ ] Shift open is required before checkout (prevents ghost sales)
[ ] Cash count is required on shift close
[ ] Variance thresholds are set (acceptable vs critical variance levels)
[ ] The branch manager walks through the shift open, cash movement, and close process before day one

Step 9 — VAT and compliance

[ ] VAT is enabled and the correct rate is applied (5% standard rate or appropriate profile)
[ ] TRN displays correctly on all receipt types
[ ] A test tax invoice is generated and reviewed for FTA compliance
[ ] The branch is included in the group's VAT ledger for quarterly returns

Step 10 — Pre-launch operational test

[ ] A full end-to-end test transaction is completed: order, payment, receipt, KDS, inventory deduction
[ ] A Khata (credit) transaction is tested if credit is enabled
[ ] A refund is processed and the manager approval workflow is confirmed
[ ] The shift is opened, test transactions run, and the shift is closed with reconciliation
[ ] All staff have logged in and confirmed their access works as expected

How long should branch provisioning take?

With a central catalog, defined roles, and a checklist-driven process, a new branch can be operationally configured in a single working day. The bottleneck is usually physical setup (printer connection, hardware), not software configuration. Without a central catalog and defined roles, configuration alone can take days and still produce errors.

How TajerGo helps

TajerGo manages all branch settings through the Admin portal's Branches section, with per-branch tabs for operational hours, service modes, payment methods, receipt branding, staff access, suppliers, and capabilities. The central catalog propagates to every branch POS the moment an item is added or updated, so there is no menu re-entry. The 168+ capability RBAC system means roles are defined once and applied consistently at every branch. The onboarding wizard and setup flow guide first-time configuration of catalog, team, and suppliers in a structured sequence. Included at AED 499 per branch, with every feature in from day one.

Frequently asked questions

How do I replicate an existing branch setup to a new branch? In TajerGo, the central catalog, VAT settings, and group-level roles are already shared across branches. For the new branch, you configure the local settings (hours, payment methods, receipt branding, suppliers) in the Branches section of the Admin portal, assign staff to the branch, and run a pre-launch test. You do not re-enter the menu or rebuild roles.

What is the most important thing to check before a new branch opens? Receipt and VAT configuration. A branch that opens with the wrong TRN, missing VAT breakdown, or wrong address on receipts is non-compliant from its first transaction. Run a test receipt and confirm it before service starts.

How do I set up staff access for a new branch correctly? Create each staff account, assign the correct static role (Cashier, Manager, Auditor, etc.), and scope the account to this branch. Do not give broader access than the role requires. If an HQ manager needs to also operate the till at the new branch, use a branch-level role override rather than elevating their global permissions.

Do I need to enter the menu again for each new branch? No, if you use a central catalog. The menu is defined once at the group level and is available at every branch. Branch-level availability toggles let you mark items unavailable at a specific outlet without removing them from the central catalog.

About TajerGo: TajerGo is a UAE-built restaurant operating system that combines POS, inventory, purchasing, Khata, AI insights, and VAT compliance in one platform, from AED 499 per branch, with every feature included and no upgrade gatekeeping.

Want restaurant operations that are ready for VAT, inventory, Khata and AI reporting?
Book a TajerGo demo