Integration health

The connection switches say what you asked for. The health panel says what is actually happening — and the two are not the same thing often enough to need a screen.

You will find it in Settings → Integrations, on the Activity tab beside the connection switches’ Apps tab.

Why this screen exists

An integration fails in ways that are invisible from every other screen in the app. The floor looks fine, the receipts look fine, the bins are right — and something upstream is nonetheless wrong. There are four such ways, and this panel is one card per way:

The switch is off and nobody remembers turning it off.
They stopped talking to us — or, which looks identical and has the opposite fix, they are talking and we keep refusing them.
We stopped talking to them — messages are piling up unsent.
Nobody is writing Shopify inventory — the silent one.

Connection status

One block per connected app — Logistified, Assemblified and Alertified, which forwards alert events such as oversell risk and SLA breaches.

The status line on the switch card says where each connection stands (Waiting for the other app, Connected, no exchange yet, Connected, Local stock active, Not answering); the block here carries — when anything is genuinely stuck — a red count of messages stuck, which is the number worth reacting to.

Connection is two independent facts, so a switch being on is not sufficient: the sibling app also needs to be installed and switched on for your shop. The status line on the switch card shows that as its stages — Waiting for the other app while its switch is off or nothing has been heard, Connected, no exchange yet once both switches are on, Connected once a message has gone either way. Floormode never writes that state — it reads it from the evidence.

What each connection has done

What we accepted from them:


Received	Messages accepted and applied
Rejected	Messages that arrived and were declined, with a reason
Last message	When they last spoke to us at all

Those three are separate on purpose. A silent connection and a connection whose every message you are refusing look identical from the warehouse floor and need opposite fixes — Last message tells them apart.

What of ours is still trying to reach them:


Queued	Written down, waiting its turn
Sending	An attempt in flight
Delivered	Confirmed applied by the other app
Held	The other app is not answering; sent once it answers
Never delivered	Given up on. Permanent
Failed	Rejected or errored
Oldest waiting	How long the oldest held message has been waiting
Rate limited	The other app asked us to slow down

Parked and held explains each state and what moves a message out of it.

Receiving ownership

Inside the Logistified block, the panel states plainly which app receives where — because with several locations this is exactly the fact people get wrong.

Shop-wide — the connection switch decides receiving for every location. This is how a shop behaves until it commits a per-location agreement, and where it returns if one is released.
Per location — an agreement is live. The panel says how many of your locations Floormode receives into, and lists every one as received here or received by Logistified.

Locations that are not handed over are listed too, deliberately: “this location is Logistified’s” and “this location is not in the agreement at all” are different situations, and collapsing them would hide the second.

If Logistified has proposed a new agreement, the panel says so — including when it was proposed but could not be accepted yet, which points you at a mapping to fix. See Who writes Shopify for the handover itself.

Nobody is writing Shopify inventory

The red alert at the top of the panel, and the most important thing on this page:

Nobody is updating Shopify for received goods. Logistified is connected, so it no longer writes received quantities — receiving happens here. But these warehouses are not live yet, so nothing we receive reaches Shopify.

It names each affected warehouse and its Shopify location, and tells you the fix: open each warehouse in Settings → Warehouses and click Go live. A live warehouse shows Keep Shopify’s quantities updated as Live.

A second, softer warning covers the reverse case — a warehouse that still writes inventory but is not handed over for receiving. That one is reported rather than fixed, because the same flag also governs sales picks and counts.

Who updates Shopify

The last card is the ownership table: every inventory flow, which app writes it, and why, given what you currently have connected. It answers “who writes what?” in one place instead of requiring you to reconstruct it from four screens.

Any row reading Nobody in red is a gap to close. Not applicable is not a problem — it means nothing in that flow currently occurs, such as work-order picks with Assemblified disconnected.

What to do when something is waiting

A short triage order:

Rate limited — do nothing. It is a pause, not a failure, and it does not consume a delivery attempt.
Held — the other app is not answering. Do nothing: the backlog goes out in order once it answers. A switched-off app holds nothing: switching it on starts fresh.
Failed — the other app rejected the message or the attempt errored. Check that the sibling is installed with an active plan.
Rejected — they are fine, we are declining. The reason usually names the fix: a Shopify location not mapped to a warehouse, or a delivery for a location you have not handed over.
Never delivered — permanent. The sibling’s records are behind by that many messages and will not catch up on their own.