Receiving is the core of your management.
If a delivery note goes in wrong, everything after it gets dirty: your dish costs, stock counts, reports and accounting. We make sure every purchase goes into tSpoonLab correctly, on time and with anything unusual visible, so you decide on clean data.
If receiving fails, everything else gets dirty.
EVERY PURCHASE
Receiving
Price, format, store and account for every line.
Your dishes
one price received wrong changes the cost of every recipe that uses it.
Your stock counts
what comes in without a store or with the wrong format doesn't match when you count.
Your reports
real cost stops resembling theoretical cost.
Your accounting
invoices that don't match their delivery notes, and VAT entered wrong.
- "Delivery notes sit in a folder until month-end."
- "We’ve already received this delivery note twice."
- "The supplier put the price up and nobody noticed."
- "We receive with VAT included in the price."
If I notice a price that should not be there, I claim it immediately, because that supplier's error will drag on across 10 more sites and 40 delivery notes.
This isn't taking a photo and forgetting about it.
It works in teams that manage. We provide the control; the decision is still yours.
What we do
We read every delivery note with AI and check it, line by line, against what tSpoonLab read and against each item's history.
We receive it in tSpoonLab: price excluding VAT and VAT separately, each line in its store and with its analysis account.
If the delivery note brings a new product, format or code, we create it and let you know.
We spot anything unusual: prices that jump, VAT included in the price, delivery charges and discounts, missing lines, duplicate delivery notes.
We leave the issue on the delivery note, for your manager or the supplier, and follow it until it's closed.
What didn't arrive isn't received: it's noted, pending the credit note.
We also receive invoices and credit notes, and group each delivery note into its invoice.
What your team does
They order from tSpoonLab, so every delivery note has its order.
They receive goods at the door and check that what arrives matches the delivery note.
They upload the delivery note the same day.
They answer issues on the delivery note itself and claim from the supplier before paying.
From the loading dock to accounting, in five steps.
Your team receives and uploads the note
To its order, as today.
We read and check it
Against what tSpoonLab read and each item's history.
We receive it
What's clear is corrected; anything doubtful is noted.
Your manager answers
On the delivery note itself, and claims if needed.
Ready for accounting
Grouped into its invoice.
Nothing unusual gets lost in an email.
Every issue stays on the delivery note itself, in your language, so your manager can answer it there and claim from the supplier before paying the invoice.
149 € a month per site
With 80 delivery notes included.
From the 81st on, each delivery note costs less the more you receive:
| Delivery notes a month | Price per delivery note |
|---|---|
| From 81 to 250 | €1.20 per delivery note |
| From 251 to 600 | €0.80 |
| Over 600 | €0.60 |
With 300 delivery notes in a month you pay 393 €.
Delivery notes, invoices and credit notes received in the month count. Prices exclude VAT.
What's not included
Fixing what was already wrong in your catalogue: items matched to the wrong product or wrong formats. If needed, we fix it before we start, separately and at a fixed price.
tSpoonLab's delivery note scanning, which tSpoonLab bills.
When we correct a match or teach the system to recognise a supplier, the next delivery note comes in better. And what we learn in one account improves all the others.
FAQ
Start with one site.