Skip to content
Companies, branches and dimensions, and what each one decides · presentation 2 of 5 · for the whole-system operator — you run the books Read the transcript · Back to the series

These slides need JavaScript to advance one at a time. Without it every slide is shown below, one after another, each with its own player — or read the transcript, which carries the same steps and every word.

Companies, branches and dimensions, and what each one decides · presentation 2 of 5

A branch is where you traded; a location is where the stock is

You can say which of the two records any given fact belongs on, name what breaks when a branch has the wrong main location…

Step 1 — Ask the two questions separately

You can file any new fact on the right record.

Where this step sits
    flowchart TD
  s1["1. Ask the two questions separately"]
  s2["2. Know that the location…"]
  s3["3. Set each branch's main location deliberately"]
  s4["4. Find both places a location is…"]
  s5["5. Know that a location can belong…"]
  s6["6. Stop waiting for the branch hierarchy"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s1 here;

Step 2 — Know that the location, not the branch, is the stock key

You know why the branch column will not answer a stock question.

What this step names
  1. The chain of movements that produces a balance is walked per location
  2. The baskets that first-in-first-out and last-in-first-out costing consume are held per location
  3. Bins and serial numbers hang off a location too

Step 3 — Set each branch's main location deliberately

One till stops refusing to finalise.

  • Set it branch by branch, and set it before the first sale
Screen capture pending the demo tenant

Organisation applet, Branch Edit, the Main Details tab

The link that is really two links

Step 4 — Find both places a location is tied to a branch

A reorganisation stops producing ghosts.

Where this step sits
    flowchart TD
  s1["1. Ask the two questions separately"]
  s2["2. Know that the location…"]
  s3["3. Set each branch's main location deliberately"]
  s4["4. Find both places a location is…"]
  s5["5. Know that a location can belong…"]
  s6["6. Stop waiting for the branch hierarchy"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s4 here;

Step 5 — Know that a location can belong to more than one branch

You can read the symptom.

What this step names
  1. If a location has stopped appearing for a branch after somebody reorganised
  2. There are exactly two places to look
  3. They can disagree

Step 6 — Stop waiting for the branch hierarchy

You will not switch on a field expecting something it does not do.

What this step names
  1. There is a Parent Branch picker
  2. Hidden behind a setting
  3. It writes a parent onto the branch record

NarrationSlide 1 of 8

Left and right arrows, or the space bar, move between slides; f is full screen and Esc leaves it. Clicking the left or right half of a slide pages it. Play and pause belong to you — nothing moves on by itself unless you tick the box above.