Bill of materials: turn component data into product content
Learn what a bill of materials contains, how it differs from sellable products and bundles, and how to map approved product facts into ecommerce channels.
Manufacturers selling on Shopify, Google Merchant Center, Amazon, or AI shopping surfaces need a reliable handoff from production records to channel-ready product information, often governed by a product information management (PIM) system. Engineering systems describe how a product is built; commerce catalogs show what shoppers can buy and compare. Without a clear mapping, a revision change can leave channel data stale or push internal component details into a listing. At Catalog, we structure channel-ready product data while your enterprise resource planning (ERP) or product lifecycle management (PLM) system remains the source of manufacturing structure.
What is a bill of materials?
A bill of materials (BOM) is a structured list of the components and quantities needed to make a specified product. The parent item is the product or assembly being built. Its BOM lines identify the child items consumed to build it. A multi-level BOM can include subassemblies, each with its own component lines.
For example, a fictional Arc Table Lamp might have this structure:
| Parent item | Component | Quantity per parent | Unit |
|---|---|---|---|
LMP-104 Arc Table Lamp | Linen shade | 1 | each |
LMP-104 Arc Table Lamp | Brass base | 1 | each |
LMP-104 Arc Table Lamp | WIR-12 Wiring assembly | 1 | each |
WIR-12 Wiring assembly | Socket | 1 | each |
WIR-12 Wiring assembly | Braided cord | 1.5 | m |
WIR-12 Wiring assembly | Plug | 1 | each |
The table shows both the finished item and the components used to build it. Production planning can expand the wiring assembly into its parts. A customer may still buy one table lamp as a finished product. The BOM overview from Microsoft Learn describes BOMs as product-definition data and separates the material list from the route or production flow that describes operations and resources.
A BOM can include more than physical parts. Depending on the ERP or PLM, records may contain:
| BOM information | What it controls |
|---|---|
| Parent item and component IDs | Which product and parts connect |
| Quantity and unit of measure | How much of each component is planned per parent |
| Level or line sequence | Where a component sits in the hierarchy or production sequence |
| Version, revision, and approval status | Which approved structure applies |
| Effective dates, site, quantity, or product dimensions | When and where a version can be used |
| Line type or procurement information | Whether a line represents an item, subassembly, phantom, or supplier relationship |
The exact fields vary by system. SAP's BOM definition identifies component numbers, quantities, and units of measure as basic line data.
Microsoft documents BOM versions that can be constrained by time period, quantity, site, and product dimensions. Some ERPs use phantom BOMs as intermediate groupings that planning expands into child components; they can have no item-master record of their own. Business Central's phantom BOM guidance explains this structure. Preserve the source version and line type when you connect this data to other systems.
Common types of BOM
Manufacturers maintain different BOM views because engineering, production, planning, and costing answer different questions. The view names and system design vary. A simple operation may use one BOM for several purposes, while a product with frequent engineering changes may require separate views.
| BOM view | Main question | Ecommerce implication |
|---|---|---|
| Engineering BOM (EBOM) | What is the product's design structure? | Approved material, dimension, or compatibility facts may inform customer-facing attributes. Design modules remain engineering structure. |
| Manufacturing or production BOM (MBOM) | What parts and assemblies does production use to build the finished item? | Use the finished sellable item as the channel record. Keep shop-floor detail in the manufacturing system. |
| Planning BOM | What component demand should forecasts or material plans include? | Planning quantities describe material demand, which can differ from a shopper's pack size or bundle. |
| Costing BOM | What material mix should a cost estimate use? | Keep internal cost inputs separate from market price and promotional offers. |
Process manufacturers may use a formula BOM for ingredients, yields, co-products, and by-products. If a customer-facing description needs an ingredient or material statement, publish an approved product specification. Do not derive broad claims from a production line alone. Microsoft's BOM and formula guidance explains these different production views and version rules.
A BOM, a sellable item, and a product listing answer different questions
A BOM describes composition: what goes into making an assembly. A stock keeping unit (SKU) identifies an item your business stocks or sells. A product listing presents that item, its approved attributes, and its offer in a particular channel. Keep the records linked by IDs, with a distinct schema and owner for each.
For the lamp example, LMP-104 may be the finished item in the ERP. The wiring assembly and its socket, cord, and plug remain BOM children. If the lamp is sold in brass and black finishes, each sellable variant needs its own identity and the right variant relationship. Google Merchant Center, for example, uses item_group_id to group product variants such as sizes or colors. That field describes the variant family; the BOM parent-child tree describes assembly.
Google's specification also treats the item ID, title, description, image, price, and availability as separate channel fields. It recommends keeping product IDs stable when data is updated and submitting only a valid global trade item number (GTIN) when one exists. A component's identifier or GTIN cannot stand in for the finished product's identifier. See Google's product data specification.
A bundle is a separate commerce decision. It applies when a shopper buys a defined set or multipack as one offer. That behavior applies to the sellable bundle; it does not turn every manufacturing BOM into a bundle.
Shopify's bundle feature creates a separate product listing and calculates bundle availability from component stock and the quantities required. In Shopify's example, a bundle of two chairs and one desk has seven complete sets available when stock holds 15 chairs and 8 desks, because the chairs are the constraint. Shopify's bundle rules explain the listing and inventory logic.
Which BOM facts should reach ecommerce?
A manufacturing record can inform product content without becoming the product content. Decide what each source field means, who approves it, and whether a shopper needs to see it.
| Manufacturing source | Channel treatment |
|---|---|
| Finished item or variant ID | Map to a stable product or variant record. Keep the BOM key, stock keeping unit (SKU), global trade item number (GTIN), and marketplace ID distinct where they serve different purposes. |
| Component ID, quantity, and unit | Preserve the relationship in manufacturing data. Publish contents only when the customer buys a kit, multipack, replacement part, or another offer where those details matter. |
| Material, finish, dimensions, or compatibility | Map to typed product attributes only when the value describes the finished sellable item and an owner approves it. Normalize units and controlled terms. |
| BOM revision and effectivity | Select the approved version that applies to the relevant product, site, and date. Trigger a content review when a change affects a published claim. |
| Supplier, cost, scrap, routing, and work instructions | Keep in operational systems unless a specific customer-facing use has been approved. |
| Price, currency, availability, shipping, and returns | Source from the systems that own the live commercial offer. A BOM carries no current price or stock state on its own. |
A material value needs the right scope. If a table lamp has one brass base and one linen shade, its product-level material should describe both accurately.
If a BOM shows recycled material in one component, that alone does not support a claim that the full product is made from recycled material. Keep the source and approval attached to the attribute so a channel update does not turn a manufacturing detail into an unsupported promise. Our product attributes guide explains how typed fields and controlled values help product facts stay consistent.
How to connect BOM data to an ecommerce catalog
Treat the BOM structure, sellable product, and channel offer as linked records. That gives engineering, merchandising, ecommerce, and channel teams a shared map without asking one system to own every kind of product truth.
- Name the source of truth. Keep released manufacturing structure in the ERP or PLM that owns it. Assign owners for customer-facing attributes, product media, price, availability, and fulfillment data. A product-data integration needs field ownership as well as a connector. Our product data integration guide covers that operating model.
- Identify what customers can buy. Create or match the finished product and each sellable variant to a stable key. Decide whether a pack or kit is its own offer. Promote a component to a separate product record only when customers can buy it as a product or replacement part.
- Choose the applicable BOM version. Match the variant, revision, approval status, date, site, and quantity context. Preserve the source BOM ID and version so an engineering change can be traced. Microsoft Business Central's production BOM version documentation describes time-valid versions and component quantities.
- Map only approved attributes. Define source field, destination field, unit conversion, allowed values, approval owner, and any conditions. A shade's material may map to a product attribute. A screw's supplier number should remain an internal component identifier. Keep free text from the BOM out of channel descriptions until it is reviewed and mapped.
- Build destination-specific records. A storefront, Google Merchant Center, Amazon, and an AI shopping surface can require different field names, formats, taxonomies, and detail. Map from a normalized product record to each channel's schema. Our product feed management guide shows how one product record becomes separate channel outputs.
- Publication gate. Before a change is published, every product ID is stable, each variant points to the correct parent, the selected BOM version is approved, units are valid, and required channel fields are present. The end-to-end change path runs from source update through attribute review, channel mapping, delivery, and confirmation that only intended product content changed.
The feed row for LMP-104 should describe the lamp the buyer sees. It can include a title, approved description, product image, category, price, availability, and variant fields. BOM children can inform a kit-contents field or replacement-parts relationship when your product model and approved specifications define it. They do not automatically become product rows. This distinction matters more as the same product record supports a storefront, marketplace listings, retail feeds, and machine-readable shopping surfaces.
Bill of materials FAQs
Is a BOM the same as a SKU?
No. A SKU identifies a stock or sellable item. A BOM describes the parent-child component structure used to make an item. One sellable product can have multiple BOM versions for different dates, sites, or product configurations.
Should every BOM component get its own ecommerce listing?
Only if the component is sold as an item, replacement part, kit component, or another customer-facing offer. Internal subassemblies, manufacturing materials, and phantoms belong in the product structure unless your business separately sells them.
Can a BOM generate a product description?
A BOM can provide verified source facts, such as a material or a kit's included contents. A product description still needs approved scope, customer language, and channel formatting. Keep a human approval step for claims that cannot be inferred from the structure alone.
Where Catalog fits
Keep engineering and manufacturing structure in the system designed to govern it. Our channel-facing product data layer structures approved product facts, maps them to destination schemas, publishes them to AI shopping surfaces, and keeps data synchronized. That lets your team reuse verified details from BOM-linked sources without making a product-content system the authority for production.
If your product facts start in an ERP, PLM, supplier file, or spreadsheet and need to reach several selling surfaces, see how Catalog works.
