Settings & admin
The Cleaver settings menu groups everything you’d tune on a per-shop basis. Most defaults work out of the box; you’ll touch a few of these within your first week and then leave them alone.
Service product pricing
Settings → Cleaver → Service Products. Five shipping defaults:
| Product | Default | Billed per |
|---|---|---|
| Cut & Wrap | $2.75 | Weight unit |
| Smoke / Cure | $2.20 | Weight unit |
| Sausage Making | $1.80 | Weight unit |
| Kill Fee | $50.00 | Per animal (flat) |
| Aging Premium | $0.50 | Weight unit |
Edit the list_price field on each product and your next sale order
picks up the new rate. No separate “rate config” table; the product
is the rate. Full breakdown in
Service products & pricing.
Cut sheet templates
Settings → Cleaver → Cut Sheet Templates. Add, edit, archive. Templates are filtered by species in the cut-sheet picker so a “Pork — Bacon Heavy” template doesn’t show up for a beef customer.
See Building a cut sheet → Building new templates.
Species & aging defaults
Settings → Cleaver → Species. Pre-seeded with beef, pork, lamb, goat, venison, poultry, etc. Each has a default aging-days target and a “requires aging” flag (off for poultry by default). Tune per-shop.
Primal cuts, cut types, fat ratios, sausage flavors
Settings → Cleaver → Lookups. Every dropdown on a cut-sheet line reads from these lookup tables. Add a new sausage flavor here once and it’s available on every future sheet.
User permissions
Settings → Users & Companies → Users. Standard Odoo group-based permissions. The shortest version:
- Cutters need Internal User + Inventory: User.
- Counter staff need Internal User + Sales: User + POS: User.
- The owner is Admin (Inventory: Administrator).
Full breakdown of what each tier can and can’t do (especially around deletion guards) is in User permissions.
Pricelists (wholesale)
Sales → Configuration → Pricelists. Tiered pricing for restaurant accounts, share-buyer groups, etc. Assign the pricelist to the customer once and every sale order they generate uses it.
Multi-location
If you’re planning a second location, see Multi-location (when you grow) before provisioning anything — picking the right model upfront avoids a migration later.