The settings that reach you, the ones that stop at the company, and one that reaches nothing — transcript

Play this as a presentation — one slide per step, with the same narration. Every word of every step is on this page.

This lesson is for you if your Print button does nothing, or an e-mail to a customer arrived empty, or somebody set your branch’s timezone and nothing changed. In about twelve minutes you will know how far a branch setting actually reaches — because some of them govern your shop completely, some are overruled at the company, and one of them is read by nothing at all and will never do what its name suggests.

Step 1 — Know what has to exist before Print works

After this step you will be able to diagnose an empty print dialog in one look. When you press Print, the dialog tries to pre-select a layout: first the default set for your branch and that document type, then the applet’s own printable setting. If neither exists, nothing is selected, and the screen fails before the request even reaches the server. This is why Print can appear to do nothing at all rather than showing an error — the failure happens in the dialog. It is also why one document type prints perfectly at your shop while another does not: the defaults are set per document type, one at a time.

Reference: Printable Formats and Per-Branch Defaults — Four rules for choosing a layout

Step 2 — Explain the e-mail that arrived with nothing attached

After this step you will recognise a silence rather than a failure. When a document goes out by e-mail through a message template, the layout is taken from the format named on the template’s own branch or company link, and if that names none, from your branch’s default. If neither exists, the e-mail is sent anyway — on time, to the right customer, with no attachment and no error raised anywhere. Your customer receives a covering message about an invoice that is not there. Nothing in your outbox says so. If a customer tells you they got an empty e-mail, this is what happened, and it is fixable.

Reference: Printable Formats and Per-Branch Defaults — Four rules for choosing a layout

Step 3 — Accept the two things your branch cannot restyle

After this step you will stop trying. The first is the e-Invoice document — the one with the QR code that your customer can check against the tax authority. Its layout comes from the company, or from a template built into the platform, and your branch’s default is never consulted. Every branch’s e-Invoice looks the same on purpose. The second is your own header and footer: your branch default carries both, but they are handed to the layout as parameters, and whether they appear depends on that layout asking for them. Some do and the ordinary print path does not. Text that never prints is usually this.

Reference: Printable Formats and Per-Branch Defaults — Four rules for choosing a layout

Step 4 — Stop asking for a branch timezone

After this step you will not lose time on it. Your branch record has a Timezone field. It saves, it shows what you typed, and nothing in the platform ever reads it back. Every place that needs to know what day something happened in — the reports, the bank reconciliation windows, the marketplace lookback — reads the company’s timezone, and if the company has none, falls back to Malaysia. So a group with a branch in another country cannot express that here, and a date that looks a day out is a company question, never a branch one. Knowing this saves the argument, and it is not a setting anybody should be changing hopefully.

Reference: Organization — Branch Details, Pick Pack, Extension and Marketplace

Step 5 — Know the branch switch that really does reach everything

After this step you will treat one tick box with the respect it deserves. Skip E-Invoice on your branch record is read at the moment any document from your shop is finalised, and a document is excluded from e-Invoicing if its own flag, your branch’s flag, or the customer’s flag is set. Any one of the three is enough. Ticked on a branch, it silently removes every sale that shop makes from everything the tax authority is told, for as long as it stays ticked, with nothing on the counter to say so. It is the most consequential single tick on your branch record, and it is covered in full in the e-invoicing series.

Reference: Organization — Branch Details, Pick Pack, Extension and Marketplace

Step 6 — Know what happens to your shop when it closes

After this step you will ask for the right thing when a branch shuts. A branch is closed, not deleted: closing takes it out of the pickers and leaves every document, every stock movement and every report line it ever carried exactly where they are. Deleting is the wrong tool and is refused once documents exist, which is the platform protecting your history rather than obstructing you. What is worth doing before the last day is running the month out, because a document finalised while a setting was wrong can sometimes be re-driven and sometimes cannot, and that is a much harder conversation once the shop is shut.

Reference: Organization — Recovering documents finalised before the configuration was right

How the steps fit together

    flowchart TD
  s1["Step 1 — Know what has to exist before Print works"]
  s2["Step 2 — Explain the e-mail that arrived with nothing attached"]
  s3["Step 3 — Accept the two things your branch cannot restyle"]
  s4["Step 4 — Stop asking for a branch timezone"]
  s5["Step 5 — Know the branch switch that really does reach everything"]
  s6["Step 6 — Know what happens to your shop when it closes"]
  s1 --> s2
  s2 --> s3
  s3 --> s4
  s4 --> s5
  s5 --> s6
  

Check yourself

Three to five questions on what you just heard. Every correct answer links to the page that makes it correct, so you can check the source, not just the mark.

Back to the series · Play this as a presentation