Skip to content

Operating material tags

Material tags are Shopify product tags that Assemblified maintains for you: a tag you mark as a default BOM tag goes on every finished good Assemblified knows about, and one you mark as a default raw-material tag goes on every material. A connected assistant can read the catalogue, and with write access change it and put the tags to work.

  • What it takes
  • Reading and changing tags on selected products
  • Reading the catalogue
  • Adding and correcting a tag
  • Applying a tag to everything that matches
  • Deleting a tag, and the products it is on
  • When a job cannot be queued

Reading needs nothing beyond a connection. Changing a tag needs write access: either an API key created with read & write scope or a web-chat connection granted read & write when it was linked. See API keys and Connect claude.ai or ChatGPT.

Reading and changing tags on selected products

Section titled “Reading and changing tags on selected products”

Ask the assistant to read current Shopify tags for 1–250 selected BOMs. It also sees your saved tag catalogue. A BOM that no longer exists is left out of the returned rows, so the number of rows can be smaller than the selection total. A BOM without a Shopify product, or whose product could not be loaded, is reported as skipped. That is different from a product successfully read with no tags. Reading does not change anything or reserve the product for a later edit.

With write access, ask for 1–25 selected BOM edits at a time, naming the tags to add or remove for each. Only those differences are requested; unrelated tags are preserved. This does not change your saved tag catalogue, set default flags or apply a default across the store. Empty edits, repeated BOMs and a tag both added and removed in the same edit are refused before any edit starts.

“For these two finished goods, add Holiday and remove Last season. Leave their other tags alone.”

Tags belong to the whole Shopify product, so all of its variants share the effect. Select one BOM per product and avoid conflicting edits while earlier changes are still outstanding.

The assistant gets a separate response for each edit: whether the request returned and, when it did, whether the work was queued or skipped. Counts describe requests and accepted edits, not completed Shopify changes. One edit can fail while later edits continue. A missing or timed-out reply can arrive after work has already started; do not automatically repeat the batch. Check current tags on the products in Shopify. A matching tag list shows what is there now, but cannot tell you which request caused it or whether earlier attempts have all finished.

For the existing dialog in the app, see Bulk BOM product tags.

The assistant can list every tag, with its two default flags and when it was last changed. The flags are the part that matters:

  • Default BOM tag — Assemblified puts it on every finished good it knows about.
  • Default raw-material tag — Assemblified puts it on every material.
  • Neither — a manual label. It is stored, and nothing applies it for you.

A tag is the literal Shopify tag, as written, and it has to be unique. An assistant that tries to add one you already have is told so rather than creating a near-duplicate.

Two things are worth knowing, because neither is obvious:

  • Creating a tag puts it on nothing. A default tag is applied from then on, as Assemblified touches each product. The products that already exist are dealt with separately, below.
  • Renaming a tag does not rename it on Shopify. The products that carry the old tag keep it; Assemblified starts maintaining the new one. If you want the old one gone, say so — the assistant can delete it with its cleanup, which is the tidy way round.

“Apply now” is how the products that already exist get a default tag without waiting. The assistant can ask for it, and there are two rules:

  • It only works for a tag with one of the default flags. A manual tag has no matching set to apply to, so the request is refused with that reason.
  • The answer is a job, not a result. Nothing is on Shopify the moment the assistant replies; the work is queued and runs in the background. Check the products, or the tag jobs on the Tags settings page, if you want to see it land.

“Add a tag called Made in house, make it the default for finished goods, and put it on the ones we already have.”

Deleting a tag from the catalogue does not strip it off your products by default: the row goes and Assemblified simply stops maintaining it, leaving every product exactly as it is. That is often what you want if the tag is doing a job in your storefront.

If you want it gone from the products too, the assistant can ask for the cleanup with the delete. Then the order matters and is deliberate: the cleanup is queued first, and the tag is only removed from the catalogue once it is. The cleanup is available for a default tag only — that flag is what defines the set of products to sweep.

Both “apply now” and the delete cleanup report whether the job actually reached the queue, and the assistant should tell you which. A job that was recorded but not queued comes with the reason, and the commonest one is the dullest: there was nothing to tag. Either way, nothing is on Shopify until a queued job runs.