Multi-branch Point of Sale: Tills, Prices and Stock
31 Oct 2026
Each branch has a till, a shift, a price list and a balance. A sale reduces that branch. A transfer between branches is a document, not a chat message. This guide covers what to settle before building the tills, and how that differs from showing quantity on an online store.
A point of sale in a branch is not only a price screen. It is the place where money is taken, an item is reduced from that branch balance, and the drawer is closed at the end of a shift with a figure someone can review. When there are several branches, two questions appear that a single shop never asks. Is the price the same in every branch, and where does the piece come from if a customer asks here while it sits somewhere else. The answers are written before development, because the screen will carry them out as they are, clear or confused.
This page is about the till and movement between branches. Another page is about showing a branch quantity on a store page to a customer who buys on the website. Do not mix the two projects. Both can exist later, but the point of sale answers the cashier day, and the store page answers a visitor who is not standing at the drawer.
The till and the shift
- Each branch has one till or more, and each till has an owner for the shift.
- A shift opens with a float the person counted, not a number carried in memory.
- Every sale, return, or payment out of the drawer is tied to the open shift.
- Closing the shift compares counted cash with what the system says, and records the difference without deleting it.
- Who sees a drawer difference: the branch manager, or accounts, as you decide.
- Permission to void a sale is narrower than permission to sell.
A gap between cash and the system is not a scandal to hide. It is a line to review. If the cashier can change the opening float after close with no trace, you are back to a book nobody can audit. Make the edit an approval with a name. A shift left open for days means closing is not a habit, and then any daily sales report is a figure with no edges.
Name what leaves the drawer besides sales: a petty expense you accept, a payout you recognise. If it has no type in the system, it will be recorded as a vague deduction or not recorded at all. A short list of movement types is enough. Do not build a full accounting ledger inside the point of sale if the accounts program is the master. Post the shift summary, or the receipts, the way the accountant asks, in one direction.
Prices across branches
Either one list owned by management and seen by every branch, or a branch list with lines that differ for a written reason: location, or a local price you have actually approved. A price the cashier changes at the moment of sale, with no limit, is a discount rather than a policy. If you allow a discount, write a ceiling or an approval. If the paper tag disagrees with the screen, the customer will say so, so the person who changes the price in the system is the person who changes what people see, on the same day, not in a file sent at night.
The same item under two codes, because two branches spelled it differently, will break transfers and counts. One code comes before many branches. If you sell a piece and a carton, the relationship is a rule, not a cashier guess each time.
Stock moving between branches
- A transfer is a document: from a branch, to a branch, items, quantities, and a status.
- Minimum statuses: requested, left the source, arrived at the destination. Do not jump from the request to both balances with no departure.
- What has left and not arrived is quantity in transit, not sold, and not still on the shelf.
- A shortage or damage on arrival is recorded on the document, not in a call that is forgotten.
- A sale reduces the branch of the till that sold it, not a branch the screen picks at random.
A WhatsApp message that says we sent you ten pieces is not a transfer. It may be the reason to open the document. If you stay on the message, both balances lie: the source still counts the goods, and the destination sells them. The document is what stops two sales of the same pieces.
Ask one scope question calmly: must the branch sell if the connection drops for an hour. That answer changes the build. Do not assume offline selling is included because the shop cannot stop. If the answer is yes, write it down, and write what happens when the connection returns: which operations upload, and what conflict exists if the last piece was sold in two branches during the gap. If the answer is no, the screen tells the cashier that, instead of showing a false success.
A till receipt and an electronic invoice
A point-of-sale receipt proves a sale in the branch. Whether it must be issued as an electronic invoice in Egypt is a decision for your accountant. It is not an ENS decision, and this page does not settle it. If the accounting program is where invoices are issued, the point of sale sends the sale there, or exports a file the accountant reviews, and does not invent a parallel tax document on its own. Write that into the scope so a printout the accountant will reject is not built.
What to send
- How many branches are in the first version, not a five-year plan.
- Whether the price is shared or differs, and who may change it.
- How goods leave one branch for another today, even as a photo of a paper docket.
- Who closes the drawer, and what you do with a difference.
- Whether a lost connection is a case in which the branch must still sell.
Questions before the build
Is each branch a separate copy of the program?
If you never transfer stock and never read a report across branches, separate copies are possible, and you will pay for merging later. If transfers and a shared price are part of the work today, one record with branch permissions is clearer than files sent every night. Do not start with separate copies and then expect one balance in the second week.
Is the online store in the same scope?
Not necessarily. A store page that shows availability to a customer is a display and integration decision. A point of sale is a drawer and a branch balance. They can meet on the same items later. Mixing them in one agreement before a drawer can be closed with confidence makes both projects stall together.
The retail context is in retail and e-commerce. Showing branch quantity to a website visitor, which is a different question, is in branch stock and the store page. The tills and the transfers are built in custom software development.
The branch count and how a transfer works today are enough to start via start your project. A photo of a transfer docket can be sent with the WhatsApp button at the bottom of this page. The chat arrives tied to the article, and this page does not print a phone number.
