A tannery owner or leather goods manufacturer evaluating ERP software runs into a problem that a furniture maker or an electronics assembler never faces: no two hides are the same. One skin from the same batch might yield 22 square feet of usable material, the next only 18, and the grade varies across a single hide, let alone across suppliers. Most manufacturing ERPs, Odoo included, are built around the assumption that a unit of raw material is a fixed, repeatable quantity. Leather breaks that assumption on day one.

This matters because the leather sector, from tanneries processing raw hides to garment, footwear, and accessories units cutting and stitching finished leather, runs on a production chain where material yield, lot-level quality, and outsourced processing stages are the norm rather than the exception. An ERP evaluation that only checks whether “Manufacturing” and “Inventory” exist as modules misses the actual decision criteria. This guide walks through how Odoo’s manufacturing engine handles the leather-specific parts of that chain, where it genuinely helps, and where a CXO should ask harder questions before signing a contract.

What the Leather Production Chain Actually Looks Like

Before evaluating any ERP against this industry, it helps to be precise about the stages involved, because each one creates a different data and traceability requirement:

• Raw hide procurement. Hides or skins are sourced from abattoirs, traders, or tanneries, usually priced by weight or area, with quality graded on the spot or after inspection.
• Cleaning, liming, and tanning. The hide is treated to remove hair and flesh, then tanned (chrome or vegetable tanning) to stabilize the collagen structure and prevent decay. This stage is frequently outsourced to a specialist tannery.
• Splitting and shaving. The tanned hide is split into layers (grain and split leather) and shaved to a consistent thickness.
• Dyeing and finishing. Color, texture, and surface treatments are applied, often in multiple passes depending on the finish specification.
• Grading and cutting. Finished leather is inspected, graded (A, B, C or similar), and cut into panels or components for the end product, whether that is footwear uppers, garment panels, upholstery, or leather goods.
• Assembly. Cut components move to stitching, molding, or assembly lines to become the finished product.

An ERP that only models the last two or three stages, and treats the earlier ones as a generic “raw material purchase,” will not give a tannery or an integrated leather manufacturer the visibility it actually needs.

How Odoo’s Bill of Materials Fits a Multi-Stage Leather Process

Odoo’s Manufacturing app supports multilevel Bills of Materials, where a finished product’s BoM can reference sub-assembly BoMs, and each sub-assembly is manufactured through its own manufacturing order before feeding into the next stage. For a leather goods company, this means treating “finished leather” as an intermediate product with its own BoM (raw hide plus tanning chemicals plus processing operations), rather than forcing the entire tannery-to-finished-goods journey into a single flat recipe.

Each BoM also has an Operations tab where individual production steps, such as liming, tanning, splitting, or buffing, are defined and assigned to specific work centers. This gives a production manager a real work order queue rather than a single undifferentiated “make the leather” task, and it lets the system track how long each stage actually takes against the planned duration, which is useful when a tannery wants to spot where a batch is falling behind schedule.

Where this gets genuinely useful for leather is BoM versioning for grade-dependent recipes. A company that runs different tanning formulations for different hide grades, or different cutting layouts for different leather thicknesses, can maintain separate BoM variants and apply them based on the product variant being produced, rather than relying on a single generic recipe and manual adjustments on the shop floor.

The Hide Variability Problem, and Where Odoo’s UoM Model Falls Short

This is the part most content on this topic skips entirely, and it is the single most important technical question a CXO should ask before selecting any ERP for leather manufacturing, Odoo or otherwise.

Odoo’s product data model assigns one unit of measure per product. A hide might be purchased and costed by square foot, consumed in cutting by square meter for a European buyer’s specification, and reported internally by weight for tanning-chemical dosing. Odoo’s own documentation acknowledges this directly: the system converts between compatible units automatically, but it tracks only one UoM per product in the database. Companies dealing with genuinely variable conversion factors, such as area-to-weight ratios that differ hide by hide, are advised to use lot numbers to separate batches with different effective conversions, and in some cases perform manual inventory adjustments to reconcile quantities across units.

In practice, this means Odoo can absolutely track hide-by-hide variability, but it does so through disciplined lot management rather than a native “variable yield per unit” field. A tannery buying hides by weight and selling cut leather by area needs to plan for:

