Skip to content

Glossary

This glossary defines the terms that appear throughout the Assemblified docs. You can also hover over any underlined term in the docs to see a quick definition without leaving the page.

Actual Cost

Also known as: actual cost

What the work order really cost, derived from materials that have been consumed by completed build runs. Stamped into the audit ledger at the moment of consumption, so it doesn’t drift if prices change later.

Alertified

Also known as: Alertified

A Shopify-native inventory alerting app. Alertified watches stock levels and fires multi-channel notifications (email always, plus optional webhook, SMS, or Slack) whenever a threshold is crossed. When connected to Assemblified, alerts cover not only Shopify variants but also virtual materials, BOM pre-assembled pools, and sub-assembly pre-assembled pools — entities Shopify itself has no visibility into.

Allow negative inventory

Also known as: negative inventory, allow negative, clamp to zero

A shop-level setting that decides whether Assemblified-managed quantities — virtual raw materials, pre-assembled stock, dynamic capacity — can stay below zero, or get clamped at 0.

Auto-generate material list

Also known as: auto-generate-material-list, autoGenerateMaterialList

A per-BOM toggle (Enhanced subscription) that creates a Materials Order flow plus a linked TODO task whenever the BOM executes on an order. Operators get a checklist they can pick or download — useful for shop floors that pull a printed material list per order before building.

Baseline Cost

Also known as: baseline cost

The cost of the work order if it were built strictly to the BOM — uses the original BOM quantities, frozen at the moment items were spread onto the work order. Compare against planned cost to see the impact of operator overrides.

Bill of Materials

Also known as: BOM, BOMs, bill of materials

A 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.

BOM Container

Also known as: container, BOM containers, containers

An automation group: define a matching rule once, and any BOM that matches is included automatically. Containers let you apply bulk operations (pricing, tags, settings) without editing each BOM individually.

BOM execution

Also known as: bom-execution, BOM execution

The pipeline that runs when a Shopify order containing a BOM-bound variant is created, edited, cancelled, or refunded. Webhook → queue → DO handler → Shopify inventory adjustment, plus pre-assembled drawdown, sub-assembly recursion, and dynamic adjustment cascade. Every run writes one execution log row.

BOM execution log

Also known as: bom-execution-log, execution log

The audit trail for one BOM execution — one row per order webhook → DO → Shopify cycle. Captures webhook receipt timestamps, queue lifecycle, DO execution, BOM processing metadata, calculated material changes, Shopify sync status, dynamic-adjustment results, refund history, and pre-assembled consumption. Surfaced in the BOM detail page.

Bottleneck resource

Also known as: bottleneck, bottleneck-resource, bottleneck component

The component with the lowest available-to-required ratio in a BOM. Determines the BOM’s displayed Shopify quantity under dynamic adjustment: the BOM can build at most as many units as the bottleneck allows. Non-essential materials are excluded from this calculation.

Build Run

Also known as: build runs, BR

One cycle of assembly inside a work order: pick the materials, build the units, then complete (or cancel, or reverse). A work order can have many build runs over its life — each one moves a defined quantity of inventory and writes a row to the audit ledger.

Decouple

Also known as: decoupled, decoupling

Detaching one work-order item from the live BOM so its material list stops following BOM updates. After you decouple, edits to the BOM no longer flow into this work order — useful when you’ve already started a build and need a frozen recipe.

Default location

Also known as: default location, fallback location

The Shopify location Assemblified falls back to when an order or fulfillment webhook doesn’t carry a more specific location. Inventory adjustments, dynamic recalculations, and per-location records all use this as their anchor.

Disposition

Also known as: dispositions, QC disposition

A QC reviewer’s verdict on a built unit: how many were approved, how many were failed, and an optional reason and category for the failure. One row per item per QC review, written when the operator finalises the review.

Dynamic adjustment

Also known as: dynamic-adjustment

A per-BOM toggle that recalculates the BOM’s Shopify-displayed quantity from current component availability after every order. The displayed quantity is the bottleneck-resource count plus pre-assembled stock — your storefront never sells more than you can build.

Effective Quantity

Also known as: effective qty

The quantity actually consumed by the work order, after operator overrides. Starts equal to the original BOM quantity, but can be adjusted up or down per material as plans change. The effective quantity is what the pick list and cost calculations use.

Keep Assembled on Return

Also known as: keep assembled, keep-assembled, onReturnKeepAssembled

A toggle on BOMs and sub-assemblies that controls cancel/refund behavior. When on, returned units restore the entity’s pre-assembled shelf instead of breaking back into raws. Cascades through nested sub-assemblies — traversal halts at any node with the flag set.

Labour cost

Also known as: labor cost, labour, labor

The cost of human work going into a BOM. Modeled either as a virtual material with unit cost equal to the hourly rate (per-unit, scales with order quantity) or as a per-work-order adder field (per-batch lump sum, doesn’t scale).

Logistified

Also known as: Logistified

