Your account works. Your numbers, not so much.
We review the tSpoonLab account you already use, centre by centre, and fix what makes your food cost and reports unreliable. With a report of what we changed and why.
Sound familiar?
- 01
"Why does this dish show zero cost?"
- 02
"We buy things every week that never appear in the stock count."
- 03
"This supplier invoices us by the box and the system thinks it’s a single unit."
- 04
"Sales have been coming in lower for months and nobody knows why."
I used to do recipe costings in Excel with old purchase prices, but I needed them to update. We did not have that.
What we review
Duplicate products, or the same product under different names.
Supplier items matched to the wrong product.
Incorrect purchase formats and units that don’t add up.
Products with several suppliers and none set as preferred, which take the price of the first one the system finds.
Products that should be materials.
Purchases not in any store with entries and exits, products in two stores, or hidden.
Recipe costings with lines without cost and unadjusted yields.
Duplicate or unreceived delivery notes, or VAT included in the price.
POS sales without a link or a group.
Leftovers from the generic database that nobody uses.
How we do it
- 01
We read your account.
Without changing anything.
- 02
We detect and propose.
A small number of reliable findings. We don’t flag what’s already right.
- 03
You decide.
We ask what only your operation knows in a clear list.
- 04
We fix and record.
Every change, with its reason.
- 05
We check.
We read the account again to confirm it matches what you approved.
If you have several sites
In a group, the catalogue belongs to everyone and each site manages its own operation. We review the catalogue once and each site’s own suppliers, stores, purchases and sales.
What you get
A clean account.
A report of what we changed and why.
A list of what’s left for you to do, if anything.
What your team needs to know so it doesn’t happen again.