POS operations guide

Branch price-control checklist for multi-outlet POS

Multi-outlet pricing becomes risky when every branch edits items locally. A good POS process lets the owner control base prices, allow approved exceptions and see whether branches are selling at the right rate.

Practical workflow

Where this setup helps

This checklist helps restaurant chains, bakeries, boutiques, pharmacies where allowed, supermarkets, ice cream parlours, salons and franchise counters with more than one outlet.

How the workflow should run

Keep a central item master, decide branch-specific exceptions, publish price changes with approval, sync branches, test sample bills and review audit logs for local edits.

What to decide before buying hardware

Decide who owns the master price, which branches can have local pricing, how offers are approved, when price changes go live and what happens if a branch is offline.

Reports or checks after rollout

Review branch-wise price variance, unauthorized edits, old price bills, offer usage, sync failures, gross margin and customer complaints after price changes.

Branch price-control flow

Central control still needs a clear exception path for real branch differences.

Step 1

Master item

Head office maintains the item name, tax group, barcode and base price.

Step 2

Exception rule

Approved outlet-level price, menu or offer exceptions are recorded separately.

Step 3

Publish change

The price change is scheduled and synced to selected branches.

Step 4

Test bill

Each branch checks sample items before peak billing starts.

Step 5

Audit report

Owner reviews mismatches, edits and failed sync after rollout.

Hardware and software required

Hardware

  • POS terminal at each outlet.
  • Receipt printer and barcode scanner where used.
  • Reliable internet for sync windows.
  • Backup storage at local outlets.
  • Central admin computer for price review.

Software and data

  • Central item master or controlled export-import workflow.
  • Outlet-wise price and offer rules.
  • Role permissions for local price edits.
  • Sync status and audit logs.
  • Branch-wise sales and margin reports.

Setup sequence

  1. Clean item names and tax groups before applying branch prices.
  2. Define who can edit prices at head office and outlet level.
  3. Create a separate rule for approved branch exceptions.
  4. Schedule price changes away from the busiest billing time.
  5. Test sample bills at every affected branch.
  6. Review unauthorized edits and old-price bills after rollout.

What each person sees

Branch cashier

Bills from approved prices and does not negotiate manual item edits.

Branch manager

Requests price exceptions instead of changing the item master casually.

Owner or head office

Controls pricing while still seeing branch-level realities and exceptions.

Mistakes to avoid

Avoid these during rollout

  • Letting every branch edit the main item price.
  • Changing tax group during a price update without review.
  • Publishing prices without branch sample bills.
  • Using offers to hide permanent price differences.
  • Ignoring sync failures after rollout.

Questions

Should all branches have the same price?

Not always. Rent, delivery cost or local market differences may justify exceptions, but they should be approved and visible.

Who should edit prices?

Usually head office or the owner. Branch exceptions should have permission and audit logs.

What should be checked after a price update?

Sample bills, old price sales, unauthorized edits, sync failures and margin changes.

Where Posnic fits

Posnic Community Edition is the free open-source local POS for billing, stock, tax setup and daily operations. Posnic Cloud is only needed when a business wants branch sync, managed backups, remote dashboards or connected ordering workflows.

Download Community Edition/Contact Posnic