• Recording incoming hides as individual lots, with the actual measured area or weight captured per lot rather than assumed from a standard conversion factor.
• Using lot-level costing so that a hide that yields less usable area than expected shows a true, higher effective cost per square foot for that specific lot.
• Accepting that some reconciliation between area-based and weight-based reporting will require manual adjustment or a light customization, not a single toggle in Settings.

Any implementation partner who tells a leather manufacturer that Odoo “handles variable yield automatically” out of the box is oversimplifying. The honest answer is that Odoo provides the lot-tracking and UoM-conversion building blocks to manage this well, but the actual yield-variance workflow needs to be configured deliberately around how a specific company measures, buys, and sells leather.

Lot Traceability From Hide to Finished Product

Leather is one of the clearer cases where lot and serial tracking earns its keep. Odoo requires a lot or serial number to be assigned to tracked products before a manufacturing order can be marked complete, which means a finished leather product can be traced back to the specific hide lot, tanning batch, and dyeing run that produced it. This is the mechanism a company would rely on if a customer reports a defect in a specific shipment and the production team needs to identify which raw hide batch, tanning chemical lot, and work center produced the affected pieces, without manually cross-referencing paper batch cards.

For export-oriented leather businesses, particularly those supplying automotive, luxury goods, or footwear brands with their own compliance documentation requirements, this backward traceability from finished product to raw hide lot is often a contractual requirement, not a nice-to-have.

Subcontracted Tanning and Outsourced Processing Stages

It is common for cutting and finishing units to buy semi-finished leather (wet blue or crust leather) rather than run their own tannery, and for tanneries themselves to send certain finishing steps, such as embossing or specialized dyeing, to third-party processors. Odoo’s Manufacturing app has a dedicated subcontracting workflow for exactly this pattern.

When subcontracting is enabled, a BoM can be marked as a subcontracting BoM, which designates the finished product as one manufactured by an outside party using components the contracting company supplies or the subcontractor sources. On receipt of the subcontracted goods, if the components involved are lot- or serial-tracked, Odoo prompts for those numbers to be recorded, preserving the traceability chain even though the actual tanning or finishing happened off-site. Companies can also choose whether raw materials physically pass through their own warehouse before reaching the subcontractor, or ship directly, which matters for businesses trying to keep working capital and in-transit stock visible.

This is a meaningfully different capability from simply recording a subcontracted job as a purchase order line item, which is how many smaller leather businesses handle outsourcing today, usually with a spreadsheet tracking which hides went out and which finished pieces came back.

Quality Checks at Each Processing Stage

Leather quality issues, uneven tanning, grain damage, inconsistent thickness, or color variation, are typically caught at specific checkpoints: after tanning, after splitting, and after finishing, rather than only at final inspection. Odoo’s Quality app supports triggering quality checks tied to specific manufacturing operations or work centers, and logging quality alerts that can be reviewed in a kanban-style board rather than scattered across paper inspection sheets.

For a tannery, this typically means configuring quality check points after the tanning and finishing operations specifically, rather than relying on a single end-of-line inspection, since a defect introduced during tanning is far more expensive to discover only after cutting and stitching have already consumed the material.

A Practical Example: A Mid-Sized Leather Goods Manufacturer

Consider a hypothetical manufacturer producing leather bags who buys finished leather from external tanneries rather than tanning in-house, but cuts, stitches, and finishes the bags internally. Their BoM structure in Odoo would typically involve:

1. A purchased product, “Finished Leather, Grade A,” tracked by lot, with each incoming shipment recorded as a distinct lot carrying its actual measured area.
2. A BoM for each bag style referencing the leather lot alongside hardware components (buckles, zippers, linings), with cutting and stitching defined as operations against dedicated work centers.
3. Quality checks configured after the cutting stage to catch grain defects before stitching labor is invested in a flawed panel.
4. Lot traceability carried through to the finished bag’s serial number, so a customer complaint about a specific bag can be traced back to the leather lot and cutting work order that produced it.

This structure gives the CXO a cost report per style that reflects actual leather consumption per lot, not a theoretical standard cost that ignores yield variance between one leather delivery and the next.

Where Odoo Needs Customization or Third-Party Apps

