We help manufacturers bring sales, purchasing, inventory and production together in Odoo. We design how the team works in the system, configure the applications and build the integrations with the tools the company already uses.
We start with the way an order travels through your organisation: who confirms the delivery date, how you know there is enough material, and what has to happen before shipping. That sets the scope of the implementation and the order of the work.
Odoo is an ERP system made of connected business applications. It runs different parts of the company in one environment: from customer contact and quotations, through purchasing and production, to goods issue and invoicing.
We match the scope to the way the plant works. Make-to-stock needs different settings from make-to-order, and assembly from bought-in components needs different ones again. Which functions are available depends on the Odoo edition, applications, version and configuration.
Odoo areas in a manufacturing company
Important: Odoo comes in a Community and an Enterprise edition. Not every function described on this page is available in both. Some additional applications and advanced features require Odoo Enterprise. Before the implementation we confirm that the functions you need are available in the chosen edition and hosting model.
We can start by designing a new system, connecting it to e‑commerce or putting an existing environment in order. Pick the situation closest to what your company needs.
You want to replace scattered spreadsheets and apps, or move off your current ERP. We analyse the processes, choose the applications, prepare the data and configure the system. The scope covers testing, user preparation and a go-live plan.
See the Odoo implementation scopeOdoo has to work with the store, the PIM, an external warehouse or accounting. We settle the data sources, the direction of exchange and the update rules, and design the connections with handling for errors, retries and mismatches.
See Odoo integrationsYou already use Odoo and need support, process changes or new functions. We start by assessing the version, configuration, additional modules and integrations, then set priorities, ticket handling rules and a plan for further work.
Discuss Odoo maintenance and developmentYou want to link orders with materials, operations and work on the shop floor. We review the product structure, the planning method and how execution is recorded, and match Odoo to make-to-stock, make-to-order or assembly.
See Odoo for a manufacturing companyWhen passing information between departments starts to hold back order fulfilment. The company takes on more orders, but checking material availability, production dates and shipping status takes more and more phone calls and manual updates.
The sales rep asks the warehouse about stock, production about capacity and purchasing about missing components. The answer for the customer is pieced together from information that may change before the quotation is even accepted.
The stock level does not show the full demand. Part of it is already allocated to other orders, and the planner only finds out about the shortage when production starts.
The customer picks a different variant or raises the quantity. The sales rep updates the quotation, but production keeps working to the earlier specification and purchasing orders components to the old plan.
D2C sales, wholesale and orders taken by account managers draw on the same stock. Without agreed reservation and synchronisation rules, every channel can promise the customer the same goods.
Implementing Odoo does not have to mean replacing every tool. A store on Magento 2 or Shopify can keep serving customers, Pimcore can keep developing product information, and the existing accounting software can keep doing the books.
Before building an integration we settle where each piece of information is created and which system may change it. Prices, availability and order statuses need the most attention, because several departments and sales channels use them at the same time.
An example split of responsibility when Odoo is the operational ERP
| Area | Odoo's role | Working with other systems |
|---|---|---|
| Materials and product structure | Item codes, units, components and BOMs | Linked to engineering data and to product identifiers in the other tools. |
| Prices and commercial terms | Agreed price lists, discounts and customer terms | The store receives the right prices; promotions created in the sales channel get rules of their own. |
| Stock and availability | Stock, reservations and planned moves in the scope run in Odoo | With an external WMS, operation confirmations come back to the ERP. Channels receive the calculated available-to-sell quantity. |
| Orders and fulfilment | Order handling after intake, purchasing, production and shipping | E‑commerce passes the order on and receives the agreed statuses and shipping data. |
| Product content and media | The data needed to handle the product operationally | Pimcore or another PIM can manage copy, images and translations for the sales channels. |
| Documents and settlements | Transaction data and the agreed set of documents | Accounting can run in Odoo or in a connected finance system. |
Materials and product structure
Odoo's role
Item codes, units, components and BOMs
Working with other systems
Linked to engineering data and to product identifiers in the other tools.
Prices and commercial terms
Odoo's role
Agreed price lists, discounts and customer terms
Working with other systems
The store receives the right prices; promotions created in the sales channel get rules of their own.
Stock and availability
Odoo's role
Stock, reservations and planned moves in the scope run in Odoo
Working with other systems
With an external WMS, operation confirmations come back to the ERP. Channels receive the calculated available-to-sell quantity.
Orders and fulfilment
Odoo's role
Order handling after intake, purchasing, production and shipping
Working with other systems
E‑commerce passes the order on and receives the agreed statuses and shipping data.
Product content and media
Odoo's role
The data needed to handle the product operationally
Working with other systems
Pimcore or another PIM can manage copy, images and translations for the sales channels.
Documents and settlements
Odoo's role
Transaction data and the agreed set of documents
Working with other systems
Accounting can run in Odoo or in a connected finance system.
Connecting the systems does not settle the business rules. We describe separately what cancelling an order means, when a reservation is released and which system confirms that goods have shipped.
Using one of your products as the example, we walk through the whole process: taking the order, checking materials, production, inspection and shipping. That shows which applications you need and where the configuration has to reflect the rules of your plant.
We put in order the data that has to travel from the quotation to the order: variant, quantity, price, agreed date and the customer's requirements. We decide who approves exceptions and how a change to an accepted order affects the next steps.
What the team gains
Everything needed to fulfil the order is recorded with the order and available to the right people.
We set the replenishment method, supplier data and delivery lead times. We check which materials the company keeps in stock and which it buys for a specific order, and when a purchase order needs approval.
What the team gains
Purchasing receives organised demand together with the date the material is needed.
We configure bills of materials, operations and work centres. We define how component consumption, working time and produced quantity are recorded, and check how partial completion and deviations from the plan are handled.
What the team gains
The planner and the people running production work from an agreed product structure and see how each order is progressing.
We design receipts, transfers and issues, and how quality control is handled. If the scope includes Odoo Enterprise and the Quality app, checks can be tied directly to the relevant warehouse and production operations. In other set-ups we match the way quality is recorded to the process and the functions available. We also agree what happens to a product that needs rework and when it can move on. If the company tracks lots or serial numbers, we build them into the stock records.
What the team gains
It is clear which products are ready to ship and which need further work.
We agree what information the production manager, sales and the board should see. That can be late orders, material shortages, stock or deviations from the plan. For each indicator we define the source and how it is updated; standard and additional reports are priced separately.
What the team gains
Reports share definitions and come from data recorded during the work itself.
We put in order the data that has to travel from the quotation to the order: variant, quantity, price, agreed date and the customer's requirements. We decide who approves exceptions and how a change to an accepted order affects the next steps.
What the team gains
Everything needed to fulfil the order is recorded with the order and available to the right people.
We set the replenishment method, supplier data and delivery lead times. We check which materials the company keeps in stock and which it buys for a specific order, and when a purchase order needs approval.
What the team gains
Purchasing receives organised demand together with the date the material is needed.
We configure bills of materials, operations and work centres. We define how component consumption, working time and produced quantity are recorded, and check how partial completion and deviations from the plan are handled.
What the team gains
The planner and the people running production work from an agreed product structure and see how each order is progressing.
We design receipts, transfers and issues, and how quality control is handled. If the scope includes Odoo Enterprise and the Quality app, checks can be tied directly to the relevant warehouse and production operations. In other set-ups we match the way quality is recorded to the process and the functions available. We also agree what happens to a product that needs rework and when it can move on. If the company tracks lots or serial numbers, we build them into the stock records.
What the team gains
It is clear which products are ready to ship and which need further work.
We agree what information the production manager, sales and the board should see. That can be late orders, material shortages, stock or deviations from the plan. For each indicator we define the source and how it is updated; standard and additional reports are priced separately.
What the team gains
Reports share definitions and come from data recorded during the work itself.
The decision depends on how the company works: product structure, production flow, number of warehouses, customer requirements and the systems that need connecting. Headcount or turnover alone is not enough to decide.
We test the key scenarios before the scope is approved. We set out what standard Odoo covers, what needs configuration or an extension, and what should stay in a specialist system.
Every stage ends with a result you can check before the next one begins.
We talk to the people responsible for sales, production, purchasing, inventory and finance. We walk through sample orders, documents and exceptions, and settle the goals, the data owners and the dependencies between systems.
ResultA process map, a list of requirements and the areas to verify in Odoo.
We test the key scenarios in a test environment. We separate standard configuration, additional development and integrations, and agree the scope of the first go-live, the acceptance criteria and the tasks on the company's side.
ResultThe scope of work split into stages, a quote and a schedule that allows for data and user preparation.
We configure the applications, roles and working rules, and prepare the data import and the agreed connections. We test the whole business scenario, including quantity corrections, missing material and partial fulfilment where they occur in your process.
ResultA solution verified together with the users on agreed cases.
We prepare users for their tasks and agree when the data moves over and how open orders are handled. After the start we check that the processes and integrations work. Further requests and changes follow the agreed scope of cooperation.
ResultA live scope with clear responsibility for the data, support and development of the system.
The budget covers preparing and implementing the solution and using the system afterwards. Subscription, environment, integration and maintenance costs are shown separately where they apply to the chosen set-up.
Implementing sales and a single warehouse is a different scope from a project covering production, subcontractors, several locations and an online store. The quote and the schedule come after we understand the processes and the data.
The first stage should cover a process that can go live and be judged by how it works. Further areas are added in line with their dependencies, so that no one builds integrations and configuration that will soon need rebuilding.
Answers to the questions we hear most often before a conversation about implementing, integrating and developing Odoo.
Yes. Odoo connects its manufacturing applications with purchasing, inventory and sales. It handles bills of materials, manufacturing orders and operations. Fitting it to a specific plant means checking the product structure, the planning method and how work is recorded. The details are on the Odoo for manufacturing page.
Yes, the project can be split into stages. Future production still has to be reflected from the start in the item code structure, the units and the stock rules. We set the order so that the first stage works on its own and does not block the next one.
Yes, through well-chosen integrations. We settle where products, prices and orders are created and how stock levels and fulfilment statuses are passed on. Before choosing how to connect, we check the system versions, the available interfaces and the limits of the chosen Odoo set-up.
It is not a condition for implementing the other areas. Accounting can stay in the current system if we design the data exchange it needs. If it is to run in Odoo, we analyse the requirements together with the finance team or the accounting firm.
We check the scope of the Polish localisation for the chosen Odoo version and edition and how documents are handled in the company. We do not assume that every Odoo set-up offers the same accounting and localisation functions. We agree which system is responsible for invoices, corrections, the Polish e-invoicing system KSeF and reporting, and verify the settlement scenarios with accounting before go-live.
Odoo Community is the free, open-source edition that forms the core of the system. Odoo Enterprise extends it with additional features and services, including functionality not available in the standard Community edition. So before choosing, we compare the company's actual processes with the applications and functions available in each edition, then factor in the cost of the subscription, hosting, additional modules, integrations and later maintenance.
The hosting model depends among other things on the edition and the extent of customisation. Odoo Enterprise can run on Odoo Online, on Odoo.sh or in your own environment, and Odoo.sh requires the matching Odoo Enterprise subscription. Odoo Community can run in your own environment. Odoo Online does not support custom code modules, so we choose the hosting only once the needs for integrations, extensions and responsibility for maintenance are clear.
No. We check which solutions are still needed, which can be replaced by standard Odoo and which only existed because of the old system's limits. Carrying over every historical customisation enlarges the project and the work on every later update.
We start by assessing the environment, the version, the additional modules, the integrations and the documentation. On that basis we set the scope of the takeover, the fixes needed and the maintenance rules. Version upgrades are planned with testing of your own extensions and connections. More on this scope: Odoo maintenance and development.
A description of what you make, a list of the systems you use and two or three problems that get in the way of work the most. An example order helps too, along with whether you make to stock, to order or a mix of both.
Tell us what you make, how you take orders and what takes the most manual work today. In the first conversation we will agree which processes are worth analysing and whether Odoo meets your organisation's needs.
Already on Odoo? Tell us what is not working as expected and which systems it is connected to.
Enquiry sent
Thank you, we'll get back to you within 1 business day.
The enquiry has not been sent
We have marked the fields that need filling in or correcting.
