Skip to content

Tagging

Assemblified can write tags onto your Shopify products (BOMs, raw materials) and Shopify orders (BOM execution status). Tags live in Shopify, are visible everywhere Shopify shows tags (admin filters, Liquid, automations), and are kept in sync in the background.

The three surfaces:

  • Material tags — tags applied to Shopify products that back your BOMs and raw materials. Configured under Settings → Catalogues → Tags; written automatically on create, or applied on demand.
  • BOM order-status tags — one of bom-processed, bom-skipped, no-bom-available or partially-disabled-at-location written onto Shopify orders so you can tell at a glance which orders Assemblified handled.
  • Bulk BOM product tags — ad-hoc tag changes against the Shopify products behind selected BOMs, driven from the Finished goods table.

All three feed the same background tagging pipeline, which talks to Shopify in batches of up to 250 products and retries transient API errors.

Every tag this feature manages is stored on the Shopify side — on the product or the order. Assemblified writes them; you can read them back in any Shopify surface that exposes tags. Assemblified keeps the configuration (which tags are defaults, what’s been queued) but not the canonical tag state itself.

That means:

  • Editing a tag in the Shopify admin doesn’t update Assemblified’s record of the tag name. If you rename a default tag inside Assemblified, the old tag stays on products until you re-apply.
  • Deleting a tag in Assemblified leaves the Shopify tag in place — unless you tick “Also remove this tag in Shopify” in the delete dialog, whose help text reads “Removes the tag from every matching BOM and raw-material product.” That option is offered only for tags carrying a default flag; see Material tags.

Tagging runs in the background, in batches of up to 250 products. A batch that Shopify refuses for a temporary reason is retried rather than abandoned at the first error.

You don’t manage the queue directly. Two things are worth knowing:

  • “Queued” is not “written”. Every confirmation you get says the change was queued. Shopify usually reflects it within seconds, but a backlog or a transient Shopify error can stretch that to minutes.
  • A job can be recorded without being queued. When that happens the Tags page tells you, as a dismissible Job not queued warning rather than a success. Re-running the action is the fix; if it keeps happening, the Shopify session behind your install probably needs refreshing.