What changes when connected

Connecting a sibling app does not rearrange Floormode. The nav is the same, the screens are the same, and the jobs on the floor are the same. What changes is where some of the work comes from, and a handful of places where a new fact becomes available.

This page is the per-screen inventory of those differences.

On this page

• Receiving
• Floor Mode
• Orders
• Stock and the variant view
• Goods that are not on Shopify
• Counts
• Settings
• What does not change
• See also

Receiving

The biggest visible change, and the one to brief your receiving team on.

	Standalone	Connected to Logistified
Where expected deliveries come from	You create them	Announced by the purchase order or transfer
The Source column	Always “Entered by hand”	“Logistified purchase order”, “Logistified transfer”, or “Entered by hand” for ones you still create
Expected date	Whatever you typed, if anything	Carried from the document
Revisions	You edit the receipt	The document is revised in Logistified and the outstanding remainder updates here
Cancellations	You cancel the receipt	Cancelling in Logistified closes what is still open

Two behaviours are worth knowing before they surprise someone:

• A revision never touches what you have already booked in. If a purchase order is cut from 100 to 60 after you have received 80, the 80 stay received and the outstanding remainder becomes zero — it does not go negative and it does not un-receive anything.
• Receiving still happens here. When the connection is on, the sibling’s own receiving step is switched off deliberately. There is one place goods are booked in, and it is the Floor receive job.

You can still create expected deliveries by hand while connected. The two coexist.

Floor Mode

Production picksProduction pickPicking a work order's components to a staging bin so they are ready to be built, rather than picking finished goods for a customer. Read more → only exist when Assemblified is connected.

• Standalone — the Floor home shows picking, packing, receiving and counting. There is no production section.
• Connected — a Production picks section appears, listing work orders whose components need collecting, each showing the work order and how many materials it needs.

The picking loop itself is unchanged. The destination is a staging binStaging binA bin holding goods marshalled for a next step — components waiting for a build, or parcels waiting for despatch — rather than stock available to pick. Read more → rather than a pack bench, which is the point of the job.

Orders

• Kit lines can expand. With Assemblified connected, an order for a bundle can be picked as its components when no finished one is on the shelf — shown indented under the line it came from. See Bundles and kits. Without Assemblified, a bundle is an ordinary product.
• A new reason for waiting. Orders can sit on “Waiting for production” because a build has not finished, rather than only because stock is short.
• Holds are unchanged. The hold reasons, the document reference field and the release behaviour are identical either way.

Stock and the variant view

The four numbers — on handOn handThe units physically in the building right now, whether or not they are already promised to an order. Read more → , committedCommittedUnits already promised to open orders and therefore no longer freely sellable, even though they are still on the shelf. Read more → , availableAvailableOn hand minus committed minus unavailable — what is left to sell after existing orders have taken their share and held-back stock (damaged, quality control, safety stock, a blocked lot's units) is set aside. It is the number Shopify shows as available. Read more → , incomingIncomingUnits on an expected receipt that has not fully arrived — stock you have coming but cannot pick yet. Read more → — mean exactly what they meant before. Connecting a sibling does not redefine any of them.

What fills in is the supply picture around them. Opening a variant shows where incoming stock is coming from, and with Logistified connected the expected date travels with it, so “when does it land?” has an answer on the row rather than in somebody’s inbox.

Note

Supplier and on-order figures come from Logistified. Until it is connected these stay blank rather than showing zero — a supplier holding nothing for you and a supplier you cannot see are different facts, and only one of them is a number.

Goods that are not on Shopify

This is the one change that fills a page rather than a column. Item setup and recovery (on Inventory → Stock, under More stock actions) holds goods the sibling owns and Shopify has never heard of: Assemblified raw materials and sub-assemblies, Logistified custom items.

	Standalone	Connected
Item setup and recovery	Empty — there are none	Lists everything the sibling has sent
Raw materials and sub-assemblies on the floor	Do not exist here	Real stock in real bins, picked and counted like anything else
Who moves that stock	The sibling, in its own records	Floormode, once the per-location agreement is committed
The “Not on Shopify” badge	Never seen	On every row, pick line and count sheet for a local item

The ownership change is the substantial one. With the connection active and the per-location agreement committed, Floormode becomes the physical truth for those goods: Assemblified stops consuming its own raw materials when a build completes, Logistified stops moving its own custom items on receipt, and both show the quantities Floormode reports instead. Before either condition is met, nothing changes on their side — they keep moving their own stock exactly as they did.

New items arrive as claims, not as stock, and land on an Unplaced items worklist until somebody walks to the shelf and enters an opening quantity into a bin. See Local items for the full rule.

Note

Nothing about a local item is ever written to Shopify. They have no storefront listing and no Shopify inventory number, so there is no single-writer question to answer for them — the push is refused rather than merely skipped.

Counts

Approving a cycle count exports it to Logistified as a stock take, so its records reflect the count you just did.

It is reporting only. Floormode already wrote the corrected quantity to Shopify and the bin-level truth is Floormode’s — the sibling records the count, it does not re-apply it. Counting itself, variances and the approval queue are unchanged.

Settings

An Apps area appears, with one switch per sibling and the integration health panel underneath it.

One fact changes meaning: whether a warehouse is live (its Keep Shopify’s quantities updated state) becomes load-bearing once Logistified is connected, because the sibling stops writing received quantities at that point. See Who updates Shopify.

What does not change

Worth stating explicitly, because the list is longer than the list of changes:

• Picking, packing, scanning and shipping. Identical.
• Customer communication. Floormode sends it, connected or not. Neither sibling emails your customers.
• Bins, placement, putaway rules and capacity. Identical.
• Returns. Entirely Floormode’s, in every configuration.
• The nav. No new top-level entries. Receiving stays inside Inventory; production picking stays inside Floor Mode.
• Your own expected receipts, holds and adjustments. Still available, still work.
• Shopify as the source of truth for what is sellable. Unchanged.

See also

• Logistified — the purchasing side in full.
• Assemblified — the production side in full.
• Standalone — the same comparison from the other direction.

Last updated: 25 October 2026