Logistified

Logistified is a Shopify-native warehouse and demand-planning app. It forecasts what you’ll need to restock, tracks stock across multiple locations, and manages purchase orders. Connecting it to Assemblified lets it see what your BOMs actually consume — not just what your customers buy.

On this page

• Why connect Logistified to Assemblified
• Capabilities
• Prerequisites
• Connect Logistified
• Subassemblies in Logistified
• ⭐ Initial retrospective demand sync
• Inbound from Logistified
• Manage and monitor

Why connect Logistified to Assemblified

Without the integration, Logistified only sees finished-good sales. A candle order looks like one unit of demand for the candle SKU — Logistified doesn’t know it just consumed wax, wick, jar, and label. Forecasts and reorder suggestions stay at the finished-good level.

With the integration, every BOM executionBOM executionEverything Assemblified does when a Shopify order containing a bill-bound variant is created, edited, cancelled or refunded: draw down pre-assembled stock, deduct or restore components, push the changes to Shopify, and cascade dynamic adjustment. It runs in the background, writing one execution log row. Read more → turns into a synthetic demand order against the components. Forecasts now reflect real consumption per materialMaterialThe atomic component of a bill of materials or an assembly BOM. Two flavours: a Shopify-linked variant, whose inventory Shopify tracks, or a virtual material, which Assemblified tracks on its own and Shopify never sees. Both sit in the same component picker and are consumed the same way. Read more → and virtual materialVirtual materialA 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. Read more → , so reorder suggestions land on the parts you actually need. SubassembliesSubassemblyA reusable assembly block that composes into bigger bills: define it once, include it in any bill of materials, and Assemblified expands it into its own components at execution time. Its definition is an assembly BOM. Read more → can be forecast the same way, because Logistified sees both their stock and the demand for them.

Capabilities

BOM execution → demand order

Every successful BOM execution pushes a per-component demand record to Logistified. Cancellations and refunds clean up the corresponding order automatically.

Virtual material and subassembly sync

Optional toggle. When on, virtual materials (consumables with no Shopify variant) and subassemblies, with their pre-assembled stock per location, are pushed alongside Shopify-linked materials. Includes a one-shot “Sync all virtual materials and subassemblies” button for the initial push.

Retrospective demand backfill

A one-shot historical sync that seeds Logistified with the demand from past orders — see the dedicated section below.

Inbound inventory updates

Purchase-order fulfillments, stock-transfer reductions/additions, stock takes and adjustments from Logistified flow back into Assemblified: into material inventory, and into the pre-assembled stock of subassemblies.

In short: anything that changes how much of a component you’ve used, will use, or have on hand syncs both ways automatically. You don’t have to touch any other surface to keep the two apps aligned.

Prerequisites

• The Logistified Shopify app installed on the same store. The Settings card surfaces a “Get App” link to the App Store if it isn’t.
• A Logistified subscription that allows external integrations (the Connect button stays disabled if the partner side blocks it).

Connect Logistified

1. Open Settings → Integrations → Logistified. The card shows the current connection state with a green dot if you’re connected.

2. Click Connect. Assemblified records the connection state and lets the partner side know it’s authorised to receive your BOM-execution data.

3. Leave “Disable inventory reduction” off (the default). Once connected, every BOM execution pushes its component demand to Logistified. The switch is an opt-out for stores where another system owns the component stock in Shopify: when it is on, Assemblified still records the execution but sends no component changes to Shopify and no demand to Logistified. The inbound side (PO / stock-transfer / stock-take updates) works either way.

4. (Optional) Turn on “Sync virtual materials to Logistified”. Turn this on if you track consumables as virtual materials, or build subassemblies, and want them in Logistified’s forecasts too. The switch covers both: virtual materials and subassemblies. Use the Sync all virtual materials and subassemblies button to push everything already in Assemblified in one go.

Note

The Connect / Disconnect toggle is non-destructive — disabling the integration just stops new messages from going out. Historical data already pushed to Logistified stays there until you remove it explicitly via the retrospective DELETE flow.

