Skip to content

Importing pre-assembled quantities

Import pre-assembled quantities from CSV/XLSX corrects the pre-assembledPre-assembled stockStock of finished goods and subassemblies already built and on the shelf, counted per location. For Shopify-linked finished goods, these units are part of the applicable on-hand balance, not extra stock to add to it. A work order draws subassemblies from the shelf first, building fresh only if it runs short; an order consumes a finished good's shelf before its components.Read more → stock of many finished goods at once: a stock take of the built units on your shelves, a count across several warehouses, a correction after an audit. One row per BOM and location, one review, and one apply.

You reach it from the Finished goods list: More actions → Import pre-assembled quantities from CSV/XLSX in the title bar.

This import adjusts counts. It builds nothing, consumes no components and returns none, and it does not change the BOM itself: not its components, its settings or its total, which always follows its locations. To record units you actually built, use Quick build; see Pre-assembled stock. To create or update BOMs from a file, use Import from a spreadsheet.

  • The four steps
  • The columns
  • Set or adjust
  • Update Shopify
  • The review
  • If the lookup or the apply stops
  • When a row is refused
  • Saved mappings
  • Common gotchas
  1. Upload. Pick a CSV or XLSX file. The file is read in your browser. If you do not have one yet, the dialog offers a template with the six headers already in place.

  2. Map the columns. Tell the dialog which of your columns is which. Your headings do not have to match ours: common spellings (Variant SKU, Qty, Adjust By, Standort, and so on) are matched for you, and you can change any of them.

  3. Review. Assemblified looks up each BOM and location, reads the pre-assembled quantity there right now, and shows you current → resulting for every row before anything is written. This is also where you choose whether Shopify is updated. See The review.

  4. Apply. The ready rows are written in batches, with a progress bar. The final screen says how many pre-assembled shelves were set, and names every row that could not be, with its location and why.

Every row is one BOM at one location, and one change to it.

Column Required What it holds
BOM ID, Variant ID or SKU One of them Which BOM. When a row fills in more than one, the BOM ID wins, then the Variant ID, then the SKU. A Variant ID can be the plain number or the full Shopify ID.
Quantity One of Quantity or Delta The number of built units that should be on the shelf. 0 or more.
Delta One of Quantity or Delta The number to add. A negative number removes units.
Location Yes Where the stock is. A location name or its ID both work.

Location is required. A row with a blank Location is not written, and your default location is not filled in for you: pre-assembled stock always sits at one location, and a count for “somewhere” would land on the wrong shelf.

A row needs exactly one of Quantity and Delta. A row that fills in both is refused rather than guessed at: pick one. A row that fills in neither is refused too.

To change the same BOM at two locations, give it two rows.

  • Quantity sets a count. 40 makes it forty, whatever it was. Use it for a stock take.
  • Delta adds to what is there. +12 adds twelve, -3 removes three. Use it for a correction you already know the size of.

You can mix the two in one file, row by row.

Assemblified turns every row into the exact number it will set when you review, not when you apply: a Delta row becomes what is on the shelf now plus your delta. That way, if a batch has to be sent again, the shelf lands on the same number instead of moving twice.

The review has one option: Update Shopify. It is unticked every time you open the dialog.

  • Unticked — only Assemblified’s pre-assembled count changes. Shopify’s available quantity stays exactly as it is. Use it when Shopify already shows the right number, or when you are only bringing Assemblified’s shelf in line with a count.
  • Ticked — each row’s change is also sent to Shopify, by the same amount: a shelf that goes from 10 to 14 adds 4 in Shopify at that location. Batches are smaller while it is ticked, so a large file takes a little longer. Before anything is written, Assemblified checks that Shopify will accept each change. If a finished good is not stocked at that location in Shopify, you choose to activate it there or skip the row; a skipped row is not set, and the final screen names it. Cancel the check to go back to the review with nothing changed.

What unticked means depends on how the finished good is sold, and the review marks the rows where it matters. The rows stay ready; the mark only explains:

The finished good With Update Shopify unticked
Only sell pre-assembled quantities Shopify sells the shelf, and it does not follow this change. The finished good shows a difference between Shopify and the shelf until you reconcile it.
Dynamic adjustment Shopify follows at the next dynamic recalculation, for example the next order or material stock change. Not straight away.
Neither (including Maintain inventory level) Shopify keeps the number it has, as intended. No mark.

The header counts the marked rows. The mark follows the finished good’s own setting, so a location where a location rule turns Only sell pre-assembled off is marked too.

Floormode. If the Floormode connection is on and Floormode keeps a finished good’s Shopify number, ticked rows for it are marked: Shopify is updated by Floormode, not by this import. The pre-assembled count still changes.

