Safety-stock reservations

Sub-assemblies support safety-stock reservations with exactly the same mechanics as BOMs. Use the dedicated Reservations tab on the Sub-Assembly detail page to create, edit, and release reservations per location.

For the full lifecycle — creating a reservation, editing the target, the two release modes (restore raw materials globally, or convert held materials into pre-assembled stock), failure handling, and edge cases — see the BOM page:

→ Bill of Materials → Safety-stock reservations

What’s different for sub-assemblies

Nothing material. The reservation expands the sub-assembly’s recipe recursively down to raw materials — exactly like a BOM reservation does — so a reservation on a sub-assembly that itself contains nested sub-assemblies still resolves to a flat list of raw materials.

The one subtle difference is that most sub-assemblies don’t have a Shopify variant (they’re internal-only artefacts). Converting a sub-assembly reservation to pre-assembled stock increments the sub-assembly’s pre-assembled shelf in the DO; the Shopify-side push (which the BOM path runs for its variant) is skipped because there’s no Shopify product to update. The “Reserved as safety stock” column on raw materials still tracks holds against sub-assembly reservations identically to BOM reservations.

Tip

Reservations are useful at the sub-assembly level when a shared building-block needs guaranteed availability for downstream BOMs. Hold a buffer of N units of the sub-assembly via a reservation, then convert-to-pre-assembled in batches as your build cadence allows.

Where to next

• Bill of Materials → Safety-stock reservations — full mechanics.
• Pre-assembled stock — the shelf that convert-to-pre-assembled feeds.
• Nesting & execution — how a sub-assembly reservation’s recursive resolution lines up with the same recursion at order time.