For every batch, the record shows which raw materials it was made from, when and by whom, and who received it. Goods with the nearest expiry date ship first, and a defective batch is found within hours.
Products spoil quickly, recipe consumption varies, and control must be documented for every batch. Paper and Excel are not enough.
The Odoo website lists the Sales, Accounting, Manufacturing, Shop Floor, Quality and Inventory apps for food. Shop Floor, Quality, PLM and Barcode are in the Enterprise edition (odoo.com/page/editions). Which apps are needed is determined during the diagnostic.
Order, delivery date, invoice; terms for wholesale customers.
Recipe (BoM), batch order, by-product, backorder, cost.
Operators are assigned to work centers; steps and quality checks are in the order.
Raw materials, semi-finished and finished goods; batches, locations, reorder rules.
Four dates tied to the batch and picking by FEFO.
Control points, inspections, defect alert, corrective and preventive action.
Raw material purchasing, supplier history, batch number at receipt.
Managing recipe changes with approval, and rolling them back.
Receiving, picking and reading the batch number with a scanner.
Stock valuation, actual cost, invoice, 12% and 0% VAT.
In Odoo a recipe is a bill of materials (BoM) that contains components, quantities and operations. A manufacturing order launches it with a specific quantity and date: one batch, one order. A large volume can be split into several orders of a set batch size (Split). If actual consumption differs from the recipe, Odoo warns on closing, and the decision is left to the workshop manager.
At each stage the document, batch and status are kept inside Odoo.
The delivery date is entered with the order; perishable products are planned against that date.
At receipt, raw materials are entered with a batch number and expiry date; the supplier's document is saved.
Materials are checked against the recipe; a purchase request is created for any shortfall; by FEFO, the raw material with the nearest expiry is reserved.
The operator carries out the steps, enters measurements and a photo, and opens an alert if there is a defect.
Finished goods are assigned a batch number and expiry date, and the quantity is received into the warehouse.
The batch with the nearest expiry is selected first for an order; an expired batch is not selected.
A batch's path from raw material to customer is visible in a single report; cost is compared with the plan.
Shelf life is assigned only to products tracked by batch (lot) or serial number. On the product card, four dates are set in days: expiration date (Expiration Date), best-before date (Best Before Date), removal date (Removal Date) and alert date (Alert Date). On receipt or production, the batch dates are calculated automatically from these values. The FEFO picking strategy works by the removal date and is chosen on the location or the product category; if it is set on both, the category takes priority.
In the Quality app, a control point defines in which operation, for which product and how often a check is created: every time, at a random percentage, periodically or on demand. Check types: instructions, taking a picture, registering consumption and output, pass/fail, measure. If a defect is found, a quality alert is opened, recording the corrective and preventive action. In Shop Floor, the operator opens the alert directly from the order.
Not everything works out of the box. The list below is clarified against your process during the diagnostic.
| Goal | In standard Odoo | Extra work (BUline) |
|---|---|---|
| Recipe, batch order, by-product | Yes: bill of materials, manufacturing order, Split, By-products | Entering and checking your recipes |
| Batch traceability and shelf life | Yes: lot, four dates, traceability report | Batch numbering rule and additional fields |
| Picking by expiry date | Yes: FEFO (by location or category) | Defining which warehouses and categories the rule applies to |
| Quality control and defects | Yes: control points, alerts (Enterprise) | Transferring your HACCP and control plan into control points |
| Label (ingredients, allergens, nutrition facts) | Odoo's website mentions label preparation; the documentation has no Uzbek format | The label template is agreed at the diagnostic; the data source is the product fields |
| Digital marking (Asl Belgisi) | The Odoo documentation does not describe a connection | Obtaining the code, printing it and linking it to reporting are estimated separately |
| Phytosanitary, veterinary and sanitary documents for export | Documents can be added and attached to an order; the process of obtaining a document in the state system is not described in the Odoo documentation | Document set and reminder procedure |
| Electronic invoice in the tax system | Odoo has an invoice; connection to the tax system is not mentioned in the Uzbekistan localization documentation | Connection to the operator is assessed separately |
| Payroll | Working-time and work-order data are available | The payroll module is a separate project: a ready-made localization for Uzbekistan is not mentioned in the documentation |
The information below comes from official sources (lex.uz, gov.uz). The regulatory framework in the food sector is changing quickly: the version currently in force is rechecked at the start of the project.
Based on the Tax Code, Cabinet of Ministers resolutions and the Odoo documentation.
Each integration is assessed and connected separately. We do not promise that a ready-made connector exists.
Metrics are built from work orders, batches and accounting entries.
The stages follow the general BUline Method; the timeline is agreed in writing after the diagnostic. We study the process for your industry during the diagnostic. Implementation process →
We study the path from raw material receipt to shipment, the recipes, control points and documents. Result: a business requirements document (BRD).
We confirm the apps, batch numbering, expiration dates, FEFO rules, roles and integrations.
In the first sprint, 1–2 product groups go through the full path from recipe to shipment, then the rest.
The planner, storekeeper, operator, quality officer and accountant are trained by role; testing on a real batch.
Intensified support, then new apps, reports and integrations.
This list speeds up the diagnostic; you can start even if not everything is ready.
Yes, when the FEFO strategy is enabled. In the product form, the expiration and removal dates are set in days, the dates for a batch are calculated automatically, and at shipment the batch with the nearest removal date is picked. The strategy is set on a location or a product category.
The batch number is recorded from raw material receipt to shipment to the customer. The traceability report shows where the batch came from, where it was stored and who it went to. The result depends on batch numbers being entered correctly, so we train staff in the entry procedure at receiving and in production.
Odoo maintains control points and inspection records, but it does not draw up a HACCP plan and does not issue a certificate of conformity. The critical points and limits are defined by a food technologist and an expert, and we transfer them into the system.
Odoo's website mentions preparing labels with ingredients, allergens and nutrition facts. Which format meets Uzbekistan's requirements depends on the labeling rules currently in force: the 2017 regulation is marked as no longer in force, so we agree the label template at the diagnostic against the official requirements.
The Odoo documentation does not describe a connection to Asl Belgisi. If your product falls into a marking group (for example, beer or water and soft drinks), obtaining the code, applying it to the product and linking it to reporting are estimated separately at the diagnostic.
Odoo's official Uzbekistan localization (Fiscal Localization → “uz Uzbekistan”) provides 12%, 0% export and exempt taxes, but the examples of exempt goods in the documentation were not found in the current list in Article 243 of the Tax Code. The accountant confirms the VAT treatment of each product, and the taxes are configured accordingly.
The Shop Floor, Quality and PLM apps are available in the Enterprise edition. Odoo Online does not allow modules with custom code; if code-level customization is needed, Odoo.sh or your own server is chosen.
The Odoo license depends on the number of users and apps (terms at odoo.com). The scope of BUline's service depends on product groups, production floors and warehouses, users, branches, integrations, data volume and training; the exact cost and timeline are given in a written proposal after the free diagnostic.
During the diagnostic, we review your processes and tell you where standard Odoo is enough and where configuration is needed — with an app list, edition and phases.