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
• ⭐ 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 executionThe 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. Read more → turns into a synthetic demand order against the components. Forecasts now reflect real consumption per raw materialRaw materialThe 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. 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.

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 sync

Optional toggle. When on, virtual materials (consumables with no Shopify variant) are pushed alongside Shopify-linked materials. Includes a one-shot “Sync All Materials” 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, and stock takes from Logistified flow back into Assemblified’s raw-material inventory.

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 shop. 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. Enable Inventory Reduction (recommended). When on, every BOM execution syncs to Logistified. Leave it off if you only want the inbound side (PO / stock-transfer / stock-take updates) without pushing component demand outbound.

4. (Optional) Enable Sync Virtual Materials. Turn this on if you track consumables as virtual materials and want them in Logistified’s forecasts too. Use the Sync All Materials button to do the initial one-shot push for everything already in Assemblified.

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.

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

Run the backfill

1. Open the Bill of Materials page from the main nav. The bulk-controls bar at the top exposes a Logistified Sync action when the integration is connected.

2. Open the dialog. It opens on the Create tab.

3. Select the BOMs to backfill. Either pick a subset from the list or leave it as “all”. The dialog shows each BOM’s last-known sync period if one exists.

4. Pick a date range. Default is the last 30 days. Tick Sync All Orders instead if you want the full lifetime of the shop (1970-01-01 → today).

5. Resolve conflicts. If your selected period overlaps any previously-recorded sync for a BOM, the dialog flags it inline. Adjust the range or unselect the conflicting BOMs to avoid double-counting demand.

6. Click Create Orders. Assemblified replays every past order through your BOMs and records the (BOM, start, end) period in its sync history so you can undo it later.

Caution

Running Sync All Orders against a busy shop 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 warnings will block double-runs, but you’ll get faster feedback by waiting.

Undo a sync

If a backfill was wrong — wrong date range, wrong BOM set, or you want to start over — switch the dialog to the Delete tab.

1. Select recorded periods. The Delete tab lists every retrospective sync period Assemblified has on file, grouped by BOM.

2. Pick the periods to remove. 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 Orders. Logistified removes the corresponding synthetic orders on its side, and the sync history on the Assemblified side is trimmed to match.

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 raw materials.

Event	What it means	Effect on Assemblified
PO fulfillment quantity changes	A purchase order received or partially received.	The raw 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 raw material’s available stock is set to the counted value at that location.

Inbound updates land on raw 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.

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. Inventory Reduction and Sync Virtual Materials each have their own toggle, so you can pause 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 guardrails. The dialog refuses to push a date range that overlaps an existing sync period for the same BOM — this is how double-counting is prevented.

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 toggle pushes into Logistified.