We are implementing NetSuite for an adhesive tape converting operation and would like guidance on best practice UOM + BOM structure.
Our manufacturing flow:
RAW WEB (coated master web, cost driven by m²)
→ JUMBO (master roll)
→ LOG (slit roll)
→ FINISHED ROLL
→ CASE (pack quantity varies by width)
The complexity:
• JUMBO is slit into LOGS.
• LOGS are cut into FINISHED ROLLS.
• The number of ROLLS per LOG varies depending on finished width.
• The number of ROLLS per CASE also varies by SKU (e.g., 24, 36, 48, 72, 144).
• Yield % and trim waste vary by slit configuration.
• We do not have a fixed universal conversion ratio.
Questions:
1. For the CONVERTING UOM group (JUMBO / LOG / ROLL), should we:
• Set base = JUMBO and conversion rates = 1 for all derived units?
• Or attempt fixed ratios?
Our concern is avoiding misleading static conversions since slit yield varies.
2. For finished goods where case pack varies per SKU, is it better to:
• Use multiple UOM definitions (CASE-24, CASE-36, CASE-48, etc.)?
• Or create packaging assemblies?
We understand NetSuite does not support item-specific conversion ratios within one UOM type.
3. Would best practice be:
• JUMBO and LOG as Assembly items
• FINISHED ROLL as Assembly item
• Case pack handled via UOM conversion only (not assembly)?
Or is it preferable to build a packaging assembly step?
4. Costing question:
Since cost is fundamentally driven by area (m²), is it recommended to:
• Keep RAW and COATED WEB in an AREA UOM type
• Use roll-count UOM for WIP/FG
• Let BOM quantities manage conversion rather than UOM math?
Our goal:
• Avoid SKU explosion for pack sizes
• Maintain accurate costing
• Prevent incorrect UOM conversions between JUMBO/LOG/ROLL
• Keep Amazon / B2B integrations clean
Would appreciate recommended structure for:
• UOM group design
• BOM layering
• Assembly vs inventory item decision
Thank you.