Sub-assemblies from Assemblified

If your store uses Assemblified, its sub-assemblies (pre-built components it keeps on a shelf, SKUs starting with ASM-) appear in Logistified like any other item. You can put them on purchase orders, transfer orders, return orders, supplier stock releases, stock takes and stock adjustments. Assemblified stays in charge of their stock: every change a document makes is sent to Assemblified, and the quantity you see in Logistified updates when Assemblified confirms it, usually within seconds.

Adding sub-assemblies to documents

Add a sub-assembly the same way as any item. The Virtual materials picker lists them after the virtual materials, each marked Assemblified sub-assembly. Imports, the forecast and the Reporting bulk actions accept them too.

How their stock changes

A sub-assembly’s quantity in Logistified always mirrors Assemblified’s shelf. When you receive a purchase order, send or receive a transfer, apply a stock take or move a return, Logistified sends that change to Assemblified instead of to Shopify. While it is on its way the line shows that it is syncing to Assemblified, and the quantity stays where it was until Assemblified’s update arrives. Nothing is ever sent to Shopify for a sub-assembly.

Purchasing sub-assemblies

Map a supplier first. Logistified never assigns a sub-assembly to a supplier on its own, not even the default supplier. Add it to a supplier on the supplier’s page (or through a supplier import) with its supplier cost, like any variant.
Generating a purchase order for one supplier (from the forecast, min-max or sales history) orders the sub-assemblies mapped to that supplier. A sub-assembly the run would have ordered but no supplier is mapped to is named in the dialog with “No supplier is mapped to this sub-assembly. Map one in Suppliers to purchase it.” A forecast filtered by supplier doesn’t show sub-assemblies no supplier is mapped to.
Receiving sends the received quantity to Assemblified, together with the unit price when the order is in your store’s currency or has an exchange rate set on it. Otherwise the price follows when you complete the order. Unreceiving, cancelling or deleting a received line takes the quantity back out of Assemblified.
Unit cost. A sub-assembly’s cost belongs to Assemblified. Completing the order (with automatic cost sync) or using Update unit cost sends Assemblified one purchase price per sub-assembly for the order (its price per unit over the units received, in your store currency) as the sub-assembly’s purchase cost. Assemblified uses it when the sub-assembly’s cost method is Purchase cost and sends the resulting cost back; a moving average is not changed by it, because it takes each purchase at the price on its receipt. A sub-assembly with nothing received on the order yet is not sent; the result names it. The dialog marks such rows Sub-assembly and notes: Sent to Assemblified as the sub-assembly’s purchase cost, which the Purchase cost method uses. It does not change a moving average, which takes each purchase at its receipt’s price. Your supplier’s catalogue cost is updated as usual. Logistified never writes a sub-assembly’s cost itself.
Minimum order quantities and pack sizes from supplier terms don’t apply to sub-assemblies, the same as for virtual materials.

Transfers

Sending a transfer takes the sub-assemblies out of the source location in Assemblified, receiving adds them at the destination, and cancelling after sending puts them back.

Stock takes and adjustments

A counted sub-assembly is sent to Assemblified as the quantity you counted, once per apply, even when the count matches what Logistified already shows. Assemblified takes the count as the physical quantity on the shelf and works out what is available from it after the orders it already holds stock for.
An adjustment sends the amount you add or remove.

Returns and supplier stock releases

Move Inventory on a return order and receiving a supplier stock release send their sub-assembly lines to Assemblified the same way. Reversing a return’s restock sends the opposite change.

When a sub-assembly can’t be added

Logistified support can pause sending sub-assembly changes to Assemblified. While it is paused, documents refuse sub-assemblies with “Sub-assembly write-back to Assemblified is paused.”, the other items on the same request are still saved, and the dialog names the ones left off. Changes already on their way still reach Assemblified.