Odoo for Bangladesh's leather and footwear export sector.

Bangladesh's Leather & Footwear Sector

Leather and leather goods are Bangladesh's second-largest export earner after RMG, anchored by a tannery cluster now concentrated at the Savar Tannery Industrial Estate (following the government-mandated relocation from the old Hazaribagh site) and a footwear manufacturing base spanning large integrated players and smaller job-work units feeding both domestic brands and export buyers. The sector's ERP requirements diverge from apparel in three structural ways: raw material (hides) is a natural, non-uniform input priced by grade and area rather than a standardized fabric roll; a single footwear style explodes into dozens of manufacturing variants across size and color; and buyer and regulatory compliance increasingly requires chemical and environmental traceability, not just production and shipping records.

Many footwear exporters in Bangladesh also run garment or accessory lines alongside footwear, and the manufacturing routing concepts that apply across both are covered in Odoo Manufacturing Routing Bangladesh, while the export documentation and duty drawback mechanics that leather exporters rely on (leather goods qualify for specific bond and drawback schemes) are covered in Odoo Landed Costs & Duty Drawback Bangladesh.

Tannery Input Tracking: Wet Blue to Crust

Leather processing runs through defined stages, each producing a distinct tradeable intermediate: raw hide, wet blue (chrome-tanned but unfinished), crust (dried and retanned, ready for finishing), and finished leather (dyed, coated, and ready for cutting). A footwear manufacturer buying finished leather from a tannery, or a tannery itself processing raw hide through to crust, needs each of these stages tracked as a distinct product in Odoo with its own lot traceability, since grade and cost differ materially at each stage and a defect discovered at cutting needs to trace back to the correct incoming batch.

Odoo's Lot/Serial tracking, enabled per product under Inventory > Configuration > Settings > Traceability, is the mechanism for this. Each incoming batch of wet blue or crust leather from a tannery is received as a distinct lot, carrying grade, thickness (measured in millimeters or ounces in leather trade convention), and area in square feet, the standard leather billing unit. This lot then flows through the BOM chain (crust to finished leather to cut components to assembled upper) with full backward traceability, so a quality issue discovered in finished shoes can be traced back to the specific hide batch and, if necessary, the specific tannery lot it came from.

Leather Grade	Typical Use	Relative Cost Index
Grade A (select)	Visible upper panels, premium export styles	100 (baseline)
Grade B	Secondary panels, linings on mid-tier styles	75–85
Grade C	Internal components, insoles, domestic market styles	50–65
Reject / offcut	Small leather goods, accessories, scrap sale	15–30

Recording grade explicitly on each lot, rather than treating all leather of a given type as one undifferentiated stock item, is what makes Odoo's standard costing meaningful in this sector. A footwear style's true material cost depends heavily on which grade of leather was actually cut for it, and a factory that averages cost across all grades will systematically under-cost premium styles and over-cost budget ones.

Size and Color BOM Variant Explosion

Footwear is one of the more demanding categories for BOM management in any ERP because a single style is never really one product, it is a matrix of size and color combinations, each with a physically different bill of materials. A men's leather shoe style offered in sizes 39 through 46 (8 sizes) and 3 colors produces 24 distinct saleable variants, and each size genuinely consumes a different quantity of upper leather, sole material, lining, and thread, since a size 46 shoe is measurably larger than a size 39.

Odoo handles this through Product Variants (configured with Size and Color as variant attributes on a template product under Inventory > Products > Attributes) combined with BOM Variants, which let a single master BOM structure carry different component quantities per variant rather than requiring 24 fully independent BOMs to be built and maintained separately. In practice, this is set up by defining the BOM at the template level with components expressed as a formula or banded quantity (a common approach uses three or four size bands, such as 39-40, 41-42, 43-44, 45-46, each with its own upper leather area and sole consumption figure, rather than a unique figure for every single size), which keeps the BOM maintainable while still capturing the real material variance across the size run.

Leather Wastage and Yield Tracking

