Skip to content
Assemblified Assemblified Docs

Operating BOMs & sub-assemblies

With write access, a connected assistant can do more than read your bills of materialsBill of MaterialsA bill of materials tells Assemblified how to build one unit of a finished good. When a customer orders the finished-good variant, Assemblified deducts the right component quantities from inventory automatically. Read more → — it can build and maintain them: create finished goods, compose them from materials and sub-assembliesSub-AssemblyA reusable assembly block that composes into bigger BOMs. Define it once, include it in any BOM. At execution time, Assemblified expands the sub-assembly into its own components recursively. Read more → , adjust pre-assembled stock, and toggle a BOM’s settings. This page explains what that covers and the guardrails around it.

On this page

Section titled “On this page”
  • What it takes
  • Building and composing BOMs
  • Working with sub-assemblies
  • Recording pre-assembled stock
  • Configuring a BOM’s behaviour
  • Doing it in bulk
  • Guardrails
  • Safety & audit

What it takes

Section titled “What it takes”

Write access is opt-in. The assistant needs either:

A read-only connection sees none of these actions — they aren’t even visible to it, and any attempt to use them fails. Existing connections keep the scope they were granted; to upgrade a chat, revoke it and reconnect with a read & write code.

Building and composing BOMs

Section titled “Building and composing BOMs”

The assistant can drive everything you’d do by hand on a BOM:

  • Create a bill of materials for a finished-good variant.
  • Edit its details, and delete a BOM you no longer need.
  • Add, remove, and re-quantify component materials.
  • Add and remove nested sub-assemblies.

When the assistant references a Shopify variant that isn’t a raw material yet — either as the finished good or as a component — Assemblified registers it as a raw material automatically, so the assistant doesn’t have to set that up as a separate step.

Working with sub-assemblies

Section titled “Working with sub-assemblies”

Sub-assemblies get the same treatment: the assistant can create, edit, and delete them, and add or remove the materials inside them — so a reusable component tree can be built up and reused across many finished goods.

Recording pre-assembled stock

Section titled “Recording pre-assembled stock”

When finished goods or sub-assemblies are physically assembled ahead of demand — or counted during a stock-take — the assistant can record that pre-assembledPre-Assembled InventoryStock of finished sub-assemblies and BOM items that have already been built and are sitting on the shelf. When a work order needs a sub-assembly, it draws from pre-assembled inventory first and only builds fresh ones if the shelf comes up short. Read more → stock directly, per location, without creating a work order:

  • Add or subtract a quantity (a delta — “we just built 3 more”).
  • Set an exact quantity (an absolute count — the safe choice for a stock-take, because repeating it can’t double-count).

A BOM with Only sell pre-assembled enabled automatically re-anchors its Shopify availability to the new pre-assembled quantity, exactly as it does in the app.

Configuring a BOM’s behaviour

Section titled “Configuring a BOM’s behaviour”

The assistant can flip the same per-BOM switches you control in the app:

  • Active / inactive status.
  • Dynamic adjustment — whether the BOM re-checks stock as orders come in.
  • Maintain same inventory level.
  • Keep assembled on return.
  • Auto-generate material list — building a BOM’s component list automatically. This one requires the Enhanced plan.

Turning on dynamic adjustment arms the order-time behaviour but doesn’t push anything to Shopify at the moment it’s toggled — the effect happens when orders arrive, just as in the app.

Doing it in bulk

Section titled “Doing it in bulk”

Bulk work is first-class, so an assistant can build out a whole catalog in a few calls instead of hundreds:

  • Create many BOMs, sub-assemblies, or their materials in one request.
  • Delete many at once.
  • Adjust pre-assembled stock for many BOMs or sub-assemblies in one pass — ideal for a full stock-take.

Every bulk call reports a per-item result, so a single bad row doesn’t sink the batch — the assistant sees exactly which items succeeded, which were skipped as duplicates, and which failed, and can resend just the failures. Bulk calls also offer a preview mode that validates everything and writes nothing, so the assistant can check a plan before committing it.

Guardrails

Section titled “Guardrails”

Write access follows the same rules as the app:

  • In-use materials are protected. A raw material or sub-assembly that’s still referenced by a BOM can’t be silently deleted — the attempt fails per item with a clear reason.
  • Duplicates are caught. Bulk creates can skip items that already exist (matched by SKU, then by name), so re-running a build is safe.
  • Every refusal is guidance. When an action is blocked, the assistant is told exactly why and what to do instead, so a capable assistant self-corrects without your involvement.

Safety & audit

Section titled “Safety & audit”

Every call the assistant makes is tied to the API key or connection it used, and access can be revoked at any time — see Managing access & security. Write access is scoped to your single store, and the assistant can never reach anything beyond the actions described in this documentation.

See also

Section titled “See also”
Impressum Datenschutz