Subassemblies in Logistified

With Sync virtual materials to Logistified on, every subassembly in Assemblified also appears in Logistified as an item, with its name, SKU, cost and its pre-assembled stock at each location. It works the same way as virtual materials.

• Stock stays current on its own. Whenever you build, use, adjust or move pre-assembled stock, or edit or delete a subassembly, Logistified is updated within a few seconds. A burst of changes arrives as one update with the final numbers. As a safety net, Assemblified also re-checks every subassembly once a night.
• Turning the switch on sends everything. The first time you turn it on, all your existing subassemblies are sent. Sync all virtual materials and subassemblies does the same on demand.
• Subassemblies get demand, so they can be forecast. When a finished good that contains a subassembly sells, Logistified records demand for the subassembly itself as well as for the materials, multiplied through every level of nesting. This happens for new orders, for the retrospective backfill below, and when you create orders in Logistified only. Switch the sync off and the demand messages go out exactly as before, without subassembly lines.
• Buy, move and count them in Logistified. Subassemblies can go on purchase orders, transfers, returns, supplier stock releases, stock takes and stock adjustments in Logistified, like any other item. Each change lands on the subassembly’s pre-assembled stock at that location in Assemblified within seconds, and Logistified shows the new stock as soon as Assemblified sends it back. Assemblified stays the owner of the stock, so you can keep building and adjusting there too.
• Purchasing needs a supplier. Map the subassembly to a supplier in Logistified first. Purchase orders created from the forecast, min-max or sales history list a subassembly without a supplier instead of ordering it.
• Receiving records what you paid. When the purchase order is in your shop currency, or has an exchange rate set, the price arrives with the receipt and becomes the subassembly’s purchase cost in Assemblified. Logistified’s cost sync then sends the purchase order’s final cost per unit (landed costs included, in your shop currency) when the order is completed or its unit costs are updated, and that replaces it. Whether Assemblified uses the purchase cost depends on the subassembly’s cost method (purchase cost, or a moving average of built and bought units), and the cost Logistified shows for the subassembly is the one Assemblified uses.
• A stock take sets the counted quantity. Assemblified sets the pre-assembled stock at that location to what you counted, minus any units already picked for a build there. An older count never overwrites a newer one, and a receipt made before a count but synced after it is already part of the count; Logistified marks such a line “Already included in a later stock take”. Units that an open order has reserved are not taken off the count, so count subassemblies after those orders are fulfilled, or adjust afterwards.
• Transfers carried out by Fulfillified are not supported for subassemblies yet. A transfer with a subassembly on it cannot be handed to Fulfillified to execute; transfer it in Logistified instead.

Note

Logistified only receives subassemblies while both the Logistified connection and the sync switch are on. If you turn the switch off, nothing is lost: Assemblified catches Logistified up the next time you turn it back on.

⭐ Initial retrospective demand sync

This is the step most easy to skip and most worth doing. Logistified’s forecasts need a history of demand to be useful from day one. Without a backfill, the first few weeks after connecting are blind — there’s no signal until enough new orders accumulate.

The retrospective sync pushes every past order’s BOM consumption into Logistified as if the integration had been connected all along. When the virtual material and subassembly sync is on, the subassemblies inside those BOMs get their demand too.

Run the backfill

1. Open the Finished goods page. Click Bill of materials in the Assemblified navigation.

2. Select the BOMs to backfill. Tick them in the table — filter or search first if that’s quicker, and you can select every row the current filters match. A bar appears along the bottom.

3. Open the dialog. In that bar, choose More actions → Integrations → Sync with Logistified. The entry only appears when the integration is connected. The dialog opens on the Sync orders tab, which names how many finished goods the run will cover.

4. Pick a period. Under Period, choose Last 6 months, Last 12 months, Last 24 months or All time. The line underneath the list spells out the span you picked, so you can check it before running. Custom range reveals a calendar: click the first day of the span, then the last. Days after today are not selectable.

