Odoo business applications
Inventory, purchasing, manufacturing, quality and fulfilment are one workflow, so they fail as one workflow. This page shows how we connect them in Odoo, which parts are configuration and which need engineering, and what that looked like on five production systems.
Reviewed by Bhavesh Selarka, COO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Odoo Partner · Updated
Businesses that run on what we built
The short answer
It connects the apps that move physical goods: Purchase, Inventory, Manufacturing, Quality, Maintenance and the Sales and Accounting hand-offs on either side. Done properly you get one stock figure, one cost, traceability from receipt to dispatch, and replenishment that reacts to real demand. Done as separate app rollouts you get three sources of truth and manual reconciliation.
Most of the difficulty is not in the apps. It's in the decisions underneath them: how a unit of measure behaves when you buy in kilos and sell in packs, whether a lot is tracked at receipt or at production, which warehouse owns stock in transit, when a cost is standard and when it's real. Those decisions are cheap to make at design time and expensive to change after go-live.
We've built this on both editions, from a foundry running ten-plus casting stages on Community to a food manufacturer with batch traceability and a Shopify storefront on Enterprise. The sections below follow the goods, not the app list.
The connected workflow
One chain, from the signal that starts it to the money it turns into. Each step names the Odoo app that carries it, or the custom work when no standard app does.
Step 01
Sales orders, eCommerce orders, forecasts and minimum stock rules create the need. Reordering rules and the scheduler decide what to buy or make, and when.
Step 02
Requests for quotation, vendor pricelists, lead times and approval limits. Blanket orders for contracted supply, drop-ship where you never touch the goods.
Step 03
Receipts against the PO, quality checks at the gate, lot or serial assigned, put-away rules deciding where it lands. Rejected material never reaches available stock.
Step 04
Multi-warehouse and multi-location stock, units of measure, variants, packaging, expiry, cycle counting and internal transfers. One stock figure, whatever the channel.
Step 05
Bills of material, routings, work centres and work orders. Components consumed, by-products and scrap recorded, finished goods received into stock with their cost.
Step 06
Lot and serial numbers upstream to the supplier and downstream to the customer, so a recall is a query, not an investigation. Certificates printed from the same data.
Step 07
Delivery orders, picking strategies, packing, barcode scanning, labels and carrier hand-off, with backorders and partial shipments handled explicitly.
Step 08
Valuation method, landed costs, manufacturing cost roll-up and automated stock journal entries, so the balance sheet matches the warehouse.
The two places this chain usually breaks: the unit-of-measure boundary between buying and selling, and the hand-off to a sales channel that keeps its own stock. Both are design decisions, not bugs.
Grouped by job
Grouped by the job it does, not by the app it lives in. Every example is from a system in production.
Lot, serial and batch tracking designed around your actual process. Hi-Tech Alloys traces a furnace heat number to every dispatched part, with EN 10204 material test reports generated from the same records.
Multi-stage production with the stages you actually run. Spicy Organic covers blending and packaging with BOM extensions and manufacturing costing. Hi-Tech Alloys tracks ten-plus casting stages including pouring, heat treatment and NDT.
Warehouse restrictions, inter-company moves and per-entity rules. Jo Ann's runs four island entities on one database, with warehouse access restricted per company and stock visible across them.
Scanning at receipt, picking and POS, with labels printed where the work happens. Zealous scans barcodes and prints ZPL price labels. Wild Cloud prints Dymo labels straight from the sales order.
One stock figure behind every channel. Spicy Organic synchronises products, customers, orders, inventory and fulfilment two ways with Shopify, so the store and the ERP agree.
Dashboards and exports built for the people running the day. Wild Cloud gets bulk Excel exports for sales, invoicing and warehouse. Hi-Tech Alloys gets a customer portal for live order tracking.
The honest three columns
The cost ladder for supply-chain requirements, in the order we try them. A requirement that can be configured should never become code.
| Requirement | Standard Odoo | Configuration or OCA | Custom engineering (and why) |
|---|---|---|---|
| Track stock in several warehouses | Yes, out of the box | Locations, routes and put-away rules | Only for access rules per entity, as on Jo Ann's warehouse restrictions |
| Lot or serial traceability | Yes, per product | Tracking policy, expiry dates, removal strategy | When the traceable unit is not the product: a furnace heat, a casting batch, a blend |
| Multi-stage production | BOMs, routings and work centres | Operation types, work-centre capacity, quality checks | When stages carry their own data and status, as in casting: pouring, heat treatment, NDT, machining |
| Barcode and label printing | Barcode app on Enterprise | Report layouts, GS1 formats | Printer-specific formats (ZPL, Dymo) and printing from screens Odoo does not offer it on |
| Selling on another platform | Odoo eCommerce only | Connector apps for common platforms | Two-way sync with field mapping, conflict rules and fulfilment status, as with Spicy Organic and Shopify |
| Costing and valuation | Standard, FIFO or average, automated | Per-category valuation, landed costs | Cost models with your own inputs, such as metal yield or blend recovery |
We quote configuration and engineering separately in the scope, so you can see what you are paying for and drop the parts that are not worth it. The cost page explains the layers.
Edition and OCA
Only the differences that matter to this family. Everything else in the chain is the same on both editions.
| Capability | Community | Enterprise | Notes |
|---|---|---|---|
| Inventory, Purchase, Manufacturing (MRP) | Yes | Yes | Core apps, same framework on both |
| Barcode app | –No | Yes | OCA and custom scanning cover most of it on Community |
| Quality app | –No | Yes | Hi-Tech Alloys runs its own lab and inspection module on Community |
| Maintenance and PLM | –No | Yes | Rarely decisive unless you run planned maintenance in the ERP |
| Shop-floor control | –No | Yes | Enterprise tablet view, or a custom or OCA screen on Community |
| Custom modules | Yes | Yes | Both, and both need upgrade-conscious code |
Supply chain is where Enterprise earns its licence most often, because Barcode, Quality and shop-floor control are Enterprise apps. It is still not automatic: Hi-Tech Alloys runs a full foundry on Community because the traceability was custom either way.
Data and boundaries
How we run it
We walk the chain with the people who run it: receiving, stores, production, dispatch. Output is the flow above, marked with what Odoo does, what gets configured and what needs code.
Units of measure, tracking policy, warehouse and location model, costing method, replenishment strategy. Written down with the reasoning, because these are the expensive ones to change later.
Standard apps configured first, then OCA where it fits, then custom modules for what is genuinely yours. Built upgrade-conscious, never by editing core.
Master data, then opening stock and open documents, each reconciled against the source system and signed off by the person who owns it.
A receipt, a production run, a pick and a dispatch, run end to end by the operators, including the awkward ones: partial delivery, rejected material, a returned lot.
Cutover in an agreed window with a rollback path, then close support through the first month-end and the first stock count.
Evidence
Each of these has the workflow described above running against real stock, not a pilot.
| Project | Industry | Odoo | Key capabilities | Technology |
|---|---|---|---|---|
| Baroda Hi-Tech Alloys | Alloy casting & foundry manufacturing | Odoo 16 Community | Casting Base · Casting Master Data · Casting Engineering · Casting Product | Odoo 16 Community · Python · PostgreSQL · OWL / QWeb · XlsxWriter |
| Spicy Organic | Organic food manufacturing & eCommerce | Odoo Enterprise | Spicy Organic Base · Spicy Organic Product Management · Raw Material Management · Manufacturing & BOM Extensions | Odoo Enterprise · Python · PostgreSQL · OWL / QWeb · Shopify APIs |
| Jo Ann's | Retail & wholesale, duty-free | Odoo 16 Enterprise | Joanns Base · Joanns POS · Joanns POS User Commission · Joanns POS Wholesale | Odoo 16 Enterprise · Python · PostgreSQL · OWL / QWeb · POS blackbox middleware |
| Wild Cloud | eCommerce, manufacturing & wholesale | Odoo 17 Enterprise | Wild Cloud Base · Access Zero Quantity Product in Shop · App Lock · E-Commerce Minimum Cart Quantity | Odoo 17 · Python · PostgreSQL · OWL · QWeb |
| Zealous | Fashion retail & eCommerce | Odoo 18 Enterprise | Zealous Custom Module · Payment (Credit Card) Module · Cash on Delivery (COD) Payment Module · Website Phone Validation | Odoo 18 Enterprise · Python · PostgreSQL · OWL |
Read the projects
A foundry that had to trace a furnace heat to a dispatched part, a food manufacturer with batch traceability and a Shopify store, and a retailer running four island entities.
Alloy casting & foundry manufacturing
Multi-stage alloy casting (molding, pouring, heat treatment, NDT, machining) on Odoo 16 Community, with furnace heat numbers traced to every dispatched part, a metallurgy lab module and Material Test Reports generated in seconds.
Organic food manufacturing & eCommerce
USDA-organic spices, herbs and teas: purchasing, BOMs, blending and packaging operations, batch/lot traceability, manufacturing costing and accounting in Odoo Enterprise, with products, customers, orders, inventory and fulfilment synchronised to the Shopify store.
Retail & wholesale, duty-free
Four Caribbean island entities (each with its own payroll law, currency, fiscal rules and eCommerce site) unified on one Odoo 16 Enterprise platform with a shared core and per-island customization packages.
Workflow review
Send us how goods move today: what you buy, what you make, where you store it and how it ships. You get the workflow mapped to Odoo apps, the decisions you will have to make, and what we would configure versus build. No obligation.
What clients say
Heliconia's Odoo Enterprise implementation, along with third-party system integration, has optimized our processes. Their expertise has been a game-changer.
Vladimir VukovicCEO, Mevalon ProdukteHeliconia delivered an impeccable Odoo Enterprise implementation with seamless integration. Their expertise has revolutionized our operations.
Kartson KrayChairman, TIMmunity GmbHQuestions
Yes, and how far you get with standard apps depends on whether your stages carry their own data. Routings and work orders cover sequential operations out of the box. When each stage has its own records, as in casting (heat request, pouring, heat treatment, NDT, machining), we model the stages explicitly in custom modules, which is what Hi-Tech Alloys runs on Odoo 16 Community.
One system has to own the stock figure, and for physical goods that is the ERP. We synchronise products, customers, orders, inventory and fulfilment both ways, so the store reserves against real stock and the ERP sees the order as it lands.
Spicy Organic runs exactly this: direct-to-consumer through Shopify and wholesale through Odoo, on the same catalog and the same inventory.
Not for the core. Inventory, Purchase and Manufacturing are in Community. Barcode, Quality, Maintenance, PLM and the shop-floor tablet view are Enterprise apps, and those are usually what decides it for a factory or a busy warehouse.
If your traceability or shop-floor screens are custom anyway, Community plus custom modules is a real option. We have built both.
Per product, with a tracking policy of lot, serial or none, and the lot assigned at receipt or at production depending on where identity is created. The important decision is what the traceable unit actually is: a supplier batch, a furnace heat, a blend, or a single serialised item.
Get that wrong and every downstream report is wrong, so we settle it in design, not in configuration.
Usually yes, and it is often custom work rather than configuration. Zealous prints ZPL price labels and scans barcodes at POS, and Wild Cloud prints Dymo labels directly from the sales order.
Tell us the printer model and where in the process people need the label, and we will tell you whether it is a report layout or a module.
Yes. The rate the customer sees at checkout can come from the couriers that will actually deliver, and the parcel status can flow back onto the Odoo delivery so nobody's opening two systems to answer one question. LittleQ quote shipping this way inside a headless Odoo order flow.
Below a few dozen parcels a day, a daily upload is still cheaper than the integration, and we will say so.
Three things, in our experience. Units of measure that were never agreed between purchasing and sales. Opening stock loaded without lots, so traceability starts empty. And a second system that keeps its own stock, which quietly becomes the real one.
All three are design problems, which is why we run the workflow review before anyone configures anything.
It depends on the number of sites, how much custom work the process needs and how clean the master data is, so we scope it after discovery rather than quoting a standard number. For reference, the projects on this site range from a few months for a focused build to multi-year partnerships where the chain keeps growing.
The rest of the chain
Odoo earns its place at the hand-offs between departments, not inside any one of them. These are the families this one exchanges data with every day.
Every operational record eventually becomes a number in the ledger.
The order is where the work and the revenue both start.
People, hours and cost rates sit behind every delivered job.
Sold work has to be planned, delivered and invoiced.
Next step
Tell us how goods actually move today. We will map it to Odoo apps, name the decisions that are expensive to change later, and show you which parts are configuration and which are engineering.