The mental model behind every screen — one organization, your companies, the modules your plan turns on, and the roles that decide who sees what.
On this page
Was this helpful?
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
Read this once, before you dig into any one task. Everything else in these docs
assumes the shape laid out here, and the whole app is built from a handful of
ideas that repeat. Keep your home screen open next to this page and you'll see
them in place.
One place, instead of spreadsheets, QuickBooks, and paper
Most operations arrive at Bettr Manager running on three things at once: a
spreadsheet for inventory, QuickBooks for the money, and paper batch sheets on
the floor. The numbers drift apart, and someone spends their week re-keying data
between them to keep the story straight.
Bettr Manager holds purchasing, receiving, inventory, production, and sales in
one system. The lot you receive is the lot you produce with and the lot you
ship — one record, followed the whole way through. Your team stops being the
glue between tools, because there's a single place for the work to live.
Your organization and its companies
When you subscribed, Bettr Manager set up your .
Within it you run one or more companies: the individual plants or entities you
operate, each with its own stock, production, and people.
A single-site maker runs one company. A business with a production kitchen and a
separate commissary runs two, side by side, under the same login. The Active
company picker in the top bar chooses which one you're working in — every lot,
order, and run you see belongs to that company until you switch.
The modules your plan turns on
Bettr Manager is built from modules — Purchasing, Sales, Production, Picking,
Waste records, Invoicing, and a few more. Your plan decides which ones are
switched on. Open the home screen and the Modules grid shows a card for every
module your plan turned on; the sidebar lists the same set. Each card is a door
into that part of the app — Inventory,
Purchase orders, and
the rest. A module your plan doesn't include simply isn't shown, so the app only
ever offers what you have.
There are four plans — Kitchen, Line, Plant, and a sales-led Group — and each
turns on more than the last. Kitchen covers buying, making, and selling; Line
adds picking, waste records, and invoicing; Plant turns on everything, down to
kitchen returns and the staff schedule. When an operation outgrows its plan,
moving up turns on the modules above it, and the work already in Bettr Manager
carries straight over.
Roles, and who sees what
Everyone you invite is a member of one or more companies. What each member can do
is set by . A role
decides who can edit recipes, approve purchases, count stock, or manage people.
Most teams get by on a handful of roles — an administrator, a floor lead, a
quality reviewer. When one person needs a little more or less than their role
gives, you grant permissions to them directly on top, without inventing a whole
new role. Access is checked on every
screen, so a member only ever reaches
the companies and actions they've been given.
The operator's day
The modules line up in the order the work actually happens, and each one hands
off to the next:
Purchasing and receiving — you order from a vendor, then
book in what arrives against that
order. Approved stock becomes real, tracked lots.
Production — recipes turn ingredients into batches on the floor, with the
cooking and cooling logs your batch records need.
Sales and shipping — you pick the right lots for an order, build the
shipment, and send it out.
Invoices — the order you shipped becomes the bill you send the customer.
Nothing is re-keyed along the way. The lot a supplier delivered is the lot you
produced with and the lot a customer received — one thread, from the loading dock
to the invoice.
Why every change is kept forever
Bettr Manager never overwrites. Every count, move, receipt, and shipment is
recorded as its own entry, and the current picture is built from the whole
history — not from a cell someone typed over. Correcting a mistake adds a
correction; it doesn't erase what happened.
That's what turns traceability from a promise into a lookup. Because the whole
chain is kept, you can trace any lot in seconds — forward to every shipment it
went into, and backward to the supplier it came from — following its
. A mock
recall or an audit stops being a scramble through binders and becomes something
you can run before the auditor reaches the door.