Docs menu

Explanation

Why ChowChirp works the way it does.

  • How ChowChirp keeps numbers trustworthy

    Why every figure traces to a stamped entry, why corrections never overwrite, why the product says what a number is based on, and why it refuses to guess.

  • Why approvals need a second factor

    Why a password is not enough for money, access and catalogue changes, how the five-minute elevation and the one-time proof work, and why support can never act as you.

  • How the advisor works

    What the AI advisor can read, why it cites facts and never computes them, why every action is a proposal, and how budgets and permissions bound it.

  • How offline works

    What keeps running when the internet drops, what waits, how the on-premises node uploads in order, and why the browser app is not the offline layer.

  • Why finance is record-only

    Why ChowChirp records payments, tax and filings instead of performing them, what that protects you from, and what would have to be true before that changes.

  • e-Invoice in ChowChirp

    What Malaysia's e-Invoice rules mean for a restaurant, what ChowChirp records versus sends, and how to read the issued, consolidated, self-billed and inbox lanes.

  • Menu engineering explained

    What stars, plowhorses, puzzles and dogs mean, how ChowChirp computes the thresholds from your own sales mix, and how to act on each quadrant.

  • Organisations, outlets and workspaces

    How one organisation holds many outlets, how people are scoped to outlets, how to switch your active outlet, save a default, and use workspaces.