A Shopify-native warehouse and demand-planning app. Logistified forecasts what you’ll need to restock, tracks stock across locations, and manages purchase orders. When connected to Assemblified, every BOM execution becomes a demand signal tied to the components consumed — not just the finished-good variant — so forecasts reflect real component usage.

Maintain inventory level

Also known as: maintain-same-inventory-level, maintainSameInventoryLevel, stable inventory display

A per-BOM toggle that keeps the Shopify-displayed BOM quantity flat after orders. After execution, Assemblified pushes a positive delta back to the BOM variant equal to what was consumed. Components still decrement underneath — only the displayed quantity is replenished. Mutually exclusive with dynamic adjustment.

Metafield

Also known as: metafields, material metafield, custom field

A custom key-value field attached to a material — examples include lot numbers, expiry dates, supplier IDs, and inspection flags. Metafields live as definitions in Settings, hold per-material defaults on raw materials, and capture per-production-batch values inside work orders. They optionally link to a Shopify metafield so values can be pulled in from Shopify.

Multi-location mode

Also known as: multi-location, location-sensitive adjustments

A shop-level setting that lets Assemblified prefer the location carried by the incoming order or fulfillment event. When off, every adjustment targets the default location regardless of payload.

Non-essential material

Also known as: non-essential-material, isNonEssentialMaterial

A flag on a raw material that excludes it from the dynamic-adjustment bottleneck calculation. The material is still consumed normally during BOM execution — it just doesn’t gate the Shopify-displayed quantity. Use for plentiful components (labels, generic packaging) you don’t want to be the bottleneck.

Only sell pre-assembled

Also known as: only-sell-preassembled, onlySellPreassembled

A per-BOM toggle (Enhanced subscription) that caps Shopify-displayed availability at the pre-assembled stock count. Buildable capacity from raw materials is hidden — customers can only buy what’s already on the shelf. Useful for sellers who don’t want to over-promise.

Pick

Also known as: picking, pick phase

The first half of a build run: reserving the materials needed off the shelf and committing them to that run. After picking, the materials are no longer “available” inventory — they’re earmarked for the build until you complete or cancel it.

Planned Cost

Also known as: planned cost

The cost of the work order based on the current operator plan — uses the effective quantities and any unit cost overrides you’ve set. Updates live as you edit the plan. This is the figure shown most prominently on the detail page.

Pre-Assembled Inventory

Also known as: preassembled, preassembled inventory, pre-assembled

Stock 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.

Raw material

Also known as: raw materials, raw-material

The atomic component of a BOM or sub-assembly. Two flavors: a Shopify-linked variant (inventory tracked in Shopify) or a virtual material (DO-side inventory only). Both kinds appear in the same component picker and are consumed identically when a BOM fires — except virtual materials never trigger a Shopify call.

Reconcile inventory

Also known as: reconcile, reconcile inventory, fix inventory

An action that aligns Assemblified’s stored inventory state with Shopify’s, in either direction, after the two have drifted. Available as a bulk action on the BOM list (across many BOMs) and as a per-BOM popover (one BOM at one location).

Residual Rounding

Also known as: residual rounding, residual inventory

How Assemblified handles fractional pick quantities when pushing to Shopify, which only supports whole-number inventory. The integer part is sent to Shopify; the leftover decimal is kept in a local “residual” balance and consumed by future picks before another whole unit gets pushed.

Retrospective demand sync

Also known as: retrospective sync, historical sync, demand backfill

A one-shot push of historical BOM executions to Logistified, used to seed demand forecasting with prior activity. You pick a date range (or “all orders”) and Assemblified queues one synthetic order per BOM per past order so Logistified can see what was consumed before the integration was connected. The dialog records every sync so you can undo it later by deleting the corresponding period.

Rework

Also known as: rework run, reworked

Re-running failed units through a fresh build cycle to fix them. Rework runs don’t consume new materials — the materials were already consumed in the original run. Once a rework run passes QC, the units land in finished stock.

Scrap

Also known as: scrapped, scrapping

Marking a failed unit as a terminal loss — it won’t be reworked. Scrapping a unit from a non-deferred run also reverses the produced output, so the unit count in finished stock drops by one.

Spread

Also known as: material spread, spread algorithm

The step that walks each item’s BOM (and any sub-assemblies inside it) and turns the result into the flat list of materials the work order needs. Runs automatically when you add an item — unless you choose “skip for now” and plan the materials yourself.

Sub-Assembly

Also known as: sub-assemblies, subassembly, subassemblies, SA

A 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.

Virtual Material

Also known as: virtual materials, VMAT, virtual

A material tracked entirely inside Assemblified — not a Shopify variant. Useful for shop-floor consumables (glue, packaging, labour units) where you need quantity tracking but don’t want a Shopify product on your storefront.

Work Order

Also known as: work orders, WO, WOs

A planned production run: pick materials, build the items, do QC, and complete — all tracked together. Use work orders when you’re building stock ahead of demand or running a multi-day project.