E-Receipt and POS: What Must Be Controlled Across Branches?

Start by defining branch, device, user, and shift. Every sale or return should carry these dimensions so differences can be explained and responsibility reviewed.

Prices and discounts need a central source and explicit permissions. Uncontrolled local changes create mismatches between branch activity, reports, and receipts, while a good rule supports documented exceptions.

For connectivity loss, decide what may continue locally and how synchronisation and duplicate prevention work after recovery. It is not enough for the terminal to operate; transactions must not disappear or repeat.

Daily close should reconcile sales, returns, payment methods, cash responsibility, and settlement. Branch control then becomes an operating cycle rather than a sales total.