Because leather is a natural material with an irregular shape, cutting yield (the percentage of a hide's area actually used in finished components versus lost to trim, defects, and unusable edge) varies by hide, by cutting pattern (nesting layout), and by operator skill, in a way that manufactured materials like woven fabric do not. A skilled cutting operation on quality hides might achieve 80 to 85 percent yield, while poor nesting or lower-grade hides with more natural blemishes can drop yield into the 60s.

Odoo tracks this by comparing actual component consumption recorded at the manufacturing work order (via the Manufacturing app's component consumption screen, ideally captured through barcode scanning at the cutting station rather than end-of-shift manual tally) against the BOM's standard quantity. The resulting variance, aggregated by cutting operator, hide grade, and cutting pattern, surfaces exactly where yield is underperforming, whether that is a specific operator, a specific batch of lower-grade hides, or a specific style's cutting pattern that leaves excessive waste at panel edges.

LWG Compliance Data Needs

Leather Working Group (LWG) certification has become a near-mandatory requirement for tanneries and, increasingly, for footwear manufacturers selling to major international brands, since LWG audits environmental performance, chemical management, and traceability practices. Odoo does not ship a purpose-built LWG compliance module, but the underlying data LWG audits require maps cleanly onto features already covered above: vendor (tannery) certification status and expiry date stored on the vendor record under Contacts > Vendor, full batch traceability from incoming hide lot through to finished goods lot via the standard BOM chain, and chemical input documentation (tanning agents, dyes, finishing chemicals) attached as documents to the relevant purchase orders.

Structured this way, an LWG audit becomes a data export exercise, pulling a specific lot's full genealogy and associated vendor certifications from Odoo, rather than the common alternative of a compliance officer manually reconstructing paper trails from separate registers in the days before an auditor arrives. Factories that have already implemented traceable lot tracking for other reasons, such as buyer-mandated RMG traceability covered in Odoo for RMG & Garments Bangladesh, find the LWG data structure a natural extension of the same discipline rather than a separate system.

Savar Relocation and CETP Compliance Context

The relocation of Bangladesh's tannery cluster from Hazaribagh to the Savar Tannery Industrial Estate, driven by environmental compliance requirements and a High Court directive, tied ongoing tannery operation to functioning Central Effluent Treatment Plant (CETP) capacity at the new site. This context matters for ERP configuration because tanneries at Savar face volume-based compliance reporting obligations to the Department of Environment and the estate's management (under BSCIC), tracking production volume and chemical discharge against CETP capacity and billing.

Odoo is not an effluent monitoring system, it does not measure discharge directly, but it is a reliable source of the production volume and chemical purchase data that feeds into this reporting. Recording chemical input quantities through standard purchase orders and production batch volumes through manufacturing orders gives a tannery's environmental compliance function a consistent, auditable dataset to reconcile against CETP billing and discharge estimates, replacing the common practice of reconstructing production figures from disconnected paper production logs each time a compliance report or an estate management query comes due.

Costing a Footwear Style End to End

Pulling the pieces together, a footwear style's true cost in Odoo rolls up through several linked BOM stages: hide procurement (recorded per lot with grade and area), cutting (with actual yield recorded against BOM standard), upper assembly and stitching, sole attachment (often itself a subcontracted or purchased component, particularly for injection-molded or rubber soles sourced from specialist suppliers), and finishing and packing. Each stage's actual cost, including any subcontracted operations handled through the same subcontracting BOM mechanics covered in Odoo Subcontracting for RMG Job-Work Bangladesh (many footwear factories subcontract specific finishing or embossing operations the same way garment factories subcontract embroidery), rolls up automatically into the finished pair's standard cost.

This end-to-end visibility is what lets a Bangladesh footwear exporter price an export quote with confidence rather than a rule-of-thumb margin on top of a rough material estimate, and it is the same underlying costing discipline that separates factories with reliable margins from those that discover a style was underpriced only after the shipment has already gone out.

Frequently asked questions

How do you track leather batches and grades in Odoo?

Leather hides are tracked in Odoo using Lot/Serial Number tracking enabled on the raw material product (wet blue, crust, or finished leather), with each incoming batch from a tannery recorded as a distinct lot carrying its grade, thickness, and area (in square feet, the standard leather trade unit). Odoo's landed cost and valuation features then let you record each lot's actual cost per square foot, since leather cost varies significantly by grade even within the same hide type, and lot traceability lets you trace a specific pair of shoes back to the specific hide batch it was cut from, which matters for both internal yield analysis and buyer traceability audits.

How do you manage size and color BOM variants for footwear in Odoo?

Odoo handles this through product variants combined with variant-specific Bills of Materials. A single footwear style is set up as a template product with Size and Color as variant attributes, generating one variant per size/color combination (a style with 10 sizes and 4 colors produces 40 variants). Each variant can carry its own BOM with size-specific component quantities, since a size 44 shoe consumes measurably more upper leather and sole material than a size 38 of the same style. Odoo's BOM Variants feature lets you define one master BOM structure and override specific component quantities per size band rather than building 40 fully separate BOMs from scratch, which keeps the setup maintainable even for styles with wide size runs.

How do you track leather wastage and yield in Odoo?

Yield tracking is set up by recording the actual leather area consumed per cutting run against the theoretical area required by the BOM's component quantity, using Odoo's Manufacturing app to log actual material consumption at the cutting work order versus the standard BOM quantity. The variance between actual consumption and BOM standard becomes your measured wastage rate, which can be tracked over time by cutting operator, hide grade, and cutting pattern (nesting layout) to identify which combinations produce below-average yield. Because leather is priced and consumed by area rather than by piece count, this variance has a direct and immediate cost impact that Odoo's standard costing reports surface automatically once consumption is logged accurately.

Can Odoo handle Leather Working Group (LWG) compliance data?

Odoo does not have a dedicated LWG compliance module out of the box, but its lot tracking, vendor management, and document attachment features can be configured to capture the data LWG audits typically require: vendor (tannery) certification status and expiry stored on the vendor record, hide batch traceability from tannery lot to finished goods lot, and chemical/input documentation attached to purchase records for tanning inputs. For factories under active LWG certification, this configuration turns an annual audit scramble for paper records into a structured data pull, though the audit and certification process itself remains external to Odoo and is managed through LWG's own assessment framework.

How does Odoo help with CETP effluent compliance reporting for tanneries?

Odoo is not an environmental monitoring system and does not measure effluent discharge directly, but it can track the production volume and chemical input data (via purchase and manufacturing records) that feeds into a tannery's Central Effluent Treatment Plant (CETP) compliance reporting to the Department of Environment and BSCIC's Savar Tannery Industrial Estate management. Recording chemical purchase quantities and production batch volumes in Odoo gives a tannery's environmental compliance team a consistent, auditable data source to cross-reference against CETP volume-based billing and discharge estimates, rather than reconstructing production figures from separate paper logs when a compliance report is due.