To evaluate this honestly: standard Odoo does not include leather-specific fields such as hide-area capture at receipt, automatic grade-based pricing tiers, or a built-in nesting/cutting-layout optimizer for maximizing panel yield from an irregularly shaped hide. Businesses with heavy cutting-optimization needs typically either build a lightweight custom module for hide-area capture during goods receipt, or integrate a specialized nesting tool alongside Odoo for the cutting-layout calculation, while keeping inventory, costing, and traceability inside Odoo itself. A CXO evaluating implementation partners should ask specifically how each of these gaps will be closed, and whether the answer is configuration, a small custom module, or a promise to “handle it later.”

A Five-Question Evaluation Framework for CXOs

Before approving an Odoo implementation for a leather manufacturing business, it is worth getting direct answers to:

1. How will hide-level yield variance be captured and costed? Ask the partner to demonstrate lot-level area or weight capture at goods receipt, not just describe it.
2. Which processing stages need their own quality checkpoints? Map this to your actual defect history, not a generic template.
3. Which stages are subcontracted today, and will that continue? Confirm the subcontracting workflow has been configured and tested with your actual subcontractor process, including whether materials transit your warehouse.
4. What is the plan for UoM conversion between purchasing, production, and sales units? If you buy by weight and sell by area, this needs an explicit answer, not an assumption that Odoo converts it automatically.
5. What will require custom development versus standard configuration? Get this in writing before the project starts, since it directly affects both cost and timeline.

Conclusion

Odoo’s Manufacturing app gives a leather manufacturer genuinely useful building blocks: multilevel BoMs for multi-stage production, lot traceability from hide to finished product, a subcontracting workflow built for outsourced tanning and finishing, and quality checks tied to specific work centers. What it does not do is solve hide-to-hide yield variability automatically; that requires deliberate lot-based configuration and, for many businesses, some added tooling for cutting-layout optimization. A CXO who goes into an Odoo evaluation asking about UoM conversion, subcontracting workflow, and lot-level costing specifically for leather will get a far more useful answer from any implementation partner than one who only asks whether Odoo “does manufacturing.” If those specifics check out against your own production process, a working demonstration built around your actual hide-to-finished-product flow is the logical next step.

FAQ

Is Odoo suitable for tanneries specifically, or only for finished-leather goods manufacturers? Both, but the configuration differs. A tannery needs the Manufacturing app configured around tanning, splitting, and finishing as distinct operations with their own work centers and quality checkpoints. A finished-goods manufacturer buying leather externally has a simpler BoM structure focused on cutting, stitching, and assembly, with the incoming leather treated as a tracked, purchased raw material.

Does Odoo handle the fact that hides vary in size and grade within the same batch? Odoo can manage this through lot tracking, recording each hide or batch as a distinct lot with its own measured quantity, but it does not do this automatically out of the box. Because Odoo tracks a single unit of measure per product, businesses buying by weight and selling by area need to plan the lot structure and UoM conversion deliberately during implementation.

Can Odoo manage tanning that is outsourced to a third-party tannery? Yes. Odoo’s subcontracting workflow lets a BoM be marked as subcontracted, tracks components sent to and finished products received from the subcontractor, and preserves lot or serial traceability on receipt, so the outsourced stage does not break the chain of custody from raw hide to finished product.

What quality control features does Odoo offer for catching leather defects early? The Quality app supports quality checks tied to specific manufacturing operations or work centers, meaning checkpoints can be placed after tanning, splitting, or finishing rather than only at final inspection, and defects can be logged as quality alerts for review.

Does Odoo include cutting-layout optimization for maximizing leather yield? No, standard Odoo does not include a nesting or cutting-optimization tool for irregularly shaped hides. Businesses with significant yield-optimization needs typically pair Odoo with a specialized cutting tool or integration, while keeping inventory and costing centralized in Odoo.

How long does an Odoo implementation for a leather manufacturing business typically take? This depends heavily on scope, particularly whether lot-based UoM handling, subcontracting workflows, and custom hide-area capture fields are required. A straightforward cutting-and-assembly implementation is materially faster to configure than a full tannery operation with multiple outsourced stages and grade-based BoM variants.

Is Odoo’s standard costing accurate for a product with variable raw material yield like leather? Standard costing assumes a fixed input quantity per unit produced, which does not reflect hide-to-hide yield variance well on its own. Lot-based costing, where actual consumption is tracked per lot rather than against a theoretical standard, gives a more accurate picture for leather and is the approach most leather manufacturers should configure rather than relying on default standard cost settings.