Where your team’s time goes
01 / 03Recipe costs worked out by hand again, every time a supplier puts prices up.
When ingredient prices move, the product cost on file stops reflecting what the next batch will actually consume.
Industries
Food & Beverage
Ingredient prices move faster than the cost sitting on the product. Basalt works out what each batch used at the prices you actually paid, puts wholesale, shop and direct margin in one view, and prepares the paperwork when a lot has to be traced. No more month-end surprise.
Where your team’s time goes
02 / 03Margin exported three times, one channel at a time, glued together in a spreadsheet only one person can run.
Wholesale, shops and direct sales describe the same product differently, leaving one person to rebuild the combined view.
Where your team’s time goes
03 / 03Waste found later, from a stock adjustment, once the batch has gone.
The loss reaches the numbers after the operational moment has passed, when the team can explain it but can no longer prevent it.
Workflows
Know what the batch cost at the prices you paid
- The agent works out what each batch really cost to make, using the price you paid for what went into it rather than the one on file.
- The real number sits next to the old one, it does not replace it.
- One producer we spoke to has 8 to 10 lines whose ingredient prices move, and redoes the margin by hand.
See one product across every channel
- Margin on a single item across wholesale, your shops and direct sales, in one answer instead of three exports.
- A food distributor we spoke to runs 18 sites, with wholesale, retail and a bakery on one Odoo.
Prepare the recall pack from the lot record
- Odoo traces the lot.
- The agent takes that record and prepares the affected customer list, what is left at each site and a draft message.
- A person checks it and sends it.
In your production operation
Does Basalt replace Odoo lot traceability?
No. Odoo remains the traceability source. Basalt assembles the information needed for a review or pack without recreating what Odoo already does.
How do you calculate the real cost of a batch?
From the actual consumption and prices recorded for the selected scope. The result sits beside the reference cost and every gap remains verifiable.
Can an agent trigger a product recall?
No. It can prepare the affected lots, sites, customers and documents. A person decides, reviews and sends the communications.
Odoo already handles expiry dates and FEFO. Is that part of the offer?
Those remain native Odoo functions and Basalt does not resell them. The work starts with missing reconciliation, explanations or controls around the process.
Can you compare margin across wholesale, shops and direct sales?
Yes, when sales, costs and channels are identifiable in the data. Map checks that foundation first and documents any limits.
Deployment and results
Does the whole process need to be in Odoo already?
No. Map also looks at spreadsheets, shared inboxes and tools around Odoo. The first workflow still needs a reliable source and a clear boundary.
How do you work with our integrator?
They remain responsible for the ERP. We document access, objects read or written and dependencies so everyone knows what belongs to Odoo and what belongs to Basalt.
How long does the first deployment take?
The scope aims for a first real use in the first month. Your team mainly explains the task, reviews exceptions and approves production.
Who keeps the final decision?
Your team does. Agents prepare, reconcile, flag and document. A person approves sensitive decisions and sends external communications.
How do you prove the workflow is useful?
We compare time, volume, exceptions and usage with the baseline written during Map. If the result is unclear, the workflow is not presented as a success.
Bring us one workflow that takes too much time.
In 30 minutes, we will see whether it is worth mapping.
Book 30 minutes- Start with a real task
- Look at the modules involved
- Identify the control points
- Choose a clear next step