BOM Line Types in D365: How Item, Phantom, Pegged Supply, and Vendor Lines Shape Your Production Structure

When I review manufacturing implementations, one of the first things I open is a handful of BOMs, because the line type choices on those lines tell me almost everything about how production orders, planning, and costing will behave downstream. The line type field looks like a small detail, but it decides whether a component generates its own production order, dissolves into its parent, drives a purchase order, or hands work to a subcontractor. Get it wrong and you'll fight phantom symptoms for months: planners drowning in unnecessary orders, costs landing in the wrong place, or warehouse work appearing for material that never physically moves.

In this article I'll walk through each of the four line types, when each one earns its place, and how the choice interacts with BOM depth: the flat-versus-deep structure question every manufacturer eventually faces.

THE FOUR LINE TYPES, BRIEFLY

Every BOM line in D365 carries one of four line types:

• Item: the default. The component is consumed from inventory. If it's a manufactured item, planning creates a separate planned production order for it; if purchased, a planned purchase order.

• Phantom: the component's own BOM is exploded into the parent's production order at estimation. No separate order, no inventory transaction for the phantom item itself.

• Pegged supply: a dedicated supply order (production or purchase) is created and hard-pegged to the parent production order, marked to it one-to-one.

• Vendor: the line represents a subcontracted service; the parent production order generates a purchase order to the subcontractor, tied to the routing operation.

Each behaves differently in planning, scheduling, costing, and warehouse execution. The decision tree below summarizes the choice; the rest of the article unpacks each branch.

ITEM: WHEN THE COMPONENT HAS A LIFE OF ITS OWN

Use the Item line type when the component is genuinely stock-managed: it's built or bought in its own lot sizes, possibly for multiple parents, and you want inventory between the levels. This is the right answer for shared subassemblies: a motor used across ten finished products, a sauce base used in twenty recipes. Planning treats each level independently, applying that item's own coverage settings, lot sizes, and lead times.

The cost of that independence is decoupling: each level means its own production order, its own report-as-finished, its own picking work in the warehouse, and its own scheduling step. In an advanced warehouse, every intermediate level is a put-away plus a pick. If a subassembly exists only because engineering drew it that way (never stocked, never shared, built only in the context of one parent), making it an Item line creates pure administrative overhead.

PHANTOM: COLLAPSING ENGINEERING STRUCTURE OUT OF EXECUTION

That's exactly what Phantom is for. Engineering often needs intermediate levels (a "wiring kit," a "hardware bag," a logical grouping of components) that manufacturing never physically builds or stocks. Set the line type to Phantom and the explosion happens at production order estimation: the phantom's components and route operations are pulled up into the parent order, and the phantom item itself never sees an inventory transaction.

Practical guidance from the field:

• Set Default order settings → Phantom as the default order type on items that should always explode, so new BOM lines inherit the behavior and nobody forgets.

• Phantoms can nest, and D365 explodes recursively, but deep phantom nests make estimation slower and make the picking list enormous. Two, maybe three levels is my comfort limit.

• Remember route handling: operations on the phantom's route are merged into the parent route. If the phantom has no route, only materials come up. Test this; merged operation numbers surprise people.

• Costing rolls through transparently, but BOM calculation reports show the exploded view; teams used to seeing the intermediate level as a cost object lose that visibility. That's usually fine, but say it out loud during design.

A typical industry example: in industrial equipment manufacturing, a control panel might exist as an engineering item with forty components. If panels are wired in-line as part of final assembly (never stocked), phantom is right. If panels are built in a separate cell, in batches, ahead of demand, Item is right. Same part, different operating model, different line type.

PEGGED SUPPLY: ONE-TO-ONE, WHEN IT MUST BE THIS ONE

Pegged supply creates a supply order hard-linked to the consuming production order: a marked, one-to-one relationship. The classic fit is configure-to-order and project-style manufacturing: the stainless variant of a frame built specifically for this parent order, a cut-to-length cable, a printed label specific to this batch. The component is real (unlike a phantom, it gets produced or purchased and receipted), but it has no independent demand and shouldn't be netted against general stock.

Cautions:

• Pegged supply defeats lot-sizing and consolidation by design. If purchasing wants to consolidate those components across orders, you've chosen the wrong type; use Item with appropriate coverage instead.

• Rescheduling tightness cuts both ways: move the parent and the pegged order moves with it, which planners love until an exception on the pegged order blocks the parent and nobody understands why.

• In batch process industries, pegged supply between a bulk batch order and a packed finished good is largely superseded by formal batch order sequencing (bulk/pack) functionality; prefer that where it applies.

VENDOR: SUBCONTRACTING AS A BOM DECISION

The Vendor line type models subcontracted operations: you ship material out, a vendor performs a service (plating, heat treatment, machining), and the service comes back as a purchased line on the parent production order. Configuration that has to line up for this to work cleanly:

1. The service item should be of type Service (or an item modeling the subcontracted work) with the vendor account set on the BOM line.

2. Tie the BOM line to the subcontracted route operation via the operation number, and use a route operation of type vendor with a cost category that books to subcontracted work.

3. The purchase order is generated at estimation; receiving it reports progress on the operation.

Where it shows up by industry: metal fabrication (outside coating/galvanizing), electronics (board assembly outsourced, final test in-house), and automotive suppliers (heat treat). If your subcontracting also involves shipping component material to the vendor and tracking it as vendor-owned-location inventory, look at the dedicated subcontracting warehouse pattern (a warehouse per vendor with transfer orders feeding it) rather than overloading the BOM further.

FLAT OR DEEP? CHOOSING THE STRUCTURE, NOT JUST THE LINE TYPE

Line types are really instruments for a bigger decision: how many levels of your engineering BOM should exist as execution levels.

My rule: a BOM level should exist in execution only if inventory genuinely needs to exist at that level, because it's shared across parents, built ahead of demand, stocked for service, or made in a different cell/site on a different cadence. Otherwise flatten it, usually with phantoms.

Deep structures multiply production orders, warehouse touches, and scheduling dependencies; every level adds latency because each order schedules sequentially. Flat structures keep execution lean but produce long picking lists and lose intermediate cost visibility. Most real answers are hybrids: stock the genuinely shared subassemblies as Item levels, phantom the engineering groupings, peg the order-specific make-to-order components, and model outside processing with Vendor lines.

TAKEAWAYS

Line type is an operating-model decision disguised as a field on a BOM line. Use Item when the component deserves its own inventory and planning life; Phantom to collapse engineering-only levels out of execution; Pegged supply for true one-to-one, order-specific components; and Vendor for subcontracted operations tied to route steps. Then step back and ask the structural question: every BOM level you keep in execution should justify itself with a real inventory need. If it can't, flatten it; your planners, pickers, and month-end will thank you.

Next time I'll stay in manufacturing and look at production scheduling: finite versus infinite capacity, resource groups, and why scheduling percentages matter more than most people think.

In this series: previous article Work Templates and Location Directives · next article Engineering Changes and Revisions