Answer

A phantom assembly in NetSuite is like a pretend item you use as a label/folder to group parts together, but you don’t keep it as its own stocked thing.
When you build the real finished product, NetSuite “opens the folder” and pulls the phantom’s components directly, instead of requiring you to build and stock that sub-assembly first.

So: Phantom = “grouping/instructions”, not “a thing you store on a shelf”.

More Details

The 5-year-old version (no bike wheels yet)

Imagine you’re packing a lunchbox.

• Finished good: Lunchbox
• Phantom assembly: Sandwich Pack (just a label)
• Components under Sandwich Pack: bread + peanut butter + jelly
• Other Lunchbox components: juice box + napkin

If “Sandwich Pack” is phantom, you don’t make a separate sandwich pack and put it in the pantry. Instead, when you “build” the Lunchbox, NetSuite says:

• “For each Lunchbox, I need 1 Sandwich Pack”
• then it immediately translates that into:
  • bread, peanut butter, jelly
• and consumes those ingredients directly.

You get the benefit of having a neat BOM structure (“Sandwich Pack”), without creating extra inventory/WOs for “Sandwich Pack”.

---

What phantom changes in NetSuite terms

If a subassembly is NOT phantom (regular subassembly)

• You typically build it first (often via its own Work Order).
• It becomes its own inventory item you can stock, move, count, pick, and use later.

If a subassembly IS phantom

• NetSuite does not treat it like something you stock in between steps.
• On the parent work order / build, the phantom line is essentially a header, and the real demand is its components.
• You often see phantom components indented under the phantom on the build/work order.

---

Now, the bike wheel example (why it “doesn’t jive”)

People imagine a wheel as a real thing you build, store, and then attach. That’s true sometimes.

Use a Phantom Wheel Assembly when:

You don’t want to stock wheels as their own item. You build wheels only as part of building the bike.

Bike Assembly BOM

• Frame (stock)
• Handlebar (stock)
• Wheel Assembly (phantom) x2
  • Rim (stock)
  • Spokes (stock)
  • Hub (stock)
  • Tire (stock)
  • Tube (stock)

When you build 1 bike, NetSuite consumes:

• 1 frame, 1 handlebar, etc.
• plus 2× (rim, spokes, hub, tire, tube)

Even though your BOM visually says “Wheel Assembly”, NetSuite treats it as “just a grouping”.

Don’t use phantom wheels when:

You actually treat wheels as a real subassembly operationally, like:

• You prebuild wheels in batches and keep them on a rack
• You want wheel inventory counts (e.g., 40 wheels available)
• You want to issue/complete wheels separately, maybe at a different location or time
• You sell wheels as a spare part as a stocked SKU

In those cases, wheels should be a normal assembly item (not phantom), and you build them into inventory, then consume them on the bike work order.

---

A better mental model: “Is it a shelf item?”

Ask: Do I ever want to see this subassembly as a quantity on a shelf?

• If yes → make it a real assembly (not phantom)
• If no → phantom is a good fit

---

Another example that usually clicks: “Hardware kit”

Desk Assembly BOM

• Desktop (stock)
• Legs (stock)
• Screw Pack (phantom)
  • 8× screw
  • 8× washer
  • 1× hex key

You probably never stock a “Screw Pack” as a SKU; it’s just a convenient BOM grouping so you can reuse it across multiple desks.

---

Where you’ll see/maintain the “phantom-ness”

• The assembly item can be marked Phantom on the item record (defaults).
• Or you can set Item Source = Phantom on the BOM/BOM Revision/Work Order line (so the same subassembly could be phantom in one parent, but stocked in another).

(If you tell me whether you’re using Advanced BOMs/BOM Revisions or the classic Components tab, I can point you to the exact screens.)

Questions

1. In your real process, do you prebuild wheels (batch build) or do you assemble wheels during bike build?
2. Do you need to pick/ship wheel components on a sales order (kit-like behavior), or are you strictly manufacturing then fulfilling?