Everything across every territory. Open one to work in it.
Each territory is a rep's book of business. Reps sign in and see only their own.
| Territory | Reps | Accounts | Configured |
|---|
The catalogue everything is priced from, and what each territory is carrying. Distributor-wide.
The OEM case rule and the equipment and promo sheets are set on the Settings card.
| Territory | Stock locations | Parts on hand |
|---|
What every invoice and delivery slip in this distributor prints. The remit-to block, the logo, and which layout the paper uses.
| Territory | Draft | Ordered | Issued | Signed | Void | All |
|---|
The loan agreement a machine goes out under, and who signs it for you. Kept per state, because the wording is not the same everywhere.
Printed above the signature line, ready for a pen. The software never draws that signature — it cannot know the officer signed.
It prints exactly as typed, blank lines and capitals included — a contract that gets reflowed has been edited. The line items appear above it on the sheet, so wording that says "listed below" is wrong here.
Changing the wording never touches an agreement already raised. Each one keeps its own copy of the text that was signed, which is the whole reason it is stored that way.
Open a territory, then an account, to the machines. Print on any heading prints that level: one page per account, on the letterhead, with a line to sign off the count.
Everything decided once for the whole distributor. Reps never see these; a distributor admin sets them.
What a rep's change waits on. Special orders, time off, new accounts and terms changes always go to the Requests card; incentive changes only when this is on. Who may approve each is ticked per role under Users › What each role may do.
Distributors run this differently, so these are settings rather than rules. They apply to every territory.
What a new fiscal year on the Sales tracker is set up with. A year already set up keeps its own rates; change those from that year's Quotas… dialog. Who may set a territory's quotas is ticked under Users (Set sales quotas).
What each role may do — the capability matrix, under Users.
The reporting calendar — when periods began and each one's length, on the organization's Check-in.
The loan agreement — who signs it and its wording per state, under Equipment.
Marketing — the newsletter and product feature every store sees.
The invoice letterhead and the distributor's own details — under Invoices.
Theme and colours are each person's own, on their Home.
How each territory's week is planned. A plan is the rep's to arrange — this is the view across all of them.
The day the pay and invoicing week ends on is set on the Settings card.
A notice is drawn on its days for every territory it names — a sales meeting, a holiday, a deadline. Nothing on anybody's week moves.
| When | Notice | For |
|---|
| Territory | Planned | Called | Overdue |
|---|
What every account manager sees beside their own numbers. Plain text; a blank line starts a new paragraph. Leave a card empty and it is not shown.
Everyone with a login, and where they sit. Open a branch to drill in; Manage beside a person edits their login.
Yours to set, per role, for this distributor. A rep never gets to change these — capabilities are the permission model.
The switches that used to sit under this table -- approvals, the warehouse, a short van -- are on the Settings card now.
Management is drawn but empty on purpose. The rung does not exist in the role
catalog yet, so nobody can be in it — and a level that quietly rendered nothing would
read as “no managers hired” rather than “not built”. Adding it is one entry in the
catalog the two products share, plus the two functions in rc-76 that hold
the whole role list.
What is waiting for somebody to decide: special orders, time off, new accounts, and changes to terms and spiffs. Approving, declining, taking an approval back and marking one filled are each an act the database records with who and when — nothing here is a status somebody typed.
Your role holds none of the approval capabilities, so this list is read-only for you. They are ticked under Users.
| Kind | Territory | Account | What | Needed by | Asked | By |
|---|
| Territory | Account | What | By | Outcome |
|---|
Revenue, year-on-year and pace, across every territory. Not built. It is designed to be its own surface shared with the menu tool rather than a panel bolted onto this page, so it is named here and lives elsewhere.
Yours, on this browser. It does not affect anyone else, and nothing here is stored against your territory or your accounts.
A preview, so a colour can be tried before the whole app wears it.
Copy the code and send it to somebody; they paste it below on their own screen.
Name it the way the route cards do — the number, e.g. 32. The account importer matches on this.
Rename it, say who runs it, or take it off the books.
Tick a territory to list its accounts, then tick the stores. One store is an ordinary login; two or more make a group the login is assigned to, and its reporting rolls them up like a rep's territory.
No email is sent. The login is handed over in person with its password, and that handover is the proof of identity.
Keep the suggestion or type your own. Their current password stops working immediately, and nothing is emailed.