Portal features
Knife register & blade history
A living inventory of every blade we look after — tagged, photographed, and tied to its own history across orders, inspections, and sites.
More portal features
Explore the rest of the portal
Each card opens a focused walk-through of one area of the same signed-in workspace.
One register, every blade
We tag the knives you want to track. From then on, each blade has its own row in your portal with type, label, last service, current site, and condition notes. Filters let you look at one site at a time, or roll everything up across the group.
Knives
42 tracked · 4 in workshop right now
| Tag | Blade | Site | Status | Last update |
|---|---|---|---|---|
| B-217 | Chef · 24cm | Manchester | In workshop | Today |
| B-204 | Boning · 15cm | Manchester | With you | Sharpened 02 May |
| B-141 | Bread serrated | Leeds | Returned | Returned 28 Apr |
| B-098 | Santoku · 18cm | Liverpool | With you | Due collection |
3 services in the last 6 months.
Last inspection: tip repaired, edge geometry corrected.
Per-knife history that follows the blade
- Every service appears against the same knife — so you can see how often a blade has been sharpened in the last year, not just the last visit.
- Workshop inspections are saved against the knife (edge geometry, tip condition, repair notes) so the next service starts where the last one left off.
- Photos over time let you see how a particular knife is wearing — useful when deciding whether to retire a blade or invest in replacements.
Useful when paperwork would have failed
Multi-site groups already deal with a lot of kit moving around. The register is built for the things spreadsheets quietly get wrong:
- Audits — quickly produce a list of every blade per kitchen with status and last service date.
- Insurance — show condition photos and service history when a claim asks for proof of upkeep.
- Moves between sites — when a blade transfers kitchens, its history follows it; no rebuilding a kit list from scratch.
- Retirement & replacement — clear evidence of how a blade is ageing, so head chef and finance agree on when to replace.
What we replace
Most kitchens we onboard rely on a head-chef spreadsheet (or memory). That is fine until staff turn over. The portal's register removes the single-person dependency: the data lives with the account, not in a person's inbox.
Not every customer wants per-blade tagging — for one-off pay-as-you-go visits we can simply track the batch. Tagging is opt-in on the account.
Linked to every other portal record
Inside the portal, each register entry links straight to the relevant order, collection, and invoice — so the “why” behind every change of state is one click away. See those areas in the feature cards at the top of the page.