Skip to content

Shopify admin extensions

Assemblified plugs into the Shopify admin in two ways: it writes data into Shopify metafields, and it renders UI directly inside the admin via extensions. Your team rarely has to leave Shopify to act on BOM data, and other tools that read from Shopify (storefronts, third-party apps) can pick up Assemblified’s component breakdown straight from the variant.

  • Metafields written to Shopify
  • Order-detail blocks
  • Packing-slip print actions
  • Product-list admin actions
  • Install and enable

Assemblified writes a material_requirements_json metafield in two places — on Orders and on Product Variants — under the same assemblified namespace. Each has its own switch on Settings → Integrations, in the sections Shopify order metafields and Shopify product-variant metafields, and both are off by default, so nothing is written to Shopify until you opt in. A third, order-only metafield, work_order_materials_json, lists what an order’s completed work orders actually used; it has its own switch in the order section and is off by default too.

Written on every Shopify order Assemblified touches. Kept up to date through the order’s lifecycle — creates, cancels, refunds, and edits all rewrite it.

Namespace / Key assemblified / material_requirements_json
Owner Order
Setting Write material requirements into order metafields
Cost option Hide cost and price in order metafields — zeros out costs while keeping quantities and structure intact
Read by The two order-detail blocks below
Shape JSON array of BOMs with quantities and their resolved material requirements

Written on a Shopify order when a work order linked to that order (and to no other) is completed, reopened, has a build run reversed or is linked to a different order; a write Shopify refuses is retried automatically. It lists what the order’s completed work orders actually used, so it suits orders whose contents are chosen on the work order rather than fixed by a bill (gift hampers, made-to-order kits). Nothing else rewrites it: order edits, cancels and refunds leave it alone.

Namespace / Key assemblified / work_order_materials_json
Owner Order
Setting Write work order materials into order metafields (independent of the material requirements switch, off by default)
Cost option Hide cost and price in order metafields applies here too; the switch shows while either order metafield switch is on
Read by Your own systems. The order-detail blocks read material_requirements_json, not this metafield
Shape One object per order: workOrders (each with its items and materials) and totalMaterials across them
{
"orderId": "13030",
"orderName": "#13030",
"generatedAt": "2026-10-29T10:00:00.000Z",
"workOrders": [
{
"workOrderId": "…",
"workOrderName": "Hamper #13030",
"shortId": "WO-0042",
"reductionType": "PRE_ASSEMBLY",
"completedAt": "2026-10-29 09:58:12.000",
// What the work order built
"items": [
{ "itemType": "bom", "itemId": "…", "name": "Foodie Hamper", "productId": "…", "variantId": "…", "sku": "HAMPER-6999", "quantity": 1 }
],
// What it used: the same entry as material_requirements_json's boms[].materials, plus three keys
"materials": [
{
"materialType": "raw_material", // or "sub_assembly" (productId and variantId are then null)
"materialId": "…",
"productId": "…",
"variantId": "…",
"sku": "JAM-340",
"title": "Strawberry jam - 340 g",
"productName": "Strawberry jam",
"variantName": "340 g",
"specifications": null,
"notes": null,
"quantity": 2, // consumed by the build runs; the planned quantity if nothing was consumed
"plannedQuantity": 2,
"consumedQuantity": 2
}
]
}
],
// The same entry as material_requirements_json's totalMaterials, plus materialType and materialId
"totalMaterials": [
{
"materialType": "raw_material",
"materialId": "…",
"variantId": "…",
"productId": "…",
"sku": "JAM-340",
"title": "Strawberry jam - 340 g",
"productName": "Strawberry jam",
"variantName": "340 g",
"specifications": null,
"notes": null,
"totalQuantity": 2,
"imageUrl": "https://cdn.shopify.com/…",
"isVirtual": false,
"unitCost": 3.1 // the work orders' unit cost, weighted by quantity; 0 when costs are hidden
}
]
}

A work order linked to several orders is never listed, because its materials can’t be split between them. When the order’s last completed work order is reopened, workOrders and totalMaterials become empty lists.

Written on the Shopify product variant linked to a BOM (the BOM’s finished good). Updated whenever a BOM is created or edited — but only while the BOM’s status is active. If a BOM is set to inactive or deleted, Assemblified clears the variant’s metafield so stale data doesn’t linger on the product.

Namespace / Key assemblified / material_requirements_json
Owner Product Variant
Setting Write material requirements into product variant metafields
Cost option Hide cost in product variant metafields — same behaviour as the order cost option
Active-only Yes — inactive or deleted BOMs have the variant metafield cleared automatically
Bulk action A one-shot sync in the same settings section — writes across every BOM, including inactive ones (the only path that ignores the active-only gate)
Read by External systems (storefront blocks, third-party catalog tools, custom reports) that want a product’s component breakdown straight from Shopify

Completing a work order refreshes the order metafield for every order that work order was created from, laying the work order’s own recorded values over the ones derived from the bill — see Material metafield tracking.

