Odoo for manufacturers of spice blends, flavourings and functional ingredients.
You make semi-finished products that another manufacturer processes further, and every shipment has to meet that customer's specification. Recipes that differ per customer, allergens on shared production lines, a certificate of analysis with every shipment, and a best-before date that drives your order picking. We set that up in Odoo from day one, so the platform holds when the audit comes and grows with you when your order volume doubles.

Trusted by food producers
Where it gets stuck
Recipes, traceability and shelf life, in one place.
Recipes that fit each customer
One product, five customers, five specifications. In Odoo the recipe is a bill of materials with variants, so you do not maintain five items side by side. When a raw material changes, you see straight away which recipes and which customers it affects.
Traceability the inspector trusts
Every batch of raw material gets a lot number at receipt and keeps it through production, packing and delivery. Forward and backward. A mock recall finds the affected batches in minutes, not days.
Quality and shelf life built in
Control points that block instead of advise, quarantine at lot level, and expiry dates that drive the picking. Expired stock runs into a block, not into a customer.
What we deliver
From recipe to pallet.
Recipes and variants
One product, five customers, five specifications. The recipe is a bill of materials with variants, and the cost per batch reflects the raw material you used that day. When cocoa or protein prices swing, you see it on the batch, not only at month-end close.
Batch and lot management
A lot number at receipt that follows production, packing and delivery. Forward and backward genealogy from raw material to pallet. A recall starts with one question to the system, not with three people and an archive.
Certificate of analysis (CoA) per batch
No shipment leaves your site without a certificate of analysis. The test results are linked to the lot, so the data for that certificate is in the system the moment the batch is ready. With the LIMS add-on the certificate comes straight out of those results, instead of someone assembling it from emails and Excel files. Without LIMS we build the document for you, with your layout and your parameters. That is custom work.
Allergens across shared lines
Allergens follow the recipe, not a separate list someone has to keep up to date. On a shared line you set a quality control point that blocks until cleaning is signed off. The person who releases the line is recorded.
Shelf life, best-before and FEFO
Expiry dates sit at lot level and drive the picking automatically: first expired, first out. Shipping expired stock runs into a block, not into a customer.
Quality control
Control points at receipt, in process and on the finished product, linked to the batch. Whoever rejects puts the lot in quarantine and the rest of the flow knows. No separate quality file next to the system.
Specification management and labelling
Labels and specification sheets come from the same data as the recipe. When an ingredient changes, the label changes with it. Per market and per customer.
EDI to retailers and industrial customers
Orders, deliveries and invoices coming in and going out the way your large customers ask. We build the connections you need and add new ones when a customer comes on board.
Your lab already knows. Your system does not yet.
At most producers, analyses live next to the system. Samples in a spreadsheet, results in a mailbox, specifications in a folder per customer. With our LIMS add-on it all sits in the same Odoo as your recipes, your stock and your invoicing.
You record the sample request, the result is linked to the lot, and the certificate of analysis comes out of it. Specifications differ per customer and per contract, and the LIMS takes that into account. If you outsource your analyses, you load your lab's results through EDI. Because in practice almost nobody outsources everything.
What happens after you get in touch.
Your first steps with Dynapps follow a clear path. No grey areas, no black box.
Discovery
We map your production, recipes, batch flows, shelf-life rules and customer requirements. What fits standard Odoo, what does not, and what your process itself needs to change. We say that last part in discovery, not during go-live.
Configuration
Recipes with variants, FEFO, batch and lot tracking, quality control points, certificates of analysis and EDI, set up the way you actually work. Your consultant has done this before at ingredient and food producers.
Go-live and training
We test against real recall drills, shift handovers and order patterns. Your operators are trained on their own work, not on a demo database.
Continuous improvement
New EDI partners, extra sites, new patterns in your segment. We stay on board after go-live.

Using Odoo feels as intuitive as using a tablet. That ease of use makes a huge difference when you're going live in countries like Kenya or Korea with teams that have never worked with an ERP system before.

Luc Van Mulders
Regional Application Manager at PuratosAt a glance
Dynapps in numbers.
Gold
Odoo partner
50+
F&B references
900+
references worldwide
280+
Odoo experts
ISO 27001
certified
Challenges
The challenges we see most often.
Replacing a legacy ERP
The system that helped the company grow is now holding it back. Exact or EBP, with spreadsheets on the side that nobody dares to touch anymore.
Traceability and recall readiness
Genealogy in hours instead of days. Retailer audits and EU rules raise the bar every year.
Retailer and clean-label requirements
Private-label charters, reformulation, label versions per market, and a specification that differs per customer.
What producers ask us.
Yes. Production, traceability, quality and accounting run on one platform, with recipe bills of materials, lot tracking and quality control points as standard. What you add depends on your segment: certificates of analysis and customer-specific specification sheets are usually custom work on top of the standard.
Every batch received gets a lot number. That lot follows every operation, every packing step and every delivery. Backward, you go from a pallet to the supplier of the raw material; forward, from a raw material lot to every customer who received it. A mock recall is one search.
As variants of one recipe, not as separate items. You maintain the base recipe and the deviations per customer. When a raw material changes, you see in one go which variants and which customers it affects.
We record the test results per lot as standard, through quality control points. The certificate as a document, with your layout and your parameters, we build on top. That is custom work. We would rather say so now than during configuration.
Expiry dates sit at lot level and drive the picking: first expired, first out. Anyone who tries to ship an expired lot runs into a block.
Allergens are linked to the recipe, so they carry through to the end product automatically. For the line itself you set a control point that blocks the next production order until cleaning is signed off, with name and time.
Partly, and we would rather say that straight away. Odoo covers work orders, backflush, quality control points and registration on the floor. If you need a full MES suite with machine connections and real-time OEE, you will need to look further or connect one. In discovery we decide which of the two you actually need.
We start from what actually happens today, not from what the old system can do. In discovery we record which spreadsheets have a real function and which exist because the system could not do it. We build in the first group and drop the second.
Yes. In practice almost nobody outsources everything; some work always stays in-house. You load your external lab's results into the LIMS through EDI, so they sit with your batch and not in a mailbox. On top of that you manage your specifications per customer in one place, and the certificate of analysis comes from the same data.
You do not have to connect anything. With us the lab data sits in the same Odoo as your production, your stock and your invoicing, so a failed result also stops the shipment. If you only run a lab, a standalone LIMS gets you far enough. If you produce and test, you win with one system.
Ready to put production on one platform?
We listen first to how you work today. Then we draw up a concrete plan together, with the gaps named.