5. Resolve conflicts. If your period overlaps any previously-recorded sync for one of the selected BOMs, the dialog names those BOMs and the periods they already cover. Adjust the range or narrow the selection to avoid double-counting demand.

6. Click Sync orders. Assemblified queues a replay of every past order through the selected BOMs and records each (BOM, start, end) period in its sync history so you can undo it later. The confirmation tells you the work is queued — it runs in the background.

Caution

Running All time against a busy store produces a lot of queued work — one synthetic order per BOM per past Shopify order. Kick it off, then let the queue drain before re-running anything against the same period. The conflict warning tells you when a range has already been covered, but it’s a warning, not a stop — read it before you click Apply.

Undo a sync

If a backfill was wrong — wrong date range, wrong BOM set, or you want to start over — select the BOMs again and switch the dialog to the Synced periods tab.

1. Review the recorded periods. The tab lists every retrospective sync period Assemblified has on file for the selected BOMs: the finished good, the period it covers, and the day it was synced. If there’s nothing to show, it says so.

2. Tick the periods to remove. Tick a row, or use the checkbox in the table header to take the lot; the count under the table tells you how many are selected. One run can remove up to 500 periods. Exact-period matches delete the history record outright. Partial overlaps trim or split the record so the rest of the period stays intact.

3. Click Delete N periods. Logistified removes the corresponding synthetic orders on its side, the material movements they made are reversed, and the sync history on the Assemblified side is trimmed to match. The button is red because this undoes real inventory movement. The run is queued, and the confirmation counts the periods that were removed.

Inbound from Logistified

The integration is bidirectional. Logistified pushes three event types back into Assemblified, and Assemblified applies them as inventory adjustments on the relevant materials.

Event	What it means	Effect on Assemblified
PO fulfillment quantity changes	A purchase order received or partially received.	The material’s available stock increases by the received quantity at the location the PO was fulfilled to.
Stock-transfer reduction / addition	Stock moves between locations in Logistified.	The source location’s stock decreases by the transferred quantity; the destination’s increases.
Stock-take quantity changes	A physical count adjusts the on-hand quantity.	The material’s available stock is set to the counted value at that location.

Inbound updates land on materials in the active session’s BOM-aware store, which is what the UI reads — so changes show up the next time the merchant refreshes the raw-materials page. No manual reconciliation is needed.

Subassemblies take the same routes. A receipt, transfer, return, supplier stock release, stock take or adjustment of a subassembly in Logistified changes its pre-assembled stock at that location in Assemblified (a stock take sets it to the counted quantity), and the price of a receipt becomes its purchase cost for its cost method. Logistified’s own stock figure for the subassembly follows once Assemblified sends it back, a few seconds later.

Manage and monitor

• Connection status. The Logistified card in Settings → Integrations shows a green / red dot for the current connection state. Disconnect at any time without losing already-synced data.
• Sub-toggle status. Disable inventory reduction and Sync virtual materials to Logistified each have their own toggle, so you can change one without touching the other.
• Per-BOM sync history. Every retrospective period is recorded against its BOM and visible inside the Delete tab. You can also fetch it programmatically per BOM if you need to audit which periods have been pushed.
• Conflict warnings. Before you run a backfill, the dialog names every selected BOM whose recorded history already covers part of your date range, and the periods it covers. Heed it — that’s how you avoid double-counting demand.

Where to next

Inventory tracking How raw-material stock is tracked per location — the surface that inbound Logistified events update.

BOM execution model What an execution actually does, and which executions trigger the outbound Logistified messages.

Refunds and cancellations The cancellation and partial-refund paths that clean up the corresponding demand orders on the Logistified side.

Virtual materials What virtual materials are, the consumables the "Sync virtual materials to Logistified" switch pushes into Logistified.

Subassemblies The pre-assembled stock that Logistified receives for each subassembly, and that its purchase orders, transfers and stock takes change.

Cost methods How a subassembly's purchase cost from Logistified is used: its recipe cost, its last build cost, its purchase cost or a moving average.