Three blocks can sit on the Shopify admin Order detail page. The first two read the order metafield through Assemblified and render on any order that has it set. If the information cannot be loaded (Assemblified cannot be reached, your session has expired, or the order cannot be read), the block says so and offers Try again. The BOM links block shows No data found or feature disabled when the order has no material requirements saved.

The Material requirements block also works on orders without the metafield, or whose metafield was saved empty because no bill of materials matched when the order came in: orders placed before Write material requirements into order metafields was switched on, and open orders when Assemblified runs BOMs only at fulfilment. Assemblified then calculates the materials from the order’s current items and today’s bills of materials, and the block says Calculated from the current bills of materials; not saved on this order. It shows No materials for this order’s current items when nothing on the order needs materials.

BOM links

A list of every BOM the order requires, with thumbnails, names, quantities, and a deep-link into the corresponding BOM inside Assemblified.

Material requirements

A breakdown of the same metafield at the material level — the materials and virtual materials needed to fulfil the order, summed across all BOMs on the order.

Choose what the Material requirements block shows under Settings → Integrations → Shopify order metafields, while Write material requirements into order metafields is on. Tick any of image, product name, variant name, SKU, quantity, unit cost, line cost and total, notes, specifications and the “Generated at” time; the columns keep their order. At least one of image, product name, variant name or SKU stays on, so every row says which material it is. The choice applies to every order and every staff member of the shop. It only changes what the block displays: the metafield keeps every field. To keep costs out of the metafield itself, use Hide cost and price in order metafields.

Why they’re useful: a fulfillment staffer reviewing an order can see exactly what to build and what components it needs without logging into Assemblified. The deep-link on each BOM gets them into Assemblified one click away if they need the full BOM context.

A separate block for building what one order is waiting for. Its Order production section shows how many finished units are held for the order, how many its reserved components can still become, what was already recorded as built, which lines can go into a normal work-order draft, and what blocks the rest. Its Record production and Create work order buttons open the app on that order; the block itself changes nothing. It needs the Enhanced plan: below it, a pinned block shows only an upgrade note and loads no order information. See Order production.

Two entries, both under Shopify’s Print menu:

  • BOM packing slip — on the order detail page. One order, one slip.
  • BOM packing slips (bulk) — on the Orders list, once you have selected orders. Many orders, one PDF.

Either one opens a preview first (“Preparing packing slip”, then “Preview ready”) and then hands the PDF to Shopify’s own Print button. The slip includes the BOM and material breakdown alongside the normal line items.

Why they’re useful: regular Shopify packing slips list the finished goods only. The Assemblified slip adds the components, so the slip a picker pulls off the printer has everything they need — no separate Assemblified printout required.

What the slip shows, and how the bulk version behaves, is configured on Settings → Shopify printing: Packing Slip Display Options, the Bulk print mode, and a PDF footer of your own.

Two entries surface inside Shopify’s Products list page action menus.

A link that opens Assemblified’s stock adjustment tool with every material in scope — the same grid you reach from Materials → More actions → Adjust stock. One click from “I’m looking at my product catalog” to “I’m entering what just arrived”.

Why it’s useful: warehouse managers spend most of their time in Shopify Products. This action removes the muscle-memory step of navigating to Assemblified separately.

An action in the Products list’s menu that runs dynamic adjustmentDynamic adjustmentA per-bill toggle that recalculates the bill's Shopify-displayed quantity after every order: the bottleneck-resource count plus pre-assembled stock. One of three mutually exclusive toggles — switching it on switches only-sell-pre-assembled and maintain inventory level off.Read more → for all eligible BOMs using the configured component inventory source. Selecting products does not limit the adjustment to those products. If your shop uses Assemblified’s local inventory index, record incoming stock in Assemblified before recalculating. Otherwise, the recalculation reads Shopify-managed component stock directly from Shopify. This action does not import component stock into Assemblified’s local index.

After confirmation, the result stays open until you choose Done. A request accepted for background processing has a different message from a completed adjustment. If no changes were needed or eligible, the action says so.

If an adjustment fails or its result cannot be confirmed, the message stays visible. Some changes may already have applied, so check inventory history before starting another adjustment. The action offers a retry only when it can confirm that processing did not begin.

Why it’s useful: after recording a shipment, you can recalculate the buildable quantities of dependent finished goods from the Shopify Products page.

Most extensions surface automatically — the moment Assemblified is installed on the store, the two print actions and the two product-list actions appear in their respective menus. No configuration needed.

The order-detail blocks are the exception. Shopify treats them as app blocks that merchants opt into per layout, so there’s a one-time setup step.

  1. Open the Shopify admin → Orders. Pick any existing order.

  2. Click the “Customize layout” / “Add section” affordance. The exact label depends on your Shopify admin version; in current admin it’s an “Add section” button on the order detail page.

  3. Pick the Assemblified blocks. “BOM links” and “Material requirements” appear in the picker. Add one or both.

    For order production, add Assemblified order workbench: on the order page, open the ⋯ (More actions) menu, choose Add block, pick it and pin it.

  4. Save the layout. The blocks now show on every order detail page where the material_requirements_json metafield is set. Orders without the metafield (e.g. orders placed before you installed Assemblified, or orders that don’t reference any BOM) render the block empty.