Summary: When an order comes in for a bundle, the warehouse management system immediately expands the parent SKU into its individual components using a Bill of Materials, then checks inventory and allocates stock at the child SKU level. This means your sellable bundle quantity is always limited by whichever component has the lowest stock. Many 3PLs use phantom assemblies, where components are stored separately and assembled at the pack station, because this approach offers flexibility and simpler inventory tracking. Before signing with a fulfillment partner, ask whether their WMS supports real-time BOM expansion, dynamic parent availability calculations, and proactive alerts for component-level stockouts. Missing components, inventory drift, and overselling often trace back to how well the system handles this parent-child relationship.
A purchase order arrives for a maintenance kit. Five components, one part number, one line item on the order.
From the buyer’s perspective, they ordered a single product. The moment that order transmits to a warehouse management system, something more complex begins.
The system sees a structured recipe, a real-time inventory check across five separate SKUs, and a set of instructions that will guide a picker through the warehouse.
We work with companies across automotive, electronics, pharmaceutical, industrial, and commercial sectors who rely on expert kitting and assembly services for their multi-component products.
Because component shortages cause 12% of unplanned downtime, costing industrial operations an average of $260,000 per hour, maintaining real-time component visibility is an operational imperative. The questions they ask during onboarding almost always trace back to the same underlying architecture.
- How does the system know what’s in a bundle?
- How does inventory get tracked?
- What happens if one component runs out?
This article walks through that sequence from the moment an order is placed to the moment a pick ticket hits the warehouse floor.
Every Bundle Needs a Bill of Materials Before It Can Ship
Before any order arrives, the warehouse management system needs a map. That map is called a Bill of Materials, or BOM. We set up BOMs for every bundle, kit, or assembled product a company moves through our facility.
Think of a BOM as a recipe card. It tells the system exactly which components make up a finished product and in what quantities.
What Is a Bill of Materials in Warehouse Management?
A Bill of Materials (BOM), is a structured list that defines which individual components make up a finished product. In warehouse management, the BOM tells the system exactly what items need to be picked and assembled when an order arrives for a bundle, kit, or multi-component product. The BOM includes the parent SKU, which is the sellable unit that appears on purchase orders, and all child SKUs, which are the physical items stored in the warehouse.
The Parent SKU Is the Orderable Unit
The bundle that appears on a purchase order or in your product catalog is called the parent SKU. This is the item with a part number, a description in your ERP, and an identifier that appears on the packing slip. When managing fulfillment for industrial products, such as an industrial maintenance kit, the parent SKU might be MNT-KIT-500.
Child SKUs Are the Physical Components Inside
Each individual product inside that bundle is a child SKU. These are the actual items sitting on warehouse shelves. The BOM defines the relationship between parent and children.
For that maintenance kit, the BOM in our system would read:
- Parent SKU: MNT-KIT-500
- Child SKU: OIL-FILTER-A1, quantity 1
- Child SKU: AIR-FILTER-B2, quantity 1
- Child SKU: GASKET-SET-C3, quantity 1
- Child SKU: LUBRICANT-500ML, quantity 1
- Child SKU: INSTALL-GUIDE-EN, quantity 1
The Flattened BOM View Shows Every Piece Required to Build the Parent
When the system cannot handle this logic properly, the symptoms show up downstream. Bundles ship missing a component. Given that human error causes 80% of warehouse inventory discrepancies, inventory counts drift rapidly when systems rely on manual workarounds rather than automated child SKU decrementing.
High-velocity kits oversell because the system did not recognize that one component was running low. This structure exists before any order arrives. It sits in the WMS, waiting.
The System Expands the Parent SKU Into Pickable Components the Moment an Order Arrives
An order transmits to the warehouse. Whether it comes through EDI, an ERP integration, an order management system, or a sales channel API, the data reaches our warehouse management system.
Our WMS receives that order and sees the parent SKU, MNT-KIT-500. Immediately, the system references the BOM attached to that SKU. In fractions of a second, the WMS expands the parent into its component child SKUs.
Where the order file showed one line item, the WMS now shows five. Internally, this order has transformed from a single bundle into a pick list of individual products. The buyer will not see this on their end.
Your order management dashboard might not display it either. Inside the warehouse system, the bundle exists as a set of instructions.
Inventory Allocates at the Child Level
With the BOM expanded, the system moves to the next question. Are all five components actually available?
Our WMS checks real-time inventory for each child SKU. It looks at what’s physically in the warehouse, subtracts any units already allocated to other orders, and determines available-to-promise quantity for each component.
If all five child SKUs have sufficient stock, the system allocates inventory. This allocation is a soft reservation. The units are earmarked for this order and have not physically moved yet. This allocation happens at the child SKU level.
Parent Availability Equals the Lowest-Stock Child Component
The parent SKU, MNT-KIT-500, often holds no physical inventory of its own.
Pre-built kits may or may not sit on a shelf depending on your assembly strategy. When using phantom assemblies, the system calculates the parent’s availability dynamically based on the lowest-stock child component.
If your warehouse has 500 oil filters, 500 air filters, 500 gasket sets, 500 lubricant bottles, and only 12 installation guides, your sellable kit quantity is 12. Our system understands that constraint automatically and reflects it in available inventory counts pushed back to your ERP or order management system.
One Shorted Component Makes the Entire Bundle Unfulfillable
When a child component runs short, the consequences cascade upward. If that installation guide hits zero, the entire bundle becomes unfulfillable.
In our system, this triggers a proactive alert. We flag the shortage before it becomes a production delay, a missed shipment, or a compliance issue.
Other systems handle this less gracefully, holding the order in limbo until someone investigates manually. The difference matters when you’re shipping kits at volume or operating under strict delivery windows.
The Order-to-Pick Sequence for a Bundle
Here is the complete workflow from order receipt to warehouse pick ticket:
- Order is placed through your sales channel, ERP, or order management system for the parent SKU
- Order data transmits to the WMS via EDI, API, or system integration
- WMS identifies the parent SKU and retrieves the associated BOM
- BOM expansion occurs and the parent becomes a list of child SKUs with quantities
- Inventory check runs against each child SKU’s available stock
- Allocation succeeds or fails based on whether all children have sufficient inventory
- If successful, soft reservation applies to each child SKU’s inventory
- Pick ticket generates with child SKUs, quantities, and bin locations
- Picker receives instructions and gathers components from their respective locations
- Components arrive at pack station where the bundle is assembled, verified, and packed
This entire sequence, steps one through eight, happens in seconds. The picker sees the output as a list of products to grab and where to find them.
The Pick Ticket Lists Components and Bin Locations
With inventory allocated, the WMS generates work instructions for the warehouse floor. This comes in the form of a pick ticket.
The pick ticket lists each child SKU, the quantity needed, and the bin location where that product lives. For the maintenance kit, a picker working in our facility would see:
- OIL-FILTER-A1: Qty 1, Bin A-12-03
- AIR-FILTER-B2: Qty 1, Bin A-12-04
- GASKET-SET-C3: Qty 1, Bin B-07-02
- LUBRICANT-500ML: Qty 1, Bin A-12-05
- INSTALL-GUIDE-EN: Qty 1, Bin C-03-01
Depending on order volume and warehouse configuration, this pick might be grouped with other orders in a batch. Or it might be handled as a single discrete task.
Either way, the picker receives location-specific instructions derived entirely from the BOM expansion that happened seconds after the order arrived.
Phantom Assemblies Pick Components Separately and Stocked Assemblies Pick Pre-Built Kits
Bundle configurations vary depending on a choice made during setup, and it affects how inventory is stored, picked, and managed.
We support both models and help companies determine which fits their product velocity and operational needs.
What Is the Difference Between Phantom and Stocked Assemblies?
Phantom assemblies exist as instructions in the system. Components are stored separately and assembled at the pack station when an order arrives.
Stocked assemblies are pre-built kits stored as finished units with their own bin locations. Phantom assemblies offer more flexibility and simpler inventory tracking, while stocked assemblies reduce pick time for high-velocity bundles and require managing inventory in two forms.
Phantom Assemblies Offer Flexibility and Simpler Inventory Tracking
Phantom assemblies are the more common approach we implement. The bundle exists as a concept in the system.
When an order comes in, the system expands the BOM, the picker gathers components from their individual locations, and assembly happens at the pack station. The kit comes together in the final moments before it ships.
Phantom assemblies offer flexibility. If you change the bundle contents, we update the BOM and the change takes effect immediately. No existing inventory becomes obsolete. Component-level inventory stays accurate because the system always tracks at the child SKU level.
This approach works well across industries. Pharmaceutical sample kits that require lot tracking on each component.
Automotive service kits where part numbers update with engineering changes.
Electronics bundles where component substitutions happen based on availability.
The phantom model handles all of these without requiring physical rework of pre-built inventory.
Stocked Assemblies Reduce Pick Time and Add Inventory Complexity
Stocked assemblies work differently. The bundle is pre-built and stored as a finished unit.
The parent SKU has its own bin location with physical inventory. When an order comes in, the picker grabs the completed kit directly. No expansion, no multi-location pick, no pack-station assembly.
Stocked assemblies make sense for extremely high-velocity bundles where the labor savings of picking one item outweigh the flexibility costs. They introduce complexity. You now have inventory in two forms, components and finished kits.
The system needs rules for when to build more kits, how to handle component returns, and what happens if you discontinue the bundle.
We default to phantom assemblies unless volume and velocity justify the overhead of pre-kitting.
Ask How the WMS Handles BOM Expansion Before You Sign With a 3PL
The sequence we’ve described, BOM expansion, component-level allocation, dynamic availability calculation, pick ticket generation, happens in seconds.
When it works, orders ship complete, inventory stays accurate, and kits arrive without issue.
When the system cannot handle this logic properly, the symptoms show up downstream. Bundles ship missing a component. Inventory counts drift because the system could not properly decrement child SKUs. High-velocity kits oversell because the system did not recognize that one component was running low.
Warehouse management systems vary in how they handle BOM logic.
Some require manual workarounds, like creating phantom inventory entries or processing bundle orders through separate workflows. Others lack the ability to dynamically calculate parent availability from child stock levels.
Questions Worth Asking Any Prospective Fulfillment Partner
- Does your WMS support true BOM expansion at the moment of order import, or does it require pre-processing?
- How does the system handle component-level stockouts? Will it alert our team proactively or hold orders silently?
- Can you support both phantom and stocked assembly models if our strategy evolves?
- When a child SKU receives new inventory, does the parent’s available quantity update in real time?
- How do returns get processed for bundles? Does the system break returned kits back into component inventory?
- Can the system handle lot tracking, serial number capture, or expiration dates at the component level for regulated products?
The answers reveal whether the system will handle your bundles reliably at scale or require manual intervention as complexity grows.
The System Logic Between Order and Shipment Is What Makes Bundle Fulfillment Reliable
When a buyer orders a bundle, they experience a single transaction. One part number, one line item, one package arriving at their dock or facility.
Between that order and that delivery, a warehouse management system executed a specific sequence of logic. It referenced a recipe, expanded a parent into components, verified availability across multiple SKUs, reserved inventory at the child level, and generated location-specific pick instructions for the warehouse floor.
Companies run into fulfillment problems with bundles when the system handling their orders cannot manage that parent-child relationship properly. The symptoms look like inventory errors, missing components, or unexplained stockouts.
The cause is almost always in the BOM architecture or the lack of it.
Whether you’re kitting automotive service parts, assembling pharmaceutical and life science sample sets, bundling electronic components, or packaging industrial maintenance supplies, understanding this sequence helps you evaluate partners, diagnose problems, and ask better questions.
Understanding what reliable bundle fulfillment actually requires helps you confirm your partner delivers it.
