BOM order-status tags
When an order comes in, Assemblified decides whether to run BOM execution against it. With BOM order tagging enabled, the result of that decision is written back to the order as a Shopify tag. You can then filter, automate, or export based on it.
Toggle it under Settings → Tags → BOM order tagging.
The three status tags
Section titled “The three status tags”Every tagged order receives exactly one of these — the other two are removed if present, so the tag set always reflects the current decision.
| Tag | Applied when | What it means |
|---|---|---|
bom-processed | At least one matched BOM is active and has materials or sub-assemblies to execute. | Assemblified recognized the order as BOM-backed and selected it for execution. |
bom-skipped | BOMs match the order, but none should run — execution is disabled, the BOM is inactive, or it has no components. | Assemblified recognized BOM candidates, but there was no executable BOM work for this order. |
no-bom-available | No order-line variant matches an Assemblified BOM. | Assemblified checked the order and found no BOM to execute. |
The three tags are mutually exclusive: when a new status is written, the other two are removed in the same queue message.
How to use the tags
Section titled “How to use the tags”A few common patterns:
- Filter the orders list in Shopify admin (
tag:bom-processed) to see only orders Assemblified handled. - Drive a Shopify Flow — when an order is tagged
bom-processed, send it to a specific fulfillment workflow; whenno-bom-available, route it as a standard ship-from-stock order. - Audit silent skips —
bom-skippedis the tag worth watching. It means a BOM was matched but didn’t run. Common causes: BOM disabled, BOM has no components, or execution is globally disabled in Settings.
Enabling and disabling
Section titled “Enabling and disabling”The switch at the top of the Tags page enables or disables the feature globally. Disabling stops new orders from being tagged but does not remove tags from previously tagged orders — they stay until you clear them manually in Shopify.
Re-enabling resumes tagging from the next order onward.
When tags get written
Section titled “When tags get written”Order tagging fires as part of BOM execution evaluation — the same path that decides whether to run components, expand sub-assemblies, and create execution log entries. It runs on the standard orders/updated Shopify webhook delivery.
If the Shopify webhook never arrives (delivery failure, app uninstalled between events), no tag is written. Re-delivering the webhook from Shopify admin will retroactively tag the order.
What’s not tagged
Section titled “What’s not tagged”- Draft orders. Tagging fires on the live
orders/updatedevent, not on drafts. - Orders processed before the toggle was enabled. There’s no back-fill — the historical orders replay tool is for BOM execution, not for tag back-fill.
- Orders without a Shopify session in scope (rare — usually means the app session was rotated mid-flight).