Skip to content
Decide who may open what, across companies and branches · presentation 5 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.

Decide who may open what, across companies and branches · presentation 5 of 5

What actually stops a sale below cost

You can set up the below-price controls so they work the way you think…

The two halves

Step 1 — Read the two halves as one rule

You will stop looking for a single switch.

Screen capture pending the demo tenant

Application Settings, the price-policy toggles

Step 2 — Know where the line-level block actually lands

You will recognise the symptom.

What this step names
  1. There are three line-level checks — below the item's minimum price
  2. Below its replacement price
  3. Below its moving-average cost — and when one trips
  4. The line is marked invalid
  5. The **Add** button is disabled

Step 3 — Meet the document-level rule, which is the one people notice

You will know why a finished invoice refuses to issue.

Screen capture pending the demo tenant

A sales invoice with the selling-below-cost banner and a greyed-out Final button

What the server does

Step 4 — Understand that none of this is the server

You will describe the control accurately.

Where this step sits
    flowchart TD
  s1["1. Read the two halves as one…"]
  s2["2. Know where the line-level block actually…"]
  s3["3. Meet the document-level rule…"]
  s4["4. Understand that none of this is…"]
  s5["5. Do not build on two switches…"]
  s6["6. Set up the way out before…"]
  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 — Do not build on two switches that cannot work

You will not waste an afternoon.

Where this step sits
    flowchart TD
  s1["1. Read the two halves as one…"]
  s2["2. Know where the line-level block actually…"]
  s3["3. Meet the document-level rule…"]
  s4["4. Understand that none of this is…"]
  s5["5. Do not build on two switches…"]
  s6["6. Set up the way out before…"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  classDef here fill:#1e40af,stroke:#1e40af,color:#ffffff,font-weight:bold;
  class s5 here;
  

The way round it

Step 6 — Set up the way out before you need it

Your counter will not be stuck.

What you do
  1. Write down which of your roles holds which…

NarrationSlide 1 of 10

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.