While Assemblified looks everything up you see a progress bar with a step counter. Nothing is written during the lookup.

The review is a table with one line per row of your file, in the file’s order: the BOM, the location, the change (Set to n for a Quantity row, or the delta, +12 or −3, for a Delta row), the pre-assembled quantity as current → resulting, and the row’s state. Above the table, badges count the ready and blocked rows, and among the ready ones the set and adjusted ones.

A row is blocked, and never written, when:

  • no BOM has that BOM ID, Variant ID or SKU;
  • the SKU belongs to several BOMs. The row names them; use the BOM ID or Variant ID column for those rows instead (see Common gotchas);
  • your store has no location by that name or ID;
  • two rows target the same BOM at the same location. Both are blocked, because neither is clearly the one you meant. Merge them into one row;
  • the current pre-assembled quantity could not be read, so the result cannot be trusted and nothing is guessed. Remove the row and apply the rest, or upload the file again;
  • the finished good is not linked to Shopify (it has no Shopify inventory item). Its pre-assembled count cannot be changed until it is, with or without Update Shopify; see Pre-assembled stock.

A row with something wrong as typed shows its error in red:

Error Fix
Name a BOM by BOM ID, Variant ID or SKU The row names no BOM. Fill in one of the three columns.
Give either a quantity or a delta, not both Keep one of Quantity and Delta.
Give a quantity or a delta Fill in one of Quantity and Delta.
Quantity must be 0 or greater A Quantity cannot be negative. To remove units, use Delta.
Location required The Location cell is blank. Fill it in: this import has no default location.

A Delta that would take the pre-assembled quantity below zero is blocked in the review (Goes below zero): a count is never set below zero.

To go on without the rows that cannot be written, click Exclude blocked, or remove a single row. Or fix the file, close the dialog and upload it again.

While the lookup or the apply is running, the dialog’s main button is Stop. Stopping parks the run where it is; Resume carries on from the batch that was next.

If a batch fails (a dropped connection, for example), Assemblified tries it once more on its own. If it fails again, the run parks with Resume to try the same batch again. During the apply, batches that already finished are not undone, and a resumed batch never moves a shelf twice (see Set or adjust).

Close is unavailable while a run is going; stop it first.

Each row is written on its own. A row that fails does not stop the others. The final screen lists every row that could not be set, named by its BOM and location (for example Desk · Main warehouse), with the reason and a code in brackets. When some rows were set and others were not, the result is shown as a warning, not an error: the set rows did change. Only a run where nothing was set is shown as an error. Common reasons:

  • The finished good is not linked to a Shopify product. The review blocks these rows (Not linked to Shopify), so this only appears when the link was removed between the review and the apply. Its pre-assembled count cannot be changed until it is linked again; see Pre-assembled stock.
  • The BOM no longer exists. It was deleted between the review and the apply.

With Update Shopify ticked, a row can be set while Shopify does not take the change. The final screen names those BOMs and what to do for each:

  • Only sell pre-assembled quantities — reconcile it.
  • Dynamic adjustment — Shopify follows at the next dynamic recalculation, or run Sync with materials to update it now.
  • Any other finished good — change its available quantity in Shopify by the same amount.

A similar note appears when a batch had to be sent again, because a resent batch does not push a change twice.

What was already written stays written, and the Finished goods list shows the new pre-assembled quantities once the run ends or you close the dialog. To retry the failed rows, fix them and upload a file with just those rows.

If you upload the same kind of file regularly, save the mapping the first time: on the mapping step, tick Save mapping as template and give it a name. Next time, pick it from Pre-load a saved mapping on the upload step. These templates are listed under the import type BOM pre-assembled quantities in Settings → Import templates.

  • A SKU used by several BOMs. Two BOMs can share a SKU. A row that names such a SKU is blocked rather than written to one of them at random. Use the BOM ID or Variant ID column for those finished goods: both always name exactly one BOM.
  • Location is required. There is no default location here, unlike the assembly BOM import.
  • Quantity and Delta are opposites. A column headed Adjust by or Adjustment maps to Delta; a column headed Qty or New quantity maps to Quantity. Check the mapping step before you review: “set to 5” and “add 5” are very different numbers.
  • One row per BOM and location. A second row for the same pair blocks both rows rather than adding them up.
  • Unticked does not mean “Shopify later”. Only finished goods with Dynamic adjustment catch up on their own. An Only sell pre-assembled finished good keeps showing the difference until you reconcile it.
  • This adjusts counts. It moves no component stock. To record units you built, and consume their components, use Quick build; see Pre-assembled stock.