Activation

Connecting takes one switch. Knowing what that switch does — and what it deliberately does not undo — takes this page.

What you need first

Two things, and the connection needs both:

Both apps installed on the same shop. The sibling must be installed and on an active plan. Floormode reads that state and never writes it — so if the sibling’s subscription lapses, the connection stops sending regardless of the switch.
Every receiving warehouse live. Connecting Logistified is refused while a receiving warehouse has not gone live, because from that moment Logistified stops updating received quantities; the card lists the warehouses with a Go live link before you flip.
Your warehouses mapped to Shopify locations. This is the one that catches people out. Documents are routed by Shopify location, so a warehouse with no mapping cannot be the destination of anything a sibling announces. Check Warehouses before you connect, not after.

Connecting

Open Settings → Integrations and find the Apps card.
Switch on the sibling you want. There is no separate save step — a connection is a single fact, and a save button would only add a state to get wrong.
Give consent in the sibling app. Each sibling asks on its own side, because each is agreeing to give something up: Logistified gives up receiving, Assemblified gives up parts of its Shopify writing.
Watch the status line under the switch: Waiting for the other app → Connected, no exchange yet → Connected (the first message exchanged). Use Check connection for a plain yes or no, and the Activity tab for the counters.

The switches read plainly enough to choose from:

Connection	What it exchanges
Logistified	Purchase orders, transfers and counts
Assemblified	Work-order component picks and kit expansions
Alertified	Alert events — oversell risk, SLA breach, count variance

What switches itself on

Connecting Logistified starts fresh: nothing was sent while it was off, and nothing from that time is sent later. Nothing else is changed for you: a warehouse goes live on its own detail page, and the switch waits until every receiving warehouse has.

Connecting Assemblified starts fresh in the same way, and from that point work orders can announce component picks and orders can expand kits into their parts.

Verifying it works

The status line under each switch says where the connection stands, from evidence only, with one sentence under it saying what to do next. The words are the same in all three apps; Run Floormode with Logistified and Assemblified lists every state and its next step. In short: Waiting for the other app (your switch is on, the other app’s is not), Connected, no exchange yet (both switches are on), Connected (a message was exchanged), Local stock active. Not answering means deliveries are paused after repeated failures.

Check connection answers in one sentence whether the other app can be reached right now. It never changes the status line; only real traffic does.

The Activity tab holds the counters: what was accepted from them, what was delivered to them, failed messages, and the Who updates Shopify table.

The most convincing single test is an end-to-end one: raise a small purchase order in Logistified, watch it appear in Receiving with its supplier and expected date, receive one line, and confirm the progress shows up on the Logistified side.

Handing over receiving per location

If you run several locations, you do not have to move them all at once. Receiving can be handed over location by location through a prepare, check and commit sequence driven from Logistified — and until you commit it, your shop keeps behaving exactly as it did.

That flow is covered in full under Who writes Shopify.

Disconnecting

Switching a connection off is safe and reversible. Worth knowing:


Sending stops	Nothing is sent and nothing is kept for later. Switching on starts fresh
Receiving waits	Documents the sibling sends are not applied; it keeps them and they land once you switch on. Its exits (leaving, releasing receiving) always land
Inventory writing stays on	Turning Logistified off does not turn the writers back off
Local stock is handed back, not dropped	Goods that only exist in the sibling go through the handover below — a separate, deliberate step

The third is intentional: with nothing connected, Floormode writing inventory to Shopify is the correct configuration. But it does mean disconnecting leaves a setting changed that you never changed by hand, so it is worth a look at Warehouses afterwards.

Work already done is never undone by disconnecting. Received goods stay received, staged components stay staged, and stock stays where the bins say it is.

Handing local stock back

If the sibling’s local items are stocked here — raw materials, sub-assemblies, custom items — then walking away is not a matter of flipping a switch. Floormode is holding the only record of how many there are. Dropping the connection without saying so would leave the other app with a stale number and no way to discover it.

So local stock is returned through a deliberate handover, and it is a separate, explicit step — not something the connection toggle does behind your back. Burying a warehouse freeze inside a control that looks like a mute button is exactly how somebody discovers it by accident.

The connection switch is what starts it. When an app’s goods are stocked here, its switch in Settings → Integrations no longer simply turns off: it asks first — “Hand local stock back to Assemblified?” — and explains what is about to happen. Confirm, and the handover starts. Cancel, and nothing at all has changed.

The sequence, once started:

Freeze. Everything of that app’s becomes read-only immediately, before anything is calculated. No receiving, no picking, no counting, no adjustments. Staged and in-transit units are settled into stable bins first, so what gets stated is what is actually on a shelf. The Local items tab says “Stock is being handed back”.
State the numbers. Floormode derives the exact quantities from its own ledger — every item, including the ones at zero. A zero has to be said out loud: leaving it out would leave the other app’s old figure standing, which is the one outcome the whole exercise exists to prevent.
Send, and wait. The quantities go to the owning app, which replaces its own figures with them in one go and confirms. Until that confirmation arrives, the health panel shows the app as “Handing back” and the handback as “Waiting for confirmation”.
Release. Only on a matching confirmation does the freeze lift. The items are marked “Handed back”, the app resumes keeping its own numbers, and Floormode stops being the physical truth for them.

Three things to expect:

If the confirmation never comes, nothing happens. The panel keeps saying “Handing back” indefinitely, and that app’s stock stays frozen. There is no timeout and no automatic release, deliberately: releasing on a guess would mean both apps writing the same numbers again. Chase the other app.
If the confirmation does not match what was sent, the handback is marked “Rejected — check the log”, the freeze stays on, and an alert is raised. Again: held open on purpose, not quietly retried — but the switches carry a Retry handback button for it, and pressing it sends the same snapshot again rather than starting a second release.
Handed-back history is kept, never deleted. If you reconnect later, that record is what lets Floormode place only the difference rather than adding a second full quantity on top of the first.