Skip to content
Branches and locations, and what each setting changes · lesson 7 of 7 · for the whole-system operator — you run the books Read the full lesson · Back to the course

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another — or read the full lesson, which carries the same steps, the same audio and the whole transcript.

Step 1 — Close a branch without losing its history

You can take a shop out of use safely.

What you do
  1. Check any downstream picker your closure procedure actually depends on…

Step 2 — Know what closing a company takes with it

You will not close an estate by accident.

  • Close branches one at a time unless you mean the whole entity
Screen capture pending the demo tenant

Company Edit, Details tab, with Status set to CLOSED and the confirmation prompt open

Step 3 — Prefer closing to deleting, always

You will keep your history readable.

What you do
  1. Delete here is a soft delete: the record's status becomes deleted…

Step 4 — Agree the code shape before you type it

You will not inherit twenty-two codes you dislike.

What this step names
  1. Company
  2. Branch and location codes are unique across the tenant and upper-cased on…
  3. A duplicate is refused outright

Step 5 — Find out who changed a setting

You will know where to look, and how far to trust it.

  • Note the asymmetry while you are here: the company…
Screen capture pending the demo tenant

Organisation applet, Audit Trail listing with one back-office event selected and its detail panel open

Step 6 — Prove the whole branch with one cash bill

You will know a branch is configured rather than hoping so.

What you do
  1. Take the new branch and finalise one cash bill for a single low-value accessory

Left and right arrows, or the space bar, move between slides. Play and pause belong to you — nothing moves on by itself unless you tick the box above.