Floormode on its own

Floormode is a complete warehouse app on its own. The siblings add documents it does not own — purchase orders, work orders — but nothing in picking, packing, shipping, receiving, counting or returns waits on them.

On this page

• Everything physical still works
• What stays empty
• What you do instead
• Connecting later: what does and does not backfill
• See also

Everything physical still works

The whole of Floormode’s own job runs unconnected:

Area	Standalone
Orders, holds, splits and merges	Fully working
Picking, packing, shipping, returns	Fully working
Receiving	Fully working — you create the expected deliveries yourself
Bins, placement, putaway, counts	Fully working
Replenishment suggestions	Fully working — export CSV to any supplier
Writing availability to Shopify	Fully working, and entirely yours

That last row is the important one. Unconnected, Floormode is the only app writing inventory to Shopify, so there is no single-writer question to answer.

What stays empty

These surfaces exist but have nothing in them until a sibling is connected:

• No supplier purchase orders in receiving. Every expected receiptExpected receiptA delivery you are waiting on. It moves from expected, through being received, to received as the floor books it in line by line. Read more → is one you created; its source reads “Entered by hand” rather than naming a Logistified document.
• No production picks on the floor. The Production pick job only ever appears when a work orderWork orderAn instruction to build something — the document in Assemblified that names what is being made, how many, and which components it consumes, and which asks Floormode to pick those components. Read more → announces one, so with Assemblified disconnected the Floor home never shows a Production picks section.
• Supplier and on-order buckets are empty. The variant view can show what a supplier is holding for you and what is on an open purchase order — but those figures come from Logistified, so unconnected they stay blank rather than showing zero as if it were a fact.
• No kit expansion. Bills of materials live in Assemblified. Without it, a kit is an ordinary product: if you stock finished ones, they pick normally; if you do not, the order goes short rather than expanding into components.
• No local items. Item setup and recovery (on Inventory → Stock, under More stock actions) exists but is empty, and there is no way to fill it: local items are goods a sibling app owns — raw materials, sub-assemblies, custom items — and they only exist here while that app is connected. You cannot create one by hand, because the item’s identity belongs to the other app.

Note

Standalone, everything you stock is a Shopify product, so the “Not on Shopify” badge never appears and the “every unit always has a place” rule never comes up. Both are consequences of holding goods for a sibling, and neither applies until you connect one.

Note

Empty is not broken. These surfaces are deliberately blank rather than showing invented zeroes — a supplier figure of nought and a supplier figure you cannot see are very different facts, and only one of them should look like a number.

What you do instead

None of the gaps above is a dead end:

• Purchasing — Replenishment still tells you what to reorder and still exports CSV. Send that to your supplier by whatever means you already use.
• Expected deliveries — create them directly in receiving. The floor books them in identically; nothing downstream can tell the difference.
• Waiting on something external — put a hold on the order and type the document reference. It is a note to the next person rather than a live link, and for most operations that is enough.

Connecting later: what does and does not backfill

This is the part worth being blunt about.

Connecting a sibling does not import history. There is no backfill of documents that already existed. Specifically:

	On connect
Purchase orders already open in Logistified	Not imported retroactively
Deliveries you already received by hand	Stay exactly as they are — never reported to the sibling
Counts you already approved	Not exported retroactively
Work orders already in progress	Not announced retroactively
Local items the sibling already holds	The list does arrive — the quantities do not. Each lands as a claim on the Unplaced items worklist for you to count onto a shelf

What you get from the moment of connection is ongoing flow: documents that reach their announcing state after the connection is live show up, and physical work you do after that gets reported back.

Caution

The practical consequence: finish or write off the in-flight paperwork before you connect, or run the two side by side until the old documents are closed. A purchase order raised in Logistified before the connection existed will not appear in receiving by itself — re-issue it in Logistified if you want it to.

The one thing that does change immediately is who writes inventory to Shopify. Connecting Logistified hands received-goods writing to Floormode straight away — see Who writes Shopify, and check the health panel once you have connected.

See also

• Activation — the connect flow itself.
• What changes when connected — screen by screen.
• Replenishment — the CSV path that works with any supplier.

Last updated: 25 October 2026