# Floormode documentation > Every page of https://docs.floormode.app/ in one file, in the order of the site's sidebar. Each page starts with its address. --- Source: https://docs.floormode.app/ # Floormode Documentation Picking, packing, shipping, receiving, returns and inventory for Shopify merchants who ship their own orders. ## What Floormode does Orders One order list with saved views, plain-English blocked reasons, holds, splits, merges and line edits. Fulfillment The queue, pick batches, scan-verified packing, carrier rates and labels, and optional release control. Inventory Stock across warehouses, receiving, cycle counts, adjustments, the full movement ledger, bins and placement. Returns A returns page in your own store, request review, and grading every unit that comes back before it re-enters stock. Insights Throughput and cycle-time reports, replenishment suggestions, and what the stock on your shelves is worth. Floor Mode A full-screen, scanner-first surface with giant tap targets and one job at a time — no admin chrome. Automation Three ordered rule cascades: order rules, order routing and shipping rules. Routing and shipping fall back to a sensible default when no rule matches. Agents & API An external [REST API] (/rest-api/overview/) and an MCP server, so an agent can read and drive the same operations the app does. Browse every operation in the [API explorer] (/rest-api/explorer/). ## Where to start Using Shopify's batches today? [Shopify batches vs Floormode] (/getting-started/shopify-batches-vs-floormode/) says what Shopify does by itself, what Floormode adds, and when Shopify alone is enough. New to Floormode? Start with [Installation] (/getting-started/installation/), then work through the [setup guide] (/getting-started/setup-guide/) on Home. Looking for a feature? Use the sidebar: the Features chapter follows the app’s nav, and [Finding your way around] (/getting-started/finding-your-way-around/) maps all eight nav entries. Lost in the vocabulary? The [glossary] (/reference/glossary/) defines every warehouse term the app uses, in one sentence each. Coming from an older version? The [URL map] (/reference/url-map/) shows where every pre-overhaul link now lands. --- Source: https://docs.floormode.app/getting-started/shopify-batches-vs-floormode/ # Shopify batches vs Floormode What Shopify's own batch fulfillment does, what Floormode adds on top of it, and when Shopify alone is enough. Since October 2026 the Shopify admin can fulfil orders in batches: one pick list for many orders, labels bought together, items scanned at packing. If you are deciding whether you need Floormode, this page says what Shopify does by itself, what Floormode adds, and when Shopify alone is the better choice. ## On this page - What Shopify’s batches do - What Floormode adds - When Shopify alone is enough - When Floormode earns its place - See also ## What Shopify’s batches do Shopify describes the feature in its [changelog] (https://changelog.shopify.com/posts/fulfill-orders-in-batches) and in the Help Center under [Batch fulfillment] (https://help.shopify.com/en/manual/fulfillment/fulfilling-orders/batch-fulfillment). In short: - A batch holds up to 250 fulfillments, grouped by things like product type or shipping destination. A batch made in bulk takes unfulfilled orders from the last 14 days. - One pick list for the whole batch. It lists the products of every order, with fields such as SKU, quantity and a bin name. - Labels for the whole batch can be bought in one go, where Shopify Shipping is available, and printed with packing slips and customs forms. - Scan to verify at packing. A right item plays a tone and turns green; a wrong or extra item is refused. Without a scanner you can adjust quantities by hand. - Your own steps. You can add, rename and reorder the batch’s steps and give each to a staff member. - It is available to every store and runs inside the Shopify admin. Removing an order from a batch, or deleting the batch, does not change the order’s fulfillment status: the batch is a way of working through orders, not a record of where stock is. ## What Floormode adds Floormode is a warehouse system that runs beside your Shopify store. It keeps its own record of where every unit is, and tells Shopify what changed. That is what the things below rest on. Floormode What it means for you Stock per bin, and a pick route Every unit sits in a [bin] (/features/inventory/bins/). The order of your warehouse layout is the order a picker walks, so a pick list leads from shelf to shelf. Shopify’s pick list can show a bin name; Floormode knows how many units are in each bin. Reserved before it is picked An order’s units are reserved in bins as it arrives. An order that cannot be covered says why, in words (see [Why isn’t this order pickable?] (/features/orders/why-not-pickable/)), before anyone walks to an empty shelf. Scan-confirmed picking and packing Pickers scan the bin and the item; packers scan every item before the parcel can be fulfilled. Each warehouse decides whether a phone without a scanner may confirm by tapping. See [Pack] (/features/fulfillment/pack/). Several warehouses, and routing Each Shopify location you ship from is linked to a warehouse. With [order routing] (/features/settings/automation/) [Elevate plan] (/getting-started/subscription-plans/) rules decide which warehouse or dropship vendor ships an order. Stock moves and counts Putaway, replenish and move tasks on the floor, and [counts] (/features/inventory/counts/) (blind if you like) that go to review before they change a number. Every change is in the [movement history] (/features/inventory/adjustments-and-movements/) with its reason. Receiving with lots and serial numbers Deliveries are booked in by scanning, straight to a shelf or through a dock and inspection. Lot numbers with their dates are recorded at receiving, serial numbers at receiving or at packing as you choose per item, and the lot that expires first is picked first. See [Lots & serial numbers] (/features/inventory/lots/). Returns Customers start a return on a page in your own store. You approve it, grade what comes back, and decide what goes back on sale. An exchange becomes a draft order in Shopify with the customer’s address. See [Returns] (/features/returns/overview/). Floor devices and roles Shared scanners with a PIN or badge, personal phones, a wallboard, and roles that decide who may do what. See [Team, roles & floor devices] (/features/settings/team/). Labels with your own carrier contracts Connect your own accounts with UPS, FedEx, USPS, Royal Mail, Canada Post, DHL, Sendcloud, EasyPost or ShipEngine and more, your own country’s carriers listed first, plus freight carriers, and print on PrintNode printers. You are not tied to the countries Shopify Shipping covers. See [Carriers & packaging] (/features/settings/carriers-and-packaging/). Several Shopify stores, one stock Stores of one business share one warehouse and one team. See [Stores] (/features/settings/stores/). Assemblified and Logistified The sibling apps for kits and production, and for purchasing and logistics, connect to the same warehouse. See [Integrations] (/integrations/overview/). Note Floormode does not replace Shopify. Orders, payments, customers and the storefront stay in Shopify; Floormode reads orders from it and writes back fulfillments and tracking, and, once a warehouse is [live] (/getting-started/go-live/), its stock numbers. ## When Shopify alone is enough Shopify’s batches are a good fit when: - you ship from one location and your team knows where everything is without bin numbers; - you have no lots, expiry dates or serial numbers to trace; - you buy labels through Shopify Shipping in a country where it is available; - one or two people pick and pack, so roles, devices and task lists add nothing; - a stock mistake costs you little, because the shelf is small enough to check by eye. In that case, start with Shopify. You can add Floormode later without changing how your store sells. ## When Floormode earns its place Floormode pays for itself when one of these is true: - Pickers walk to empty shelves, or a parcel goes out with the wrong item: bins, reservations and scans close that gap. - Stock in Shopify drifts from the shelf: counts, putaway and the movement history keep one number for each bin. - You have more than one warehouse or store, or ship some orders from a dropship vendor. - You must trace a lot or a serial number to the orders it went to. - Several people work the floor and you want work handed out, approved and counted per person. - You ship with your own carrier contracts. ## See also - [Why isn’t this order pickable?] (/features/orders/why-not-pickable/): the reasons an order waits, and what to do. - [Subscription plans] (/getting-started/subscription-plans/): what each plan includes. - [Initial setup] (/getting-started/initial-setup/): the first steps after installing. Last updated: 5 November 2026 --- Source: https://docs.floormode.app/getting-started/installation/ # Installation Install Floormode from the Shopify App Store and approve the permission scopes. Floormode is a Shopify app. Install it from the Shopify App Store, approve the permissions, and it opens inside your Shopify admin. ## On this page - Steps - Permissions - In your Shopify admin or on its own - First-time access - Uninstalling - See also ## Steps 1. From the Shopify App Store, search “Floormode”. 2. Click Install. 3. Approve the permission scopes (products, inventory, orders, fulfillment, locations). 4. Floormode opens inside your Shopify admin. ## Permissions Permission Used by Read products Stock, picking, packing, replenishment. Read / write inventory Receiving, counts, adjustments, availability sync. Read orders Orders, allocation, the fulfillment queue. Write fulfillments Packing, shipping, tracking back to Shopify. Read locations Warehouse-to-location mapping. Read / write returns Return requests, returns and return receipts. Nothing is switched on by the install itself. Every feature in this documentation is optional and off until you turn it on, so an existing picking, packing and receiving routine keeps working exactly as before. ## In your Shopify admin or on its own You can open Floormode in two ways: - In your Shopify admin, where most office work happens. - On its own web address, with its own sign-in. This is how floor staff without a Shopify admin account reach Floor Mode on a warehouse tablet: see [Standalone access] (/getting-started/standalone-access/). Both show the same pages and the same data. Only the menu around them changes: in your Shopify admin, Floormode’s pages are listed in the admin’s menu; on its own address, in Floormode’s sidebar. ## First-time access After install you land on Home, where the [setup guide] (/getting-started/setup-guide/) first asks which Shopify locations you pack orders from, then takes each warehouse through its steps: Bins, Stock, Live. Each step is detected from your data; the store import starts by itself on the server, and you can close the page while it runs. Setup works without a plan. New orders are released to the floor once you choose one under Settings → Billing; on a development store, Shopify approves any plan as a free test charge. See [Subscription plans] (/getting-started/subscription-plans/). Caution The step that matters most is linking a warehouse to a Shopify location. Until a warehouse carries that link, availability never syncs and Shopify keeps selling stock you cannot see. ## Uninstalling Uninstalling Floormode deletes your warehouse data at once: warehouses, bins, the stock in them, pick, pack and receiving history, settings, labels and other documents, and the history archive. Nothing is kept for a later reinstall. Reinstalling starts a new, empty setup. Floormode imports your products and orders from Shopify again, and the setup guide starts from the beginning: locations, bins, stock and going live. Your Shopify data stays as it is: products, orders, customers and the stock levels Shopify shows. Caution Before you uninstall, download what you must keep: the history archive’s books under Settings → Customer privacy, and any report or export you need. In an account with more than one store, only the last store’s uninstall deletes the warehouse data. Any other store that uninstalls leaves the account, with its orders and its archived orders, and the warehouse stays with the other stores: see [When a store leaves] (/features/settings/stores/#when-a-store-leaves). ## See also - [Initial setup] (/getting-started/initial-setup/) — what to configure first, in order. - [The setup flow] (/getting-started/setup-guide/) — the guide on Home. - [Subscription plans] (/getting-started/subscription-plans/) — which tier to pick. Last updated: 25 October 2026 --- Source: https://docs.floormode.app/getting-started/initial-setup/ # Initial setup Choose your warehouse, organize bins and stock, go live, then prepare your first shipment. A warehouse map is optional. Start Floormode with one warehouse and a few clearly named bins. You can add more locations, a detailed layout and automation as your team needs them. The [setup flow on Home] (/getting-started/setup-guide/) keeps track as you work. ## Connect your Shopify locations Your Shopify locations describe where your store holds stock. A Floormode warehouse connects one of those locations to its bins, stock and operating settings. The import starts by itself when you first open the app; its progress sits on the one line above the setup guide on Home. You do not wait for it to finish before choosing a warehouse. 1. Choose your warehouse. On Home, tick the Shopify location your team ships from and choose Set up with its name. Floormode creates the warehouse for it; no warehouse is created from a location by itself. 2. Other locations. Add Shopify locations under the guide’s list offers the locations that are not warehouses yet. Tick each site you operate. 3. To use a warehouse you already created, open it under Settings → Warehouses and change its location link on its Details tab instead. New warehouse also supports sites without a Shopify location, such as a staging area. Already set up in Shopify? Keep your existing Shopify locations. The warehouse link connects Floormode to them; adding a warehouse does not create a new Shopify location. Check the location name carefully if you also have retail stores or third-party fulfillment locations. An unlinked warehouse cannot keep Shopify’s quantities updated, and orders Shopify assigns to a location without a warehouse never reach the pick queue. After the first import, Shopify updates continue automatically. You can run another import from Home when needed; importing store data alone does not book physical stock into bins. ## Your country, your units Floormode reads your store’s country, time zone and units from Shopify, so a store in the US, Australia, the UK or Germany starts on its own ways with nothing to set: What Follows For example Time zone: a warehouse’s days, lot expiry and shifts Your store’s, on every warehouse, until you set a warehouse’s own on its Details tab Australia/Sydney The night’s work and the accounting months One time zone for the account: your oldest warehouse’s; the accounting months keep the zone they were first counted in Australia/Sydney Weights and lengths Your store’s unit system lb, oz and in in the US; g, kg and mm in a metric store Paper for slips and label sheets Where the warehouse is (label sheets: your store’s country) US Letter in the US, Canada, Mexico and Puerto Rico; A4 elsewhere Carriers offered first Your store’s country USPS in the US, Royal Mail in the UK, DHL Paket in Germany Customs Where the parcel ships from A US parcel to another state needs no declaration; one to Canada does Accounting export: the chart a first setup starts on Your store’s country Xero in the UK, Australia, New Zealand and the US; SKR03 with DATEV in Germany and Austria; every chart stays on the list Rules of one country appear only there: the works council (BetrVG) in Germany, the GDPR’s impact assessment in the EEA and the UK. The German charts and the DATEV file are listed first in Germany and Austria and last elsewhere. See [Shipping → International] (/features/fulfillment/shipping/#international) for customs. ## Organize bins and stock ### Start with named bins On the warehouse page, Add 4 bins creates a starter set in one click. To build your own, use the Layout tab and add the places stock can sit, such as A-01, A-02 or SHELF-01. The layout’s order is the pick route, the order your team visits the bins. You can run a small warehouse with flat bins and no aisle hierarchy. A [bin] (/reference/glossary/#bin) holds stock. Zones, aisles, bays and levels organize bins; they are not destinations for receiving goods. ### Add a map if it helps The 2D map is optional. Bins, receiving and picking work without drawing a floor plan or placing bins on a map. For a larger site, organize the hierarchy on the warehouse’s Layout tab, then open its map to represent the floor. Add the map later if your first priority is getting stock into bins. ### Put your Shopify stock on shelves The Stock tab on the warehouse page first asks Where is your stock today?, then Import into your warehouse reads the quantities Shopify holds at the warehouse’s location and books them into the unassigned bin. Orders can be picked from there. Give items their own bins before or after going live, on the same tab or with Put away. - Existing stock in Shopify: import it here. Check the warehouse’s Shopify location link first. - No stock in Shopify yet: there is nothing to import, and the step reads No stock in Shopify. Add stock in Shopify and the step comes back, or go live and receive goods as they arrive. Importing does not delete or change Shopify quantities. Avoid recording the same opening balance both as an import and as a new receipt. ### Review warehouse settings Open Settings → Warehouses and your warehouse to check the policies that affect your operation, including overselling, payment capture, receiving tolerance and packing quality checks. Leave advanced rules for later unless your workflow requires them. [Warehouse settings reference] (/features/settings/warehouses/). ## Prepare your first shipment 1. Add your packaging under Settings → Shipping & carriers. Enter the box sizes your team actually uses. 2. Connect a carrier from Shipping so packed orders can receive shipping labels. 3. Choose how to print labels. Connect PrintNode for direct printing, or skip this step to download label PDFs. 4. Go live. Go live on the warehouse page checks Shopify’s quantities against the warehouse; when they match, orders for its location flow through Floormode and it keeps Shopify’s quantities updated. See [Go live] (/getting-started/go-live/). 5. Choose a plan under Settings → Billing. Setup works without one, but new orders are released to the floor only with a plan. On a development store, Shopify approves any plan as a free test charge. Review your first order before releasing it: the correct warehouse, available stock, packaging and carrier should be in place. Finishing the setup steps confirms their checks; it does not release an order or buy a label. ## Continue when you are ready You can leave setup and use the rest of the app at any time. Hide setup folds the guide into one line on Home; Continue setup brings it back. Completed steps are detected from your saved configuration. - [The setup guide] (/getting-started/setup-guide/) - [Bins] (/features/inventory/bins/) - [Carriers & packaging] (/features/settings/carriers-and-packaging/) - [Finding your way around] (/getting-started/finding-your-way-around/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/getting-started/compatible-hardware/ # Compatible hardware Barcode scanners, label printers, labels, a shipping scale and the devices that work with Floormode, and what each one needs. Floormode runs in the browser, so you don’t need special hardware to start. A phone camera scans, and labels download as PDFs. The devices below make the warehouse faster. For each kind, this page says what Floormode needs, then names one device we know fits. Affiliate links The product links on this page are affiliate links: as an Amazon Associate, P&H Cloud Solutions earns from qualifying purchases. The price you pay is the same. Any device that meets the requirements works just as well. ## Barcode scanners Floormode treats a scanner like a very fast keyboard. Any scanner that types what it reads works: keyboard mode (HID), which most scanners use out of the box. Choose a 2D scanner: it reads the codes on items, bins and labels (EAN, UPC, Code 128, Code 39, QR and Data Matrix). - At the pack station: a corded USB scanner. It needs no pairing and never runs flat. Our pick: [Tera D5100Y] (https://link.amazon/B03WglCi5) - On the floor: a cordless Bluetooth scanner, paired with the phone or tablet that runs [Floor Mode] (/features/floor/overview/). Our pick: [Tera HW0009] (https://link.amazon/B037zA2aS) No scanner yet? Every scan field also has [Scan with camera] (/features/floor/overview/#scanning-with-the-phone-camera). ## Label printer Shipping labels come as 4 × 6 in (100 × 150 mm) thermal labels (ZPL) or as a PDF. With [PrintNode] (/features/settings/carriers-and-packaging/) connected, a bought label prints straight at the station. Any 4 × 6 thermal printer with a Windows or macOS driver works through PrintNode. A ZPL printer, such as a Zebra, takes the ZPL label directly. The same printer prints your [bin labels] (/features/inventory/bins/). Our pick: [Phomemo PM241-BT] (https://link.amazon/B0bM21VGe) (100 × 150 mm, direct thermal, USB, drivers for Windows and macOS) ## Labels Use 100 × 150 mm direct-thermal labels on a roll or fanfold that fits your printer. Direct thermal needs no ink or ribbon. Our pick: [Labelident 100 × 150 mm thermal labels] (https://link.amazon/B0da08dLE) ## Shipping scale The [pack station] (/features/fulfillment/pack/) reads the parcel’s weight from a USB scale in Chrome or Edge. Use a standard shipping scale, such as a Dymo M-series or a Mettler PS-series. Choose it once with Connect scale, and a steady reading fills the weight by itself. Our pick: [DYMO M10] (https://link.amazon/B05d9EQcX) ## Phones and tablets for the floor Floor Mode runs on any current phone or tablet in the browser, and you can [install it like an app] (/features/floor/overview/#install-it-on-the-phone-or-tablet). A tablet gives pickers and packers a bigger screen, and a cordless scanner pairs with it. Our pick: [Apple iPad] (https://link.amazon/B0j4L0xSL) ## Computers for the office and the pack station Any current computer with Chrome or Edge runs the app and the pack station. The browser is what matters, because the scale connects through it. Our pick: [Apple MacBook Air] (https://link.amazon/B0eEbon1H) ## See also - [Floor Mode] (/features/floor/overview/) - [Packing] (/features/fulfillment/pack/) - [Carriers & packaging] (/features/settings/carriers-and-packaging/) - [Initial setup] (/getting-started/initial-setup/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 19 October 2026 --- Source: https://docs.floormode.app/getting-started/setup-guide/ # The setup flow Home lists each warehouse in setup with its next step; the warehouse page does the work, from a Shopify location to a warehouse that keeps Shopify's numbers up to date. Until your first Floormode warehouse is live, Home is the setup guide, Your warehouses. Setup belongs to each warehouse: the guide lists every warehouse that is not live yet with its next step, and the warehouse page does the work. The store import runs by itself on the server and is reported in one line above the guide; you can close the page while it runs. ## The first decision: your Shopify locations The guide starts by asking Which Shopify locations do you pack orders from? Locations that fulfil online orders and hold stock come first as suggestions; stores, pickup points and other places fold under Other locations. Nothing is ticked for you. Tick the location your team ships from and choose Set up with its name. Floormode creates a warehouse for each ticked location and names it after it. Later, Add Shopify locations under the list opens the same choice for the locations that are not warehouses yet. ## The steps of a warehouse Each warehouse row shows its steps and one button for the next one: Step What you do Link a Shopify location Only for a warehouse without a location: choose it on the warehouse’s Details tab. Bins Add bins opens the warehouse. Add 4 bins creates a starter set in one click, or build your own on the Layout tab. Stock Import stock opens the warehouse’s Stock tab. Import into your warehouse copies what Shopify has on hand at the location into the unassigned bin. Shopify is not changed. Live Review and go live opens the warehouse page, where Go live checks Shopify’s quantities and then keeps them up to date for that location. See [Go live] (/getting-started/go-live/). Every step is detected from your data each time the page reads it: nothing is ticked by hand, and another person who opens the warehouse sees the same step. Imported stock waits in the unassigned bin, and orders can be picked from there. Giving items their own bins is not a step: do it before or after going live, on the Stock tab or with Put away. No stock in Shopify yet? If Shopify holds no stock at the location, there is nothing to import: the step reads No stock in Shopify instead of a tick, and the warehouse goes on to Live. Add stock in Shopify and the Stock step comes back; or go live and bring stock in through receiving. ## Your plan Setup works without a plan, but new orders are released to the floor only once you have one. Until then the guide’s plan line says so. Once Shopify has confirmed that the store has no active plan, it reads Confirm Essential or a higher plan to release new orders. Existing fulfillment work continues., naming the plan that fits your order volume, with Review plan & allowance. Before that it reads Setup works without a plan. New orders are released once you choose one., with Choose a plan. Both open Settings → Billing. The go-live step shows it again. On a development store, Shopify approves any plan as a free test charge. See [Subscription plans] (/getting-started/subscription-plans/). ## Hide setup Hide setup folds the guide into one line on Home that counts the warehouses still in setup; Continue setup brings it back. Setup never blocks the rest of the app. ## After you are live When a warehouse goes live, its page says so once, with Go to Home. Home then shows your work: the open work per operation, what needs attention and recent activity, with the guide above it while other warehouses are still in setup. Packaging, a carrier, a printer and your team are optional and live under Settings. ## If the import needs attention A stuck or failed import shows Retry import on the import line. If Shopify withholds protected customer details, the guide says which details are hidden; the import still finishes. ## See also - [Initial setup] (/getting-started/initial-setup/) - [Go live] (/getting-started/go-live/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/getting-started/go-live/ # Go live What going live does, what to check first, and what to do when Floormode's numbers differ from Shopify's. Going live is the last setup step for a warehouse: from then on Floormode keeps Shopify’s quantities for that location up to date. It is one click on the warehouse’s page; Review and go live on Home leads there. ## On this page - What going live does - Before you start - Run Go live - When items differ from Shopify - Items Floormode can’t check yet - Locations Logistified passed to Floormode - See also ## What going live does Floormode reads Shopify’s current quantities for the location, compares them with what is on your shelves, and, when they match, starts updating Shopify from every receipt, pick, count and adjustment. Until a warehouse is live, nothing you do in Floormode changes a Shopify number. ## Before you start - The warehouse is linked to the Shopify location you pack from. - Its opening stock is imported (Import into on the warehouse’s Stock tab). Items can wait in the unassigned bin; giving them their own bins is not required. If Shopify holds no stock at the location, the step reads No stock in Shopify and there is nothing to import. - If Logistified is going to be connected, every receiving warehouse must be live first: the Logistified switch refuses otherwise. ## Run Go live 1. Open Settings → Warehouses and the warehouse, or choose Review and go live on Home. 2. Click Go live and confirm. Floormode checks Shopify’s quantities against the warehouse. 3. Read the result. The warehouse page says the warehouse is live when the numbers matched and Shopify is now updated from Floormode. A list of items that differ from Shopify means some items need a look first. ## When items differ from Shopify The check lists each item whose Shopify quantity does not match the shelf, with both numbers. Fix the side that is wrong: count the bin in Floormode, or correct the quantity in Shopify. Then click Check again on the warehouse page. Going live never overwrites Shopify with a number nobody checked: either the numbers match, or you confirm your counts (below). ### You counted during setup Shopify does not hear about the counts you make in Floormode before the warehouse is live. After the opening import, give the stock its shelves, then count. When every difference comes from counts or adjustments made after the import finished, the check lists them as Shopify 5 → counted 7, and the button reads Set Shopify to your counts at your location. Floormode cannot tell whether anything was sold or shipped outside Floormode between your count and now, so you decide. Confirm only if nothing was. Floormode then goes live and sends each count to Shopify. Shopify takes a count only while its on-hand number is still the one the check read, so nothing that changes in between is overwritten. Orders placed meanwhile stay reserved. A count Shopify refuses is not sent again: the item asks for a new count under Shopify synchronization on its stock page. Your confirmation covers the whole list and the location, even when the confirm shows only part of a long list. If someone counts again, Shopify’s number changes, or the warehouse is linked to another location before you confirm, the check shows the new list and asks once more. Items marked with a count in a longer list wait until nothing else blocks. Counts are not offered for: - an item counted before the opening import finished, even when the count was approved later; - an item with units still in the unassigned bin (give them a shelf first, then count); - an item Shopify still expects on an open transfer or purchase order (receive or cancel it in Shopify first); - an item Assemblified sets in Shopify. ## Items Floormode can’t check yet Some items are skipped by the opening import with a reason (a bundle whose stock sits on the bundle itself, an item Shopify does not track, an inventory item with inconsistent states). They are listed under Inventory → Stock → Item setup and recovery with a next step. Go live waits until they are fixed or excluded. ## Locations Logistified passed to Floormode When Logistified hands receiving for a location to Floormode, that location’s warehouse must be live before the handover takes effect. The Integrations card lists such warehouses with a Go live link. ## See also - [The setup flow] (/getting-started/setup-guide/) - [Warehouses] (/features/settings/warehouses/) - [Who updates Shopify] (/integrations/who-writes-shopify/) Last updated: 22 October 2026 --- Source: https://docs.floormode.app/getting-started/finding-your-way-around/ # Finding your way around The eight places in Floormode, what lives inside each, and how tabs and sub-pages fit together. Floormode has eight places. Everything else is a tab or a sub-page inside one of them. Learn this table and you can find anything. ## On this page - The eight nav entries - Home is not a nav entry - Tabs, sub-pages and Advanced - Settings is the odd one out - See also ## The eight nav entries Nav entry Route What is inside Orders /orders One order list with saved views Fulfillment /fulfillment Queue · Batches · Pack · Shipping · Production · Waves Inventory /inventory Stock · Receiving · Counts · Movements · Lots · Serials · Transfers · Bins · Placement Returns /returns Requests · Shopify returns · Receipts Insights /insights Reports · Replenishment · Stock value · Alerts Team /team Today · Plan · Output · Shifts · Time Settings /settings Twelve sections in three groups: Operations, Customers, Account Floor Mode /floor The scanner screen for the warehouse floor Floor Mode sits last on purpose: it leaves the admin chrome behind. Opening it replaces the whole shell with the full-screen scanner surface. ## Home is not a nav entry Home (/) is reached by clicking the app name, the way every Shopify app works. It does not take one of the nav slots. ## Tabs, sub-pages and Advanced Clicking a nav entry never shows a page of its own — it lands on that section’s first tab. /inventory takes you to /inventory/stock, /fulfillment to /fulfillment/queue. Two tabs are marked Advanced: Waves (/fulfillment/waves) and Placement (/inventory/placement). They are fully visible and fully usable — the label just says “most warehouses never need to touch this”. Detail pages (an order, a pick batch, a receipt, a count task) are not tabs. They keep their section’s nav entry highlighted and get a breadcrumb instead. Note Every tab and sub-page has a real URL. A support hand-off is always just a link — there is no state hidden behind an in-page tab that a URL cannot reach. ## Settings is the odd one out Settings is the one entry whose children are not a tab strip. It renders a sidebar-within-the-page with thirteen sections in three groups — Operations (from Warehouses to Returns), Customers (Customer emails, Customer privacy) and Account (Apps & API, Stores, Team & devices, Billing) — each breadcrumbed. A URL that matches nothing shows a proper “Page not found” with a link home, rather than quietly dropping you on the dashboard. ## See also - [Plain-English names] (/getting-started/plain-english-names/) — the warehouse jargon we translated. - [Search everything] (/getting-started/search/) — ⌘K from anywhere. - [URL map] (/reference/url-map/) — where every old link now lands. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/getting-started/lists-and-views/ # Lists, filters and saved views How every list in Floormode works: filters, sort, columns, saved views and export. Every big list in Floormode works the same way: Orders, Merge groups, Shipping, Receiving, Transfers, Stock, Pack, Batches, Release, Return requests, Movements, Counts, Returns, Return receipts, the Exceptions tab of Shipping, Alerts, Bins, the pick Queue with its Other floor work, and Production. ## On this page - What a view is - Switching views - Changing what you see - Saving a view - Links and the Back button - Export - Describe a view - Pages - Ticking rows - When a list is empty - Every list at a glance - See also ## What a view is A view is a named way to look at the list: which filters are on, in what order the rows come, and which columns show. - Presets come with the app. Every shop has them. They cannot be changed or deleted. - Saved views are yours or your shop’s. ## Switching views The View button at the start of the list’s toolbar names the view you are on. A star on it says this is the view the list opens with for you. Click it to open the view switcher: - The presets come first, then the saved views. A saved view says who sees it: Shared (everyone in this shop) or Only you. On Orders the same answer sits under the page title while the saved view is open. - A check mark sits on the view you are on, a star on your default. - The search box has the focus: type to find a view by name. The arrow keys move through the views, Enter opens one, Esc closes the switcher. The actions for the view you are on sit beside the views, each where it applies: Save view, Save as new view…, Edit view…, Set as my default or Clear my default, and Reset. They live only here. ## Changing what you see Change the filters, the Sort (where a list offers more than one order) or the Columns. The list follows at once. Unsaved changes on the View button says the view now differs from what it saved. Reset in the view switcher appears while a view is edited. It puts filters, sort and columns back to what the view saved. Columns opens the list’s columns. Tick what you want to see. A list keeps at least one column. ## Saving a view Open the view switcher: - Save view (⌘S, Ctrl S on Windows) stores what the list shows now in the saved view you are on, under the same name and for the same people. It appears once a saved view is edited. Presets cannot be overwritten; save them as a new view instead. - Save as new view… stores the current search, filters, sort and columns as a new view. - Edit view… renames the saved view you are on, changes who sees it or deletes it. It also saves what the list shows now. The dialog asks for a View name. Tick Share with everyone in this shop to make it a shop view. Otherwise only you see it. A shared view belongs to everyone. Anyone in the shop can edit or delete it. Saving over a shared view asks first: it replaces the filters for the whole shop and cannot be undone. Delete view sits in the edit dialog and asks too. If a colleague changed the view since you started editing it, the save is refused and says so. Look at the view again and save once more. Set as my default makes the view you are on the one the list opens with for you; Clear my default goes back to the list’s own default. Nobody else’s default changes. A link to a view that no longer exists shows the default list and says so. A view that asks for a sort or a column the list no longer has still opens; the list tells you what it left out. ## Links and the Back button The address of the page carries the view, the filters, the sort and the page you are on. Copy the link and a colleague lands on the same list. The browser’s Back button returns to the list exactly as you left it. An order, a receipt or a transfer opened from its list also remembers the list: the page’s own way back returns to the same view, filters, sort and page. ## Export Export downloads the rows on screen with the visible columns, as Download CSV or Download XLSX. The file is named after the list and the view. When more rows match than are on screen, the entries read “(loaded rows only)”. The file name then ends in “-partial” and its first row says what is missing. Most lists also offer Export matching rows as CSV… and as XLSX…. This walks the whole view as it is now: up to 10,000 rows within 60 seconds. A larger view comes out partial and says so. You can cancel; then no file is written. Export matching rows is offered on every list except Orders, Bins, Production and Checkout options. Transfers offer it only under Newest first, not under Recently changed. ## Describe a view Every list has Describe a view in its toolbar. While suggestions are unavailable, the button is hidden. Type what the list should show, for example “items from Shopify”. Choose Suggest filters. The app proposes filters and names the words it could not use. Apply filters sets them as a draft. Nothing is saved until you save a view. The app may answer that it could not turn the sentence into filters, or that the list already shows this. ## Pages Every list except Production and Checkout options pages. The footer counts the rows on the page, shows the page number and has Previous page and Next page. Changing the view, a filter or the sort returns you to page one. If the list changed so much that your page no longer exists, the footer says “This page is out of date.” and offers Restart at page one. Rows per page sits in the footer of Orders (10, 25 or 50; 25 until you choose), Receiving and Stock (10, 20 or 50; 20 until you choose). The choice is yours alone: Floormode keeps it for you on that list, and colleagues keep their own. A new choice starts at page one. The other lists show a fixed number of rows. Production is one page, soonest due first. When more work orders exist than fit, a notice says so. Its tab under Fulfillment shows once Assemblified is connected. Checkout options are one page too, needs review first; a row you map keeps its place until you change the view or a filter. ## Ticking rows Orders, the Queue, Stock and Bins let you tick rows for an action: Hold, Release hold and Merge on Orders, Create batch in the Queue, Print labels on Stock and Bins. Your ticks stay when you turn the page, so one action can cover rows from several pages. Each list has a limit: 500 orders on Orders, 20 orders for one batch in the Queue, 200 items or bins for one label batch. Changing the view, a filter, the sort or the warehouse clears the ticks. ## When a list is empty An empty list says why and offers one way out: - You changed the filters and nothing matches: Clear filters puts the view back as it was saved. - Another view shows nothing: Show and the name of the list’s default view, for example Show All open on Orders, opens that view. - The default view itself is empty: the list’s own first step, for example Finish setting up on Orders or New receipt on Receiving. - A later page is empty because its rows moved on: Go back a page. - On a very long list a page can come back empty while more rows exist further on. The message says so; narrow the filters or use Next page. ## Every list at a glance Filters show their “all” choice until you pick something. Where a list has one order only, no Sort control appears. List Presets Filters Sort Orders All open · Ready to ship · Blocked · Backordered · Pickup & delivery · Pack today (with [delivery dates] (/features/settings/delivery-dates/) on) Search orders · Fulfillment status · Delivery · Filters (Placed · Ship-to country · Stock reservation · Hold reason · Hold state · Risk level · Order tag · Pack day, with delivery dates on) Newest first · Oldest first Orders → Merge groups Open · Finished · All groups Group status Newest first · Oldest first Fulfillment → Queue All orders · Single-item · Late · Mine · Unassigned (the last two only while pick work is assigned) Order filter (All orders · Single-item orders) · Age filter (Any age · Late only) · Assignment filter (Assigned to me · Unassigned) Oldest first · Newest first Queue → Other floor work Open · Mine · Unassigned · All Task type · Task status · Task assignment Oldest first · Newest first Fulfillment → Batches Open · Components · All batches Batch status · Picking for (Customer orders · Work orders) Newest first · Oldest first Fulfillment → Pack Open jobs · Every job Pack job status · Warehouse Newest first · Oldest first Fulfillment → Shipping All shipments · To buy · In transit · Exceptions Search · Shipment status Newest first · Oldest first Shipping → Exceptions Open · Resolved · All Status · Reason Newest first · Oldest first Fulfillment → Production In flight · Finished · All work orders Stage Soonest due Fulfillment → Release All releases · Planned · On the floor · Closed Release status Newest first · Oldest first Inventory → Stock All items · Shopify · Assemblified (raw material) · Assemblified (sub-assembly) · Logistified (custom item) Search · Item source By item Inventory → Receiving Open · Expected · Receiving · Received · Cancelled · All receipts Status · Warehouse · Source Newest first · Oldest first Inventory → Counts All counts · Waiting for approval · On the floor Status Newest first · Oldest first Inventory → Movements All movements · Adjustments · This week Movement · Reason · When · Item · Bin Newest first · Oldest first Inventory → Lots All lots Search (the lot number’s start) · Item Lot A–Z · Lot Z–A Inventory → Bins All bins · Empty · Flagged · Not sellable · Archived Search · Zone · Bin type · Level · State · Occupancy · Sellable · Pickable · Flagged By code · Pick route Inventory → Transfers Open · Needs attention · Completed · All transfers Transfer warehouse · Transfer direction · Transfer status · Channel update Newest first · Recently changed Returns → Requests All requests · Longest waiting · To settle Return request status Newest first · Longest waiting first Returns → Returns All returns · Without a completed receipt · Open on Shopify Return status · Receipt (Any receipt · Without a completed receipt) Most recently added here · First added here Returns → Receipts All receipts · Being received Receipt status Newest first · Oldest first Insights → Alerts Open alerts · Urgent · Needs attention · This week · Resolved too Severity · Alert type · Raised · Status (Open · Open and resolved) Newest first · Oldest first Settings → Shipping & carriers → Checkout options All options · Needs review · Mapped · Rules decide Search · Status · Source · Seen Needs review first The warehouse on Queue, Batches, Release, Counts and Bins is the page’s scope. It is not part of a view. A view saved there applies to whichever warehouse you are looking at. Alerts lists the open alerts. An oversell risk or a backorder resolves by itself when its order’s stock is reserved, or when the order ships or is cancelled. A newer alert about the same shortage replaces the older one. Resolved too lists the resolved alerts as well, each with when and why it resolved: restocked, order changed, order fulfilled, order cancelled, order closed, or replaced by a newer alert. On Return requests the last column is headed Actions: each request’s next step, such as Approve, Pay out or Decline. The Queue’s actions and the Receive column on Returns are headed the same way. ## See also - [View tabs] (/features/orders/view-tabs/) - [Finding your way around] (/getting-started/finding-your-way-around/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/getting-started/plain-english-names/ # Plain-English names The warehouse jargon Floormode translates, the industry terms it keeps, and why. Warehouse software is full of words nobody says out loud. Where a plain-English name exists and loses nothing, Floormode uses it. ## On this page - What we renamed - What we kept - Statuses read as sentences - See also ## What we renamed Industry term What you see Slotting Placement Inbound Receiving RMA Return request Blind return, unauthorised return Unexpected return (a parcel no return announced) WISMO Customer emails ATP Available to promise Topology Layout (a warehouse’s bins in pick order) Old links still work and land you in the right tab — see the [URL map] (/reference/url-map/). ## What we kept Some terms are precise and have no honest short translation, and some are the words every warehouse system uses, so a team that worked in one reads Floormode at once (owner decision, 2026-11-08: read like the big warehouse systems). Those stay, and carry a small ⓘ with a one-sentence explanation the first time they appear on a page: - [Blind count] (/reference/glossary/#blind-count) - [FEFO] (/reference/glossary/#fefo) (expiry-first picking) - [Cluster picking] (/reference/glossary/#cluster-picking) (some software says multi-order picking) - [Waves] (/reference/glossary/#waves) (Floormode used to say “release”; you still Release wave) - [Putaway] (/reference/glossary/#putaway) (the process; the task’s verb is Put away) - [Replenishment] (/reference/glossary/#replenishment) (topping up pick bins from reserve stock) - [Cycle count] (/reference/glossary/#cycle-count) Note Renaming a concept you actually need is worse than teaching it. A wave, a putaway or a cycle count is what a team calls it in every warehouse system, so Floormode says the same word; a plain name only replaces jargon nobody says out loud. ## Statuses read as sentences The same rule applies inside every list. Statuses are shown as words a merchant can repeat to a customer, not as codes: Instead of You see payment_pending Waiting for payment awaiting_production Waiting for production address_issue Address problem short (allocation) Not enough stock allocated Reserved verifying (pack job) Scanning items restock (disposition) Back to sellable stock ## See also - [Finding your way around] (/getting-started/finding-your-way-around/) — the eight-entry map. - [Glossary] (/reference/glossary/) — every term, one sentence each. - [Waves] (/features/fulfillment/waves/) — holding picking work back and releasing it together. Last updated: 22 October 2026 --- Source: https://docs.floormode.app/getting-started/search/ # Search everything Search orders, products, lots, serial numbers, shipments and returns, and jump to any page, from one box. Click Search in Floormode’s header. One box searches eight kinds of record, the app’s pages and settings by name, and this guide, and takes you straight to the result. In standalone Floormode, press ⌘K (Ctrl K on Windows). Inside Shopify, use Alt+Shift+K (Option+Shift+K on Mac) while focus is in Floormode. Shopify keeps ⌘K/Ctrl K for its own Admin search. You can always reach the Floormode Search button with Tab and press Enter. ## On this page - What it searches - How to use it - Why Floor Mode has no search - See also ## What it searches Kind Typical thing you type Orders Order number, customer name Products & SKUs SKU, product or variant title, barcode Shipments Tracking number Returns The return Shopify announced Return requests A customer’s request from the returns page Return receipts What actually arrived back Lots A lot or batch number, or its start Serial numbers A unit’s serial number Pages A page’s name, such as “Receiving” or “Billing” Settings A setting’s name or what it does, such as “approval limit” or “pack checklist” From the guide A question in this guide’s words, such as “blind count” or “return label” Results are grouped by kind, and picking one opens that record, its page or its panel, rather than a filtered list you then have to read. A return request opens the Requests list, which says so on the result. Pages and settings show at once. Records follow, and From the guide comes last, under them, so nothing you are looking at moves. A guide result opens the section of this guide in a new tab. From the guide finds sections in this guide’s own words as you type. Its first row, Search docs for “…”, searches the whole guide with exactly the words it shows, in any language, but only when you choose it. Numbers, codes and e-mail addresses are left out of those words. Its sections replace the ones under the row. ## How to use it Start typing. There is no “search in” selector and no advanced syntax to learn; the box looks in every kind at once and ranks what it finds. If you already know the exact identifier, type it — an order number or a tracking number lands on the record directly. ## Why Floor Mode has no search Floor Mode deliberately has no search box and no keyboard shortcut. A scanner gun is a keyboard: it types fast and it presses keys nobody chose. If ⌘K worked on the floor, a barcode scan mid-pick could open a search overlay and swallow the rest of the scan. Caution This is a safety property, not an oversight. On the floor the screen is the job in front of you, plus the ⋯ menu for the task and the device. ## See also - [Floor Mode overview] (/features/floor/overview/) — the scanner-first surface. - [Finding your way around] (/getting-started/finding-your-way-around/) — where things live when you’d rather browse. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/getting-started/standalone-access/ # Standalone access & your team Use Floormode in a normal browser tab outside the Shopify admin, and bring in warehouse staff who have no Shopify login. Floormode runs in two places: embedded inside your Shopify admin, and standalone in a normal browser tab. Standalone access is made for the people who work in the app all day but have no reason to hold a Shopify staff account: pickers, packers, receivers. ## On this page - How standalone access works - Your company and your stores - Bringing in your team - Roles - Signing in - See also ## How standalone access works When you install Floormode, it sets up your company, with P&H accounts as the sign-in outside Shopify, or connects the company you already run on the P&H platform. Where an invitation is needed, the first person to open Floormode from the Shopify admin, normally the store owner, gets one by email; accept it once, and you can sign in at the app’s own web address with an email and password (or single sign-on), no Shopify login involved. Both doors lead to the same app and the same data. There is nothing to keep in sync and no separate “standalone version”: a pick recorded in a browser tab shows up in the embedded app at once, and the other way round. ## Your company and your stores Everyone you bring in joins your company’s team and works in your warehouses: orders, inventory, floor work. One account can hold several Shopify stores; see [Stores] (/features/settings/stores/). Someone who signs in without belonging to a company sees a screen saying so instead of data, never someone else’s warehouse. Someone whose sign-in has no Floormode role yet sees You have no Floormode role yet until an Admin gives them one. ## Bringing in your team 1. Open Settings → Team & devices. 2. For someone who works only on the floor, choose Add floor person: they need no email, just a PIN or a badge. 3. For someone who should sign in with an email, choose Invite, pick their role and warehouses, and send it. Inviting needs your own P&H account. 4. Once they accept, they sign in directly: no Shopify account needed. Shopify staff who open Floormode from the Shopify admin are on the team too, with the role set under Settings → Team & devices → Defaults. The team always keeps at least one active Admin, so it can never lock itself out. ## Roles - Admin: everything, including integrations, customer data requests, billing, the API, stores and roles. - Manager: all the desk work and settings except those six; adds and invites people as Floor. - Floor: Floor Mode only (pick, pack, receive, count and move stock). Admins can also make roles of their own, such as a lead who approves floor exceptions. A person’s warehouses decide where they work on the floor, not what they see at the desk. [Team, roles & floor devices] (/features/settings/team/) has the details, including floor devices, PINs and badges. ## Signing in Embedded: open Floormode from your Shopify admin’s Apps section, as always. Standalone: visit the app’s web address and sign in with the email your invitation was sent to. If your company uses single sign-on, the same screen offers it. Floor people sign in on a [floor device] (/features/settings/team/#floor-devices) with their PIN or badge. Note Standalone access is included on every plan. If you only ever use Floormode inside Shopify, you can ignore it entirely: nothing changes for you. ## See also - [Team, roles & floor devices] (/features/settings/team/) - [Installation] (/getting-started/installation/) - [Finding your way around] (/getting-started/finding-your-way-around/) Last updated: 25 October 2026 --- Source: https://docs.floormode.app/getting-started/subscription-plans/ # Subscription plans The four tiers — Essential, Elevate, Enhanced and Enterprise — and exactly which features each one unlocks. Floormode has four tiers, set under Settings → Billing (/settings/billing). Almost everything in this documentation is on Essential; only five features need a higher tier. ## On this page - The four tiers - Choosing a plan - What each tier unlocks - How orders count and what happens at the limit - What happens if payment fails - See also ## The four tiers All plans are billed monthly through Shopify and start with a 14-day free trial. Tier Price Orders / month For Essential $20/mo up to 300 The full WMS + OMS: orders, picking, packing, receiving, counts, returns, inventory and FEFO allocation. Elevate $49/mo up to 1,500 Everything in Essential plus the automation rules engine, pick profiles, reports and stock value. Enhanced $99/mo up to 5,000 Everything in Elevate plus cluster picking. Enterprise $199/mo up to 40,000 Everything in Enhanced plus the external REST + MCP API, outgoing webhooks and priority support. ## Choosing a plan Setup works without a plan: you can link locations, add bins, import stock and go live. New orders are released to the floor once Shopify confirms a plan. Choose one under Settings → Billing; Shopify shows the plan and asks you to approve it. On a development store, Shopify approves any plan as a free test charge. ## What each tier unlocks Five features need a tier above Essential. If a feature is not in this table, it is on every tier. Feature Minimum tier Where Automation rules Elevate [Automation] (/features/settings/automation/) Analytics: reports, stock value and team targets Elevate [Reports] (/features/insights/reports/), [Stock value] (/features/insights/stock-value/) Pick profiles Elevate [Fulfillment settings] (/features/settings/fulfillment/) Cluster picking Enhanced [Cluster picking] (/features/fulfillment/cluster-picking/) External REST + MCP API, outgoing webhooks Enterprise [REST API] (/rest-api/overview/), [Webhooks] (/integrations/webhooks/) Note “Cluster picking” is the industry’s name for picking several orders in one walk, each in its own slot on the cart; some software calls it multi-order picking. Everything else — the order queue, holds, splits and merges, the fulfillment queue, pick batches, scan-verified packing, carrier rates and labels, freight, receiving, cycle counts, adjustments, the movement ledger, bins, placement, returns and the order and returns pages in your store, replenishment, FEFO (expiry-first) allocation and all of Floor Mode — is on Essential. ## How orders count and what happens at the limit The allowance follows your confirmed Shopify billing cycle, not a calendar month. An order counts once when Floormode first releases it for fulfillment: picking, dispatch to a dropship vendor, or a direct shipping-label purchase or freight booking. Importing an order, reserving stock, preparing a shipment or requesting a rate does not count. Open older orders count when first released for work. Edits, discounts, split shipments and repeat processing do not count the same order again. Historical imports, draft orders and test orders do not consume the allowance. A cancellation before release does not count; a return after release does not undo work already counted. Work started before allowance tracking was introduced continues without a retrospective count. On Essential, Elevate and Enhanced, Floormode shows a warning at 80% of the allowance. If you exceed the allowance, new releases can continue until the current billing cycle ends. After that grace period, confirm the indicated plan or a higher plan in Shopify to release new orders. Existing fulfillment work, imports, inventory operations and synchronization continue. Changing the calendar month does not erase an unresolved upgrade requirement. No plan has per-order fees, and there are no automatic paid upgrades: Shopify asks you to confirm a plan change. Enterprise is listed for up to 40,000 orders a month; Floormode shows no warning and holds no order for an Enterprise store’s volume. The billing page shows the last verified plan, cycle and any grace deadline. While Shopify has not provided the current cycle, Floormode does not display an invented usage period. Trial work before the first paid cycle is not carried into that cycle’s allowance. ## What happens if payment fails Only an active subscription grants the paid feature tier. When Shopify confirms that no active subscription remains, releasing new orders also requires an active plan. Already released fulfillment work can continue. A temporary failure to read Shopify does not erase your last verified subscription or your data. Payment status and the order-allowance grace period are separate. The billing page shows your current plan, its status, and what each tier unlocks. ## See also - [Billing] (/features/settings/billing/) — the settings page itself. - [Automation] (/features/settings/automation/) — the Elevate rules engine. - [Reports] (/features/insights/reports/) — the Elevate analytics. Last updated: 25 October 2026 --- Source: https://docs.floormode.app/features/home/overview/ # Home The page that answers "what needs doing today" — setup progress, open work per operation, and what is off track. Floormode’s Home (/) is the page you land on and the page you come back to. It answers one question — what needs doing today — in three blocks: how far setup has got, how much work is waiting in each operation, and what is off track. Home is not one of the eight nav entries. You reach it by clicking the app name, the way every Shopify app works. ## On this page - What you can do here - Where to next ## What you can do here [The setup flow] (/getting-started/setup-guide/) Four steps — Warehouse, Bins, Stock, Live — detected from your data as you go. [Today's numbers and operation tiles] (/features/home/operation-cards/) One line of today's numbers, then one tile per operation — Receive, Pick, Pack, Ship, Count, Returns — with what is waiting and what is late. [Needs attention] (/features/home/needs-attention/) A ranked list of everything off track: holds, shorts, delivery problems, stalled orders and failed actions. ## Where to next - [Finding your way around] (/getting-started/finding-your-way-around/) — the eight places everything else lives in. - [Orders] (/features/orders/overview/) — where most of what Home surfaces ends up being fixed. - [Fulfillment queue] (/features/fulfillment/queue/) — the single list of all floor work. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/home/operation-cards/ # Today's numbers and operation tiles One line of today's numbers, and one tile per operation showing how much work is waiting and how much is late or stuck. On Floormode’s Home, the Today tab opens with one quiet line of numbers — shipped today and yesterday, due today and late (with [delivery dates] (/features/settings/delivery-dates/) on: to pack today and overdue), packed today and the team’s average pack time. Under it, one tile per operation in the order of a warehouse day — Receive · Pick · Pack · Ship · Count · Returns. Each tile carries its number, what that number is (“orders to pick”), and two lines for the part that is late or stuck. ## On this page - The six tiles - Clicking through - Reading the numbers - See also ## The six tiles Tile What is waiting Where it takes you Receive Expected deliveries not yet booked in /inventory/receiving Pick Work waiting for a picker /fulfillment/queue Pack Pack jobs waiting for scan verification /fulfillment/pack Ship Verified parcels waiting for a label /fulfillment/shipping Count Open and in-review count tasks /inventory/counts Returns Requests to review and goods to grade /returns/requests ## Clicking through The whole tile is the way in: clicking it lands you in that queue already filtered to what the tile was counting. The number you clicked and the list you arrive at are the same set of records — you never have to reconstruct the filter yourself. ## Reading the numbers The lines under each tile’s number are the part that is late or stuck, and they are the ones worth watching. A Pick tile reading “48 · 3 waiting over a day” is a normal day. The same tile reading “12 · 11 waiting over a day” is a problem the volume alone would have hidden. A tile with nothing waiting still says so (“Nothing to pack”): zero is an answer. Long lists behind these tiles stop at a safe number of rows and say so. A count shown as “300+” means at least 300, not exactly 300 — the app will not scan an unbounded number of rows to produce a prettier number. ## See also - [Needs attention] (/features/home/needs-attention/) — the ranked list of what is actually off track. - [Fulfillment queue] (/features/fulfillment/queue/) — where the Pick tile lands. - [Receiving] (/features/inventory/receiving/) — where the Receive tile lands. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/home/needs-attention/ # Needs attention A ranked list of everything off track — holds, stock shorts, delivery problems, stalled orders and actions the app tried and failed. On Floormode’s Home, where the operation cards count what is waiting, Needs attention lists what is wrong. It is a ranked list, worst first, and every row ends somewhere you can act. ## On this page - What shows up here - How each row reads - Failed actions - See also ## What shows up here - On hold, one row per reason: waiting for payment, address problem, waiting for production, waiting for supplier stock, and the rest. - Not enough stock: orders whose lines could not be reserved, so nothing can pick them. - No product in Shopify: orders with an item that has no product in Shopify. Edit or cancel the item in Shopify. - Waiting for a plan: orders that can be picked once you confirm a plan in Shopify. Review plan opens the plan. - Reserving open orders: Floormode is still reserving stock, for example on the first day. It clears by itself. - Carrier problems: parcels the carrier could not move. - No progress for over a week: open orders with no change for over a week. Nothing is technically wrong with them, which is exactly why they get missed. - Did not go through, Held back and Dropped: updates the app could not send, is holding until a connection is back, or that expired. See Failed actions below. - Stores, with several stores: a store that joined and waits for Start, new products waiting for a link, a store whose plan ended, and a store that left. For what to do about each order reason, see [Why isn’t this order pickable?] (/features/orders/why-not-pickable/). ## How each row reads Each row shows the count, a few concrete examples, and a View all link into the filtered list. The examples matter: “14 orders on hold — waiting for payment” is a category, but seeing three order numbers tells you in a glance whether it is one customer’s bad card or a payment gateway outage. Holds grouped by reason are the most-used block on the page. A hold is applied with a reason, a note and a reference to the document you are waiting on — a [hold] (/reference/glossary/#hold) on production or supplier stock is not the warehouse being slow, and the list says so. ## Failed actions The last block is the one most systems hide. When the app tries something on your behalf and it does not work — a fulfillment Shopify rejected, a stock update Shopify refused, a refund that did not go through — it appears here, named in words such as Did not go through: marking an order fulfilled, rather than disappearing into a log. Nothing self-heals silently and nothing is silently dropped: the item stays on the list until it succeeds on a retry or you resolve it. Most lead to where they are dealt with: What did not go through Where it leads A stock, tag, location, lot or Flow update Settings → Apps & API, its Shopify updates, to send it again A hold, edit, payment, refund or cancellation of an order The Orders list filtered to Update did not go through; open each order to see what to do An order’s parcel The same list; open the order’s parcel to send it again A decision on a customer’s return request The return, to decide it again A webhook or a message to a connected app Settings → Apps & API, which says why it failed and offers a retry where one can help (an alert, for example, is never sent again) View all shows only for people who may open that list. ## See also - [Today’s numbers and operation tiles] (/features/home/operation-cards/) — the volume view of the same day. - [Orders overview] (/features/orders/overview/) — where holds and shorts get resolved. - [Blocked reasons] (/features/orders/blocked-reasons/) — the plain-English vocabulary behind the groupings. - [Why isn’t this order pickable?] (/features/orders/why-not-pickable/) — from each reason to what you do. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/orders/overview/ # Orders One order list with saved views, plain-English blocked reasons, holds, splits, merges and line edits. In Floormode, Orders (/orders) is one list, not five. Instead of a separate screen per order state, there is a single list with view tabs on top — the built-in ones plus any you save yourself. Shopify remains the source of truth for the order itself. Floormode adds what a warehouse needs on top: whether stock is reserved, what is holding the order up, and which warehouse is shipping which part of it. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Views & saved views] (/features/orders/view-tabs/) All open, Ready to ship, Blocked and Backordered in one view switcher — plus your own filters saved as a view, private or for the whole shop. [Blocked reasons] (/features/orders/blocked-reasons/) Why an order is stuck, in plain words, with the missing SKUs one click away. [Order detail] (/features/orders/order-detail/) Fulfillments, shipments, timeline, notes, and the progress stepper with its Waiting stage. [Split, merge & edit] (/features/orders/split-merge-edit/) Split in-stock from backordered, merge orders to one address, and edit lines with a preview. [Holds] (/features/orders/holds/) Apply and release holds with a reason, a note and a reference to the document you are waiting on. [Order address map] (/features/orders/address-map/) A privacy-safe static map of the delivery address, rendered once a map key is configured. ## Key concepts - [Fulfillment] (/reference/glossary/#fulfillment) — the part of an order that one warehouse ships together. An order can have several. - [Committed] (/reference/glossary/#committed) — units promised to open orders and no longer freely sellable. - [Hold] (/reference/glossary/#hold) — a deliberate block on an order, with a reason and usually a document reference. - [Backorder] (/reference/glossary/#backorder) — an order waiting for stock that could not be reserved. - [Saved view] (/reference/glossary/#saved-view) — a filter set kept as a tab, shared with the whole shop. ## Where to next - [Fulfillment queue] (/features/fulfillment/queue/) — where a released order becomes floor work. - [Stock] (/features/inventory/stock/) — the per-warehouse numbers behind a short. - [Needs attention] (/features/home/needs-attention/) — the same problems, ranked. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/orders/view-tabs/ # Views & saved views The five built-in order views, the view switcher, saving your own as a private or shared view, and how lists keep their place. The order list opens on All open and carries four more built-in views. Anything else you filter for can become a view of your own. Every list in Floormode works the same way, so what this page says about Orders holds for the others too. ## On this page - The five built-in views - Switching views - Saving your own view - Links, Back and the way back - Pages and ticked rows - See also ## The five built-in views View Shows All open Every order still needing work. The default. Ready to ship Stock reserved, nothing holding it — pick these now. Blocked Someone put a [hold] (/reference/glossary/#hold) on it. Backordered Waiting for stock that could not be reserved. Pickup & delivery Orders the customer collects or you deliver yourself. The distinction between Blocked and Backordered is worth internalising: blocked is a decision (a person held the order), backordered is a condition (there was not enough stock to reserve). They need different fixes, so they get different views. The Delivery filter beside Filters narrows any view to shipping, pickup or local delivery orders. ## Switching views The View button at the start of the toolbar names the view you are on. Click it to open the view switcher: - Presets are the built-in views; Saved views follow, each marked Shared or Only you. - A check mark sits on the view you are on, a star on the view the list opens with for you. - Type to search by name. The arrow keys move, Enter opens the view, Esc closes the switcher. Beside the views sit the actions for the view you are on, each where it applies: Save view, Save as new view…, Edit view…, Set as my default (or Clear my default) and Reset. ## Saving your own view Filter the list however you like, then open the view switcher and choose Save as new view…. Give it a name. Tick Share with everyone in this shop to make it a shop view; otherwise only you see it. Typical saved views merchants build: - Same-day cutoff — paid before 14:00, ready to ship, not yet picked. - Waiting on production — blocked, reason “Waiting for production”. - One warehouse only — for a site that wants its own queue. In the switcher a saved view says who sees it. While a saved view is open, the same answer sits under the page title. A shared view belongs to everyone: anyone in the shop can edit or delete it, and saving over it asks first. Changed a saved view? Save view (or ⌘S, Ctrl S on Windows) stores what the list shows now under the same name. Edit view… renames it, changes who sees it or deletes it. Note Unsaved changes on the View button says the list now differs from what the view saved. Reset in the switcher puts filters, sort and columns back. ## Links, Back and the way back The page address carries the view, the filters, the sort and the page. Copy the link and a colleague lands on the same list. - The browser’s Back button returns to the list exactly as you left it. - Where a row opens a panel on the same page (a shipment, a stock item, a bin), Back closes the panel. - Where a row opens its own page (an order, a batch, a pack job, a count, a receipt, a transfer, a return), that page’s breadcrumb returns to the same view, filters, sort and page. ## Pages and ticked rows The footer shows the page and has Previous page and Next page. Changing the view, a filter or the sort returns you to page one. Rows per page sits in the footer of Orders, Receiving and Stock; your choice is kept for you alone. Tick rows to act on several at once: Hold, Release hold and Merge on Orders. Ticks stay when you turn the page, up to 500 orders. Changing the view, a filter or the sort clears them. ## See also - [Blocked reasons] (/features/orders/blocked-reasons/) — the vocabulary the Blocked view groups by. - [Order detail] (/features/orders/order-detail/) — what opens when you click a row. - [Backorders and oversell] (/features/inventory/backorders-and-oversell/) — how orders end up in the Backordered view. - [Lists, filters and saved views] (/getting-started/lists-and-views/) Last updated: 9 October 2026 --- Source: https://docs.floormode.app/features/orders/blocked-reasons/ # Blocked reasons Why an order is stuck, in words you can repeat to a customer, with the missing SKUs one click away. In Floormode, every order row shows why it is stuck in plain words, in the Blocked reason column — not a status code. If someone rings up asking about their order, you can read the reason out loud. For what to do about each reason, see [Why isn’t this order pickable?] (/features/orders/why-not-pickable/). ## On this page - The vocabulary - Short of stock - Waiting for the pack day - Allocation states - See also ## The vocabulary Reason Means Waiting for payment Payment has not settled yet. Possible fraud Flagged for review before it ships. Address problem The delivery address needs fixing. Waiting for stock Held until stock arrives. Waiting for production Held on a build or work order. Waiting for supplier stock Held on an inbound supplier delivery. Customer asked to wait The customer requested the delay. Other reason Anything else, with the note explaining it. Production, supplier stock and the customer’s request matter for expectation-setting: they say plainly that the warehouse is not the thing that is late. A hold placed in the Shopify admin or by another app shows Shopify’s own reason and, under it, Placed outside Floormode: release it in the Shopify admin. ## Short of stock Where an order is short, the row does not just say so — it tells you how many SKUs are missing (Missing stock: 2 SKUs). One click shows which ones, broken down per warehouse, with Open stock to go to the stock list. When the missing item has no product in Shopify at all, for example a custom line, the row says No product in Shopify instead: no delivery can cover it, so the fix is to edit or cancel that item in Shopify. + Filter → No product in Shopify lists these orders. That chain — row → missing SKUs → per-warehouse stock → the documents causing each number — is the fastest path from “this order is stuck” to “this is why, and here is the receipt that fixes it”. ## Waiting for the pack day Where you use delivery dates and picking waits for the pack day, an order planned for a later day says when it packs: Packs Thu, 16 Oct, or Waits for its pack day. The order’s page can let it through early with Pick now. ## Allocation states Underneath the blocked reason sits the line-level reservation state, shown in the same plain register: State Means Reserved Stock is set aside for this line. Being picked A picker is walking it now. Not enough stock The reservation could not be made — a [short] (/reference/glossary/#short-pick). Reservation released The reservation was given back. Fulfilled Shipped and consumed. ## See also - [Why isn’t this order pickable?] (/features/orders/why-not-pickable/) — what to do about each reason. - [Holds] (/features/orders/holds/) — applying and releasing a hold with a reason and a reference. - [Views] (/features/orders/view-tabs/) — the Blocked and Backordered views. - [Stock] (/features/inventory/stock/) — where the missing-SKU link lands. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/orders/why-not-pickable/ # Why isn't this order pickable? Every reason Floormode gives for an order that does not reach the Queue, where you see it, and what to do about it. An order reaches the [Queue] (/features/fulfillment/queue/) when its stock is reserved in bins and nothing holds it back. When an order is not there, Floormode says why. This guide goes from the words the app shows to what you do. ## On this page - Where to find the reason - Stock - Holds - The pack day - Locations and stores - Your plan - Orders already on their way - Waiting for Shopify - See also ## Where to find the reason - Home → Needs attention groups the orders that wait, one row per reason, with View all leading to exactly those orders. - Orders, the Blocked reason column, says what stands in the way of each order. The Blocked view lists held orders, Backordered lists orders short of stock. - Fulfillment → Queue, when nothing is ready, counts the orders it leaves out and links to each list. - The order’s page shows where the order stands: Open, Reserved, Picking, Packed, Fulfilled, or what stopped it. ## Stock You see It means What to do Reserving open orders (Home) Floormode is reserving stock for open orders, for example on the first day. Nothing. It clears by itself. Not enough stock (Home), Missing stock: 2 SKUs (Orders), short of stock (Queue) Some lines could not be reserved: the free units in the order’s warehouse are not enough. Click the reason to see which items are missing, per warehouse, then Open stock. Receive the delivery, move stock in from another bin, or [count] (/features/inventory/counts/) a bin you think is wrong. The order is reserved again as soon as stock is free. No product in Shopify An item on the order has no product in Shopify, for example a custom line or a deleted product. No delivery can cover it. Open order, then edit or cancel that item in Shopify. Note When stock reaches a sellable bin, Floormode tries again to reserve it for the orders waiting on that item. Reserving is all that happens by itself: nothing is picked, packed or shipped until someone does it. See [Backorders & oversell] (/features/inventory/backorders-and-oversell/#when-the-stock-arrives). ## Holds A held order has a reason. Holds placed in Floormode are released on the order’s page or from Needs attention; see [Holds] (/features/orders/holds/). You see It means What to do Waiting for payment The payment has not settled. Check the payment in Shopify. When it has arrived, release the hold. Possible fraud Shopify flagged the order, or one of your order rules held it. Check the order in Shopify. Release it, or cancel the order. Address problem The delivery address needs fixing. Correct the address, then release the hold. Waiting for stock Someone held it until stock arrives. Release the hold when the stock is in. Waiting for production, Waiting for supplier stock The goods are being made or are on their way. The order’s page shows Waiting and the document it waits for, such as a purchase order. Release the hold when the goods arrive. Customer asked to wait The customer asked for a delay. Release it when the customer is ready. Other reason Anything else; the note says what. Read the note. On hold outside Floormode, Placed outside Floormode The hold was placed in the Shopify admin or by another app. Release it in the Shopify admin. Floormode cannot release it. Releasing hold You released it; Shopify has not confirmed yet. Nothing. It moves on once Shopify answers. ## The pack day Where you use [delivery dates] (/features/settings/delivery-dates/) and picking waits for the pack day, an order planned for a later day is not picked yet. You see It means What to do Packs Thu, 16 Oct, Waits for its pack day (Orders), waiting for their pack day (Queue) Its pack day has not come. It joins the Queue on that day. Nothing. To pick it now, open the order and choose Pick now; Undo sends it back to waiting. Where you hold work back in a [wave] (/features/fulfillment/waves/), a reserved order reaches the floor when its wave is released. ## Locations and stores You see It means What to do at a Shopify location without a warehouse (Queue) Shopify assigned the order to a location no warehouse is linked to. Set up locations: link that location to a warehouse, or move the order to a linked location in Shopify. … joined. Start it when you are ready (Home) A new store’s open orders wait until you start the store. Open the store and press Start. Until then nothing is written to its stock. New products in … wait for a link (Home) Floormode leaves a store’s new products alone until they are linked. Open the store and link the products, or bring them in. …’s plan ended (Home) That store’s plan in Shopify ended. Its new orders wait; stock updates continue. Renew the plan in that store’s Shopify admin. … left Floormode (Home) The store uninstalled Floormode. Its paid orders keep their stock for a while, then go back to stock. Open the store’s page to put them back now, or wait. See [Stores] (/features/settings/stores/) for how stores join and leave. ## Your plan You see It means What to do Waiting for a plan (Home), orders wait for a plan (Queue) The orders are ready, but your plan’s order allowance is used up after its grace period, or no plan is active. Review plan and confirm a plan in Shopify. Work already released carries on. See [Subscription plans] (/getting-started/subscription-plans/#how-orders-count-and-what-happens-at-the-limit). ## Orders already on their way Some orders are left out of the Queue because they are already being worked on. Nothing is wrong with them. You see It means already in a batch (Queue) The order is in a [pick batch] (/features/fulfillment/batches/). See batches shows which. Picking, Packed (the order’s page) Someone is picking it, or its parcel is packed. Fulfilled, Nothing to ship, Cancelled The order is finished, needs no parcel, or was cancelled. ## Waiting for Shopify The order’s page lists changes still on their way to Shopify under Waiting for Shopify. Two of them stop new floor work for the order until Shopify answers: - Cancellation on its way to Shopify: wait for Shopify’s answer. Once it confirms, the order’s work is released. - Cancellation not confirmed by Shopify: Shopify neither confirmed nor refused it. On the order’s page, Check with Shopify again. If you checked the order in the Shopify admin and it was not cancelled there, Shopify did not cancel: return to floor sends it back to the floor. - Refund with restock on its way to Shopify: new picks wait until Shopify confirms the refund. ## See also - [Blocked reasons] (/features/orders/blocked-reasons/): the words on the Orders list. - [Needs attention] (/features/home/needs-attention/): the list on Home. - [Holds] (/features/orders/holds/): placing and releasing a hold. - [Backorders & oversell] (/features/inventory/backorders-and-oversell/): what happens when stock runs out. - [Lifecycles] (/reference/lifecycles/): every state an order, a shipment and a return can be in. Last updated: 30 October 2026 --- Source: https://docs.floormode.app/features/orders/order-detail/ # Order detail Fulfillments, shipments, timeline and notes for one order — plus the progress stepper and its Waiting stage. Opening an order in Floormode (/orders/:id) gives you everything the warehouse knows about it in one page: what is shipping from where, what has already gone, what happened and when, and what anyone wrote down. Open in Shopify opens the same order in Shopify Admin. ## On this page - Fulfillments and shipments - The progress stepper - Timeline and notes - See also ## Fulfillments and shipments A [fulfillment] (/reference/glossary/#fulfillment) is the part of an order that one warehouse ships together. An order split across two sites has two fulfillments; an order shipped complete from one site has one. Each fulfillment lists its lines, its allocation state and the warehouse it belongs to. Under it sit the shipments — the actual parcels, with their carrier, service, tracking number and current delivery status. ## The progress stepper The stepper across the top shows where the order actually is. It gains a Waiting stage when a [hold] (/reference/glossary/#hold) is on production or supplier stock, so the picture is honest: the order is not sitting in a picking queue being ignored, it is waiting on a document. That distinction is the whole point of the stage. Without it, “not shipped yet” looks identical whether the cause is a busy floor or a supplier who has not delivered. ## Timeline and notes The timeline is the order’s history in order: allocation, holds applied and released, picks, packs, labels bought, fulfillments pushed to Shopify, delivery events coming back. When someone asks why an order took four days, the timeline is the answer. Show details lists the names, counts, bins and notes an event recorded. Notes are for the things a system cannot infer — a phone call, a customer’s request, a decision someone made. They sit alongside the timeline rather than inside it, so a human note is never confused with a recorded event. ## See also - [Holds] (/features/orders/holds/) — how the Waiting stage gets set. - [Split, merge & edit] (/features/orders/split-merge-edit/) — changing the order from this page. - [Shipping] (/features/fulfillment/shipping/) — where the shipments come from. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/orders/holds/ # Holds Deliberately block an order with a reason, a note and a reference to the document you are waiting on. In Floormode, a [hold] (/reference/glossary/#hold) is a decision, recorded. It stops an order reaching the floor and says why, so nobody has to guess and nobody picks something that should not ship. ## On this page - Applying a hold - The document reference - Releasing a hold - See also ## Applying a hold Holds are applied and released on the order detail page (/orders/:id). Each one takes three things: 1. A reason — from the fixed list (waiting for payment, possible fraud, address problem, waiting for stock, waiting for production, waiting for supplier stock, customer asked to wait, other). 2. A note — free text for the specifics. 3. A reference — the document you are waiting on, if there is one. The reason drives everything downstream: the Blocked tab groups by it, Needs attention ranks by it, and the order row shows it verbatim. ## The document reference Where the hold is waiting on something, you can record what: Kind Typical reference Purchase order PO-1042 Transfer The inbound transfer you are expecting Work order The build that has to finish first Bundle build The kit assembly this order needs Note Floormode owns no purchase orders or work-order documents — the sibling apps do. The reference is therefore a merchant-typed identifier, not a live link into another system. It is there so the next person to open the order knows exactly what to chase. Where a sibling app is connected, the work behind those references does reach you directly — a purchase order becomes an [expected delivery] (/integrations/logistified/) and a work order becomes a [production pick] (/integrations/assemblified/) — but the reference typed here stays a note to the next person rather than a live link. ## Releasing a hold Releasing takes the block off and moves the order back into the normal flow — allocation re-runs, and if stock is available the order becomes ready to ship. Both the apply and the release land on the order’s timeline with who did it and when, so a hold is never an unexplained gap in an order’s history. ## See also - [Blocked reasons] (/features/orders/blocked-reasons/) — the full vocabulary. - [Order detail] (/features/orders/order-detail/) — the Waiting stage a hold creates. - [Needs attention] (/features/home/needs-attention/) — holds grouped by reason on Home. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/orders/split-merge-edit/ # Split, merge & edit orders Split in-stock from backordered, merge orders going to one address, and edit order lines with a preview. Real orders do not always arrive in the shape you want to ship them. All three of Floormode’s reshaping tools live on the order detail page (/orders/:id). ## On this page - Split - Merge - Edit lines - When an order changes in Shopify - Payment capture and risk - See also ## Split Splitting divides an order into an in-stock part and a [backordered] (/reference/glossary/#backorder) part. The in-stock half ships today; the rest waits for stock without holding up the customer’s whole parcel. This is the standard answer to a partially-allocated order: rather than holding everything until the last unit lands, ship what you have and keep one clean record of what is outstanding. ## Merge Merging groups open orders going to the same address in a merge group, so the warehouse sees that they belong together. It is a grouping inside Floormode only: the orders stay separate in Shopify, and each keeps its own fulfillment, shipment and label. A group creates no pick batch, shipment or shipping label. To pick the orders on one walk, select them in the [Queue] (/features/fulfillment/queue/) and choose Create batch. ## Edit lines You can add lines, remove lines and change quantities, with a preview before anything commits. The preview matters: an edit changes what is reserved, what needs picking and what the customer is charged, and you should see all of that before it happens rather than after. Caution An edit re-runs allocation. Adding a line to an order that was ready to ship can make it short — the preview shows you that before you commit, not once a picker is already walking. ## When an order changes in Shopify Shopify stays the place where an order lives. When someone edits, moves, holds or cancels an order in the Shopify admin, Floormode reads the change and adjusts its own work. You do not have to tell it. Done in Shopify What Floormode does A line added, or a quantity raised The new units are reserved like a new order line. If the stock is not there, the order shows Not enough stock for them. A line removed, or a quantity lowered The units no longer ordered are given back to free stock. Picks not yet made shrink or are cancelled. Units already picked stay recorded as picked; the ones the order no longer needs leave the order at the pack station. A custom item added, one with no product in Shopify The order shows No product in Shopify: no delivery can cover it. Edit or cancel the item. The shipping address changed A shipment not yet bought goes back to Draft: rates fetched for the old address are dropped, never bought. The fulfillment moved to another location The reservation at the old warehouse is released, and the order is planned again at the warehouse linked to the new location. A location with no warehouse leaves it waiting (at a Shopify location without a warehouse). A hold placed The order shows On hold outside Floormode and is not picked. Release it in the Shopify admin. Fulfilled in Shopify, or by another app The reservation is released. Open picks for it read Fulfillment order closed. The order cancelled The reservation is released and open picks read Order cancelled. A parcel already packed is handled as described under [Pack] (/features/fulfillment/pack/#the-pack-checklist). What an edit in Shopify cannot do in Floormode: - Undo a pick. Units already picked are never un-picked on the record; they are taken off the order instead. - Change a parcel already handed to the carrier. A fulfilled parcel stays fulfilled. Changes after that are returns or refunds. Edits you make with Edit lines in Floormode go to Shopify and come back the same way. While a change that conflicts with it, such as a cancellation, a refund, a return or another line edit, is still on its way to Shopify, the order’s page lists it under Waiting for Shopify, and a new edit is refused with the reason until Shopify answers. ## Payment capture and risk Two related behaviours sit alongside these tools: - Capture payment at fulfillment — payment is captured automatically when the order is fulfilled, rather than at checkout. It is a per-warehouse policy, set on the warehouse (/settings/warehouses/:id). - A risk queue flags suspicious orders for review before they reach the floor, so a possible-fraud order never quietly gets picked. ## See also - [Order detail] (/features/orders/order-detail/) — where all three tools live. - [Holds] (/features/orders/holds/) — the other way to stop an order. - [Why isn’t this order pickable?] (/features/orders/why-not-pickable/) — every reason an order waits. - [Warehouses] (/features/settings/warehouses/) — where the capture-at-fulfillment policy is set. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/orders/address-map/ # Order address map A privacy-safe static map of the delivery address, shown inside the order. Floormode’s order detail page can show the delivery address on a map. It is a small feature that answers a surprisingly common question: is this address real, and is it where I think it is? ## On this page - What it shows - Why static - Setting it up - See also ## What it shows A static map image of the delivery address, rendered inline in the order. Useful for spotting an address that has been mistyped into a different city, a residential delivery marked as commercial, or a remote drop that will attract a carrier surcharge. ## Why static The map is a privacy-safe static image served by Floormode, not an embedded third-party map widget. Note An embedded map widget would load scripts from a map provider inside your admin and hand that provider your customer’s address along with the request. Rendering a static image server-side means the address never leaves Floormode in the browser, and no third-party script runs in your admin. ## Setting it up There is nothing to set up: Floormode runs the map service. When it has no map for an address (it cannot place the address, or the map service is not configured), the map says that a preview is unavailable and you continue with the shipping address shown above it. Open in Maps still opens the address in your maps app. Like everything else in the app, it is optional. An order works exactly the same with no map key configured. ## See also - [Order detail] (/features/orders/order-detail/) — the page the map sits on. - [Blocked reasons] (/features/orders/blocked-reasons/) — including “Address problem”. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/overview/ # Fulfillment Everything between a paid order and a parcel on the van — queue, batches, packing, shipping and waves. In Floormode, Fulfillment (/fulfillment) covers everything between a paid order and a parcel on the van. Six tabs, in the order work actually flows through them. The office view lives here. The people doing the work use [Floor Mode] (/features/floor/overview/), which shows the same jobs one at a time on a scanner-first screen. ## On this page - What you can do here - Production - Key concepts - Where to next ## What you can do here [Queue] (/features/fulfillment/queue/) The orders ready to pick, and, where work is handed out, the other floor work: receiving, putaway, counting, replenishment and moves. [Batches] (/features/fulfillment/batches/) The pick batches on the floor, how far each has walked, and the route they follow. [Pack] (/features/fulfillment/pack/) Scan-verified packing and automatic box selection from your catalog. [Shipping] (/features/fulfillment/shipping/) Rate-shop, buy, print and void labels — plus manifests, pickups, exceptions and freight. [Production] (#production) With Assemblified: each work order from its materials picked to its finished goods put away. [Waves] (/features/fulfillment/waves/) Advanced. Hold picking work back and release it to the floor in waves. [Cluster picking] (/features/fulfillment/cluster-picking/) Enhanced plan. Pick several orders in one walk, each in its own slot on the cart. ## Production With [Assemblified] (/integrations/assemblified/) connected, the Production tab follows each [work order] (/reference/glossary/#work-order) through the warehouse, one row each: announced, picking, staged, in production, awaiting putaway, put away. - The materials are picked on the floor to the work order’s [staging bin] (/reference/glossary/#staging-bin), WO-STAGE-01 — see [Production pick] (/features/floor/production-pick/). They leave stock when Assemblified reports the build that used them. - The finished goods are booked onto the same bin, the workbench, the moment Assemblified reports the build, and a [putaway] (/reference/glossary/#putaway) task brings them to a shelf. An output that needs the receiver — serial numbers taken at receiving, or a date Floormode cannot work out — waits on its receipt instead. Without Assemblified the tab stays empty. See [Assemblified] (/integrations/assemblified/#what-you-can-see-about-production) for the stages in full. ## Key concepts - [Pick batch] (/reference/glossary/#pick-batch) — a set of lines one picker walks in one trip. - [Pick path] (/reference/glossary/#pick-path) — the route order picks are sorted into: zone, aisle, side, bay. - [Pack job] (/reference/glossary/#pack-job) — one parcel’s worth of scan verification at the pack station. - [Cartonization] (/reference/glossary/#cartonization) — choosing the cheapest suitable box from your catalog. - [Waves] (/reference/glossary/#waves) — groups of held picking work released to the floor together. ## Where to next - [Floor Mode] (/features/floor/overview/) — the same work, on the floor. - [Carriers & packaging] (/features/settings/carriers-and-packaging/) — carrier accounts, printers and the box catalog. - [Fulfillment settings] (/features/settings/fulfillment/) — auto-assignment, replenishment and routing. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/queue/ # Queue The orders ready to pick, and, once work is handed out, who holds which pick and the rest of the floor's work. In Floormode, Queue (/fulfillment/queue) lists the orders that are ready to pick in your warehouse: their stock is reserved and no hold is left on them. From here you cut them into pick batches. Once work is handed out to people, the same page shows who holds which pick, and the floor’s other work in a list of its own. ## On this page - The orders ready to pick - Making a batch - When nothing is ready - Handing out work - Other floor work - Where the floor sees it - See also ## The orders ready to pick Each row is one order, with its lines, its bins, when it was placed and when it became ready. The heading counts every ready order in the warehouse, not just the page in view. Choose the warehouse in the toolbar; it is the same choice on every Fulfillment tab. The views across the top narrow the list: View Shows All orders Every order ready to be picked. Single-item One line, one unit: the classic batch material. Late Ready for more than a day. Mine Orders whose pick is yours (once work is handed out). Unassigned Orders nobody has taken yet (once work is handed out). On the plan that has [pick profiles] (/features/settings/fulfillment/), + Filter → Pick profile shows one profile’s orders. ## Making a batch Create batch turns orders into a [pick batch] (/features/fulfillment/batches/): tick the orders you want, or leave them unticked and the batch takes the first ones listed. Once the batch exists, its page opens and the floor can pick it. ## When nothing is ready An empty queue says why, with the way to each list: orders short of stock (See shortages), held (See held orders), already in a batch (See batches), waiting for their pack day where you use [delivery dates] (/features/settings/fulfillment/), and orders at a Shopify location without a warehouse (Set up locations). ## Handing out work With Auto-assign pick tasks on (Settings → Picking & floor → Work assignment), a ready order’s pick goes to someone in the warehouse whose zones and skills fit: the people planned for picking today first, then whoever holds the least work. A pick that waits for its pack day or for a release stays in the pool until then. Zones and skills are set under Settings → Warehouses → your warehouse → Zones, stations & staff. Once picks are being handed out, the queue adds an Assignee column and these actions: - Claim next takes the next task in the pool that fits your zones and skills, a pick or other floor work, and switches the list to Mine. - Take on a row takes that pick, and Start begins it. A pick closes when it is picked, in its batch or on the floor. - Your own unstarted work can be given back to the pool; a lead can unassign anyone’s, or give it to someone with Hand to…. Note Auto-assignment is off by default: until you switch it on, nobody is handed a pick automatically. You can still give work to someone yourself, for example the picker of a new batch. Picks and other tasks are listed per warehouse, so with several warehouses choose one in the toolbar to see them. ## Other floor work Under the orders, Other floor work lists the floor’s tasks that are not order picks: put away, replenish, move, count, receive, and returning cancelled picks to a shelf. It appears once there is such work or picks are handed out. Its views are Open, Mine, Unassigned and All. A task is taken and started the same way and closed with Complete; a return to shelf closes with its last scan, and a transfer plan with Mark planned. Status Means Unassigned In the pool, nobody on it Claimed Someone took it Assigned Someone was given it In progress Being worked now Done Finished Cancelled Withdrawn ## Where the floor sees it People on the floor do not work from this page. [Floor Mode] (/features/floor/overview/) shows each person the work for where they work, one job at a time, and what they do there updates this page. ## See also - [Batches] (/features/fulfillment/batches/): what a batch becomes on the floor. - [Waves] (/features/fulfillment/waves/): holding work back and releasing it to the queue together. - [Fulfillment settings] (/features/settings/fulfillment/): the auto-assignment switch. - [Team, roles & floor devices] (/features/settings/team/): who may take and hand out work. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/batches/ # Batches The pick batches on the floor, how far each has walked, and the route order that shortens the trip. In Floormode, Batches (/fulfillment/batches) shows the [pick batches] (/reference/glossary/#pick-batch) currently on the floor and how far each one has got. Click through for the batch detail: route-sorted lines, what has been picked, and any exceptions. ## On this page - Route order, not alphabetical - Batch statuses - Line statuses - Batch methods - See also ## Route order, not alphabetical Picks are ordered along a walking route — zone → aisle → side → bay — rather than by SKU or alphabetically. That single choice is most of the time saving in picking: a picker walks the building once in one direction instead of doubling back for every line. Warehouses that record bin coordinates get more than that: the route is optimised against the actual geometry, which shortens the trip again. ## Batch statuses Status Means Ready to pick Built and waiting for a picker Being picked Someone is walking it Picked Every line resolved Cancelled Withdrawn ## Line statuses Inside a batch, each line carries its own state: Status Means To pick Not yet reached Picked Pulled and confirmed Picked short A [short pick] (/reference/glossary/#short-pick) — the bin did not hold what the system expected Cancelled No longer needed A short pick is the interesting one. It does not silently reduce the order — it records that the physical count and the system disagreed at that bin, which is a signal worth counting on. ## Batch methods Method Means Single-item orders One line, one order — the fastest possible walk Batch picking The same SKU pulled once for several orders Cluster picking Several orders in one walk, each in its own slot on the cart (Enhanced) ## See also - [Queue] (/features/fulfillment/queue/) — where pick work is handed out. - [Cluster picking] (/features/fulfillment/cluster-picking/) — the Enhanced method. - [Floor pick] (/features/floor/pick/) — what the picker actually sees. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/pack/ # Pack Scan-verified packing and automatic box selection, so the wrong thing cannot go in the box. In Floormode, Pack (/fulfillment/pack) lists the [pack jobs] (/reference/glossary/#pack-job) waiting for verification, and opens the pack station itself. ## On this page - Before you pack - The pack flow, step by step - Scan verification - Sort a batch at the pack station - The pack checklist - Gift orders - The command sheet - Choosing the box - Weighing with a USB scale - Pickup and local delivery orders - Pack job statuses - See also ## Before you pack Set these up once per warehouse. Each line says what happens without it. You need Where Without it A barcode scanner, or a camera A USB or Bluetooth scanner on the pack PC types into the scan field. On a phone or tablet, Floor Mode’s Scan with camera reads barcodes. You type each barcode, or, on the floor, confirm by tapping where the warehouse allows it (below). How workers confirm a step Settings → Warehouses → your warehouse → Settings → Stock policies → Floor Mode: Scan only, Scan or tap, or Tap, no scanner. Scan or tap is the default: people scan, and a phone without a scanner can switch on This device has no scanner in Floor Mode’s ⋯ menu to get confirm buttons. Under Scan only there are no confirm buttons, except for items allowed without a scan (next row) and a lead’s approval; under Tap, no scanner every step has a confirm button. Barcodes on your products Each variant’s barcode or SKU in Shopify. An item with no barcode, SKU or alias cannot be scanned. On its stock page, Confirm on the floor → Can be confirmed without a scan lets Floor Mode confirm it by eye. A pack checklist Settings → Packing → Pack checklist, one per warehouse. Just pack: scan, then fulfil. A pack station, for a printer, scale or camera Settings → Packing, and on the pack PC Use this PC at …. Labels download as a PDF, weights are typed, photos are taken with a phone or uploaded. A carrier account Settings → Shipping & carriers. No label can be bought. The built-in test carrier lets you try the flow. ## The pack flow, step by step The pack station walks the parcel through the warehouse’s checklist. Only the steps your checklist turns on appear; the Pack checklist card on the job shows them, and the line above the button names what is Still needed. 1. Open the pack job from Fulfillment → Pack, or on the floor from Today. 2. Read the order’s note, when it has one, and confirm the pack instructions. 3. Scan every item into the field (Scan or type a barcode…). A right scan counts the unit; a wrong or extra item is refused. 4. Serials: for an item whose serial numbers are recorded at packing, record the serial number of every unit. 5. Box and weight: confirm the box the app proposes, or choose another, then read the scale or type the weight. 6. Verify parcel: saves the box and weight. The job reads Items verified and names anything still needed. 7. Photo, Details (such as a seal number) and Check, where your checklist asks for them. A weight far off the expected one warns the packer, or waits for a lead’s approval, as the checklist says. A failed check always holds the parcel. 8. Label and fulfil, as the checklist’s Label step is set. The button says what one press does: - Required: the label is bought before the order is fulfilled. Fulfil + print label buys the label at your rules’ rate, prints it on the station’s printer, then fulfils; without a printer it reads Fulfil + buy label, and with a label already bought, Print label + fulfil. A label bought elsewhere counts once its tracking number is entered. - Optional: the same press buys a label when a rate is found. With no rate, a second press, Fulfil without a label, fulfils without one. - Off: Fulfil fulfils the order and buys no label. Use it when your labels come from somewhere else. 9. Shopify confirms the fulfillment, and the job reads Fulfilled. Pickup and local delivery orders never need a label; see below. When something goes wrong at step 8, the pack station says what and offers the one next step: Try again, Print again, It printed · Fulfil, Fulfil without printing or Open the shipment to choose a service. ## Scan verification The packer scans every item before completing the parcel’s fulfillment. Wrong and extra scans are refused. Buying or printing a shipping label is a separate step. Tip This is the single highest-value control in the whole app. A mis-ship costs a return shipment, a replacement shipment, the original margin and usually the customer. Scanning at pack makes putting the wrong thing in the box a physically blocked action rather than a mistake to catch later. ## Sort a batch at the pack station A batch pick brings several orders’ items to the pack station in one tote. Sort them first: scan an item, and Floor Mode names its slot (“Slot 3”) — the shelf or pile position of the order that still needs it. Put the item there and scan the next one. Each scan counts as that order’s pack scan, so a full slot opens Pack with every item already checked. - When it is offered: by default for a batch whose orders are one item each. Under Settings → Packing → Pack checklist, choose Every batch or Only on demand. Any batch pick can be sorted from its Sort at the pack station button, or by scanning its pick list on Today. - Several packers can sort one batch at once: an item never gets two slots, and a reload shows the slots as they are. - A sort wall is optional: name its slots (for example S01, S02, S03) and print each name as the slot’s barcode. After each item, Floor Mode asks for that slot’s label, which confirms the item is in. - An item no order of the batch needs, or one too many, is refused by name: put it aside for the office. - A cluster pick is never sorted here: its picker already put each order in its own tote. ## The pack checklist What a parcel walks through between the scan and the fulfilment is the warehouse’s pack checklist, set under Settings → Packing → Pack checklist (one per warehouse). Start from a preset — Just pack, Weigh + label or Proof photo — and set each step to Off, Optional or Required: a photo of the contents, the weight, packing details such as a seal number, a quality check, and the label before fulfilment. A required step must be done before the parcel can be fulfilled; the pack station lists what is still missing. The order’s packing note shows at the pack station and on the floor before the parcel is sealed. Photo check (on by default wherever a photo is taken; each warehouse can turn it off): with Check the photo against the order on, Cloudflare Workers AI compares each saved pack photo with the parcel’s items and the pack station shows one line until fulfilment — No visible difference found, or Check the box with Details. It is advice, never a block, and scanning stays the check: it counts products, not sizes or similar variants, for parcels of up to 3 items. Only a reduced crop of the box frame is sent, and not stored (a photo taken without the frame, such as an upload, is not checked); take the photo before the packing slip goes in. A parcel that fails its quality check goes to the damaged stock location (HOSP-01). Its units leave Shopify’s available at once as damaged, and the order is planned again from the stock that is still free. When an order is cancelled after packing, Floormode reads Shopify’s stock level for its items. If Shopify put the units back on sale, Floormode marks them as quality control until they are back on a shelf, so they can’t be sold from the pack station. In Shopify’s inventory, units Floormode holds back this way count as unavailable and are listed under Managed by apps → Floormode, not in your own Damaged or Quality control count: Shopify keeps a state an app sets apart from the ones you set by hand. If Shopify didn’t restock them, they wait at the pack station for you to check them. ### Print the label on the last scan Turn on Print the label when the last item is scanned on the pack checklist card, and the scan that counts a parcel’s last item verifies it and starts Fulfil + print label on its own: the same press, with the same checks, so a label is never bought twice. It starts only where the press prints a label (the Label step is on, at a pack station with a label printer), only for a parcel that ships (pickup and local delivery keep their own button), and only when nothing is still required — a weight that is needed, a check, serial numbers, packing details, an order note nobody has read — and never for a weight outside the tolerance or one still being typed or read: if the weight changes before the label is bought, the packer presses Fulfil. Then the packer goes on as before. An optional step left out does not hold it. The switch is off until you turn it on. ## Gift orders An order is a gift when its cart says so: the common gift fields that themes and gift apps write (gift, gift-wrapping, gift-note, Gift Note, gift-message) are read without any setup. When your gift app writes a field of its own name, enter that name as Gift field under Settings → Packing → Packing slip. A gift order shows a Gift chip and the gift message at the pack station, and its packing slip prints as a gift slip: titled so, with the gift message, its date in the shopper’s language. A gift slip leaves the buyer’s order note out; the packer still sees it at the pack station. A Floormode slip never prints prices. ## The command sheet A pack station with a scanner and no keyboard can do everything by scanning. Open ⋯ → Print command sheet at the pack station and keep the page beside the scanner: its barcodes are Fulfil + print, Box 1 to Box 9, Use the scale’s weight, Next parcel and Skip an optional step. A command does what the button does on that step and nothing else; it never counts an item. The sheet prints on US Letter or A4, as the device’s language does. ## Choosing the box At packing, the app runs [cartonization] (/reference/glossary/#cartonization): it picks the cheapest suitable box from your box catalog using the item dimensions, and splits into several boxes where one will not do. This needs two things you set up once: - Boxes in the catalog under Settings → Shipping & carriers — without them nothing can be cartonized. - Item dimensions on your products — optional, but cartonization gets much better with them. ## Weighing with a USB scale The pack station can read the parcel weight from a USB scale. It works in Chrome or Edge, with a standard shipping scale (for example a Dymo M-series or a Mettler PS-series). The weight is in the warehouse’s units. In a warehouse on imperial units it reads “2 lb 12 oz”; type 2 lb 12 oz or a bare figure in pounds (2.75). In a metric one it reads “1,361 g”; type the grams without a thousands separator (1361). Warehouses follow your store’s units from Shopify. Floormode saves whole grams either way. Click Connect scale next to the weight field and choose the scale once. The browser remembers it for the next parcel. A steady reading fills an empty weight field by itself. If you already typed a weight, the station offers Use scale weight instead and never overwrites what you typed. When the reading is far from what the items and the box should weigh, the station shows Check the parcel with both numbers. With When the weight is off → Warn the packer in the pack checklist it is a warning, not a stop; with A lead approves the parcel waits for a lead’s approval or a new weight within the tolerance. It stays quiet when an item in the parcel has no weight in the catalog. Give your boxes an Empty weight under Settings → Shipping & carriers, so the comparison counts the box too. Note Inside the Shopify admin the browser may not allow a USB device at all. Then Connect scale does not appear. Open Floormode in its own tab to use the scale. ## Pickup and local delivery orders An order the customer collects, or one you deliver yourself, needs no shipping label. Its pack station says Pickup order: no label needed or Local delivery order: no label needed. - Mark ready for pickup tells Shopify the order is ready, and Shopify lets the customer know. The pack job shows Ready for the customer. - Mark ready for delivery marks the parcel ready in Floormode only. Shopify has no way to take that step from an app, so you run the delivery from Shopify as usual. A pickup or delivery parcel must hold everything the order still owes. Ship all never buys a label for such an order. ## Pack job statuses Status Means Not started Waiting at the station Scanning items Verification in progress Items verified Every item scanned; the job adds what is still needed, such as the weight Ready to fulfill Every item scanned and every required step done Queued for fulfillment Being pushed to Shopify Ready for the customer A pickup or delivery parcel, waiting for handover Fulfilled Shopify has it Failed The push did not succeed — it surfaces in Needs attention Cancelled Withdrawn ## See also - [Shipping] (/features/fulfillment/shipping/) — buying the label for the verified parcel. - [Item dimensions & capacity] (/features/inventory/item-dimensions-and-capacity/) — what makes cartonization accurate. - [Floor pack] (/features/floor/pack/) — the scanner-first version of this screen. - [Pack stations] (/features/settings/pack-stations/) — the printer, scale and camera of each pack table. - [Compatible hardware] (/getting-started/compatible-hardware/) — scanners, scales and printers that work. - [Inserts] (/features/fulfillment/inserts/) - [Gift messages] (/features/fulfillment/gift-messages/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/inserts/ # Inserts Put a flyer, a thank-you card or a sample in with an order. A flyer, a thank-you card or a sample can go in with an order. Floormode adds it to the order’s parcels by an automation rule, shows it to the packer at the bench, and takes it out of stock when the parcel is fulfilled. Shopify’s order is never changed: the insert is not an order line. ## On this page - The item - The rule - At the bench - Stock - Ending a campaign - Split orders - See also ## The item An insert is a Floormode item (Inventory → Items → New material), counted in pieces and not lot or serial tracked. Give it a SKU or a barcode so packers can scan it. Put its stock in bins like any other item, and count it like a box. ## The rule Settings → Packing → Add to the parcel lists the rules that add an insert. Add an insert opens the rule editor from a starting point: - Every order - Orders over an amount (the order total, in your store’s currency) - Orders with a tag - Orders with an item (an order holding a given SKU) - Orders to a country (the shipping address’s country; Shopify Markets are not read) Each rule’s Add to the parcel action has: Setting What it does Default Item The flyer, card or sample — How many 1 to 20 1 How often Once per order (in the first parcel started) or In every parcel Once per order Packer confirms it The packer scans the insert’s code or taps Added On Parcels that need a customs form Leave it out, or Include it (printed matter with no value): nothing is declared for it Leave it out An order takes at most 5 inserts. The same item from two rules is the later rule’s line. Only some warehouses. To send an insert from one warehouse only (a German flyer from your German site), give the rule a Warehouse is (or is any of) condition, joined with AND. The rule’s trigger must know the warehouse, for example Order routed. Any other form of the warehouse condition (is not, is none of, OR) is refused when you save. The same rules are in Settings → Automation: one list, two views. ## At the bench The bench lists each insert under Add to the parcel: “Add 1 × Spring flyer”, with its rule. Scan the insert’s code, or tap Added where your warehouse allows taps. If you skip it, tap Not added. If there is none left at all, tap None left: you get the run-out alert at once, and every bench shows the insert as Ran out (not required) until it is restocked. You can change your answer until a label is bought for the parcel or it is fulfilled. On the floor, the inserts have their own step once every item is scanned, before the photo of the open box: the photo, and its check, see them. Fulfil waits until each insert the packer confirms is added or not added. What a line can say: State Meaning To add Not recorded yet Added Recorded as in the parcel Not added Recorded as not in the parcel Ran out None left here: a packer tapped None left, or a parcel found none to take; its alert is open In parcel P-1042 A once-per-order insert another parcel of the order carries Item removed The item was deleted or can no longer be an insert Campaign ended The rule was switched off or deleted before this parcel added it ## Stock Each insert is taken from stock when its parcel is first fulfilled: the full quantity from one bin (never split across bins). An insert recorded as not added, or that ran out, takes nothing. When an insert runs out at a warehouse, you get one Packaging ran out alert for it there; it clears when the next parcel takes one, or when no rule adds the item any more. A parcel sent back to the bench keeps what its first fulfil took. ## Ending a campaign Switch the rule off (or delete it). Parcels not started yet stop getting the insert; a parcel that already added it keeps it. Switching the rule on again brings the insert back to parcels that have not added it yet. ## Split orders A once-per-order insert goes in the first parcel started. The order’s other parcels show “In parcel P-1042”. If that parcel is cancelled before it is fulfilled, the next parcel takes over. ## See also - [Pack] (/features/fulfillment/pack/) - [Order rules] (/features/settings/order-rules/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/gift-messages/ # Gift messages Print the gift message your customer typed on the gift slip, word for word. Floormode prints the gift message your customer typed, word for word, on the gift slip. It reads it from an order field you name. It never guesses it from the order note. Shopify keeps the fields a cart or a gift app adds to an order as Additional details on the order page. Floormode reads them as they are, finds the gift message, who it is for and who it is from, and prints them on the gift slip. Nothing is sent anywhere: no AI, no other service. ## On this page - 1. Add a gift-message field to your theme - 2. Map the field - 3. What prints - What changed with gift fields - For developers - See also ## 1. Add a gift-message field to your theme Skip this step if a gift app (Giftship, Giftnote) or a checkout field already collects the message. In Dawn and most themes, open Online Store → Themes → Edit code, then sections/main-cart-footer.liquid, and add this inside the cart footer: ```liquid ``` - attributes[Gift message] becomes the order’s Gift message field. - The checkbox is optional. It marks a gift without a message. - A name that starts with __ (attributes[__Gift message]) is private: the customer does not see it at checkout, and Floormode still reads it. Shopify Plus: a Checkout Blocks custom field set to Save as order attribute works the same way. Fields added in checkout cannot be filled in an Apple Pay or Google Pay express checkout, so keep the cart field too. ## 2. Map the field Open Settings → Packing → Packing slip (in the Advanced section) and press Edit gift fields. 1. Add a field. Pick its name from the list: it shows the field names on your newest 1,000 orders first, then the common gift fields. Or type a name no order has yet. 2. Holds: Gift message, To, From, or Marks a gift. 3. Stores (with two stores or more): read it on some stores only. Empty means every store. 4. Press Done, then Save in the page’s bar. Case and separators do not matter: Gift Note, gift_note and gift-note are one field. Up to 10 fields. The first field in the list that holds words wins. Under each saved field the card says what your newest orders show: On 7 recent orders, Not on your newest 1,000 orders (check the name in Shopify under Additional details), or A common gift field. Also read the common gift fields (on by default) reads these names without mapping them: Gift message, Gift note, Gift notes, giftnote_message, giftnote_to, giftnote_from, gift, is_gift, gift-wrap, gift-wrapping, gift-wrapped. Turn it off to read only your fields. ## 3. What prints The order The slip’s title What it prints of the gift The order note no gift, or Gift slips off Packing slip (label: Delivery note) nothing printed a gift message Gift slip To, the message, From not printed a gift without a message (marked, or To / From only) Gift slip To and From see below Order note on a gift slip decides the last row: Only when the gift has no message (the default: the card text may be in the note) or Never. It works with the common fields alone, so Gift: Yes with Never prints no note. The packer always sees the whole message, where it came from and what will print, at the pack station before printing. The order page shows the same line. Limits. The A4 / Letter slip prints up to 6 lines of the message and one line each for To and From. The label-size delivery note prints up to 2 lines per section. A longer text ends in “…”. Line breaks are kept. Letters the standard font lacks (Cyrillic, Greek) print in the label font; a character no font has prints as ?. A field longer than 500 characters, or past an order’s 50th field, cannot be kept by Floormode. If it is a gift message, the order still counts as a gift and the pack station says A gift field was too long or too many to keep: see the order in Shopify. A slip printed before you change a setting is not changed: reprinting a stored slip prints it as it was, and a new print after the change is a new slip. Archived orders reprint as they were archived. ## What changed with gift fields These print differently from before, even with nothing mapped: - private common fields (__gift-note, _giftnote_message) now count; - Giftnote’s giftnote_message, giftnote_to and giftnote_from are common fields, so To and From lines print; - a common message field Floormode could not keep now makes the order a gift (before, it did not). The single field of the old Gift field setting is not carried over: map it again. ## For developers packing_slip_settings_get / _set (REST and MCP) carry giftFields, commonGiftFields and giftNoteOnSlip. orders_get.gift and packing_get.gift answer { message, to, from, field, unavailable }. values_suggest with facet: "order_attribute_key" lists your orders’ field names with their order counts. ## See also - [Pack] (/features/fulfillment/pack/) - [Inserts] (/features/fulfillment/inserts/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/shipping/ # Shipping Rate-shop, buy, print and void carrier labels — plus manifests, pickups, delivery exceptions and freight. In Floormode, Shipping (/fulfillment/shipping) is where a verified parcel becomes a bought label. It also holds everything else that happens between the pack station and the carrier’s van. ## On this page - Rates and labels - Manifests, pickups and exceptions - Freight - International - Setup - See also ## Rates and labels You see every rate for a shipment, sorted by price and speed, and buy the one you want. Labels come as a 4×6 thermal label (ZPL) or a PDF. Most can be voided if you made a mistake; labels of Hermes and DPD Germany (carriers in Germany) cannot, because those carriers offer no way to take a label back, so check the parcel before you buy. Where you have [shipping rules] (/features/settings/automation/) configured, the rule cascade picks the service for you — the cheapest rate, a preferred carrier per country, or the cheapest non-express service when the fast option is not worth it. Without a matching rule, the cheapest rate is preselected: the fulfillment order’s fulfill-by date is when it must ship, not when it must arrive. A purchase that did not finish. If the carrier does not answer while a label is being bought, a label may still exist, so Floormode never buys a second one blindly. Where a safe retry is not possible (DHL, UPS and Hermes), the shipment asks you after five minutes. Check your carrier account first, then choose No label was created to buy it again, or A label exists and enter its tracking number. You print that label from your carrier account; its tracking still goes to Shopify with the parcel. With Sendcloud or another shipping platform, choose Buy again on the shipment: it buys the same rate, and a label the carrier already made comes back, so you pay once. ## Manifests, pickups and exceptions - End-of-day manifest — the document the driver takes, listing everything going out today. - Scheduled carrier pickups — booked from here rather than by phone. - Delivery exceptions queue — parcels the carrier has flagged: failed attempts, address problems, parcels returning to sender. They also appear in [Needs attention] (/features/home/needs-attention/) on Home. ## Freight Freight (LTL/FTL) handles pallets and oversized goods that will not go as parcels: handling units, multiple freight quotes side by side, and a Bill of Lading with accessorials. Freight needs its own account — a ShipEngine LTL account for less-than-truckload, or Uber Freight for full-truckload. Uber Freight needs enrollment. Floormode books with Uber Freight through your own shipper account, so you enrol with Uber Freight first: 1. Request a shipper account on Uber Freight’s website ([uberfreight.com] (https://www.uberfreight.com)), or ask your Uber Freight account manager if you already ship with them. 2. Once you are enrolled, ask your account manager for API access. Uber Freight issues an OAuth client id and client secret, and your shipper id if your company has more than one shipper account. 3. In Floormode, open Settings → Shipping & carriers, choose Connect carrier → Uber Freight and enter them. The secret is stored encrypted and never shown again. ## International Floormode looks at every parcel from where it ships: the address of the warehouse’s Shopify location, or your store’s country when the location has no address. A US store’s parcel to another state is domestic, as is a UK store’s parcel within the UK or an Australian store’s within Australia. - Within your country there is nothing to declare. No customs declaration, no customs form. - Within the EU there is nothing to declare either. The EU is one customs area, so a parcel from a warehouse in one EU country to another EU country needs no declaration; the shipment says “No customs declaration needed inside the EU”. - Across a customs border, every parcel needs a customs declaration. From the US to Canada, from the UK to the EU, from Australia to New Zealand, from the EU to Switzerland, Norway or the UK. A few places inside EU countries lie outside the EU’s customs area and count as abroad too: the Canary Islands, Ceuta and Melilla, the French overseas departments, Åland, Heligoland and Büsingen, Livigno, Campione d’Italia and Mount Athos. The shipment shows a Customs marker on the Shipments list and on the pack station, and its rate panel says where it goes (“Ship to: Toronto, Canada (CA)”). - When Floormode knows neither address nor country for where a parcel ships from, it asks for no declaration and leaves it to the carrier. Map each warehouse to its Shopify location to avoid this. - The declaration fills itself from your Shopify products. Each item of the parcel becomes one line: its HS code and country of origin from Shopify (Product → Shipping → Customs information), its weight, and the price the customer paid, in the order’s currency. Fix a missing HS code in Shopify and press Fill from products, or correct a line by hand for this parcel only. - No label without a complete declaration. While a line lacks a description, quantity, value, weight, an HS code (6 to 13 digits) or a country of origin, Floormode fetches no rates and buys no label, and says which item is missing what. Ship all skips such a parcel with the same sentence. - Which carriers cross a border. EasyPost (with your own linked carrier accounts), Sendcloud, DHL Express and Aramex ship abroad from anywhere and send the declaration with the label. Royal Mail and DHL eCommerce UK do from the UK, Bring from Norway, DHL eCommerce from the United States, and DHL connected directly from Germany (below). UPS and FedEx connected directly, ShipEngine parcels and the national carriers (USPS, Canada Post, Purolator, Evri, DPD UK, Hermes, InPost, PostNL, The Courier Guy, Fastway, Pargo) ship within one country; DPD Germany, GLS, Austrian Post, Mondial Relay and Packeta within the EU, PostNord within the Nordics, Correos within Spain’s peninsula and the Balearic Islands. A carrier account that cannot reach the destination is marked in New shipment and refused before the carrier is asked. - The customs form prints beside the label. The carrier generates it (CN23 or commercial invoice) from the declaration; open it as a PDF in the rate panel and print it on an office printer, and the pack station reminds the packer to attach it. - Leaving the EU, goods worth €1,000 or more also need an export declaration (ATLAS), which Floormode does not file: the declaration says so. When lines are in another currency than euros, it says it could not check the limit. - Changing the declaration after getting rates drops those rates: get rates again, so the declaration you buy is the one that was rated. ### In Germany: DHL abroad - DHL Paket International. Add your DHL Paket International billing number (procedure 53) and a contract estimate to the DHL account, and parcels to Austria, Switzerland, the UK or Norway get a DHL Paket International rate (up to 120 × 60 × 60 cm). With a Warenpost International billing number (procedure 66) too, parcels up to 1 kg and 35.3 × 25 × 10 cm get that cheaper rate beside it, once the box size is known. Warenpost International is tracked to the door only when your contract books it as Premium. Without the international billing number, a parcel abroad is refused with a sentence saying which number to add. - Letters abroad. A shipment marked as a letter or a large letter goes with DHL only abroad, as Warenpost International; within Germany, frank it with Deutsche Post Internetmarke. - Not to the US. DHL takes goods to the US and Puerto Rico only with its duty-paid service, which Floormode does not book yet: use another carrier there. - The customs form states the order number as the invoice and the shipping the customer paid, after discounts, as postal charges. Warenpost International prints its CN22 on the label itself. If DHL returns no customs form, the rate panel and Ship all say so: print it in the DHL business portal. - Heligoland and Büsingen ship with DHL as ordinary DHL Paket within Germany, with no declaration. For Büsingen, attach two copies of the invoice to the outside of the parcel. ### Landed cost Landed cost (duties plus taxes, via Zonos) applies to freight bookings only and is configured by Floormode’s operator; there is no merchant Zonos connection. A freight booking with duties paid (DDP) that crosses a customs border is priced, from any country to any country. Its customs lines and the freight price must be in one currency; otherwise the booking still goes through and says why no landed cost was priced. ## Setup Everything you need is reachable from the empty state on this tab: - Carrier account and label printer (PrintNode) — under Settings → Shipping & carriers (/settings/shipping). - Freight account — ShipEngine LTL or Uber Freight, as above. - Customs information — the HS code and country of origin on your Shopify products, for parcels that cross a customs border. Note Without a printer you can still download and print labels by hand. PrintNode saves a step; it is not a requirement. ### Which carriers Connect carrier offers each of them with the fields it needs. It lists your store’s own country’s carriers first, then the ones that ship from anywhere; the national carriers of other countries come last, under From other countries, still there for a warehouse abroad. - Any country: Sendcloud, EasyPost, ShipEngine, UPS, FedEx, DHL Express and Aramex. UPS and FedEx connected directly ship within one country; DHL Express ships worldwide with the commercial invoice and, until Floormode’s labels have been checked on DHL Express’s test environment, connects only with test environment credentials; Aramex collects cash on delivery. - From the United States: USPS, Pitney Bowes (USPS), DHL eCommerce (US), Amazon Shipping, and OnTrac within its network (with the former LaserShip area). Pitney Bowes (USPS) buys USPS labels at Pitney Bowes’ commercial prices with no USPS business account, closes out with the USPS SCAN form and, until Floormode’s labels have been checked on Pitney Bowes’ sandbox, connects only with sandbox credentials. OnTrac cannot be connected yet: its key travels in each request’s address, which Floormode’s request traces keep. DHL eCommerce’s SmartMail Parcel is delivered by USPS, its international parcels carry the customs lines, and the close-out prints the driver’s manifest; until Floormode’s labels have been checked on DHL eCommerce’s sandbox, it connects only with sandbox credentials. - From Canada: Canada Post and Purolator. - From the United Kingdom: Royal Mail (with Parcelforce), Evri, DPD UK, DHL eCommerce UK (formerly DHL Parcel UK), InPost UK (within Great Britain: to the InPost Locker your customer picked, or dropped at a locker for delivery to the door) and Amazon Shipping (to the door, or to an Amazon Hub Counter with Deliver to Counter). Until each has approved Floormode’s labels, Evri connects only with its sandbox credentials, DHL eCommerce UK only with its test system’s credentials, InPost UK only with its test credentials (until Floormode has checked InPost’s answers for unpaid labels), and DPD UK not at all (use it through Sendcloud UK, EasyPost or ShipEngine). DHL eCommerce UK offers only the services DHL serves for each parcel’s route and size, priced at your contract estimates, and books Jersey, Guernsey and abroad with the customs lines; Northern Ireland waits for the Windsor Framework declaration. - From Germany: DHL Paket DE, Hermes Germany, DPD Germany and GLS. For letters, Deutsche Post Internetmarke: postage for letters, large letters and the Warensendung, paid from your Portokasse, offered only for shipments from a warehouse in Germany. - From France: Colissimo (La Poste), to the door with or without a signature within the EU, with Colissimo Retour France labels for returns; Colissimo Point Retrait is not offered yet. Colissimo prices nothing through its API (your contract decides) and cancels no label (an unused one is never billed). Until Floormode’s labels have been checked on Colissimo’s test system, it connects only as a test connection. - From Spain: Correos, Paq Estándar and Paq Premium to the door within the peninsula and the Balearic Islands, priced at your contract estimates, with PDF or ZPL labels. Until Floormode’s labels have been checked on Correos’s test system, it connects only as a test connection. - From Austria, Belgium, France and Ireland: GLS, on your GLS contract of that country (you pick the country when you connect). - Amazon Shipping (US and UK): you sign in to Amazon Shipping instead of typing a key (Authorize with Amazon), one connection per region, on your rate card; Amazon collects from your pickup location. Within the US or within Great Britain, one parcel per label; Northern Ireland, returns and Amazon’s collection forms are not offered yet. Until Amazon has reviewed Floormode’s labels, it connects only to Amazon’s sandbox. UPS Ground Saver is a choice on a UPS connection: on once UPS enabled it on your account. - From Austria: Austrian Post (Österreichische Post), on your Post business contract through its Post-Labelcenter, within Austria and to the rest of the EU where no customs declaration is due, as a PDF or ZPL label. Post prices nothing through its API (your contract decides); a label can be voided until Post has the parcel. Tracking updates, Post branches and lockers, cash on delivery and returns are not offered yet. Until Floormode’s labels have been checked on Post’s test system, it connects only as a test connection. - Within the EU: Mondial Relay and Packeta; InPost Poland, and PostNL from the Netherlands and Belgium. - From South Africa: The Courier Guy, Fastway and Pargo. The Courier Guy and Fastway run on the same platform, ShipLogic, each with its own API key. - From Norway, Sweden and Denmark: Bring, to the door or a Bring pickup point, and from Norway abroad with the customs lines. Until Floormode’s labels have been checked on Bring’s test system, it connects only as a test connection. - From Sweden, Denmark, Norway and Finland: PostNord, within the Nordics where no customs declaration is due, to a PostNord service point or parcel box, to the door or to a business, priced at your contract estimates (you pick the PostNord country when you connect). Until Floormode’s labels have been checked on PostNord’s test system, it connects only as a test connection. - From Australia and New Zealand: Sendle, Australia Post / StarTrack, Aramex Australia and CouriersPlease from Australia; NZ Post from New Zealand. Aramex Australia has no test system, so its first label is a real one. - Freight: Freightview and Uber Freight. InPost, Mondial Relay, Packeta, PostNL, Bring, PostNord and The Courier Guy deliver to pickup points and lockers too, Pargo to its pickup points. ### The test carrier No carrier account yet? Use the test carrier on the empty state, or at the pack station, makes TEST labels so you can try the flow: the parcel is fulfilled without tracking and no shipping confirmation goes to the customer. Connecting a real carrier turns it off; the Test carrier switch under your carrier accounts turns it on again beside the real one. ## See also - [Pack] (/features/fulfillment/pack/) — what produces the parcels rated here. - [Carriers & packaging] (/features/settings/carriers-and-packaging/) — accounts, printers, boxes. - [Customer notifications] (/features/settings/customer-notifications/) — telling the customer the label exists. - [Collection times] (/features/fulfillment/collection-times/) - [Outbound lanes] (/features/fulfillment/outbound-lanes/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/collection-times/ # Collection times When each carrier's driver comes, and how the queues and the end of day follow it. When does your carrier’s driver come? Tell Floormode once, and the work of the next collection is picked and packed first, the outbound lanes close per collection, and End of day is offered for each collection that passed. Nothing changes until you add a time: orders are worked oldest first, as before. ## On this page - Set your times - What you then see - End of day - For a bigger operation - See also ## Set your times Settings › Shipping & carriers › Collection times, per warehouse: - Carrier: a connected carrier account, or Every carrier — one time for the whole warehouse, also when you buy labels elsewhere and have no carrier connected yet. Every carrier is the default for orders whose carrier is not chosen yet; lanes never use it. - Services: leave empty for all of the carrier’s services, or tick the ones this time is for. A service’s own time comes before an all-services time, so “Ground 16:00” and “Express 18:00” can share one carrier. - Days: leave empty for every packing day, or pick days. A day that is not one of the warehouse’s packing days is said so: the time is not used then. - Collection times: up to six a row, in the warehouse’s time zone. - Use for orders whose carrier is not chosen yet: one row per warehouse. Orders in by (Settings › Orders & dispatch, the warehouse’s packing days): an order that arrives fewer than this many minutes before a collection goes to the next one. Marketplaces may ask for a buffer — Amazon Seller Fulfilled Prime names 30 minutes. Empty is 0. Times show in your own clock format (4:00 PM or 16:00). ## What you then see - Pick queue: Ships soonest is the default order once the warehouse’s open work is stamped (a few moments after your first save). Oldest first stays one choice away. Each order says “Ships 16:00”, “Ships Tue 16:00”, or “Ships today” when no truck takes it (pickup, local delivery); a Ships column is in Columns, and the Ships today view shows only the work for today’s collections and the ones missed. - A collection that passed with work still open says “Missed 16:00”; that work keeps its place at the front. The late tile and its 24 hours are unchanged. - Start picking, batches and the pack bench’s Up next take the next collection’s orders first; Start picking, a pick batch and the pack screen say when their work ships. - Order page: “Ships Tue 16:00” beside the due date, in the warehouse’s time zone. - Outbound lanes: a lane’s collections follow its carrier’s times; a Ground parcel joins 16:00 and an Express parcel 18:00 in the same lane. ## End of day Shipping › Logistics › Collections today lists today’s collections with the work to pack (all carriers) and, after a collection passes, offers End of day per carrier: “DHL · Collection 16:00 passed · 23 labels to close out”. It closes out only that collection’s labels — bought before it, of the services it serves — and leaves the labels a lane closes itself. Yesterday’s leftovers are offered before today’s first collection. A carrier with no time set is offered the labels bought before today. A carrier that closes every open label of the account at once (a SCAN form service, for example) says so and asks you to confirm the whole account. More labels than the carrier takes in one close-out read “Close out 30 of 537” (DHL Paket takes 30 a call; most carriers 200). ## For a bigger operation - Set rows per warehouse; each counts in its own time zone. - Several collections a day (multi-shift): up to six times a row. - Chilled goods Monday to Wednesday: a row with those days. - Times from a TMS: the same through the API and MCP (collection_times_save, collections_today, manifests_close_out with collectionAtMs). ## See also - [Outbound lanes] (/features/fulfillment/outbound-lanes/) - [Shipping] (/features/fulfillment/shipping/) - [Queue] (/features/fulfillment/queue/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/outbound-lanes/ # Outbound lanes A place on your dock for each carrier's parcels: load them, close the collection, hand over to the driver. In Floormode, an outbound lane is a place on your dock where one carrier’s parcels wait for its driver: a staging lane, a cage, a hamper. Each parcel is scanned into its carrier’s lane, and when the driver comes the lane’s collection is closed, the carrier’s manifest is printed and the parcels are handed over. Lanes are optional. Until you add one, nothing changes: no screen, no step. ## On this page - Setting up - The day on the floor - When something goes wrong - Who may do what - See also ## Setting up Go to Settings › Shipping & carriers › Outbound lanes and choose Add lane. - Lane code: the code on the lane’s label, which the floor scans (USPS-1, RM-CAGE-1). - Carrier account: whose parcels go here. - Services (optional): service codes this lane takes. A lane for a service is chosen before a lane for all services, so you can keep a separate cage for express parcels. - Collection times (optional): set them under Settings › Shipping & carriers › Collection times (the carrier’s times; the lane editor shows them read-only). They count in the warehouse’s time, on its packing days (11:00, 16:30). A parcel loaded after a collection time, or after its collection was closed, joins the next one. With no times, one collection stays open until you close it. - Default lane: with several lanes for one carrier, the one a parcel is sent to first. - Closing makes the carrier’s manifest: on for carriers that close out (USPS SCAN form, Australia Post order summary, Royal Mail, Canada Post, DHL Paket). Off, or for a carrier without a close-out, closing only freezes the collection. Australia Post and Canada Post make it at every close, as they take nothing without it. A lane keeps its carrier while its collection is under way: hand the collection over first. An empty open collection changes carrier with the lane. - The lane’s location belongs to the lane: change or archive it here, not in the layout. Archive the lane first to use the location for anything else. Labels bought before you added a lane for their carrier (in the last 14 days) are added to Not in a lane within a few minutes. ## The day on the floor Open Load parcels in Floor Mode. 1. Scan a lane, then its parcels. Or scan a parcel first: the screen says which lane it goes to (“This parcel goes to RM-CAGE-1”); scan that lane. 2. Each scan answers at once: Loaded · USPS-1 · 34 in the 16:30 collection, Already in USPS-1, Moved to USPS-2, or what is wrong. A label without a tracking number (a franked letter) loads by its packing slip or its order number. Undo beside a scan takes that parcel back off the lane. 3. When the driver comes, tap Close collection. The screen names the collection (“Close the 11:00 collection”) and the parcels loaded for a later one, which stay unless you take them along. 4. The carrier’s manifest is made in the background: Manifest: making…, then SCAN form ready · Print. With a document printer at the station it prints there; otherwise it opens. 5. Tap Mark collected when the driver has taken the parcels. Australia Post and Canada Post take nothing without their manifest: the screen waits for it. A manifest made in several parts (one per carrier batch) shows All 2: each part prints or opens on its own. A closed collection stays on screen until it is collected, with its Print and Mark collected, even while new parcels load into the next one. With several live collections, the switcher above the panel chooses which one you see. ## When something goes wrong - Wrong lane: “This parcel goes to RM-CAGE-1 (Royal Mail Tracked 48)”. Put it in its own lane. - Label voided while in a lane: “Label voided. Take it out.” The collection counts it under To take out until someone takes it out: open To take out from ⋯ on the Load screen, or the collection in Shipping › Collections, and tap Taken out for each parcel. A void that was requested and not answered yet says “Void requested. Don’t load.” - Not in a lane: labels bought that are in no lane and that the carrier has not scanned yet. Open it from ⋯ on the Load screen, or from Shipping › Collections. A parcel leaves the list once it is loaded, voided, or the carrier’s tracking shows it on its way. - Two parcels share a number: scan the packing slip instead. - The manifest failed: the carrier refused it. Fix the cause (an expired account, a parcel it does not know) and choose Make manifest again in Shipping › Collections. - Partly made: the carrier refused some parcels by name. Resolve the manifest in Shipping › Manifests & pickups, then make it again. - Not answered yet: the carrier did not answer. Make it again asks the same request again and never announces the parcels twice; if the carrier has no record, resolve the manifest as not announced first. - Royal Mail manifests every label of the account not yet manifested at the shipping location, not only the collection’s: the close says so. - Collection times changed: an open collection keeps its time and shows “not in the lane’s times”; close it as usual. New loads use the new times. ## Who may do what - Loading, taking out, closing and printing the manifest: the Floor role (Load parcels into outbound lanes), Managers and Admins. - Setting up lanes: whoever sets up warehouses or buys labels. A person who only loads lanes can print a collection’s manifest, never a label. ## See also - [Collection times] (/features/fulfillment/collection-times/) - [Shipping] (/features/fulfillment/shipping/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/waves/ # Waves Advanced. Hold picking work back and release it to the floor in waves instead of letting every order flow straight through. Waves (/fulfillment/waves) is the advanced tab that decides when paid orders reach the floor. A [wave] (/reference/glossary/#waves) is a group of orders released for picking together. Floormode used to call a wave a “release”; the old address /fulfillment/release still opens this tab. ## On this page - Continuous is the default - When holding work back helps - How waves work - Releasing at a set time - Wave statuses - See also ## Continuous is the default Out of the box, release is continuous: a paid, allocated order becomes floor work immediately. Most warehouses should leave it that way — continuous flow is simpler, and the floor pulls work when it is ready rather than waiting for a wave to be cut. Note Holding work back is opt-in. Waves is marked Advanced precisely because turning it on is a decision about how your warehouse runs, not a setting you tune casually. ## When holding work back helps Waves earn their keep in a few specific situations: - Carrier cutoffs — cut a wave timed to the collection so everything in it makes today’s van. - Zone balancing — release work sized to the people actually on shift, rather than flooding the queue. - Priority separation — release express orders as their own wave so they cannot get buried behind standard ones. If none of those describe your operation, continuous release is the right answer. [anchor: how-release-works] ## How waves work Work accumulates instead of flowing to the queue. You create a wave — by warehouse, priority, carrier cutoff or whatever filter fits — and when you click Release wave, everything in it becomes floor work at once, appearing in the [queue] (/features/fulfillment/queue/) as normal pick tasks. There is no wave setting elsewhere: each wave’s timing is decided right here, when you create it. ## Releasing at a set time Give a wave a time in Send to picking at when you create it. At that time it goes to picking by itself, if it is still planned. The list shows the time under the wave’s name. The same plan rules apply as when you click Release wave. If your plan does not allow new orders, the wave stays planned, the list says it did not go, and a warning appears under Alerts. It is not tried again by itself: release it by hand once your plan is confirmed. Leave the time empty to release the wave by hand. To give a planned wave a time, click Set time on its row; to move its time, click Change time. Remove the time sends it by hand again. A time in the past is refused. [anchor: release-statuses] [anchor: waves] ## Wave statuses A wave moves through planned → released → closed. Closing or deleting a wave puts its unfinished tasks back into continuous picking rather than dropping them. ## See also - [Queue] (/features/fulfillment/queue/) — where released work lands. - [Fulfillment settings] (/features/settings/fulfillment/) — how work is assigned once it reaches the floor. - [Plain-English names] (/getting-started/plain-english-names/) — why some industry words stay. Last updated: 9 November 2026 --- Source: https://docs.floormode.app/features/fulfillment/cluster-picking/ # Cluster picking Enhanced plan. Pick several orders in one walk, each order in its own slot on the cart. [Enhanced plan] (/getting-started/subscription-plans/) Floormode’s Cluster picking lets one picker walk the building once and fill several orders at the same time, each order in its own [slot] (/reference/glossary/#slot) on the cart. Some warehouse software calls it multi-order picking. ## On this page - How it differs from batch picking - When it pays off - The trade-off - See also ## How it differs from batch picking The three [pick batch] (/reference/glossary/#pick-batch) methods answer different problems: Method The walk The sort Single-order batches One order per batch Nothing to sort Batch picking One SKU pulled once for many orders Sorted afterwards at the pack station Cluster picking Many orders in one walk Sorted during the pick, into the cart’s slots The distinction that matters is when the sorting happens. Batch picking defers it to a separate step; cluster picking does it at the shelf, so what leaves the aisle is already order-separated and can go straight to packing. ## When it pays off Cluster picking wins where orders are small and scattered — a handful of lines each, spread across the building. Walking that building once for six orders instead of six times is where the whole saving comes from. It wins least where orders are large, or where each order already fills a walk on its own. In that case a single-order pick is already efficient and adding slots just adds handling. ## The trade-off Each order needs its own slot, so the cart’s slots cap how many orders one walk can hold, and every pick carries a “which slot?” decision. That decision is scanner-guided rather than remembered — but it is still a step that single-order picking does not have. A [tote] (/reference/glossary/#tote) is one container without slots: its orders are sorted at the pack station. Note This is one of the industry terms kept on purpose. It carries a small ⓘ with a one-sentence explanation the first time it appears on a page, rather than being renamed into something vaguer. Included on the Enhanced plan. ## See also - [Batches] (/features/fulfillment/batches/) — the three methods in context. - [Subscription plans] (/getting-started/subscription-plans/) — what else Enhanced unlocks. - [Floor pick] (/features/floor/pick/) — the picker’s screen. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/overview/ # Inventory Stock across warehouses, what is arriving, where it lives, and every movement that got it there. Inventory (/inventory) is the biggest section of Floormode: eight tabs covering what you have, what is coming, where it sits, and how every number got to be what it is. Shopify is the source of truth for what is sellable. Floormode is the source of truth for where in the building it is and why the number changed — and it syncs availability back to Shopify from every linked warehouse. Not everything on your shelves is a Shopify product, though. With a sibling app connected, raw materials, sub-assemblies and custom items are stocked here too — see [Local items] (/features/inventory/local-items/). ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Stock] (/features/inventory/stock/) Per-variant stock across warehouses in Shopify's own vocabulary: on hand, committed, available, incoming. [Receiving] (/features/inventory/receiving/) Expected deliveries, receiving progress, discrepancies and putaway — the office view of booking goods in. [Counts] (/features/inventory/counts/) Cycle counts a few bins at a time, with variances, an approval queue and optional blind counting. [Adjustments & movements] (/features/inventory/adjustments-and-movements/) Every reason-coded adjustment, and the full stock ledger of what moved, why and who did it. [Lots & serial numbers] (/features/inventory/lots/) Where a lot or a serial-numbered unit is, where it came from and which orders it went to. [Local items] (/features/inventory/local-items/) Goods that are not on Shopify — raw materials, sub-assemblies and custom items — and the Unplaced items worklist. [Bins] (/features/inventory/bins/) Bin master data, the bulk location generator and bin label printing. [Placement] (/features/inventory/placement/) Advanced. Home bins, putaway rules, re-slotting suggestions and automatic pick-bin replenishment. [Item dimensions & capacity] (/features/inventory/item-dimensions-and-capacity/) Optional product dimensions and per-location capacity, so the app can answer 'is this bin full?' [Backorders & oversell] (/features/inventory/backorders-and-oversell/) Allow selling beyond on-hand, per warehouse, and what arriving stock does for waiting orders. ## Key concepts - [On hand] (/reference/glossary/#on-hand), [committed] (/reference/glossary/#committed), [available] (/reference/glossary/#available), [incoming] (/reference/glossary/#incoming) — the four numbers on every row. - [Available to promise] (/reference/glossary/#atp) — what you can actually sell right now. - [Bin] (/reference/glossary/#bin) — where stock physically sits. - [Expected receipt] (/reference/glossary/#expected-receipt) — an inbound delivery you are waiting on. - [Putaway] (/reference/glossary/#putaway) — moving received goods from the dock to their bin. - [Cycle count] (/reference/glossary/#cycle-count) — counting a few bins at a time, all year round. - [Local item] (/reference/glossary/#local-item) — stock that exists here but not on Shopify, held for a connected sibling app. ## Where to next - [Floor receive] (/features/floor/receive/) — where goods are actually booked in. - [Replenishment] (/features/insights/replenishment/) — what to reorder, from these numbers. - [Warehouses] (/features/settings/warehouses/) — the stock policies behind the behaviour. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/stock/ # Stock Per-variant stock across warehouses — on hand, committed, available and incoming, with the documents behind each number. In Floormode, Stock (/inventory/stock) shows per-variant stock across every warehouse, using Shopify’s own vocabulary rather than inventing a parallel one. ## On this page - The four numbers - Drilling into a row - Reordering from here - See also ## The four numbers Number Means [On hand] (/reference/glossary/#on-hand) What is physically in the building. [Committed] (/reference/glossary/#committed) Already promised to open orders. [Available] (/reference/glossary/#available) On hand minus committed minus unavailable (damaged, quality control, safety stock and a blocked lot’s units) — what is left to sell. [Incoming] (/reference/glossary/#incoming) On a receipt that has not fully arrived. Using Shopify’s words matters more than it sounds. A merchant who already understands “committed” in the Shopify admin does not have to learn a second meaning here — the numbers reconcile because the vocabulary does. Incoming is clickable: it drills straight into the [Receiving] (/features/inventory/receiving/) tab, filtered to that product, so “where is my stock?” is one click rather than a search. ## Drilling into a row Open any row for the per-warehouse breakdown. That view shows: - The four numbers for each warehouse separately. - Bin reservations — which bins are holding stock for which orders. - The documents causing each number — the receipt behind an incoming figure, the orders behind a committed figure. That last point is the one that ends arguments. A number you disagree with is traceable to the document that produced it, not just asserted. ## Reordering from here Low-stock rows offer + Reorder, which takes you to [Insights → Replenishment] (/features/insights/replenishment/) already filtered to that SKU. You never have to re-find the product you were just looking at. ## See also - [Receiving] (/features/inventory/receiving/) — what the incoming number is made of. - [Movements] (/features/inventory/adjustments-and-movements/) — the ledger behind every change. - [Replenishment] (/features/insights/replenishment/) — where + Reorder lands. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/stock-differences/ # Stock differences with Shopify What Floormode does when its shelf count and Shopify's quantity disagree, and how to resolve it. A live warehouse keeps Shopify’s quantity in step with the shelves. When the two disagree, Floormode tells you and asks you to look, instead of guessing which side is right; only a difference found while going live or during a stock check pauses that item’s updates. ## On this page - What a stock difference is - When Shopify shows a different number - Before you count - Count every bin - Confirm the new total - Parcels with missing or extra goods - Stock Shopify does not track - When to count again - See also ## What a stock difference is Shopify reported a quantity for an item that does not match what Floormode has on shelves for that location. Sales, picks and receipts continue. A difference found while going live or during a stock check holds that item’s Shopify update until it is resolved; a difference the alert reports later does not. ## When Shopify shows a different number An alert on Home and under Insights → Alerts says which item and which location disagree. The alert only reports: updates for the item keep flowing. Reset the number in Shopify, or record an adjustment here, and the alert clears itself on the next Shopify update. ## Before you count Finish open shipments for the item and put released goods back into their bins. A unit that sits in a parcel or on a pack station is not shelf stock. ## Count every bin Open the item in Inventory → Stock and start the review. Count the item in every listed bin and lot, including goods that were never recorded. Enter what you see, not what you expect. ## Confirm the new total The review shows the verified total and corrects Shopify’s on-hand quantity to it. Shopify updates resume for the item once the correction is recorded. ## Parcels with missing or extra goods A shipped parcel with fewer or more units than picked is reviewed in the item’s stock drawer under Inventory → Stock. Record what was actually in the parcel; Floormode corrects the shelf and, where needed, the Shopify quantity. ## Stock Shopify does not track An item with Shopify tracking off has no Shopify quantity to compare. Floormode keeps it as local stock only; a review records what is on the shelf and sends nothing to Shopify. ## When to count again Count again when the difference reappears after a correction, or when a bin was moved or emptied outside Floormode. A count task on the bin is the quickest way. ## See also - [Stock] (/features/inventory/stock/) - [Counts] (/features/inventory/counts/) - [Go live] (/getting-started/go-live/) Last updated: 27 September 2026 --- Source: https://docs.floormode.app/features/inventory/receiving/ # Receiving Expected deliveries, receiving progress, discrepancies and putaway — the office view of booking goods in. In Floormode, Receiving (/inventory/receiving) is where goods arriving are booked in and reconciled. It shows what you are expecting, how far each delivery has been booked in, where expected and received disagree, and what still needs putting away. ## On this page - Booking goods in: the desk and the floor - What happens after: the warehouse’s receiving policy - Straight to packing (cross-docking) - Reading a receipt - Discrepancies and over-receipt - Where expected receipts come from - See also ## Booking goods in: the desk and the floor Goods can be booked in two ways, and both write the same receipt: - At the desk. Open a receipt and use Receive on a line: enter the quantity and, if you want, the bin. Leave the bin empty and Floormode suggests one. This suits a delivery checked against a paper delivery note. - On the floor. [Floor Mode → receive] (/features/floor/receive/) books in by scanning the item, confirming the quantity and scanning the bin. ## What happens after: the warehouse’s receiving policy Where received goods go first is the warehouse’s receiving policy (Settings → Receiving & stock, the warehouse’s Receiving card): Policy Received goods go to The next job Straight to a shelf The bin the receiver scans, or the suggested shelf None: putaway happens as goods are received. At the dock, shelved later DOCK-01 A putaway task brings them to a shelf on the floor. Check goods first (inspection) QC-IN-01 An inspection: passed units go to DOCK-01 and get a putaway task; failed ones go to HOSP-01 or QUAR-01. Goods on the dock or in inspection are on hand but not offered for sale until they reach a sellable shelf. ## Straight to packing (cross-docking) When a delivery brings the units an order is waiting for, they can skip the shelf. Turn on Send units for waiting orders straight to packing in the warehouse’s Receiving card (Settings → Receiving & stock). It is off by default. With it on, a booking can send a waiting order’s units to packing in the same step. An order goes only when: - the booking alone completes it: everything it still needs is the item (and lot) just booked, into that bin, and nothing of it is picked yet; - it could be picked right now: not on hold, and not waiting for a planned release or a later pack day. A booking sends a few orders at most, oldest first. Any other order is picked from the shelf as usual, and so is the rest of the delivery. A booking is never refused because of this. - The receiver is told where the units go, for example Take 3 to packing for #1001, and Done names the orders again. - The order arrives at packing as if it had been picked, so nobody walks to a shelf for it. It works with the Straight to a shelf policy. Under a dock policy the switch keeps its value but does nothing, because goods wait at the dock first. ## Reading a receipt Open a receipt (/inventory/receiving/:id) to compare expected against received, line by line. Each receipt carries a status: Status Means Expected Announced, nothing booked in yet Being received Partly booked in Received Complete Cancelled Withdrawn Under the lines sits [putaway] (/reference/glossary/#putaway): received goods sitting in a receiving bin still have to reach their home. Until they do, the stock is on hand but not yet pickable from where a picker would look. ## Discrepancies and over-receipt A [discrepancy] (/reference/glossary/#discrepancy) is any line where received ≠ expected — short, over, or the wrong thing entirely. They are surfaced rather than quietly absorbed, because a supplier who consistently ships 98% is a fact worth having. Over-receipt tolerance (Extra units a delivery may bring) is a per-warehouse policy on Settings → Receiving & stock (/settings/stock): how much more than expected the floor is allowed to book in before the app pushes back. Where a location has a capacity set, putaway also warns on over-receipt into a bin that cannot hold it. ## Where expected receipts come from An [expected receipt] (/reference/glossary/#expected-receipt) is a delivery you are waiting on. Today those are created in Floormode — from a replenishment suggestion, a transfer, or entered directly. Note This changes when Floormode is connected to a sibling app. Where Logistified owns your purchasing, purchase orders and transfers announce themselves here as expected receipts — with their supplier and expected date — rather than being typed in twice, and the Source column tells announced deliveries apart from ones you created. [Integrations → Logistified] (/integrations/logistified/) covers what travels, what goes back, and how revisions and cancellations behave. [Who writes Shopify] (/integrations/who-writes-shopify/) covers which warehouses are allowed to receive against which document. ## See also - [Floor receive] (/features/floor/receive/) — booking goods in by scan. - [Stock] (/features/inventory/stock/) — the incoming number these receipts produce. - [Placement] (/features/inventory/placement/) — the putaway rules that decide where goods go. - [Dock doors and arrivals] (/features/inventory/dock-doors/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/dock-doors/ # Dock doors and arrivals Plan when a delivery arrives at which dock door, check it in and land the goods in the door's bin. Floormode can plan when a delivery arrives, at which dock door, and land the goods in that door’s own bin. Nothing here is required: a warehouse that receives straight to the shelf keeps working exactly as before. ## On this page - Dock doors - Receiving at a door - Plan arrivals - The put-away tour from a door - Correcting a dock booking - For integrations - See also ## Dock doors Add a door under Settings → Warehouses → your warehouse → Zones, stations & staff → Add station, kind Dock door. - Direction: Inbound (the default) or Inbound and outbound. A door that only ships is an outbound lane’s dispatch station (see outbound-lanes.md). - Door bin code (optional): the code of the door’s own bin. When empty, the bin takes the door’s code. The bin is named once: renaming the door later keeps the bin’s code. - The door’s bin belongs to the door. It is never picked from, never sold, never counted by a count task, never suggested for put-away and never a product’s home. You cannot edit, move, archive or retype it from Locations: edit the door instead. - Turning a door off keeps its bin; turning it on again uses the same bin. Deleting a door archives its bin with its history; adding a door with the same code later takes that bin back. - A door that still holds goods to put away, or that has a delivery checked in or being received at it, cannot be turned off or deleted. Deliveries only planned at the door lose the door and can be planned at another one. ## Receiving at a door A receipt’s receive place is a receiving station or an inbound dock door, chosen in Receiving station & route on the receipt page. There is one place per receipt. - In the Dock receiving flow, goods booked on a receipt at a door land in that door’s bin and owe a put-away from there. Without a door they land in DOCK-01, as before. - In Dock + inspect, goods always go to QC-IN-01 first. - In Direct, the door is only where the delivery is received; goods go to the shelf. - On the floor, ⋯ Change door moves the receipt to another door; a booking that names a door’s bin (the REST API, MCP) does the same. - If another phone moved the receipt to a different door while you were receiving, the floor asks “This receipt is now at DOOR-5. Book these there?” before booking. Nothing is booked twice. ## Plan arrivals Turn on Plan arrivals in Settings → Receiving & stock. Then: - A receipt shows an Arrival card: the day and time the delivery is due at the dock (in the warehouse’s own time zone), the door and a Reference (a trailer, container or booking number). Edit arrival changes the time and reference; Change door opens the receive place. - New receipt has an optional Arrival group. - Check in when the truck is at the door: on the receipt page, or on the floor under ⋯ in the receive screen. Receiving never waits for a check-in: the first booking marks the delivery as arrived. Undo check-in is offered while nothing is booked. - A delivery whose time has passed by 30 minutes with nothing checked in or booked shows Not arrived. A supplier’s promised day that has passed stays Overdue. - The Schedule and Home’s next deliveries list a receipt on its arrival day when one is planned, otherwise on its promised day. Turning Plan arrivals off hides the arrival fields and the check-in; what was planned is kept. ## The put-away tour from a door On Floor Today, a person whose place is a dock door (in a warehouse using the Dock flow) walks the put-aways out of that door’s bin: “Put away 14 items · From DOOR-3”. Choosing another place walks every door’s put-aways. The tour from a door never adds another door’s work by itself. ## Correcting a dock booking A booking keyed wrong, or a carton found damaged, never has to go onto a shelf first. On the receipt’s Dock card, “Waiting at the dock” lists each putaway with Correct: - Reverse the booking takes the units back out of stock, and the receipt line is owed them again, as if they were never booked. It works on an open receipt of your own; a receipt a connected app sent (it was told what was received) or a delivery linked to a document keeps its bookings. - Set aside moves the units to a bin that sells nothing: damaged or packaging to HOSP-01, a wrong item, expired or other to QUAR-01. They count as rejected on the receipt line. Either way the putaway carries fewer units, and is cancelled when none are left. A putaway a worker has already started is theirs to finish. Both need the receiving manage permission, and neither can be undone. ## For integrations The REST API and the MCP server offer the same doors: receiving_set_station, receiving_set_arrival, receiving_check_in, receiving_check_in_undo, and receiving_record_line’s optional expectedAcceptanceBinId (the bin your screen showed), and receiving_dock_units / receiving_dock_correct for the corrections above. ## See also - [Receiving] (/features/inventory/receiving/) - [Bins] (/features/inventory/bins/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/inventory/transfers/ # Warehouse transfers Move stock between your own warehouses, from the draft to the receipt at the destination. A transfer moves stock from one of your warehouses to another. Floormode reserves it at the source, tracks it in transit, and books it in at the destination like any other delivery. ## On this page - What a transfer is - Plan a draft - Pick and dispatch - In transit - Receive at the destination - Missing or damaged goods - Cancelling a transfer - Both warehouses must be live - See also ## What a transfer is A document with lines (item and quantity) between two warehouses you run. Shopify sees the stock leave one location and arrive at the other. ## Plan a draft Open Inventory → Transfers → New transfer, choose source and destination, and add lines. Save the draft; it reserves nothing yet. If someone else saves the same draft while you edit, compare with the saved revision before you continue. ## Pick and dispatch Reserve selected stock puts the goods aside at the source; the floor picks them into the staging bin. Record departure moves them to in transit. ## In transit Goods in transit belong to neither shelf. The transfer shows how many units are on the way; the stock value moves with them. ## Receive at the destination The destination sees the transfer as an expected delivery. Receive what physically arrives, into real bins. ## Missing or damaged goods Receive only what arrived. Units still in transit stay open until you record what happened to them; cancelling the rest of the source work does not bring dispatched stock back. ## Cancelling a transfer A draft is deleted. A reserved transfer releases its reservation. A dispatched transfer cannot be cancelled; receive it or record the loss. ## Both warehouses must be live Transfers between warehouses change Shopify’s quantities at both locations, so both warehouses have to be live. A transfer to a warehouse that is not live is refused with the reason. ## See also - [Receiving] (/features/inventory/receiving/) - [Go live] (/getting-started/go-live/) Last updated: 26 September 2026 --- Source: https://docs.floormode.app/features/inventory/counts/ # Counts Count a few bins at a time all year round, with variances, an approval queue and optional blind counting. In Floormode, Counts (/inventory/counts) is [cycle counting] (/reference/glossary/#cycle-count): counting a few bins at a time, continuously, instead of shutting the warehouse for an annual stocktake. ## On this page - Why cycle counting - Counts on a schedule - Count statuses - Blind counts - Variances and approval - A bin being counted takes no stock - Count through the year instead of a full stocktake - See also ## Why cycle counting A full stocktake stops the operation for a day or more, and produces one accuracy figure a year. Cycle counting spreads the same work across the year, catches drift within days of it happening, and never closes the building. Counts appear in the [fulfillment queue] (/features/fulfillment/queue/) as ordinary floor work, and are performed in [Floor Mode → count] (/features/floor/count/). ## Counts on a schedule Turn on Count bins on a schedule in the warehouse’s Cycle counts card, and every day each stocked bin that is due gets a count. How often depends on how fast the items in the bin sell. Fast movers (A) are counted every 7 days, steady items (B) every 30 and slow movers (C) every 90. You can change each number. A bin follows the fastest item in it. A bin is due again once its last approved count is older than its number of days. A bin that is already in an open count is never counted twice. The schedule is off until you turn it on. The first round is spread out, so the floor never gets every bin at once. Each bin that was never counted gets its first count on one day within its number of days. If the schedule did not run that day, the bin is counted on one of the next few days instead. ## Count statuses Status Means Open Created, nobody counting yet Being counted In progress on the floor Needs review Counted, variance waiting for a decision Approved Variance accepted and posted Cancelled Withdrawn ## Blind counts A count can be blind: the counter never sees the expected quantity. Tip This is the difference between a count and a confirmation. Show someone the expected number and — with the best will in the world — a bin holding 47 where the system says 48 tends to get counted as 48. A blind count produces a genuinely independent number, which is the only kind worth reconciling against. Blind counting is one of the expert terms kept on purpose, with a one-sentence ⓘ explanation the first time it appears on a page. ## Variances and approval Where counted and expected differ, the count goes to Needs review rather than posting itself. The approval queue is where someone with authority decides whether the count is right (adjust the system) or the count is wrong (recount). Approving posts a reason-coded adjustment, which lands in the [movement ledger] (/features/inventory/adjustments-and-movements/) like any other change — attributed, timestamped and traceable. With [approval by value] (/features/inventory/adjustments-and-movements/#approval-by-value) on, a count difference worth more than the limit waits for a second person, as an adjustment does. The person who counted cannot approve it. ## A bin being counted takes no stock While a count is Being counted, no stock can be put into its bins: a putaway, a move or a receipt into such a bin is refused, with a message that the bin is being counted. Putaway suggestions skip these bins. Picks and stock taken out still work. Once the count is handed over for review, or cancelled, the bin takes stock again. ## Count through the year instead of a full stocktake Every approved count records, for each bin, when it was counted in full (every item counted, or the bin confirmed empty) and by whom. At your year end, Use my cycle counts (the Home card in the stocktake season, or ⋯ → Stocktake… → Bins not counted since…) puts only the bins your counts missed on count sheets; if every bin was counted, the stocktake signs off at once. ⋯ → Export counts… (also on Reports) downloads every approved count of a range as one CSV for your accountant. Ask your accountant whether this replaces a full count for you. ## See also - [Floor count] (/features/floor/count/) — the counter’s screen. - [Adjustments & movements] (/features/inventory/adjustments-and-movements/) — where an approved variance lands. - [Bins] (/features/inventory/bins/) — what gets counted. - [Counting through the year] (/features/inventory/counts-through-the-year/) - [Count from a photo] (/features/inventory/count-from-a-photo/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/counts-through-the-year/ # Counting through the year Count every location once in the financial year instead of one stocktake day. Many accountants accept a permanent (perpetual) inventory instead of counting everything on one day: every location is physically counted at least once in the financial year, each count is recorded with its date and the people who counted, and the stock records are corrected by what was found. Floormode keeps exactly those records for every approved count, so the year-end stocktake can count only what your cycle counts missed. Ask your accountant whether this replaces a full count for you: some goods (high value, high loss) may still need one. ## On this page - When a bin counts as done - Use my cycle counts - The counts export - See also ## When a bin counts as done A bin is covered when an approved count — a cycle count, a count a pick raised, an ad hoc count or an earlier stocktake sheet — counted every item in it, or confirmed it empty, between the date you choose and the count date. A bin with one item left uncounted, a count that was cancelled or sent back, or a count still waiting for review does not cover it. When a bin was counted again after the count date, it goes on a sheet too (only the newest count is kept on the bin): a needless count, never a missed one. ## Use my cycle counts In the stocktake season, the Home card offers Use my cycle counts next to Count everything on a date when the warehouse has approved counts since the start of the year. Inventory → Counts → ⋯ → Stocktake… opens the same dialog at any time: 1. Choose Bins not counted since… and the day (by default the first day of your financial year; at most a year before the count date). 2. The dialog says how many bins your counts already cover and how many go on count sheets (“1,240 of 1,600 bins counted since 1 Jan 2026 · 360 go on count sheets”). 3. Prepare sheets: only the remaining bins go on sheets. If every bin was counted, the stocktake has no sheets and you can sign it off at once. The stocktake page shows Counted this year beside the usual figures, and its sign-off keeps the split: counted through the year, on this stocktake’s sheets, on no sheet. The report PDF prints the same section. ## The counts export Export counts… (Counts page ⋯, and the Reports page ⋯) downloads every approved count of a range as one CSV: each count, each location with its state, who confirmed it empty and when, when this count observed it and whether that lies in the range, each line with what was expected, counted, by whom and when, and the difference booked. A count approved shortly after the range (a December count approved in January) is included. The last row (end) says whether the file is complete. A stocktake of the bins not counted since a date offers the same file for its own range in its Download menu. Counts older than two years — one year when closed orders stay 45 days or fewer — have moved to the counts history (Settings → Customer privacy → History archive), which keeps them month by month. Who may: See stock, Plan counts, or See reports alone for the export. Floor devices count; they never export. ## See also - [Counts] (/features/inventory/counts/) - [Count from a photo] (/features/inventory/count-from-a-photo/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/inventory/count-from-a-photo/ # Count from a photo Photograph a bin while counting in Floor Mode and let a model count the boxes it sees. While counting a bin in Floormode’s Floor Mode, the counter can photograph it, and a model counts the boxes it sees. A person always books the count: the photo only checks a figure, or suggests one. It is meant for a narrow case: boxes of one item, 1 to 12 of them, every box visible from above. Everything else is counted by hand. ## On this page - Turn it on - Before the photo - What a photo never does - Privacy - See also ## Turn it on Settings › Receiving & stock › Cycle counts › Count from a photo, one choice per warehouse. It is Off by default. Choice What the counter sees Off Nothing changes: counts are entered by hand. Check the count After the counter enters a count, Check with a photo (under the quantity, or in ⋯). The photo says Photo agrees with 8 or Count by hand: the photo did not confirm 8. It never shows the photo’s own number. Suggest a count Count from a photo fills the quantity with the photo’s count. The counter checks it and books it with Count 9 as always. A blind count always works as Check the count, whatever the warehouse chose: the counter never sees a number they did not count themselves. ## Before the photo Every photo starts with one question: Only boxes of this item, and every box visible from above? - All boxes visible opens the camera. - Count by hand closes the question. A photo from above sees the top layer only. Boxes under other boxes cannot be counted from it, so answer Count by hand for a bin with more than one layer. ## What a photo never does - It never books a count. Booking is the same Count N as a hand count, with the same rules: a difference beyond ±20 % still needs a manager’s acceptance, and a rejected count comes back with its figures kept. - In Check the count, it never shows a number or says which way a count is off. Every answer other than an exact match is the same line, Count by hand: Count again starts a fresh count (your first figure stays in view as yours), Keep 8 books your figure as it is. After Count again, enter the new figure and check it with a photo again if you like. A count of 0 or of more than 12 can never match a photo, so its check always says Count by hand. - In Suggest a count, it never fills in fewer than the count expects: a photo that sees fewer says Photo sees fewer than expected: units may be hidden. Count by hand. - It is not offered for an item counted in kg, l or m, an item with a carton barcode, or a bin holding more than one lot of the item. Your answer before the photo is the guard. Loose goods (bottles, cans, jars), bags, more than 12 boxes or a second item in the bin should answer Count by hand, but the model can misread bags as boxes. Answer Count by hand to the question for anything but boxes of this one item. A busy service or a slow answer says Count by hand too, and never holds up the count. ## Privacy What happens to a photo: [Floormode’s privacy policy] (https://p-h.solutions/floormode/privacy-policy). ## See also - [Counts] (/features/inventory/counts/) - [Counting through the year] (/features/inventory/counts-through-the-year/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/adjustments-and-movements/ # Adjustments & movements Every reason-coded stock adjustment, and the full ledger of what moved, why and who did it. Floormode’s stock records rest on one idea: nothing changes a quantity without leaving a record. - Adjustments are the deliberate corrections, each with a reason. You make one with Adjust stock on the Stock tab, or Adjust on an item’s page. - Movements (/inventory/movements) is the tab that lists every stock change, adjustments included, newest first. An old link to /inventory/adjustments opens it. ## On this page - Adjustments - Approval by value - The movement ledger - Why a ledger rather than a running total - See also ## Adjustments An adjustment is a deliberate change to a quantity: damage found, a correction after a count, a write-off, stock reconciled after an import. Every one carries a reason code, so the adjustment log answers not just what changed but why someone changed it. Bulk imports go through the same path. An imported correction is still a reason-coded adjustment, not a silent overwrite. ## Approval by value Large corrections can need a second person to check them. Set Ask for approval above an amount in Settings → Receiving & stock → Stock adjustments. The amount is in your store’s currency. - An adjustment worth more than the amount does not change stock yet. It waits for approval, and the desk or the floor says so. - Someone else with the permission Approve adjustments above the value limit approves or rejects it. Approve 2 waiting at the top of Movements opens the list. Nobody approves their own adjustment. - An item without a cost never waits. - The same limit applies to [count] (/features/inventory/counts/#variances-and-approval) differences. The field appears once a second person can approve: someone with that permission, and another person who changes stock. With only one approver, their own adjustments above the amount wait until someone else can approve them. ## The movement ledger Movements is the full ledger — every stock change of every kind, newest first: Movement kind Comes from Receipt Goods booked in Putaway Dock to home bin Pick Pulled for an order Pack / ship Consumed by a fulfillment Count adjustment An approved variance Adjustment A deliberate correction Return Graded back into stock Move / replenish Relocated between bins Each row records what moved, how much, from where to where, why, and who did it. ## Why a ledger rather than a running total A running total tells you what the system currently believes. A ledger tells you how it came to believe it. When a number is wrong — and eventually one always is — the ledger is what lets you walk backwards to the movement that broke it, rather than adjusting to a number that “looks right” and losing the evidence. It is also what makes [short picks] (/reference/glossary/#short-pick) and count variances into a signal about specific bins rather than an anonymous shrinkage figure. ## See also - [Counts] (/features/inventory/counts/) — where approved variances come from. - [Stock] (/features/inventory/stock/) — the totals this ledger produces. - [Receiving] (/features/inventory/receiving/) — the inbound side of the ledger. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/lots/ # Lots & serial numbers Where a lot is, where it came from and which orders it went to; and the same for each serial-numbered unit. For items that track lots or serial numbers, Floormode keeps every lot and every unit, and every movement of them. That is what lets you answer a supplier’s or a customer’s question, or run a recall, from one page. ## On this page - Turning tracking on - Finding a lot - A lot’s page - Blocking a lot - Serial numbers - See also ## Turning tracking on Tracking is set per item, on the item’s Tracking card: None (units only), Lot (a lot number at receiving; its date is left out, optional or required, as the item says) or Serial (one serial number per unit, recorded at receiving or at packing). ## Finding a lot Inventory → Lots lists every lot. Find one by its number (typing its start is enough), or filter by item. [Search] (/getting-started/search/) finds a lot by its number too. ## A lot’s page - The four numbers: on hand now, units shipped, the orders it shipped to, and the units that came back on a return. - Shipped to: every shipment of the lot to an order, newest first, with the order, the day, the units and the warehouse. A row whose order was deleted in Shopify says so. Export gives the list as a spreadsheet, the start of a recall. - Stock now: the bins that hold the lot. Received from: the receipts that brought it in. - Made from and Went into: for a batch made from other lots, which lots went into it, and which batches it went into. - Shipped earlier: when an older closed order moves to the history archive, its lot shipments move with it. Show archived shipments reads them back. The shipments list shows 50 a page. Export gives order, Shopify order id, day, units, warehouse and store as CSV or XLSX; “Export matching rows” walks every page. An order’s Shipments tab lists the lots its parcels carried. The lot page holds no customer data. Open an order to see who it went to; that needs a role that may see orders. ## Blocking a lot Block lot stops a lot for a recall, a quality hold or a supplier’s notice. Floormode picks nothing from it, and the orders it was reserved for get other stock or wait. Its free units on the shelves leave Shopify’s available at once: Shopify counts them as unavailable, listed under Managed by apps → Floormode (quality control set by Floormode, apart from your own Quality control count), until you Unblock the lot, which gives back every unit it moved there. Units that orders hold stay committed in Shopify, so blocking a lot never takes Shopify’s available below zero. When one of those orders is cancelled or gets other stock, its unit joins quality control too. A warehouse whose stock Floormode does not update in Shopify keeps Shopify’s own count; the dialog says what happens in each warehouse before you confirm. Quarantine this lot on the lot’s page then creates the tasks that move the units to the quarantine bin, QUAR-01, to clear the shelves. Units moved there stay there when you unblock. ## Serial numbers Inventory → Serials lists every serial-numbered unit; find one by its serial, or filter by item and state. A unit’s page shows where it came in, where it went and the other units of its item. Search finds a serial number too. Tip For a recall, start on the lot’s page: Shipped to names every order, Stock now every bin, Block lot takes what is left off sale and stops the picking, and Quarantine this lot clears the shelves. ## See also - [Receiving] (/features/inventory/receiving/): where lots and serials are booked in. - [Stock] (/features/inventory/stock/): why a blocked lot’s units are not available. - [Search everything] (/getting-started/search/): lots and serials from one box. Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/inventory/local-items/ # Local items Goods you stock and move here that do not exist on Shopify — raw materials, sub-assemblies and custom items — and the one rule that governs them. Some of what sits on your shelves was never a Shopify product, and Floormode tracks it all the same. A drum of resin, a half-built sub-assembly waiting for its final step, a one-off item made for a single customer — real, countable, pickable goods that your storefront has never heard of. Item setup and recovery is where those live: on Inventory → Stock, open More stock actions. They come from Logistified and Assemblified, they behave like any other stock inside Floormode, and exactly one thing is different about them: nothing about them is ever pushed to Shopify. ## On this page - What a local item is - Where they come from - How to recognise one - What you can do with them - The supply outlook covers them too - The one rule: every unit always has a place - The Unplaced items worklist - When an item is blocked - See also ## What a local item is A [local item] (/reference/glossary/#local-item) is a good that Floormode stocks on behalf of a sibling app, because the sibling has no warehouse of its own and Shopify has no product for it. There are three kinds, and the app they belong to is shown on every row: Kind Belongs to What it usually is Raw material Assemblified (raw material) An input to a build — sheet stock, fasteners, fluid, packaging components Sub-assembly Assemblified (sub-assembly) Something you build in order to build something else, and never sell on its own Custom item Logistified (custom item) A purchased good with no storefront listing — tooling, consumables, a bespoke order They are ordinary stock in every way that matters on the floor. They have a title, a SKU, [bins] (/reference/glossary/#bin), a quantity, a movement history and a place in a pick list. ## Where they come from You do not create local items, and you cannot. They are synced automatically from the connected app that owns them: Assemblified sends its materials and sub-assemblies, Logistified sends its custom items, and each keeps its own catalogue. That sync only runs while the connection is active. With nothing connected, there are no local items at all — the tab is empty and stays empty. See [Standalone] (/integrations/standalone/). Note The owning app names the item; Floormode holds it. If a title or a SKU is wrong, correct it in Assemblified or Logistified and the change arrives here. Editing it here would put the two catalogues out of step, so the app does not offer it. ## How to recognise one Two signals, and both are always present: - The id prefix. Local ids begin VMAT- (raw material), ASM- (sub-assembly) or CSTM- (custom item). The prefixes are exact and case-sensitive — an ordinary SKU that happens to start with the letters “vmat” is not a local item. - The “Not on Shopify” badge. Every screen that can show a local item shows this badge beside it: the stock list, the item detail, pick lines, receiving lines, count sheets. Hovering it says which app the goods are held for. The badge exists because a local item is otherwise indistinguishable from a Shopify variant, and the difference is invisible: it will never appear in your storefront, your Shopify inventory screen or a Shopify report. That is not something you should have to deduce from a number that does not add up. ## What you can do with them Almost everything. Local items are first-class stock: Local items Receive against an expected delivery Yes [Put away] (/reference/glossary/#putaway) into a bin Yes Pick — including [production picks] (/reference/glossary/#production-pick) for a work order Yes [Cycle count] (/reference/glossary/#cycle-count), with variances and approval Yes Adjust with a reason code Yes Move bin to bin Yes Count towards [available to promise] (/reference/glossary/#atp) Yes Show supplier stock and quantities on order Yes Appear in the stock ledger and movement history Yes Push a quantity to Shopify Never That last row is the whole exception, and it is a refusal rather than an omission: the Shopify push is blocked for local items at the point where it would happen, so no configuration, no setting and no future connection can cause one to leak into your storefront’s inventory. There is no Shopify number for them to be the [single writer] (/integrations/who-writes-shopify/) of. One smaller exclusion follows from the same fact: - Counts of local items are not exported to Logistified. An approved [cycle count] (/reference/glossary/#cycle-count) still corrects your bins here; it just is not copied into the sibling’s stock-take records, which only track Shopify goods. ### The supply outlook covers them too Open a local item and its [available to promise] (/reference/glossary/#atp) breakdown carries the same two forward-looking figures a Shopify variant has — supplier, what a supplier is holding for you but has not shipped, and on order, what is on an open purchase order. Both come from Logistified, which knows what it has bought for a raw material just as it does for a sku. Three things to know about those two numbers on a local item: - They are display truth, never stock. Nothing about them puts a unit in a bin, and they are shown separately from on hand and incoming rather than added to anything. - The owning app has to have introduced the item first. A supply figure for something Floormode has never received a catalogue record for is not shown and does not create the item — a forecast may not invent a good you could then receive against. It appears once the record arrives. - A handed-back item stops showing them. After a [handover] (/reference/glossary/#handback) the figures go blank rather than to zero, because Floormode is no longer the app that speaks for those goods. If nothing has ever been sent, both figures read as unknown rather than zero — the same honest blank a shop with no Logistified sees. ## The one rule: every unit always has a place Local items obey a rule that Shopify variants do not need: Every unit of a local item is in a bin. Always. From the first one. Shopify tells Floormode how many of a variant exist, so a variant can have a quantity before anyone has decided where it lives. A local item has no such outside source — the only record of how many there are is the one you make. So the app refuses to let a local item hold a quantity that is not in a specific bin, because a floating number nobody can walk to is exactly the number that goes wrong. The consequence is the worklist below. ## The Unplaced items worklist When a connection is first made, everything the owning app already holds arrives as a claim — a statement that the thing exists, with no quantity attached. Claims appear at the top of the Local items tab under a banner counting how many still need a location. Items the sibling introduces later, after that first sync has finished, are new by definition: they have no history and nothing on your shelf, so they skip the worklist and become ordinary empty stock immediately. The worklist is an opening exercise, not a permanent queue. Caution An [unplaced item] (/reference/glossary/#unplaced-item) contributes nothing, anywhere. Zero to bins, zero to available to promise, zero to counts and zero to planning. Until it is placed it cannot be received, picked or counted — a scan against one is refused, and the refusal says the item has not been placed yet. (Its supplier and on order figures are still shown if the owning app has sent any: those describe what is coming, not what you have.) This is deliberate. A claim is the other app saying “this thing exists”; it is not a statement about your shelves. Placing an item is exactly the first-install setup you already know: go and look, then type what is there. 1. Find the item on the worklist. Its columns are Item, Belongs to, On hand and Place into. 2. Go and count what is actually on the shelf. The On hand column is blank, and that is not a display fault — the owning app has never had a warehouse, so it has no quantity to send. The number is yours to establish. 3. Type the quantity and the bin code, then press Place. 4. The row clears. The quantity is posted into that bin as an opening movement, the item becomes ordinary stock, and the owning app is sent the resulting figure so both sides start from the same number. Four details worth knowing before someone hits them: - A quantity above zero needs a bin. There is no “place it somewhere and sort it out later” — that is the rule above, enforced. - Zero is a real answer. Entering 0 means “I looked, there are none”. It closes the claim, posts no movement, and the item becomes ordinary stock with nothing in it — ready to be received into normally. Use it rather than leaving the row open. - Placing is the only way to clear a row. An adjustment cannot onboard an item, and while a claim is open adjustments are refused anyway. (A first-install CSV import counts as placing, so the two can never disagree.) - You can place before going live. Placing opening quantities is allowed as soon as the per-location agreement has been prepared, before it is committed — so the opening count can be done in advance rather than on the morning of the switchover. It is the one flow permitted in that window; everything else waits for the commit. Work through the list the way you would an opening stocktake: it is finite, and once a row is cleared it never comes back. ## When an item is blocked Besides being unplaced, a local item can carry one of three badges explaining why it will not move: Badge What it means What to do Waiting for details The app that owns this item has not sent its details yet. It unlocks by itself once they arrive. Retired The owning app retired this item. What is on the shelf can still be picked or moved out; nothing new is received. Handed back This stock went back to its app when the connection was switched off. The history stays; the stock cannot move. A fourth case freezes every item of one app at once rather than a single row. While a [handback] (/reference/glossary/#handback) is in progress the page carries a banner — “Stock is being handed back” — and nothing for that app can be received, picked, counted or adjusted until the other side confirms it has taken the quantities back. That is covered under [Activation] (/integrations/activation/). Beyond the item itself, local stock also needs the connection to be on and the per-location agreement to cover the location you are standing in. If a flow is refused for either reason the message says which, and the refusal is always explicit — a blocked pick is reported as a blocked pick, never as a successful pick of nothing. The [health panel] (/integrations/health-panel/) shows the current state for both siblings under Local stock (not on Shopify). Note Order matters when you first switch this on. The agreement and the sibling’s catalogue sync have to meet: if the agreement is committed only after the sibling has finished sending its catalogue, local stock stays dormant and flows are refused as not yet activated until the sibling sends its catalogue again. Commit the agreement first, or ask for a fresh catalogue sync afterwards. ## See also - [What changes when connected] (/integrations/what-changes-when-connected/) — where local items fit among the other differences. - [Who writes Shopify] (/integrations/who-writes-shopify/) — why local items have no Shopify writer at all. - [Activation] (/integrations/activation/) — connecting, and the handback that happens when you disconnect. - [Production pick] (/features/floor/production-pick/) — the job that consumes most raw materials. - [Stock] (/features/inventory/stock/) — the four numbers, which mean the same thing for local items. - [Fill items from a photo] (/features/inventory/fill-items-from-a-photo/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/fill-items-from-a-photo/ # Fill items from a photo Fill an item's blank master data, such as its barcode or country of origin, from a photo of its pack. Many items arrive with blank master data: no barcode on file, no country of origin, no dangerous-goods class. With Fill items from a photo on, Floormode reads what the pack prints and suggests the missing values. Nothing is saved until someone saves the item’s card. ## On this page - Turn it on - Fill an item - What each field means - Privacy - See also ## Turn it on Settings › Receiving & stock › Fill items from a photo. It is off by default. One checkbox a field: untick a field you keep elsewhere (an HS code from your customs broker, for example), and the fill never reads it. ## Fill an item 1. On the item’s page, open ⋯ › Fill from photo. From a receipt, focus the line and open ⋯ › Complete item details, then Fill from photo. 2. Take a photo of the Front, and of the Back if it prints more (the back usually holds the barcode, the origin and any battery or hazard mark). On a laptop, pick the photo files instead. 3. Tap Read the pack. Each field gets one row: - Use puts the value into the item’s card below. Save the card to keep it. - Copy copies a value Shopify keeps (origin, HS code). Paste it with Edit in Shopify on the customs card. - Skip leaves the field as it is. - The info button beside a value shows the words it was read from. Floormode only fills what is empty. A barcode is added beside the codes the item already has, never in place of one. A dangerous-goods class is offered only when you did not change the class yourself, and only from both sides of the pack. ## What each field means Field What is read What happens Barcode (GTIN) the barcode, decoded on your device; else the digits printed under it Use adds a decoded barcode to the item’s barcodes. Printed digits are shown for you to check and add yourself. A barcode another item already has is shown with a link to that item, never added. Net content the printed contents: “Net Wt 16 oz (454 g)”, “Füllmenge 0,5 l”, “6 x 330 ml” Shown only. It is not the shipping weight: weigh the packed item for that. A stored weight lighter than the contents, or about 1,000 times off, is pointed out. Country of origin “Made in …”, “Product of …”, “Hergestellt in …”, “Fabriqué en …” Copy. “Designed in”, “Imported by”, “Made in EU” or a bare “Korea” is never read as an origin. Dangerous goods a lithium battery mark (UN 3480, 3481, 3090, 3091) and its words, hazard statements such as H222 Use puts the class and UN number into the dimensions card. An aerosol or a flammable liquid is named, never set: you choose the class. HS code your own Shopify country codes, else another variant of the same product Copy, marked Suggested. You’re responsible for the classification. Check it before you use it. A value the photos do not show clearly is left out, never guessed. Every value read from the pack’s text says “Read from the photo: check it against the package”: only a barcode your device decoded is offered for Use without it. If the text takes too long to read, the barcode still shows and the sheet says so: read the pack again for the rest. ## Privacy What happens to a photo: [Floormode’s privacy policy] (https://p-h.solutions/floormode/privacy-policy). ## See also - [Local items] (/features/inventory/local-items/) - [Item dimensions and capacity] (/features/inventory/item-dimensions-and-capacity/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/inventory/bins/ # Bins Bin master data, the bulk location generator and bin label printing — plus the warehouse shape behind them. In Floormode, Bins (/inventory/bins) is the master list of the places stock can sit, plus the tools to create them in bulk and label them. ## On this page - Bin types - Creating bins in bulk - The warehouse shape - Labels - See also ## Bin types A [bin] (/reference/glossary/#bin) has a type, and the type is what tells the app how to treat what is in it: Type Holds Receiving Goods just booked in, awaiting putaway Quality check Stock held for inspection Quarantine Damaged or suspect stock, not sellable Bulk storage Reserve stock, not picked from directly Pick bin Where pickers actually go Packing At the pack station Staging Marshalled for despatch or production Returns Goods received back, awaiting grading The bulk/pick split is what makes automatic replenishment possible: pickers only ever visit pick bins, and [Placement] (/features/inventory/placement/) replenishes those from bulk. ## Creating bins in bulk Nobody types in four hundred bin names. The bulk location generator creates them from a pattern — a range of aisles, bays and levels becomes a full set of locations in one action. ## The warehouse shape The bins list is the flat view. The shape of the warehouse is set up on the warehouse’s Layout tab (Settings → Warehouses → your warehouse): - A template picker for common layouts. - A grid generator that creates hundreds of locations at once. - A 2D map you can colour-code by fill. - Zones, aisles, racks and shelves — or flat bins and floor positions for oversized goods. Note Simple flat bins work with zero setup. The zone/aisle/rack hierarchy is available when you need it, not imposed when you do not — a small warehouse can run on a dozen named bins and never build a layout of groups. ## Labels Bins are scanned, so they need labels. Bin label printing is built into this tab, and works with the same PrintNode setup as shipping labels — or as a PDF you print yourself. Label text supports Latin, Greek and Cyrillic letters, including accented names. Other scripts and emoji show a message before printing. Enlarge the text box or reduce its type size if a name does not fit, then check the PDF before printing a batch. Barcode values are kept unchanged. ## See also - [Placement] (/features/inventory/placement/) — home bins, putaway rules and replenishment. - [Item dimensions & capacity] (/features/inventory/item-dimensions-and-capacity/) — telling the app how much a bin holds. - [Initial setup] (/getting-started/initial-setup/) — bins and the pick path as a setup step. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/layout/ # Layout Add bins and groups in bulk and set the order your pickers walk. Floormode’s Layout adds bins and groups in bulk and sets the order your pickers walk. Where: Inventory → Layout, beside Bins (with one warehouse it opens straight on it; with more, pick the warehouse at the top), or the Layout tab of Settings → Warehouses → your warehouse: the same list in both places. Stock lives only in bins; areas, aisles, racks and shelves are optional groups around them. The Layout list is the order pickers walk. One word for each thing: - Area, Aisle, Rack, Shelf, Bin are the kinds of location, from the biggest group to the bin. What a location is, is its Kind. - A zone is something else: a group of bins for picking and staff (with a default station), made under Zones, stations & staff on the warehouse’s page. Stock never lives in a zone, and a location’s code never makes one. ## On this page - Add locations - The pick walk - Walk points on the 2D map - See also ## Add locations Add one location adds a single location by its own code: an area, aisle, rack, shelf or bin (pick its Kind). Inside a group (its ⋯ → Add one location here…) it starts from the kind one level down. One button, Add locations, adds many bins and groups three ways. Every way skips codes that already exist, so running it again is safe, and new locations join the end of their group’s walk. - Range — a prefix and a numbered run (B-01 … B-40, or B-00001 … B-10000), up to 50,000 at once. - Pattern — aisles, racks per aisle, shelves per rack and bins per shelf, with Create the aisles, racks and shelves too to add the groups around the bins. The button names both: Add 240 bins and 102 groups. Code starts with is the codes’ first part (A gives A-01-01-1); Zone files the new bins into a zone the warehouse already has, or none. Edit levels names each level and its code part. - List — paste codes, one per line, or upload a spreadsheet. A row may say what it sits inside, its kind, its purpose (pick, bulk, …) and its location type. Press Check rows first: the check says how many rows are new, already exist or are refused, and why each refused row is refused. Download refused rows (CSV) gives them back to fix. Up to 500 locations are added at once. A bigger pattern or list (up to 50,000) runs in the background: the dialog shows how far it is, and you can close it — the job keeps going. When it is done, Continue to labels prints the new locations’ labels. The Bins list (Inventory → Bins) can show All warehouses at once, in code order; pick one warehouse to sort by its walk. ## The pick walk A pick list is walked in the Layout list’s order (or, with pick classes, each class of it in that order). Change the walk by dragging rows, or with Move to…, Move up, Move down and Move to position… (its place in its group, typed). Serpentine walk… (the Layout tab’s ⋯ menu) runs every second aisle the other way (up one aisle, down the next) where bins sit directly in an aisle or group. Each group is its own change, and stopping keeps the groups already done. Where bins sit in shelves, it keeps the shelves’ order: drag shelves to change the walk. Labels already printed keep their codes; a serpentine walk changes only the order. A layout of any size keeps its walk in order as you add and move locations. Where the walk is packed solid at one spot, that addition is refused there: add it under another aisle or shelf. ## Walk points on the 2D map On the map (Open 2D map), the Walk card turns the racks you drew into walk points, the spot in the aisle a picker stands at to reach a rack’s bins. 1. Arrange from layout proposes a point for every rack drawn on the map. A rack facing two aisles asks you to Choose a side (or Same side for all, or Alternate by rack); a rack no picker can reach is listed so you can move it. 2. Accept N points saves them. 3. Follow the map makes pick lists follow the map: a pick list (or, with pick classes, each class of it) whose bins all have accepted walk points is walked nearest first, storey by storey; one bin without a point and that list (or class) is walked in the Layout list’s order. Use the Layout list turns it off again. Moving a rack on the map, adding bins to it or setting a bin’s point by hand clears those walk points; Review points proposes them again, and Accept takes them. ## See also - [Warehouses] (/features/settings/warehouses/) - [Bins] (/features/inventory/bins/) - [Placement] (/features/inventory/placement/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/labels/ # Labels and the label designer Print bin and item labels, choose paper and barcodes, and keep a design for your team. Floormode prints bin labels, item labels and receiving labels as PDFs, or straight to a connected printer. The label designer sets the size, the barcode and what the label shows. ## On this page - Where to print labels - Paper and label size - Barcode formats - Printing tips - Save a design - Printer profiles and corrections - Items without a barcode - See also ## Where to print labels Bins: Inventory → Bins (all bins, or the ones a generator just created). Items: from the item’s drawer or a receipt. Receiving: one label per booked unit from the receipt. ## Paper and label size Pick a sheet layout or a roll. The designer shows the placement; the PDF prints all positions even when the preview shows only the first ones. A new design, and a download that names no design, start on your store’s paper: 57 × 32 mm labels, 3 across and 8 down, on A4, or centred on US Letter for a store in the US, Canada, Mexico or Puerto Rico. A saved design keeps the paper it was saved with. ## Barcode formats Code 128 is the default and reads on every scanner. QR codes hold more; hide the readable text under a QR code when the value is long. A GS1-128 or GS1 Data Matrix label needs the item’s exact GTIN-14 first: see [GS1 barcodes] (/features/inventory/gs1-barcodes/). ## Printing tips Print at 100 %: turn off “Fit to page” and browser headers. Test one label and scan its barcode before a batch. ## Save a design Save the design to reuse it; your team sees the same designs. The default design is what the one-click prints use. ## Printer profiles and corrections A connected printer has a profile with its paper and offsets. If labels print slightly off, correct the offset in the profile rather than in every design. ## Items without a barcode Floormode prints a label with the item’s own barcode; an item without one gets a Floormode barcode you can scan on the floor. ## See also - [Bins] (/features/inventory/bins/) - [Receiving] (/features/inventory/receiving/) Last updated: 5 November 2026 --- Source: https://docs.floormode.app/features/inventory/gs1-barcodes/ # GS1 barcodes What a GS1-128 or GS1 Data Matrix code needs before Floormode reads and prints it — the exact GTIN-14, the scanner's setup, lots and expiry dates. A GS1 barcode carries more than the item: the same code can hold its lot number, its expiry date or its serial number. Floormode reads those fields at receiving and checks them while picking, and it prints GS1-128 and GS1 Data Matrix labels. A few things have to be in place first. ## On this page - The fields Floormode reads - Before the first scan - Receiving - Picking, packing and other scans - Printing GS1 labels - See also ## The fields Floormode reads Field What it holds How Floormode uses it (01) The item’s GTIN-14, exactly 14 digits Finds the item by its barcode (10) Lot number, 1–20 characters Filled in at receiving; checked against the line’s lot while picking (15) Best before, as YYMMDD The lot’s date when the code has no (17) (17) Expiry, as YYMMDD The lot’s expiry date (21) Serial number, 1–20 characters The unit’s serial, for an item that tracks serial numbers A day of 00 means the last day of that month. A code with any other field, or with one field twice, is refused rather than read in part. ## Before the first scan - The item. Give the item its exact 14-digit GTIN as its barcode or as an extra barcode. When Shopify holds the 13-digit EAN or the 12-digit UPC, add the GTIN-14 beside it: Floormode never adds or drops leading digits itself. A code whose GTIN no item carries is refused with the GTIN it read, so you know which number to add. - The scanner. Turn on AIM symbology identifiers in the scanner’s settings, so it sends ]C1 before a GS1-128 code and ]d2 before a GS1 Data Matrix. Also keep the separator between fields of varying length (FNC1): keyboard scanners send it as Ctrl+]. Codes typed or scanned in their printed form, (01)…(17)…(10)…, are read as well. A long number without these marks is never taken for GS1; it is read as an ordinary barcode. - Lots. Floormode writes lot numbers in capitals with no spaces at either end. A GS1 lot written another way is refused, never changed silently. Turn on lot tracking for the item, and the warehouse’s [expiry-first picking] (/reference/glossary/#fefo) if you pick by date. ## Receiving Scanning a GS1 code while receiving finds the item and fills its lot and expiry fields from the code. A booking whose lot or date contradicts the code it was scanned from is refused. For an item that tracks serial numbers, the code’s serial is the unit’s serial number; on any other item a code with a serial is refused. ## Picking, packing and other scans - Picking checks a scanned lot and expiry against the lot the line is reserved from, before any stock moves. A pick line without a reserved lot has nothing to check them against, so such a code is refused there. - Elsewhere (the pack scan, counting, moving stock) a GS1 code that carries only the GTIN identifies the item as any barcode does. One that carries a lot or an expiry is refused, because those screens check no lot: scan the item’s plain barcode instead. - The pack station’s serial step takes a GS1 code that carries a serial, whatever else it holds: the serial is recorded for the unit, and the code’s lot and expiry are not checked there. ## Printing GS1 labels In the label designer, choose GS1-128 or GS1 Data Matrix as the barcode. Both need the item’s exact GTIN-14. - A receiving label combines the GTIN with the lot and expiry captured when the goods were received. - An item whose stored barcode is already a complete GS1 code prints it with its own fields. - A day of 00 prints as the actual last day of the month; the date means the same. Tip A long GS1-128 code may not fit a small label. GS1 Data Matrix holds the same fields in much less space. Check the preview and the actual PDF before printing a roll. ## See also - [Labels] (/features/inventory/labels/): paper, printers and the other barcode formats. - [Receiving] (/features/inventory/receiving/): booking goods in on the desk and the floor. - [Lots & serial numbers] (/features/inventory/lots/): where lots and serials go after receiving. - [Compatible hardware] (/getting-started/compatible-hardware/): scanners and printers that work. Last updated: 26 October 2026 --- Source: https://docs.floormode.app/features/inventory/placement/ # Placement Advanced. Home bins, ordered putaway rules, re-slotting suggestions and automatic pick-bin replenishment. In Floormode, Placement (/inventory/placement) is the advanced tab that decides where things live. Warehouse software calls it slotting. ## On this page - Home bins and putaway rules - Re-slotting suggestions - Automatic replenishment - Do you need this? - See also ## Home bins and putaway rules A home bin is where a given SKU belongs. When goods are put away, the app suggests the home bin rather than making the operator decide. Behind that sit ordered putaway rules, evaluated top-down: the first rule that matches decides. Typical rules send fast movers near packing, heavy goods to floor level, and cold-chain or hazardous stock to their designated zones. ## Re-slotting suggestions Demand moves. A SKU that was slow in March can be your best seller in November, and it is still sitting at the far end of the building. Placement watches this and suggests moving fast movers closer to packing. Accepting a suggestion creates a move task in the [fulfillment queue] (/features/fulfillment/queue/) — so a re-slotting decision becomes real floor work someone actually does, rather than a report nobody actions. ## Automatic replenishment [Pick bins] (/reference/glossary/#bin) can be replenished from bulk storage automatically when they drop below a minimum. The replenishment appears as a task in the queue before the picker finds the bin empty, rather than after. Note The switch for automatic replenishment is under Settings → Receiving & stock (/settings/stock), and this tab links straight to it. Like auto-assignment, it is off until you turn it on. ## Do you need this? Probably not at first, which is why the tab is marked Advanced. Placement earns its keep once you have enough SKUs that walking distance is a real cost, and enough bulk stock that pick bins run dry mid-shift. A warehouse with a few dozen bins and one person picking will do fine without ever opening it. ## See also - [Bins] (/features/inventory/bins/) — the locations placement assigns to. - [Queue] (/features/fulfillment/queue/) — where move and replenish tasks appear. - [Fulfillment settings] (/features/settings/fulfillment/) — the replenishment switch. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/item-dimensions-and-capacity/ # Item dimensions & location capacity Optional product dimensions and per-location capacity, so the app can answer "is this bin full?" Floormode takes two optional pieces of data that make several other features noticeably better: how big each product is, and how much each location holds. ## On this page - Item dimensions - Location capacity - What it unlocks - Optional means optional - See also ## Item dimensions You can record each product’s dimensions and weight. Nothing forces you to, and nothing breaks without them. Type them in your store’s units: inches and pounds or ounces in a store on imperial units (as Shopify’s store settings say), millimetres and grams in a metric store. A figure may name its own unit (2 lb 3 oz, 30 cm, 12"). Floormode keeps an item’s measures in millimetres and grams, to a tenth, so a figure reads back the way you typed it. With them, [cartonization] (/reference/glossary/#cartonization) stops guessing. The pack step can genuinely choose the cheapest suitable box, and split into several when one will not do, because it knows what it is fitting. Dimensions also improve freight quoting, where handling units are measured rather than estimated. ## Location capacity A location can carry a capacity, expressed in whichever unit actually constrains it: - Max units — a shelf that holds 200 of something. - Weight — a shelf rated to a load, in kg or lb, as your store. - Volume — a bin of a given size, in litres or cubic feet, as your store. - Pallet slots — a rack bay that takes two pallets. Each item counts against it by how many of it a full pallet holds, set on the item once you have a pallet location. Without that number the pallet limit is not checked, and the putaway suggestion says so. A bay holding several items is not judged as full: each item counts only its own units. Different bins are limited by different things, so the capacity is not forced into one unit. ## What it unlocks Together they let the app answer questions it otherwise cannot: - “Is this bin full?” — during putaway, before someone carries a pallet across the building. - Over-receipt warnings — putaway warns when a delivery will not fit where it is heading. - Better box selection — the cheapest box that actually holds the order. ## Optional means optional Note A location with no capacity set is treated as unlimited. It is not treated as zero, and it does not block anything. The same is true of products with no dimensions: cartonization falls back to what it can infer, and everything still ships. This is the general pattern in Floormode — richer data makes features smarter, but absent data never turns a feature into an obstacle. ## See also - [Pack] (/features/fulfillment/pack/) — where cartonization uses dimensions. - [Bins] (/features/inventory/bins/) — where capacity is set. - [Receiving] (/features/inventory/receiving/) — over-receipt tolerance and warnings. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/inventory/backorders-and-oversell/ # Backorders & oversell Allow selling beyond on-hand, set per warehouse, and what arriving stock does for the orders waiting on it. [Oversell] (/reference/glossary/#oversell) is selling stock you do not have yet. Floormode lets you allow it per warehouse. Done deliberately it is a legitimate commercial tool; done accidentally it is the fastest way to disappoint a customer. ## On this page - The switch - What happens to an oversold order - When the stock arrives - The other kind of oversell - See also ## The switch The Accept backorders switch lives on the warehouse (Settings → Warehouses → your warehouse → Settings), and it is off by default. Per-warehouse is the right granularity: a main distribution centre with reliable inbound supply may happily take backorders, while a retail store shipping its own shelf stock should never promise what is not on it. ## What happens to an oversold order An order that cannot be reserved becomes a [backorder] (/reference/glossary/#backorder). It: - Lands in the Backordered view on the [order list] (/features/orders/view-tabs/). - Shows on Home under [Needs attention] (/features/home/needs-attention/) as short of stock. - Shows Not enough stock rather than silently reserving nothing. Nothing about it is hidden. A backorder is a visible commitment with a date attached, not an order that quietly fails to pick. ## When the stock arrives When stock reaches a sellable bin in that warehouse (goods received or put away, a count that finds more, a return graded back to sellable, a transfer received), Floormode tries again to reserve it for the orders waiting on that item. Nobody has to remember which orders were waiting. Reserving is all that happens on its own. Once all its stock is reserved, an order joins the [queue] (/features/fulfillment/queue/) like any other ready order: when no hold is left on it, when its pack day has come (where you use delivery dates), and, where you hold work back in a [wave] (/features/fulfillment/waves/), when its wave is released. It is then picked, packed and shipped as usual. Nothing is picked, packed, shipped or fulfilled automatically, and a customer’s parcel is not on its way until someone has packed it. ## The other kind of oversell Caution The unintentional kind comes from a warehouse that is not linked to a Shopify location. Availability never syncs, so Shopify keeps selling from a number that does not move — and you are overselling without ever having chosen to. That is why the warehouse-link step in the [setup guide] (/getting-started/setup-guide/) completes on the link, and why an unlinked warehouse carries a warning badge. ## See also - [Warehouses] (/features/settings/warehouses/) — the switch and the other stock policies. - [Views] (/features/orders/view-tabs/) — the Backordered view. - [Stock] (/features/inventory/stock/) — where committed and available diverge. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/returns/overview/ # Returns A returns page in your own store, request review, and grading every unit that comes back before it re-enters stock. In Floormode, Returns (/returns) covers the whole reverse journey: the customer asking, you deciding, the parcel arriving, and every unit in it being graded before it touches sellable stock. Three peer tabs, in the order things happen. ## On this page - What you can do here - Key concepts - Where to next ## What you can do here [Requests] (/features/returns/requests/) Customer-initiated returns from the returns page in your store — review, approve or deny. [Returns] (/features/returns/returns/) The returns Shopify knows about, and the shipments coming back to you. [Receipts] (/features/returns/receipts/) Grade every returned unit as it arrives and decide where it goes. ## Key concepts - Return request — what an RMA is called here: the customer’s ask, before you have agreed to it. - Return — the thing Shopify tracks once a return is agreed. - Return receipt — what physically arrived back, graded unit by unit. - [Disposition] (/reference/glossary/#disposition) — where a returned unit goes: back to sellable stock, quarantine, or written off. ## Where to next - [Customer notifications] (/features/settings/customer-notifications/) — what the customer hears along the way. - [Stock] (/features/inventory/stock/) — where restocked units land. - [Backorders & oversell] (/features/inventory/backorders-and-oversell/) — a restocked return is reserved for an order waiting on it. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/returns/requests/ # Requests Customer-initiated returns in your own store — no login — that you review, approve or deny. In Floormode, Requests (/returns/requests) is where customer-initiated returns arrive. Customers start their own; you decide. ## On this page - Returns in your store - What the customer chooses - Reviewing a request - Fees and value deductions - Request statuses - See also ## Returns in your store Customers start a return or exchange on the returns page in your own store (/apps/floormode-tracking/r, in your store’s look). The link in their order e-mails, the order page and Shopify’s order status page open their order directly; anyone else finds it with the order number plus email or postcode — no account, no login, no password reset at the worst possible moment. The returns page lives in your storefront, deliberately separate from the merchant admin. You share its address (Settings → Returns → Returns page, Open returns page); customers do the rest. Tip Requiring a login for returns is a reliable way to generate support email. Order number plus email is enough to prove the customer has the order in front of them, which is the actual thing being checked. ## What the customer chooses On the returns page, the customer picks: - The outcome — refund, store credit or exchange. - The reason — arrived damaged, faulty, wrong item sent, not as described, too small, too large, changed mind, arrived late, or other. What happens next depends on your return settings and the parcel: - The returns page makes the label. With a carrier account that can make return labels, a complete return address and the page’s own labels switched on (Settings → Returns → Return labels), the customer gets a prepaid return label, so the parcel is trackable from the moment it is created. - You send the label. When the page’s own labels are off, the carrier account cannot make return labels, or the label needs something first (the carrier’s approval, customs details), the request waits for you to send a label. - The customer sends it themselves. With no return carrier, a parcel abroad your carrier cannot declare, or dangerous goods, the page shows your return address and the customer ships the parcel on their own. - US carriers. USPS and UPS make return labels too, free until posted. USPS can also make a QR code the customer shows at a participating Post Office. Both need your usual return box size in Settings → Returns → Return labels, and USPS needs Enrolled in USPS Returns turned on for its connection; until each is set, the request waits for you to send the label, and the settings name the step. The label dialog lets you pick the service and type another size for one return. - The customer asks you first. When no complete return address is set (for example, Automatic with several warehouses and none chosen), the page tells the customer to contact you before sending, so you can say where the parcel goes. Settings → Returns → Return labels names the missing address as a step to finish. ## Shopify’s return rules Settings → Returns → Return rules lets the return rules you keep in Shopify decide how long customers have to return an order, instead of Floormode’s own number of days. It is off until you switch it on. - Order by order, as placed. Each order follows the rules of its market as they were when it was placed. Changing your rules in Shopify only affects later orders, as in Shopify. - From delivery. The window starts at the item’s delivery, or the last item’s, as your rules say, and moves past a weekend when they say so. Without a delivery date Floormode counts from the shipment plus 7 days for transit (change it under More, 0–30) and never refuses a return on that estimate. - When it can’t tell, you decide. If the rules changed between two of Floormode’s reads, or a market moved, the request waits for your review rather than being refused, and the customer sees no deadline. - Faults stay possible. Past its window, or final sale, an item can still be returned for a fault — damaged, defective, wrong item, not as described — and the request waits for your review. - Permission. Floormode needs your permission to read return rules and markets: Allow on the card. Without the markets permission every order uses your default rules. Note Shopify doesn’t let apps read final-sale items or window overrides for products and collections. Keep your final-sale items in Settings → Returns as well. ## Reviewing a request You review each request here and approve or decline it. The reason the customer gave is right there, alongside the order, so the decision is made with context rather than from a list of order numbers. ## Fees and value deductions Settings › Returns › Return fees (off until Add a fee) sets a [restocking fee] (/reference/glossary/#restocking-fee) and a flat return shipping fee, tax included. They come off the refund when the goods are back: - never on an exchange; - never, and no [value deduction] (/reference/glossary/#value-deduction) either, on an item whose reason is a fault: damaged, defective, wrong item, not as described; - with Waive for store credit, never on store credit; - the shipping fee only on orders in your store’s currency. A request keeps the fees in force when it was made. Its sheet shows the refund, each fee and deduction, and what was paid. Change an item’s reason to a fault after the money went out and Floormode refunds what it took at once; the request reads Received until Shopify confirms. A change away from a fault never takes money back. In the EU, EEA and UK a customer who cancels within 14 days pays no restocking fee: the card reminds a store there. The customer sees the fees on your returns page before asking, and what a request refunds is the amount after them. ## Request statuses Status Means Requested Submitted, awaiting your decision Approved Agreed — the customer can send it back Declined Denied Received The goods arrived back Refunded, Credited, Exchanged Resolved by what the customer asked for: money back, store credit, or an exchange order. The status filter calls all three Resolved. Cancelled Withdrawn An exchange creates a draft order in Shopify with the customer’s address. When there is no address to copy, the request says so: add the address to the draft before you send it. Every state and what follows it is on [Lifecycles] (/reference/lifecycles/#a-return). Where goods land against an approved request, completing their receipt refunds it, unless you untick that in the dialog. See [Receipts] (/features/returns/receipts/). ## See also - [Receipts] (/features/returns/receipts/) — grading what arrives. - [Returns] (/features/returns/returns/) — the Shopify-side record. - [Customer notifications] (/features/settings/customer-notifications/) — keeping the customer informed. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/returns/returns/ # The returns list and return statuses In Floormode, the returns list shows the returns Shopify knows about and the shipments coming back to you. In Floormode, Returns (/returns/all) is the Shopify-side view: the returns Shopify has announced, and where each one currently stands. ## On this page - Two sources, one list - Return statuses - The shipment coming back - See also ## Two sources, one list Returns reach you two ways, and both end up here: 1. From your returns page — a customer request you [approved] (/features/returns/requests/). 2. From Shopify directly — a return created in the Shopify admin, or by another app. Whichever way it started, the warehouse’s job is the same, so the list is the same. You never have to remember which system a given return came from to know where to look for it. ## Return statuses Status Means Requested Announced, not yet agreed Open Agreed and in progress Closed Finished Declined Refused Cancelled Withdrawn Alongside the return sits the reverse fulfillment — Shopify’s word for the return-side shipment — with its own Open / Closed / Cancelled state. ## The shipment coming back Opening a return (/returns/:id) shows the returned fulfillments, the deliveries on their way back to you, and the receipts you have already made against it. That last part is the join between the Shopify record and the physical reality: a return can be “open” in Shopify for a week while the parcel is in transit, and this page tells you which of the two you are actually waiting on. When the parcel arrives, it becomes a [return receipt] (/features/returns/receipts/) and every unit gets graded. ## See also - [Requests] (/features/returns/requests/) — the returns page side. - [Receipts] (/features/returns/receipts/) — grading what arrives. - [Search] (/getting-started/search/) — ⌘K finds returns, requests and receipts by name. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/returns/receipts/ # Receipts Grade every returned unit as it arrives and decide where it goes — sellable, quarantine or written off. In Floormode, Receipts (/returns/receipts) is where a returned parcel becomes decisions. Every unit is graded as it arrives, and every unit gets a [disposition] (/reference/glossary/#disposition). ## On this page - Find the parcel - Grade every unit - The three dispositions - At the returns station - Refunds when the receipt closes - See also ## Find the parcel Receive a return opens with a Parcel field. Scan the return label’s barcode, or type its tracking number, the return request’s number (RMA-00042) or the Shopify return’s name (#1042-R1). Floormode lists the returns the parcel may be as cards. None is picked for you: compare the customer on the card with the sender on the label, then press Use this. - The barcode won’t scan (taped over, crumpled, torn): tap the camera and fit the barcode and its number in the frame, then Read the number. Only that strip of the label is sent to Cloudflare Workers AI, which reads the tracking number. Floormode compares it with your returns itself, exactly, and never guesses a close number. If the card says Carrier not read, also compare the carrier on the label. A warehouse can turn this off in Settings → Stock → Receiving. - Already received: the parcel’s number is on another receipt. Open that receipt instead. - An outbound label (delivered): the customer reused your box, so the label is the old outbound one. Floormode lists that order’s open returns. Scan the return label if there is one. - Returned to sender: your own shipment came back undelivered. Receive it against the order. - No match: receive it as an unexpected return. A number read from the label shows as Read: …. It is a reading, not a confirmed parcel. The receipt can still be linked to its order. The receipt keeps the parcel’s tracking number. When you pick a return request, completing the receipt settles that request only, even if the order has another one. ## Grade every unit Each returned unit is inspected and recorded as sellable or damaged. Not the parcel — the unit. Caution Grading per unit rather than per parcel is the whole point. A three-item return where one item is scuffed is not “a damaged return” and not “a sellable return” — it is two units back on the shelf and one in quarantine. Grading at parcel level either loses a sellable unit or puts a damaged one back into stock, and the second mistake ships to the next customer. ## Grades With Grades on (Settings › Returns › Grades, off until Add a B-stock grade), the receiver picks a grade instead of sellable or damaged. Each grade says where its units go and how they are refunded: Refund Means Full refund The unit is paid in full. Hold for review The unit’s money waits for you (it is booked as damaged). Deduct % The refund is less that share of the unit’s value: a [value deduction] (/reference/glossary/#value-deduction) for worn or opened items, never for a fault. [B-stock] (/reference/glossary/#b-stock) goes to BSTK-01, a held bin each warehouse gets with its first B-stock unit, unless the receiver scans another bin. Through the API, a warehouse’s returnGradeBins setting names a bin per grade. A grade’s percentage is fixed on the unit when it is booked, so editing the grade later never re-prices units already back. An exchange releases no replacement for a unit that came back with a deduction: the request waits for you to release the replacement or refund it in Shopify, then Resolve it. ## The three dispositions Disposition Means Back to sellable stock Restocked. Available to promise again immediately. Damaged & quarantine Held out of sellable stock, in a quarantine bin, pending a decision. Write off Removed from inventory entirely, with the loss recorded. Each of these posts a movement to the [ledger] (/features/inventory/adjustments-and-movements/), so a returned unit’s fate is as traceable as any other stock change. A unit restocked here is reserved for a [backordered order] (/features/inventory/backorders-and-oversell/) waiting on it, just as a supplier’s delivery would be. That order is then picked and packed as usual; nothing ships on its own. ## At the returns station On the floor, a returns station checks a parcel in item by item: scan the return, its order or the packing slip, grade each item and say where it goes, then Finish return. The receipt is the same one this page shows, named “Received at RET-1”. The finish settles the approved return requests exactly as closing a receipt here does, and the screen says what was queued, held for review or still waits for items. Only people whose role holds Receive returns at a returns station see it (Admin and Manager do; the built-in Floor role does not). ## Refunds when the receipt closes When you Complete a receipt whose order has an approved return request, the dialog offers Refund approved return requests for the goods that came back, ticked by default. The refund, store credit or exchange then goes out as the receipt closes. Untick it and nobody is paid; the requests stay approved. You approved the return when you had the context, so there is no second approval once the parcel is in your hands and graded. Returns that arrived without an approved request still need a human decision, and they wait for one. ## See also - [Requests] (/features/returns/requests/) — where approval happens. - [Adjustments & movements] (/features/inventory/adjustments-and-movements/) — where dispositions are recorded. - [Bins] (/features/inventory/bins/) — the returns and quarantine bin types. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/insights/overview/ # Insights What the operation did, and what it has to buy next. Floormode’s Insights (/insights) answers two questions: how did the operation perform, and what does it need to buy next. ## On this page - What you can do here - Bounded lists - Where to next ## What you can do here [Reports] (/features/insights/reports/) Elevate plan. Throughput, cycle time, on-time ship, pick accuracy, returns and COGS/margin. [Replenishment] (/features/insights/replenishment/) Velocity-based reorder points, safety stock, and reorder plus transfer suggestions. [Stock value] (/features/insights/stock-value/) What the stock on your shelves is worth and what it cost you, including landed cost. ## Bounded lists Note Long lists here stop at a safe number of rows, and say so. A count shown as “300+” means at least 300 — not exactly 300. This is deliberate honesty about a real constraint. Producing an exact count of a very large set means scanning all of it, which is slow and gets slower as you grow. Rather than showing a number that is quietly a sample, or a page that times out, the app shows a bound and tells you it is a bound. ## Where to next - [Stock] (/features/inventory/stock/) — the numbers replenishment reasons about. - [Subscription plans] (/getting-started/subscription-plans/) — Reports needs Elevate. - [Home] (/features/home/overview/) — the same day, as work rather than analysis. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/insights/reports/ # Reports Elevate plan. Throughput, cycle time, on-time ship, pick accuracy, returns and the COGS/margin report. [Elevate plan] (/getting-started/subscription-plans/) In Floormode, Reports (/insights/reports) is the operational analytics view: what the warehouse actually did, measured. ## On this page - The reports - What each one is for - COGS and margin - See also ## The reports Report Measures Throughput How much work went through, per period Cycle time How long an order took from paid to shipped On-time ship Whether you hit your own promise Pick accuracy Lines picked in full, against the ones that came up short Returns What is coming back, and why COGS / margin What you sold cost you, and what was left ## What each one is for Throughput is capacity planning. It tells you what a normal day looks like, which is the only way to know whether tomorrow is a busy day or a problem. Cycle time is where delays hide. An order that took four days might have been picked in an hour and then sat waiting for a carrier collection — cycle time broken down by stage shows which. On-time ship is the promise you made to the customer, measured. It is the number to quote when someone asks whether the operation is working. Pick accuracy counts, per day, the pick lines picked in full against the ones that came up short: the picker found fewer units than the line asked for. A rising share of short lines usually points at stock records that drift from the shelves: count those bins. It does not count wrong items: scan verification at [pack] (/features/fulfillment/pack/) stops those before the parcel is closed. Returns by reason is a product-quality signal as much as a warehouse one. A SKU with an unusual “not as described” rate has a listing problem, not a picking problem. ## COGS and margin The COGS/margin report builds on the same weighted-average unit cost that drives [stock value] (/features/insights/stock-value/), tracked at ship and including landed cost. Because the cost is captured when the unit ships rather than recomputed later, margin reflects what that specific unit actually cost you. Included on the Elevate plan. ## See also - [Stock value] (/features/insights/stock-value/) — the same cost basis, on the shelf. - [Subscription plans] (/getting-started/subscription-plans/) — what Elevate unlocks. - [Counts] (/features/inventory/counts/) — accuracy at the bin level. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/insights/replenishment/ # Replenishment Velocity-based reorder points, safety stock, and reorder plus transfer suggestions across warehouses. Floormode’s Replenishment (/insights/replenishment) answers “what do I need to buy, and what can I just move?” ## On this page - Reorder points and safety stock - Reorder or transfer - Where a suggestion ends up - See also ## Reorder points and safety stock Reorder points are velocity-based: how fast a SKU actually sells decides when it needs reordering, rather than a fixed threshold someone set once and never revisited. [Safety stock] (/reference/glossary/#safety-stock) is the buffer underneath that — the cushion that absorbs a supplier being late or a week being unusually good, without going to zero. ## Reorder or transfer Not every shortfall needs a purchase order. Where one warehouse is short and another is long on the same SKU, the answer is a transfer, and suggestions include both: - Reorder — buy more from the supplier. - Transfer — move it between your own warehouses. Getting this right is where multi-warehouse operations save real money: buying stock you already own, in the wrong building, is a common and expensive mistake. You can arrive here pre-filtered. The + Reorder action on a low-stock row in [Stock] (/features/inventory/stock/) lands you on this page already filtered to that SKU. ## Where a suggestion ends up Every suggestion ends somewhere concrete — the draft does not vanish back into the app: - Send it to Logistified, where purchasing lives, or - Copy it as CSV to hand to your supplier directly. Note Deciding what to buy is where Logistified takes over: the purchase order itself is raised there, and once it is confirmed it comes back to you as an [expected delivery in receiving] (/integrations/logistified/). See [Integrations] (/integrations/overview/) for how the two apps divide purchasing and receiving. The CSV export remains the path that works with any supplier and any system, connected or not. ## See also - [Stock] (/features/inventory/stock/) — where + Reorder starts. - [Receiving] (/features/inventory/receiving/) — where ordered goods arrive. - [Stock value] (/features/insights/stock-value/) — what holding that stock costs. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/insights/stock-value/ # Stock value Elevate plan. Recorded warehouse and transit costs, shelf retail value, and cost of goods sold. [Elevate plan] (/getting-started/subscription-plans/) In Floormode, Stock value (/insights/stock-value) separates inventory at recorded acquisition cost, shelf retail selling value, and the cost of goods sold. ## On this page - Warehouse and in-transit cost - Weighted-average unit cost - Tracked at ship - Landed cost - See also ## Weighted-average unit cost Cost is tracked as a weighted average per unit. When you buy the same SKU at different prices — a normal thing over a year of supplier price changes and currency movement — the average moves with the mix you actually hold, rather than pretending every unit cost what the last one did. ## Warehouse and in-transit cost Inventory at recorded cost shows warehouse cost, in-transit cost and their combined recorded cost for each currency. Currencies remain separate; the report does not convert or add them together. Dispatching a physical warehouse transfer moves its recorded cost from the source warehouse into transit. Partial receipts move only the accepted quantity into the destination warehouse’s cost position. Cancelling an unshipped remainder does not remove goods already in transit. Accepted arrivals at an external destination retire the corresponding transit value without creating a second warehouse cost position in Floormode. Confirmed returns and recorded losses also reduce outstanding transit quantities. A transfer is not a sale and does not itself create cost of goods sold. The view reads current warehouse cost positions and outstanding transfer executions, rather than historical movement records. It includes at most 500 warehouse positions and 500 active transit lines. If either limit is reached with more rows remaining, Incomplete cost subtotal appears and amounts are marked with a plus sign. These are partial amounts, not the full inventory value. Units with an unknown cost or currency are counted and excluded from the displayed amounts. Warehouse stock without any recorded cost position is outside this report’s valuation scope. An empty report does not mean physical stock has zero value. ## Tracked at ship The cost is captured at ship, when a specific unit leaves. Note This is what makes the number stable. If cost were recomputed at report time, last quarter’s margin would change every time a new delivery landed at a different price — which makes historical comparison meaningless and makes accounting reconciliation genuinely difficult. Capturing at ship means a shipped unit’s cost is a fact from that day forward, and the same report run twice gives the same answer. ## Landed cost Landed cost is included: not just what the supplier invoiced, but what it cost to get the goods to you. For international inbound that means duties and freight rather than the ex-works price. The difference is not marginal. A product with a 45% margin on the invoice price can be a 20% margin product once landed cost is counted, and only one of those two numbers is worth making decisions with. The same cost basis feeds the COGS/margin report under [Reports] (/features/insights/reports/). ## See also - [Reports] (/features/insights/reports/) — margin built on the same cost basis. - [Replenishment] (/features/insights/replenishment/) — what to buy next. - [Stock] (/features/inventory/stock/) — the quantities being valued. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/insights/accounting-export/ # Accounting export Each month's cost of goods sold and stock value from Floormode as a Xero journal, a CSV, or in Germany and Austria a DATEV file, for your accountant. In Floormode, Accounting export is the last card on Insights → Reports (/insights/reports). Pick a month and a file, then press Download. It comes with every plan. ## On this page - The two numbers - How your accountant books purchases - Setting it up - Importing the file - When a month is ready - lexoffice (Germany) - Post to QuickBooks or Xero - Where the detail lives ## The two numbers - Cost of goods sold: what the goods you shipped that month cost you, at the weighted-average cost of each item in its warehouse. Shipments of items without a recorded cost are left out and counted on the card. - Stock value at the month’s end: every item’s units times its weighted-average cost, at midnight when the month ends. Units without a recorded cost are not part of it, as on [Stock value] (/features/insights/stock-value/). Both come from the same records, so the file, the CSV detail and the stock value agree to the cent. Each currency gets its own lines. Which midnight. A month ends at midnight in one time zone, which Set up names: “Months end at midnight in …”. It is fixed by whichever comes first: saving the setup, the first stock cost Floormode records (a costed receipt, for example), or the first month’s stock value. Until then it is your oldest active warehouse’s time zone. A warehouse uses your store’s time zone from Shopify unless you set its own on its Details tab, so a store in Sydney counts its months in Sydney. Only when neither is known is it UTC. A warehouse’s time zone changing later never moves a month boundary. ## How your accountant books purchases You choose this once. Each chart starts on its usual way, and you can change it. - As expense when bought (the usual way in Germany and Austria; SKR03, SKR04 and your own numbers start here): every supplier invoice is booked as an expense at once. The month then posts the stock change: the stock value at the month’s end minus the one at its start. An increase is posted to the stock account (SKR03 3980, SKR04 1140) against the stock change (SKR03 3960, SKR04 5880); a decrease the other way round. - To stock (Xero’s way; a Xero setup starts here): purchases go to the stock account. The month then posts the cost of goods sold: goods expense (SKR03 3400, SKR04 5400, Xero 310) against stock (SKR03 3980, SKR04 1140, Xero 630). Floormode does not see your supplier invoices, so any difference between your stock account and the stock value (shrink, write-offs) is shown in the CSV, not posted. A month with nothing to post gets no posting file, only the CSV. ## Setting it up Open Set up on the card and answer three questions: the chart of accounts, how purchases are booked, and the two accounts that posting uses. The first setup starts by your store’s country: Your store is in The setup starts on The file The UK, Australia, New Zealand or the US Xero, in your country’s Xero edition, with its zero tax rate (“No VAT”, “BAS Excluded”, “No GST” …) Xero manual journal Germany or Austria SKR03 (or pick SKR04) DATEV Anywhere else Your own numbers CSV Every chart stays on the list, wherever you are: outside Germany and Austria, SKR03, SKR04 and the DATEV file come last. While Floormode is still reading your store’s country, the chart shows “Loading…” and Save waits; picking a chart yourself ends the wait. The German charts’ accounts are digits of your account length (4 unless your accountant says otherwise); Xero codes are up to 10 letters or digits. Under DATEV details you can add the consultant and client numbers and the month your fiscal year starts; under Xero details, your region and the name of your zero tax rate. One line per warehouse writes a line per warehouse (in DATEV as the cost centre, in Xero as the tracking option Warehouse, which must exist in Xero). ## Importing the file - Xero: go to Accounting → Reports → Journal Report → Manual Journals → Import and choose floormode-xero-journal-2026-10.csv. The journal arrives as a draft for you or your accountant to post. Xero takes your base currency only; lines in another currency are in the CSV. - CSV: everything behind the numbers, one row per kind of record: the posting lines, the cost of goods sold per day and per item, and the stock value per item and warehouse at the month’s end. Any other accounting system, or your accountant’s spreadsheet, starts from this file. - DATEV (Germany and Austria): give the file (EXTF_Floormode_2026-10.csv) to your accountant. They import it in DATEV under Stapelverarbeitung → Import as a Buchungsstapel. It is one batch per month. ## When a month is ready A month’s file is ready once its books are complete: usually on the 2nd or 3rd of the next month, after the night that writes the last day and the month-end value. Until then the card says when. The current month offers the CSV so far; its posting comes when the month closes. Stock values start with the month Floormode first recorded a cost change in (a costed receipt, or a shipment from stock without a cost). An earlier month has its cost of goods sold but no stock value, and the card names the month the values start with. ## lexoffice (Germany) lexoffice (Lexware Office), a German bookkeeping tool, cannot import bookings ([Lexware help: Buchungsdaten importieren] (https://help.lexware.de/de-form/articles/548556-buchungsdaten-importieren), [Wie importiere ich Daten in Lexware Office?] (https://help.lexware.de/de-form/articles/548172-wie-importiere-ich-daten-in-lexware-office)). It imports master data, bank transactions and receipts ([bank2lexware] (https://www.bank2lexware.de/ratgeber/lexware-csv-import-formate/)). Give your accountant the DATEV file instead: lexoffice’s own output to the accountant is a DATEV export too. ## Post to QuickBooks or Xero Connect QuickBooks Online or Xero under Settings → Apps & API → QuickBooks or Xero, and Floormode posts each closed month to that ledger as one journal: the same lines the file holds (the cost of goods sold, or the change of your stock value). Nothing else is sent: no sales, no bills, no tax. Every store’s costs post to the one ledger. - Accounts: choose the stock and cost accounts from your ledger’s own list (Accounts in its dialog). Nothing posts until they are chosen. - When: from the month after you connect, so a month another app already posted is not posted twice. Turn off any other app or inventory tracking that posts cost of goods sold for the same items. With Post each month automatically off, a closed month waits for Post now. - Locked months: a month your ledger has locked waits for you; Post on instead posts it on the first open day. - A change after posting: Re-post reverses the posted journal (exactly as it was posted) and posts the month again. A month that is now zero is only reversed. - Unconfirmed: if Floormode cannot tell whether a journal reached the ledger, it never sends it again blind. Check QuickBooks / Xero looks again; Mark as posted takes your word; Post again sends a new journal (check the ledger first). - Disconnect ends Floormode’s access to the ledger. The journals already posted stay in your ledger. ## Where the detail lives Every line names its month. The records behind it are the cost of goods sold books (one part per day) and the stock value at month end book (one part per month) on the History archive card under Settings → Customer privacy: written once, checked, and kept ten years. ## See also - [Stock value] (/features/insights/stock-value/): today’s value and the weighted-average cost. - [Reports] (/features/insights/reports/): margin on the same cost basis. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/overview/ # Settings Thirteen sections in three groups, from warehouses to billing, with a sub-nav down the side and breadcrumbs throughout. Floormode’s Settings (/settings) has thirteen sections in three groups: Operations, Customers and Account. Unlike the other nav entries it does not use a tab strip — it renders a sub-nav down the side, with breadcrumbs so you always know where you are. You see only the sections your role can open. Find a setting sits at the head of the sections: type what you want to change — “box”, “fraud”, “printer”, “return window” — and pick it from the list. Settings opens the page that holds it and puts you on its card, opening the page’s Advanced fold when the setting is inside. The list shows only settings your role can open; ↑ and ↓ walk it, Enter opens one and Esc closes it. ## On this page - Operations - Customers - Account - Where to next ## Operations [Warehouses] (/features/settings/warehouses/) Your locations, their Shopify location mapping, and every per-warehouse stock policy. [Fulfillment] (/features/settings/fulfillment/) How work reaches the floor and is packed: work assignment, pick profiles, the pack checklist and packing slips. [Pack stations] (/features/settings/pack-stations/) Each pack table with its printer, scale and camera, used from the PC that stands there. [Automation] (/features/settings/automation/) Elevate plan. Three ordered rule cascades: order rules, order routing and shipping rules. [Carriers & packaging] (/features/settings/carriers-and-packaging/) Carrier accounts, label printers and the box catalog packing chooses from. ## Customers [Customer emails] (/features/settings/customer-notifications/) The emails your customers get, milestone by milestone, and the brand they wear: Emails, Brand, Words, and Sender & page. [Customer privacy] (/features/settings/privacy-requests/) Customer data requests Shopify forwards: review them, export the records and track delivery. ## Account [Apps & API] (/integrations/health-panel/) Connections to the sibling apps, and the health panel that says what each one has actually done. [Stores] (/features/settings/stores/) Where your company's orders come from: one page per Shopify store. [Team & devices] (/features/settings/team/) Everyone who works in Floormode: their role, their warehouses, the floor devices they sign in on, and each warehouse's time clock. [Billing] (/features/settings/billing/) Your plan, its status, and what each tier unlocks. Shipping & carriers, Orders & dispatch, Customer emails, Apps & API and Team & devices have a tab strip of their own, each tab with its own URL: Customer emails’ Emails, Brand, Words and Sender & page; Team & devices’ People, Roles, Floor devices, Time clock and the trailing Defaults tab marked Advanced. A page’s rarely changed settings sit in its Advanced fold at the end, which opens by itself when one of them is changed. ## Where to next - [Initial setup] (/getting-started/initial-setup/) — the order to configure these in. - [Finding your way around] (/getting-started/finding-your-way-around/) — why Settings works differently. - [Subscription plans] (/getting-started/subscription-plans/) — what each tier unlocks. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/warehouses/ # Warehouses Your Floormode locations, their Shopify location mapping, and every per-warehouse stock policy. In Floormode, Warehouses (/settings/warehouses) connects each stock site to Shopify and holds its fulfillment settings. ## On this page - Shopify location mapping - Per-warehouse stock policies - Bins & pick path - Zones, stations & staff - See also ## Shopify location mapping Each warehouse maps to a Shopify location. A warehouse that is not mapped carries a warning badge in the list. Caution An unmapped warehouse cannot send availability to Shopify. Link its Shopify location before going live. The [setup guide] (/getting-started/setup-guide/) tracks the connection. ## Per-warehouse stock policies Set per warehouse on the Settings page of the question each answers; with several warehouses, the page’s warehouse switcher chooses which one you see (?warehouseId=): Policy Where What it does Accept backorders Orders & dispatch › Dispatch (/settings/orders) Permit selling beyond on hand. Off by default. Charge the card when the parcel ships Orders & dispatch › Dispatch Take payment when the order ships rather than at checkout. Expiry-first picking (FEFO) Receiving & stock (/settings/stock) Allocate the shortest-dated stock first. Every plan. Extra units a delivery may bring (%) Receiving & stock How much more than expected the floor may book in. Expiring soon (days) Receiving & stock How far ahead stock counts as approaching expiry. The warehouse’s own page keeps what the warehouse is: Layout, Stock and Details (the Shopify location, go live, the time zone). Per-warehouse is the right granularity for all of these. A distribution centre and a retail store shipping its own shelf stock should not share one oversell policy, and a site handling perishables needs [FEFO] (/reference/glossary/#fefo) where a site shipping hardware does not. ## Bins & pick path On the warehouse’s Layout tab (Settings → Warehouses → your warehouse). The Layout tab is one list of your locations. Bins are the only places stock can live; zones, aisles, racks and shelves are optional groups whose order is the route pickers walk. Use Add locations for a numbered range, a pattern of aisles, racks and shelves, or a pasted list; Add aisle, rack or shelf for one group; and the + on any group row to add locations inside it. Drag a row onto a group to move it inside, between rows to reorder, or use Move to… in the row menu. Flat bins work too: you can receive, store and pick stock without any group and without drawing a map. ### Optional 2D map Open 2D map when a visual floor plan would help your team. 1. Start with Rectangle, L shape or U shape, or draw connected floor areas for your building. Starter shapes appear only while the plan is empty. 2. Find an existing location in the search list. Selecting it centers the canvas and opens its position and size fields. 3. Move or resize locations to place them. Dashed outlines indicate suggested positions that have not been saved as placements. 4. Add walls for partitions. Select a floor area or wall to adjust its dimensions or endpoints in the side panel. ### Build directly on the map Choose Zone, Aisle, Shelving or Bin in Build locations. Click the map for a standard footprint or drag to choose its size. Check the location code and parent, then choose Place. A failed placement keeps your code and footprint so you can correct it and retry. Shelving creates a container. Open its contents to add the bins inside it. You can also use Use standard footprint and the directional buttons with a keyboard. Escape cancels a pending placement. Depth view gives bins and shelving a slight 3D appearance. Turn it off for the flat plan. This only changes the display. Faces stay inside the location footprint, so selection and map coordinates stay the same. Layout Undo changes drawings and positions; it does not delete a location you created. Manage a location from Locations when you need to archive it. Pan lets you drag anywhere, including over a rack. Scroll to zoom or use Zoom to fit. Double-click an aisle or rack, or choose Open contents, to arrange the next level. Position and size fields apply when you leave the field or press Enter. The toolbar shows Saved, Saving… or Unsaved changes; while changes are unsaved, Save in the page’s save bar saves them at once. Undo and Redo cover the latest 50 edits in the current level, including an edit that has already saved. A drag counts as one edit. Use the toolbar or ⌘/Ctrl Z and ⌘/Ctrl Shift Z while the editor has focus. History resets when you create a location, leave a level or reload. The size fields use map units. Physical walking previews use the building settings below; metre distances appear only after calibration. Manage locations returns to the location tools. Erasing a drawing never deletes a bin or its stock. ### Storeys and walking routes Use Building settings to add storeys, name them and set a scale. Existing plans start on Ground floor. A building storey is separate from an aisle, rack level or Shopify location. Choose the storey above the map; the selection survives a reload. Enter the metres represented by 100 map units. For example, if a 500-unit wall measures 50 metres, enter 10. Leave the value at zero if the scale is unknown. The preview then reports map units. Routes between storeys require a scale on the connected storeys. Add stairs or lifts with one endpoint on each storey. Both endpoints must be on walkable floor. You can disable a connection or allow travel only from its first endpoint to the second. Carts use lifts. Traversal and lift-wait seconds are estimates separate from walking distance. Use Blocking fixtures for the footprints of storage or equipment that people cannot walk through. A visual rack rectangle does not automatically block travel. Select a location and open Building placement to set its storey and the point a worker can approach from outside storage. Children share their physical parent’s storey. Moving a container to another storey clears its children’s approach points so they can be checked again. Stations are placed on the same map: drag a station’s marker, or select it under Stations beside the map to type its position, place it, and set its storey and approach point. The map draws one storey at a time: a station appears on the storey of its building placement, and in a building with several storeys a station without one is listed as No storey until you choose its storey. Every floor area, wall and station can also be selected from the lists beside the map, so the map works from the keyboard. Save or discard building settings before editing the map. If another user changes the building while you edit, saving refuses the stale revision. Discard edits and reload saved layout restores the saved plan. Reassign mapped locations and stations before removing a storey. Preview walking route checks a path through floor areas, around walls and blocking footprints, and through enabled connections. The calculation may use a coarser grid to stay within its work limit. Narrow gaps can remain unresolved; the preview does not promise the shortest possible path or vehicle-clearance measurements. Missing approaches, missing scales and unreachable paths are shown explicitly. Pick batches also offer Remaining pick route. It follows the existing order from the first remaining bin to the saved destination station. Completed picks stay unchanged. At most 24 remaining lines are previewed; a partial preview does not draw a shortcut to the final station. Continue with the full pick list when the preview is partial or unavailable. ## Zones, stations & staff Sub-page: /settings/warehouses/:id/work-areas. Give staff their zones and skills, and define the stations they work at. This is what makes auto-assignment sensible: work routes to someone who is in the right part of the building and trained for the job, rather than to whoever is least busy on paper. ## See also - [Bins] (/features/inventory/bins/): the locations this defines. - [Queue] (/features/fulfillment/queue/): where zones and skills decide assignment. - [Backorders & oversell] (/features/inventory/backorders-and-oversell/): the oversell switch in context. - [Layout] (/features/inventory/layout/): adding locations in bulk and the pick walk. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/fulfillment/ # Fulfillment settings How work reaches the floor and how it is packed — work assignment, pick profiles, the pack checklist, packing slips and delivery dates. In Floormode, how work gets from an order to a person, and how that person packs it, is set on three Settings pages: Picking & floor, Packing and Receiving & stock. The three work switches stand beside what they switch, all off until you turn them on: Auto-assign pick tasks on Picking & floor, Replenish pick bins automatically on Receiving & stock, Route orders with rules on Orders & dispatch › Order routing. ## On this page - Work assignment - Everything is opt-in - The other cards - Reached from where it matters - See also ## Work assignment Switch What it does Auto-assign pick tasks As soon as an order has its stock reserved, its pick goes to the least busy person who works in that zone, instead of waiting for someone to claim it. Replenish pick bins automatically When a pick takes a pick bin below its minimum, a replenish task tops it up from bulk stock. Route orders with rules Your routing rules choose which warehouse ships each order. Without a rule that fits, the nearest warehouse that has everything ships it. When work reaches the floor is not a switch here: you decide it on the [Waves] (/features/fulfillment/waves/) tab, wave by wave. ## Everything is opt-in Note All three start off. Nobody is handed work automatically, no replenish tasks appear on their own, and routing rules do not run until you switch them on. That is deliberate. Each switch changes how your team’s day works — who gets which job, what appears in the queue without anyone asking, which warehouse ships an order. Your warehouse chooses those; they do not come switched on with the app. Worth knowing: if the queue is not handing out work, nothing is broken. That is the default, and this card is where you change it. ## The other cards The page’s other cards include: - Pick profiles — named recipes for cutting pick batches: which orders, picked how, how many at a time. - Pack checklist — per warehouse, the steps every parcel goes through at the pack station before it is fulfilled: start from Just pack, Weigh + label or Proof photo, then set Photo, Weigh, Details, Check and Label to off, optional or required. See [Pack] (/features/fulfillment/pack/#the-pack-checklist). - Packing details — extra fields the packer fills in, such as a seal number. - Packing slip — what the printed slip in the parcel shows. It prints on the warehouse’s paper: US Letter in the US, Canada, Mexico and Puerto Rico, A4 elsewhere, with the day as the warehouse’s country writes it, in its time zone. The delivery note for a label printer is 4 × 6 in in those countries and 100 × 150 mm elsewhere. - Delivery dates — read the delivery date your customers chose and pack each order on the right day. See [Delivery dates] (/features/settings/delivery-dates/). ## Reached from where it matters Each switch is linked from the screen where you would notice you want it: - The [queue] (/features/fulfillment/queue/) links to auto-assignment. - [Placement] (/features/inventory/placement/) links to automatic replenishment. - The routing rules link back to the routing switch. The routing rules themselves — which warehouse or dropship vendor ships an order — live under [Automation] (/features/settings/automation/). This card only decides whether they run at all. ## See also - [Queue] (/features/fulfillment/queue/) — auto-assignment in practice. - [Placement] (/features/inventory/placement/) — automatic replenishment in practice. - [Waves] (/features/fulfillment/waves/) — when picking work reaches the floor. - [Automation] (/features/settings/automation/) — the routing rules themselves. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/delivery-dates/ # Delivery dates Read the delivery day a customer chose at checkout, pack the order in time for it, and hold its picking back until its pack day. Some customers choose a delivery day at checkout, with a date picker app in your store (Buunto, Zapiet, EasyRoutes and others). Floormode can read that day and work out when the order has to be packed. Orders, the order page and Home then show the pack day instead of Shopify’s fulfil-by date. Delivery dates are off until you set them up. Orders without a chosen day are not affected: they keep Shopify’s fulfil-by date. ## On this page - Set it up - When an order is packed - Picking waits for the pack day - Where you see it - When a date cannot be read - Turning it off - See also ## Set it up 1. Open Settings → Orders & dispatch, the Delivery dates card on its Dispatch tab. 2. Under Read the date from, choose the order attribute your date picker writes the day into, for example Delivery Date. The list shows the attributes your recent orders carry; the line under it says how many of them carry the one you chose. If yours is not there, choose Another attribute… and type its name. 3. Check the Date format. Automatic reads dates whose order is never in doubt, such as 2026-10-17 or 17 October 2026. A date like 03/04/2026 can be read either way, so choose day first or month first if your date picker writes dates like that. 4. Check the Store time zone. It starts on your store’s time zone from Shopify, or your browser’s while Floormode does not know the store’s yet. 5. Look at the preview. It shows how many of your recent orders it can read, with a few examples. 6. Choose Save in the bar at the bottom. After saving, Floormode reads the delivery date of every open order again; the line at the bottom of the card shows how far it has got. Closed orders are not changed. ## When an order is packed Each warehouse has its own packing days: the Packing days card under the delivery dates, on the same Dispatch tab; with several warehouses, choose one in the page’s warehouse switcher. The calendar can be set before delivery dates are on; it is used once they are. - Packing days before delivery: how many packing days before the delivery day an order is packed. The default is 1. Use 0 to pack on the delivery day itself. - Packing days of the week: the days this warehouse packs. The default is Monday to Friday. - Closed days: holidays and other days without packing. Days off and closed days are skipped. With the defaults, an order for Tuesday is packed on Monday, and an order for Monday is packed on the Friday before. The day turns at midnight in the warehouse’s own time zone. ## Picking waits for the pack day Turn on Picking waits for the pack day in the same card to hold such orders back from picking. An order with a delivery date is then ready to pick on its pack day, not before: the pick queue, Floor Mode’s Start picking and new batches leave it out until that day begins in the warehouse’s time zone. Its stock stays reserved for it the whole time. The switch is off until you turn it on, warehouse by warehouse. - On Orders, a waiting order says Packs and its pack day. - In Floor Mode, Start picking says how many orders wait and when the first one packs. - To pick one order early, open it and choose Pick now next to its delivery date. Undo makes it wait again. The order page says who let it through and when. ## Where you see it - Orders: the Pack today view lists the open orders whose pack day is today or has passed, oldest first. The Pack day filter narrows any view: Overdue, Today, Next pack day, Later, No pack day or Unreadable date. Add the Delivery date column under Columns to see the customer’s day and the pack day in each row. The Due column shows the pack day for orders that have one. - The order page: under Ship to, the delivery day, the day it is packed and where. - Home: the due and late numbers count by pack day. ## When a date cannot be read An order whose date cannot be read keeps Shopify’s fulfil-by date and is never held back. The order page says why, for example that the date could be day first or month first. Pack day → Unreadable date on Orders finds these orders. Changing the date format usually fixes them: after saving, Floormode reads the open orders again. ## Turning it off Choose Off under Read the date from and save. Orders go back to Shopify’s fulfil-by date. A saved view that filters by pack day stops filtering by it until delivery dates are on again. Tip A warehouse’s Packing days card says Used when delivery dates are on until you set them up here, with a link to this card. ## See also - [Fulfillment settings] (/features/settings/fulfillment/): the page this card is on. - [Views & saved views] (/features/orders/view-tabs/): the Pack today view and the Pack day filter. - [Waves] (/features/fulfillment/waves/): holding picking work back by hand. Last updated: 5 November 2026 --- Source: https://docs.floormode.app/features/settings/pack-stations/ # Pack stations Set up each pack table with its printer, scale and camera, tell the pack PC where it stands, and decide what every parcel goes through there. In Floormode, a pack station is a pack table with its devices: the printer its labels print on, the scale that weighs its parcels and the camera for a photo of the contents. Packers use those devices from the PC that stands there. Stations are set up under Settings → Packing; what each parcel walks through at them is the warehouse’s [pack checklist] (/features/fulfillment/pack/#the-pack-checklist). ## On this page - Add a station - The pack PC: where it stands - The list - What a parcel goes through: the pack checklist - See also ## Add a station 1. Open Settings → Packing and choose Add pack station. It takes about two minutes. 2. Code: the station’s name on the floor, such as PACK-01. The next free code in that series is filled in. 3. Warehouse: where the table stands. 4. Printer: the label printer, from your PrintNode account. Labels for parcels packed here print on it. With no PrintNode printer yet, Connect PrintNode leads to Settings → Shipping & carriers. 5. Scale: A USB scale on the pack PC (Chrome or Edge on that PC; one click allows the scale the first time, and not inside the Shopify admin), a scale through PrintNode on the computer it is plugged into, or No scale · weights are typed. A PrintNode scale is listed once it is plugged in and Refresh scales ran. 6. Test the scale: put something on it. Saving never waits for the test. 7. Camera: On the device, or None. 8. Save. On the PC at this table, tick Use this PC at PACK-01: its scale and printer are then used for parcels packed here. ## The pack PC: where it stands A station’s devices follow the PC, not the person. The browser on the pack PC remembers which station it stands at: - In Settings → Packing, tick Use this PC at … while setting the station up on that PC. - On the floor’s pack screen, the station line says PACK-01 · scale ready, or No pack station chosen. Choose or Change opens This PC stands at: pick the station, and its scale and printer are used here. Your work list stays as it is. - At the desk, Choose the pack station offers two separate answers: This PC stands at this station (the devices follow this PC) and Use it for my work too (your floor work follows this station). When the PC stands at one station and your work is set to another, a line says so, for example “This PC is at PACK-01 · your work is set to PACK-02”, so a parcel never prints at the wrong table. ## The list Each row names its station, its Printer, Scale and Camera, and under Devices here whether the station’s PC is there: Connected · heard 14:02, Not connected · last heard 14:02, or Not seen yet. Set up changes a station’s devices. ## What a parcel goes through: the pack checklist Each warehouse decides the steps every parcel walks at its pack stations before it is fulfilled: Settings → Packing → Pack checklist. Start from a preset (Just pack, Weigh + label or Proof photo), then set each step to Off, Optional or Required: a photo of the contents, the weight, packing details such as a seal number, a quality check, and the label before fulfilment. A required step must be done before the parcel can be fulfilled. Under the steps, the card checks your stations against them, one line per gap: - “PACK-02 has no scale: weights are typed there.” - “PACK-02 has no camera: the photo is taken with a phone or tablet, or uploaded.” - “PACK-02 has no label printer: labels print from the desk there.” When nothing is missing it says Every pack station has what these steps need. Tip For a weighing step, a USB scale on the pack PC needs nothing installed. A scale on another computer needs PrintNode on that computer. ## See also - [Pack] (/features/fulfillment/pack/): the pack station at work, the checklist and weighing. - [Floor pack] (/features/floor/pack/): packing on a scanner. - [Compatible hardware] (/getting-started/compatible-hardware/): scanners, scales and printers that work. - [Carriers & packaging] (/features/settings/carriers-and-packaging/): PrintNode and the box catalogue. - [Station devices and the packing slip] (/features/settings/station-devices/): the devices each station takes. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/station-devices/ # Station devices and the packing slip The devices each station kind takes, which station a PC stands at, and the packing slip with the label. Every Floormode station — a pack bench, a receiving desk, a QC table, a count station, a dispatch table — can have its devices. Set them up once from the desk; every screen at that PC uses them. ## On this page - Which devices a station takes - Which station this PC stands at - The packing slip with the label - The returns station - See also ## Which devices a station takes Station kind Devices Packing Label printer, document printer, scale, camera Receiving, Quality check Label printer, scale, camera Counting Label printer, scale Dispatch Document printer, label printer, scale Production Label printer Returns Label printer, camera, document printer - Label printer — parcel, item and lot labels. - Document printer — packing slips, customs papers, manifests, on Letter or A4. - Scale — a USB scale on the PC, or one connected through PrintNode. - Camera — the PC’s webcam, or a phone’s or tablet’s own camera. Printers and PrintNode scales come from PrintNode: connect it under Settings → Shipping & carriers → Carriers & printing, then pick them. Where: Warehouses → Work areas → Stations, the Devices column (every kind), or Settings → Packing → Pack stations. Both open the same dialog. A station’s kind can change only while it has no device its new kind does not take: remove it first (“Remove the camera first: a count station has no camera.”). ## Which station this PC stands at On the floor, Choose on the station line (or the pack bench’s station chip) tells this PC which station it stands at. Any kind works: a one-table shop can bind its one PC to its pack bench, and the pack screen of a PC bound to a receiving desk uses that desk’s label printer and scale, saying “Using RECV-01’s devices.” The receiving screen shows which station the PC stands at; its steps still take typed weights and the label sheets you print from the desk. Your own work station (the lists you see) is a separate choice. A person uses a station’s devices for any task they may do, at stations of their own warehouses. ## The packing slip with the label With a document printer at the pack station, Fulfil + print label prints the packing slip beside the label, and the carrier’s customs papers too. - Settings → Packing → Packing slip → “Print the slip with the label” — on by default. It only acts where a station has a document printer, so a bench without one works as before. - The paper is the warehouse’s (Letter in the US, Canada, Mexico and Puerto Rico, A4 elsewhere), unless the document printer names its own in the Devices dialog. The recipient’s country never decides. - Each slip is kept once per parcel and content. Pressing again, reloading or packing the parcel at another bench prints the same slip; it never prints twice by itself. An edited note makes it a new slip. - A document never holds up the parcel. If the slip did not print, the parcel is still fulfilled, and the bench and the finished parcel say “Slip not printed · Print slip”. Print slip prints the slip alone, never the label again. - Print again reprints the label only. ## The returns station A Returns station is a table where customers’ parcels are opened and checked in. Add one under Warehouses → Work areas → Stations (kind Returns); bind the PC at it like any other station. - On the floor: ⋯ → Returns, or a return left open on Today. Scan the return, its order or the packing slip’s QR; No paperwork opens a return without one. A return opened by mistake, with nothing booked, is cancelled from ⋯. Each item: its condition, where it goes (Back to stock, Quarantine, Scrap), its bin, and its lot, expiry or one serial per unit when the item tracks them. Finish return settles the order’s approved return requests and says what it queued (refunds, store credit, exchanges), what owed nothing, what is held for review and what still waits for items. - Who: the permission Receive returns at a returns station. Admin and Manager hold it; the built-in Floor role does not, because finishing can queue refunds. Add it to a role under Team → Roles (the Stations panel says so while no other role has it). - Where a return was received: the station of the PC that opened or finished it, else the person’s own returns station, else — while the warehouse has no returns station — the station the PC stands at. The receipt page says “Received at RET-1”; nothing is refused for a missing or retired station. - Output: Team → Output shows Returns by station (returns, units, the typical time from the first item to finish) and each person’s returns; My stats shows the returns a person finished. ## See also - [Pack stations] (/features/settings/pack-stations/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/automation/ # Automation Elevate plan. Three ordered rule lists in one place — order rules, order routing and shipping rules. [Elevate plan] (/getting-started/subscription-plans/) Floormode has three sets of rules, each an ordered list read top-down, each with its own URL as a tab: the order rules and the order routing under Settings → Orders & dispatch, the shipping rules under Settings → Shipping & carriers. ## On this page - The three cascades - How each list runs - When no rule matches - What rules can and cannot do - See also ## The three cascades Tab Route Decides Order rules /settings/orders/rules Tag, hold, prioritise or alert on incoming orders. Order routing /settings/orders/routing Which location or dropship vendor ships each order. Shipping rules /settings/shipping/rules Which carrier and service a shipment is rated and bought with. Order rules act the moment an order arrives — tag an order over a value threshold, hold anything to a flagged address, prioritise an express service, alert someone on a high-value order. Order routing picks the origin, including ship-from-store. Dropship vendors are supported as a destination: a routed dropship order sends the vendor a purchase order by email. Shipping rules pick the service: the cheapest rate, a preferred carrier per country, or the cheapest non-express service where the fast option is not worth its price. Beside them, the Checkout options tab maps each shipping option your customers choose at checkout to a carrier service. A mapped option wins over the shipping rules: see [Checkout options] (/features/settings/checkout-options/). ## How each list runs All three lists are read from the top, but they do not stop in the same place. - Order rules run every rule that matches. Each matching rule acts, in list order: an order over your value threshold that also ships to a flagged address gets the tag of one rule and the hold of the other. Where two rules set the same thing, such as a priority, the rule lower in the list has the last word. - Order routing and shipping rules stop at the first match. The first rule that matches decides the origin or the service, and the rules below it are not used for that order. A shipping rule whose carrier or service is not among the shipment’s rates passes the shipment on to the next rule. To understand an outcome, read down the list until you reach the first match. Tip In Order routing and Shipping rules, order the list from most specific to most general: a rule that matches everything, placed second, makes every rule below it dead (a shipping rule only while its service is among the rates), and the list will not tell you that. In Order rules, put a rule whose outcome should win below the rules it overrides. ## When no rule matches - Order routing: the order still gets an origin. Floormode picks an active warehouse by stock, then distance, and the Order routing tab says in one sentence how it picks for your warehouses. A rule whose warehouse, store or dropship vendor is no longer active is passed over the same way, so a stale rule never strands an order. - Shipping rules: the shipment gets the cheapest rate. A checkout option mapped to a service decides before the rules do. - Order rules: nothing happens to the order: no tag, hold, priority or alert. There is no fallback here, and none is needed. With Hold high-risk orders switched on (Orders & dispatch › Dispatch › Order handling), the built-in fraud hold holds the open fulfillments of an order Shopify flags as high risk, with no rule of its own. ## What rules can and cannot do Order rules Order routing Shipping rules Run when An order is created, is paid, has been routed, or its risk changes (you choose one per rule). An order needs a warehouse. A shipment is rated. Can match on Channel, tag, SKU, order total, destination country, shipping option, risk level, weight, line count, dangerous goods. Destination country and SKU. Destination country, shipping option, weight, order total, SKU, channel, dangerous goods, tag. Can do Add a tag, hold the fulfillment with a reason, set a priority, route to a warehouse, send an alert. Ship from a warehouse or a store (ship-from-store), or send the order to a dropship vendor as a purchase order by email. Assign a carrier and service, take the cheapest rate, or downgrade to a standard service. What no rule can do: - Change the order itself. A rule never edits lines, prices, the address or the customer. Edit the order in Shopify, or with Edit lines on the order’s page. - Cancel, refund or fulfil an order, or buy a label on its own. Labels are bought at the pack station or under Shipping, with the service your rules chose. - Keep an order in place against a matching rule. With no rule matching, an order stays where it is while its warehouse can fill it, and for good once picking has started there. A routing rule that matches is your instruction, and it still moves the order, closing the work already started at the old warehouse. - Test a fact Floormode does not know yet, such as the dangerous goods of an item not yet read from Shopify, or a checkout option it does not know. The rule is skipped for that order and its preview names the reason. - Look at stock, a customer’s history or the time of day. Rules see the order and its shipment only. Included on the Elevate plan. ## See also - [Fulfillment settings] (/features/settings/fulfillment/) — the switch that enables routing. - [Shipping] (/features/fulfillment/shipping/) — where shipping rules take effect. - [Subscription plans] (/getting-started/subscription-plans/) — what Elevate unlocks. - [Order rules] (/features/settings/order-rules/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/order-rules/ # Order rules Floormode rules that watch a moment in an order's life, check its conditions and act on the order. In Floormode, an order rule watches for one moment in an order’s life, checks its conditions, and acts: it adds or removes a tag, holds the order, sets its priority, sends it to another warehouse, tells the packer something, sends you an alert, or tells your own tools. Rules are in Settings → Orders & dispatch → Order rules. ## On this page - Start from an example - When a rule starts - What a rule can check - What a rule can do - Stop processing more rules - Holds that release themselves - Rules on the moments on the warehouse floor - When a rule could not apply - Rules on a schedule - Run on all open orders - Condition groups - Run a rule by hand - Test rules on an order - When a rule waits - A rule’s own effects - Test a rule - The run log - Describe a rule - See also ## Start from an example With no rule yet, the page shows examples under the empty list; once you have rules, Start from an example opens the same list. An example opens in the editor filled in, for example “Hold high-risk orders” or “Late orders first”. Change what you need, then Create: nothing is saved before that. Amounts are in your store’s currency. To start from a rule you already have, open its ⋯ menu and choose Duplicate. The editor opens with a copy named “Copy of …”; the copy is saved switched off, so it never runs beside the original until you change it and turn it on. ## When a rule starts Trigger Starts when How often Order created A new order arrives Once per order Order paid An order arrives paid, or turns paid Once per order Order routed Shopify assigned the order to a location Once per order Risk changed Shopify changed the order’s fraud risk Once per order Tags added Tags were added to an order in Shopify Once per set of added tags Address changed The order’s delivery address changed Once per change Return requested A customer asked for a return, in your returns page or in Shopify Once per return Return received The goods of a return arrived and were checked at your warehouse Once per receipt Delivery problem The carrier reported a problem with a parcel Once per problem Order late An order passed its fulfil-by time, or the end of its packing day, and has not shipped Once per due time it misses Order put on hold A hold was placed on the order in Shopify Once per hold, so once for each part of a split order that is held Order hold released A hold Floormode placed on the order was released Once per hold Order backordered Part of the order started waiting for stock (your warehouse sells on backorder) Once each time a part starts waiting, never while it waits Backorder resolved A backordered part of the order is fully reserved again Once each time a part stops waiting Pick short A picker found fewer units in a location than the pick asked for Once per pick line Order cancelled The order was cancelled in Shopify or in Floormode Once per order Parcel packed A packer finished a parcel of the order Once per parcel Parcel fulfilled Shopify confirmed the fulfillment of a parcel Once per parcel Label bought Floormode bought a shipping label for the order Once per label Delivered The carrier delivered a parcel Once per shipment On a schedule At the times you choose, on every open order Once per run, or once per order (you choose) Only when run by hand Never on its own: only when someone runs it on chosen orders Once per run A rule runs at most once for each moment. Some details: - Tags added counts the set of tags one change added. If a tag is removed and added again, that is the same set, so the rule does not run a second time. Two rules that add and remove each other’s tags stop after one round. - Return requested: a return asked for in your returns page and then answered in Shopify is one return. The rule runs once. - Return received: goods that came back without an order start no rule, because there is no order to act on. - Delivery problem: a parcel that was moving again and then runs into a new problem is a new problem, so the rule runs again. - A new order’s own tags are not “added”: use Order created with a tag condition. - Order cancelled knows how far the order’s work had come: not started, picking, picked, packing or packed. A cancel you start in Floormode records it when it stops the work, so the rule sees “picking” even after the work was stopped. - After packing (Parcel packed, Parcel fulfilled, Label bought, Delivered, Order cancelled) a rule can add or remove tags, send an alert or tell your webhooks and Flow. Holding, routing or packing instructions mean nothing there. Order put on hold can also set the priority, but never hold again. - Order backordered starts once when a part of the order begins to wait for stock. While it waits, more or less stock missing starts nothing; once it is reserved again (Backorder resolved) and runs short again later, it starts again. When Shopify splits the order or moves part of it, the new part begins its own wait. Use Units short to act only on bigger shortfalls. Neither moment can hold the order: it already waits, and it reserves itself when the stock arrives. Backorder resolved can release the holds a rule placed while it waited. - Pick short knows the units the picker could not find (Units short). A line booked short again starts nothing. It can add or remove tags, send an alert or tell your webhooks and Flow. - Warehouse on these moments is the order’s warehouse, as on Order put on hold: on an order split across two warehouses, a Pick short in one also matches a rule that names the other. - Order hold released knows the hold’s reason. It can do everything an open order takes except hold or release again. - Order late counts from the first rule, webhook or Shopify Flow workflow that listens for it: an order that was already late then starts nothing. An order split over several shipments is late at its earliest due time; a due time moved later is a new due time, so the rule can run again. An order that asked for a delivery day is due by the end of its packing day in the warehouse’s time zone. The rule runs within 15 minutes after the due time passes. ## What a rule can check Each trigger offers the conditions it can answer. The editor shows only those. If you change a rule’s trigger, every condition stays: the ones the new trigger cannot answer are marked “Not available for …”, and the rule cannot be saved until you remove them or pick another trigger. The same check runs for rules saved through the API. Condition Offered by Channel, tag, SKU, order total, destination country, shipping option, risk level, weight, line count, dangerous goods Every trigger Store (only when you have more than one store) Every trigger Order source (Shopify’s source: online store, point of sale, draft order, an app) Every trigger Priority Every trigger Warehouse Order routed, Risk changed, Tags added, Address changed, Order late, Order put on hold, Only when run by hand (a change before routing waits and is decided once the order is routed, with what it changed; not on returns or delivery problems: the order has shipped) Tags added Tags added Return reason, units returned Return requested, Return received Return value Return requested Condition on receipt (sellable, damaged) Return received Carrier, problem (failed attempt, returned to sender, other) Delivery problem Due by (fulfil-by time, packing day), minutes late Order late Units, product vendor, product type, state or province, postcode, day placed, time placed, order is held for Every trigger Backordered Order routed and every trigger after it Hold reason Order put on hold Packed at (the parcel’s warehouse) Parcel packed, Parcel fulfilled Carrier Delivery problem, Label bought, Delivered Work stage Order cancelled Each condition offers the comparisons its value takes: is any of, is none of, contains, starts with, is empty, is not empty, at least, at most, and for the order’s lines all lines are. A rule saved before these existed keeps its comparisons. Some details: - Money (order total, return value) is compared in each order’s own store currency. The editor shows the currency code beside the amount. With stores in more than one currency it shows every code until the rule names one store; add a Store condition for an amount meant for one store’s currency. - Warehouse on an order split between warehouses: “is” matches when any of its warehouses is the one you chose, “is not” when none of them is. An order with nothing left to ship has no warehouse to check: a rule that asks is skipped, and the order’s timeline says why. - Priority is read when each rule is checked, so a later rule in the list sees the priority an earlier rule just set. - Tags do not chain within one moment: a tag a rule adds reaches the order through Shopify, as Tags added. Use that trigger to act on a tag a rule added. - Return value is known only for returns asked for in your returns page. A rule that checks it skips a return from Shopify, and the order’s timeline says why. The same goes for any fact a moment does not state. - Product vendor and product type are read from your catalog. A line whose product has not synced yet cannot tell: “is none of” and “all lines are” wait until it syncs, while “is any of” already matches when another line has the value. A custom item has no vendor, which counts as empty. - State or province is the code Shopify stores, such as US-AK, AU-TAS or DE-BY. - Postcode (“starts with any of”, “starts with none of”) names one country and its postcode prefixes, for example GB: HS, IV, KW, ZE for the Highlands and Islands or US: 995, 996 for Alaska. Spaces and hyphens do not matter. “Is none of” also matches orders to other countries: add a Destination country condition to limit it. The postcode itself never shows in a run log or a test, only whether it matched. - When Shopify does not share an order’s address with Floormode, a state or postcode rule is skipped for that order and its timeline says why: it never guesses. - Day placed and time placed use your store’s time zone (UTC until Shopify has told Floormode the zone). ## What a rule can do The action list is grouped: what happens to the order, what the packer is asked, and who is told. A trigger offers only the actions that fit it. Action What it does Triggers Add tag, Remove tag Adds or removes the tags on the order in Shopify Every trigger Hold fulfillment, Set priority, Route to warehouse As their names say. A hold can release automatically (below) Every trigger Release holds Releases the order’s holds that a rule placed, of one reason or any. With Also release holds not placed by a rule, people’s and risk checks’ holds too Order triggers, and runs by hand Pack in box The bench starts the parcel in this box; the packer can still choose another Order triggers Add pack note A note the packer reads at the bench, up to 500 characters. With Packer confirms on, the packer taps Got it before the parcel goes on Order triggers Require pack step Makes the photo, the weight or the check required for this order’s parcels Order triggers Add to the parcel A flyer, card or sample (a Floormode item) goes in the order’s parcels, confirmed by the packer, taken from stock at the fulfil. See [Add to the parcel] (/features/fulfillment/inserts/) Order triggers Send alert Sends you an alert Every trigger Tell webhooks and Flow Sends “Rule matched” to your webhooks and, while Also start Shopify Flow is ticked, to Shopify Flow, with the rule, the trigger and the order. Unticked, it tells your webhooks only. It never starts another rule Every trigger The packing actions fit the order triggers only (created, paid, routed, risk, tags added, address changed, late): after a return or a delivery problem there is no parcel left to pack. If you change a rule’s trigger, an action that no longer fits stays in the list, marked, and the rule saves once you remove it. At the bench. A rule’s note shows in the parcel’s instructions with the rule’s name (“Order note · from the rule Gift wrap”). When it asks to be confirmed, Got it is saved for that parcel. A device that is offline keeps the tap and sends it when it is back online. Each parcel of a split order confirms the note on its own. At the desk station the note has a Confirm button. A required step names its rule too (“The rule Express check asks for a photo on this order”). A photo can be required anywhere, and a lead can still let a parcel go without it. The weight and the check can only be required where the warehouse already weighs or checks parcels. Elsewhere the rule skips the step, the editor names those warehouses, and the run log says why. Once packing starts, the order’s packing instructions are fixed. After the first parcel of an order is started, a rule can no longer change its box, note or steps. The run log says the rule was skipped because packing had started. An order no rule marked looks the same at the bench as before. ## Stop processing more rules Tick Stop processing more rules for this order under a rule’s trigger. When that rule acts on an order, the rules after it in the list do not run for that order on the same trigger. A rule that runs later in the list, for another trigger, is not affected. - Only a rule that changed something stops the others. A rule that matched but changed nothing (“No change”) stops nothing. - When the stopping rule waits for a fact (for example the order’s fulfillment orders for its hold), the rules after it wait behind it. Their run log says “Waiting behind Express first”. When the fact arrives, the stopping rule runs first, and the others follow what it did. - Its run log shows Stopped later rules, and Test rules shows “Stopped by Express first” on a rule it stopped. - A rule you switch off, delete or untick no longer stops the others, from its next moment. - A rule run by hand runs alone, so there is nothing after it to stop. ## Holds that release themselves A hold can end by itself. In a rule’s Hold fulfillment action, and in the Hold fulfillment dialog on the order and the orders list, choose Release automatically: - Release after a number of minutes, hours or days (up to 90 days), counted from when the hold is placed; - Release on a date and time in your main store’s time zone (UTC until Shopify has told Floormode the zone), the same for every store’s orders. The hold shows “Releases 14:00 Tue” on the order. Its Change release sets another time, or Keep holding until someone releases it. Release ends it now. - If the order is already on hold, it keeps that hold as it is: a rule’s timer is never added to a hold that waits for a person, and its run log says “Already on hold”. - A rule that holds again later may move its own release later, never earlier. You can move a rule’s release later too, or release it now. - A release time that has already passed when the rule runs places no hold. - Tells the customer about the delay: a hold for “Waiting for stock”, “Waiting for production” or “Waiting for supplier stock” sends the customer the delay notice, whether a person or a rule placed it. The templates use reasons that send none. ### When Shopify still lists a released hold Sometimes Shopify puts a hold back on an order after Floormode released it. This happens when a request to place the hold was slow to answer and Shopify finished it late. When Floormode next reads the order and sees its own hold listed again, it checks with Shopify and releases it again. The hold on the order says Checking with Shopify meanwhile. This works the same whether the hold was released by its timer, by a person or by a rule. - Floormode only releases holds it placed itself, never another app’s. - After three such releases, Floormode only checks: if Shopify has put the hold back again, or refuses to release it, the hold says Needs a person. Use Open in Shopify to release it there, or Try again. If you can’t use Shopify admin, ask someone who can. The holds_list API lists these holds with drift: "stopped". ## Rules on the moments on the warehouse floor Pick short, Order backordered, Backorder resolved, Parcel packed, Label bought, Parcel fulfilled, Delivered and Order cancelled each take at most 20 switched-on rules. Their rules run in the same moment as a scan on the floor (a short pick, a putaway that brings stock for a backorder, the bench), so the cap keeps picking and packing fast. When Backorder resolved rules are on, a putaway reserves stock for fewer waiting orders at once and Floormode reserves the rest a moment later, so the scan stays fast. A 21st rule can be saved switched off; the editor says “This moment already has 20 rules switched on” before you save, and switching it on waits until you switch another off. Deleted and switched-off rules do not count. A rule on these moments names each action once: put its tags in one action. Up to 5 of a moment’s rules can Tell webhooks and Flow or Send alert (an alert reaches your webhooks too). Events reach your webhooks a few seconds after the moment, in order for each order, and a failed delivery is retried for up to three days (Settings › Webhooks). The 5 keep a webhook that was down for three days caught up within a day; the moment’s other rules tag without telling anyone. At most 3 of them can also start Shopify Flow: each Flow start uses the store’s Shopify budget, the one fulfilments use too. When a moment already starts Flow from 3 rules, a new event comes with Also start Shopify Flow unticked and tells your webhooks only; ticking it again says why it waits. The editor says either bound before you save. A moment’s Flow starts go out together, so two of one order may reach Flow in either order, as Shopify’s own Flow starts may. ## When a rule could not apply When a rule cannot do one of its actions for a reason you can fix (the box it names was deleted, an action has nothing set, it asks for a pack step the warehouse does not use), you get one alert, Rule “…” could not apply on order …, in Alerts, through Alertified and on a webhook that listens to alert.raised. It stays one alert while the reason stands; it closes by itself once the rule applies again on an order of the same store (and, for a pack step, the same warehouse), or when you change the rule’s actions, switch it off or delete it. A reason that comes back opens a new alert. Things that are fine (the tag was already there, nothing to release) never alert. ## Rules on a schedule Pick the trigger On a schedule and the rule runs at the times you choose, on every open order: for example “every weekday at 09:00, alert me to orders placed more than 48 hours ago and not started”. A new scheduled rule starts as Every weekday at 09:00; the line under the schedule says it in words and when the next run is. - Runs: once a day at a time (on the quarter hour), or every 1, 2, 3, 4, 6, 8 or 12 hours, optionally between two times. Pick the days it runs on. - More options: the time zone (the store’s by default, or one of your warehouses’), Act on an order once (the default: an order the rule acted on is left alone at later runs) or Act on every run (up to 100 times an order across scheduled rules), and what happens when a run was missed: Run it late (the default) or Skip it when it is more than 15 minutes late. - A scheduled rule can check what a run knows of each order: Hours since placed and Work stage (not started, picking, picked, packing, packed), besides the order’s own facts. - At most 10 scheduled rules can be switched on at once. - A rule switched on, or whose schedule changes, counts from then on: it never runs the times it was off. - When a run is still busy at the next time, the next time is folded into one run and the run’s card says so. - Run now in a scheduled rule’s ⋯ menu runs it at once, as at its next time. ## Run on all open orders A rule’s ⋯ menu offers Run on all open orders…: the rule is checked on each order that is open when the run reaches it, about as many as the dialog says. An order that changes during the run may be checked again, but the rule never acts twice on it in one run. The run’s progress is in the rule’s Runs: “Checked 1,200 of about 8,000 open orders”. - A run waits while a scheduled run goes first (“Paused behind the scheduled run”), and while Shopify is still taking earlier changes (“Waiting for Shopify to catch up”). - Stop run stops it. Orders already handled keep what the rule did; orders waiting for a missing fact are still decided when that fact arrives, and the card says how many. - A rule that checks something only its moment knows (for example the tags just added) cannot run this way. - One run a rule at a time; at most 10 such runs at once. ## Condition groups Add group beside the conditions’ heading puts the conditions you have into group 1 and opens group 2. Each group matches All or Any of its conditions, and Match groups says whether all groups or any group must match: “(Germany and express) or (Austria and over €200)” is two groups of All, matched by Any. Up to 5 groups and 20 conditions. Removing a group down to one makes the rule flat again. A group that cannot tell yet (for example the order’s shipping option is not known) waits; a group already decided never makes the rule wait. ## Run a rule by hand Select up to 50 orders on the Orders list and choose Run rule…, or open an order’s ⋯ menu and choose Run a rule…. Pick the rule and confirm: Floormode runs it now on those orders and shows what each one did. A rule’s Test also offers Run on these orders for the examples it would match. - Any switched-on rule can run by hand, unless its conditions check something only its moment knows (for example the tags just added). The picker says why such a rule is greyed. - A run by hand never uses up the rule’s own trigger: running “Express first” by hand today does not stop it from running when the next order is paid. - A rule with the trigger Only when run by hand runs only this way. - Running a rule needs the rights of what it does: for example a rule that tells your webhooks needs the right to manage integrations. - If you run the same selection twice by accident, the second run repeats the first answer and changes nothing. - One order can be run by hand at most 100 times; after that each rule stops for it. ## Test rules on an order On an order’s ⋯ menu, Test rules… shows every switched-on rule against that order now: whether it would match, each condition with a ✓, ✗ or ?, and the order’s own value for it (never the postcode), whether the rule is waiting on the order, how often it ran on it, and what it would do, including an action that would not apply and why. A condition on something only its moment knows is “decided when the trigger happens”. Nothing changes. ## When a rule waits Some actions need facts Shopify sends a little later, such as the order’s fulfillment orders for a hold. Until they arrive, the rule waits and the order’s timeline says so. When the facts arrive, the rule runs for each moment it waited for, as the rule is then. An order keeps at most 20 such moments waiting; a later one is noted on its timeline and skipped. ## A rule’s own effects A rule’s change never starts another rule in the same moment. It can start one later: - a tag a rule added comes back from Shopify as Tags added; - a hold a rule placed counts as the order being held once Shopify confirms it. When several rules add tags to an order for the same event, Floormode sends them to Shopify together, once. One order runs rules at most 100 times on each trigger that can repeat by itself (tags added, address changed, delivery problems, holds, late orders and runs by hand). Every run counts: one that changed something, one that found nothing to change, and one skipped for a fact no later update will give. A rule that is only waiting does not count. After 100, each rule stops for that order on that trigger, its run log says so, and you get one alert. The moments that come with a new parcel, label or return (packed, fulfilled, label bought, delivered, returns) are never stopped: an order with 30 parcels runs its rules for each. ## Test a rule Open a rule’s ⋯ menu and choose Test. Pick one of your newest examples of the rule’s trigger: an order, a return, a return receipt, or a shipment with an open delivery problem. The test shows whether the rule would match, the facts the trigger gave it, and what it would do. It changes nothing. - Tags added is tested with an order’s current tags, as if they had just been added. Floormode does not keep a list of recent tag changes, so this is an approximation. - Cannot tell means the example is missing a fact the rule checks, such as a shipping option Shopify has not sent yet. The live rule skips such an order instead of guessing. ## The run log Open a rule’s ⋯ menu and choose Runs to see every time it ran or was skipped, newest first. A run names its order, when it ran and what came of it: - Applied: what it changed; - No change: it matched, but nothing changed, and why (a target that no longer exists, packing that had started); - Skipped: a fact it checks was not known yet, and when it is decided again (it says whether it is still waiting or was decided since), or a fact no later update will give (“Not decided”); - Stopped: the order reached the limit of 100 runs, or too many of its moments were waiting at once. It also names the moment it ran for: - Tags added: the set of tags it ran for. A very long set is shown as the trigger alone. - Delivery problem: when the problem began. - Order late: the due time it missed, and whether it was a fulfil-by time or a packing day. - Only when run by hand and a run by hand of any rule show as runs by hand. - The other triggers run once per order, parcel, label, hold, return or receipt, so the run’s order is enough. A rule runs once for each moment, so each applied run in the log is a different moment. The order’s timeline shows the same outcomes. A rule that has not run yet offers Test this rule instead. ## Describe a rule Describe in the rule editor drafts the conditions from your sentence, for example “orders with more than 5 units”, “orders placed before 2 pm”, “orders to California”, “UK orders to postcodes starting IV or KW”, or “cancelled orders that were already packed”. It knows every condition except the store, the warehouse, the checkout source, the priority, the carrier and the packing warehouse, which you pick in the editor. A vendor or a product type is read only when your sentence says “vendor”, “brand” or “type”. A region is read for the US, Canada and Australia; another country’s region is named as something a rule cannot test. Describe sends only your sentence and the trigger, never an order or a customer’s details. ## See also - [Automation] (/features/settings/automation/) - [Inserts] (/features/fulfillment/inserts/) - [Holds] (/features/orders/holds/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/checkout-options/ # Checkout options Map each shipping option your customers choose at checkout to the carrier service its label is bought with. In Floormode, a mapped checkout option wins. Otherwise your shipping rules decide, then the cheapest rate. Every shipping option your customers choose at checkout (“Express before 10:30”, “Standard”, “Pickup at our Downtown store”) appears under Settings → Shipping & carriers → Checkout options with its first order. There is nothing to type. When Floormode imports your store it also reads the options of the orders from the last 60 days, so the list shows what your shop sells from the start. ## On this page - Map an option - Suggestions and review - Map it where you see it - Find orders by their option - Use an option in a rule - See also ## Map an option 1. Open Settings → Shipping & carriers → Checkout options. Options that need review are at the top. 2. In the Ship with column, choose Choose… (or the current service). 3. Pick the exact carrier service, grouped by carrier account. Or pick Shipping rules decide. The choice is saved at once and applies to every order with this option from then on. Labels already bought are not changed. - Pickup and local delivery take no label. They are listed, but cannot be mapped. - A carrier account marked Reconnect needed can still be chosen. Its orders follow your shipping rules until you reconnect it under Settings → Shipping & carriers. - Back to unreviewed in the picker undoes a mapping. ## Suggestions and review - Needs review changes nothing: those orders follow your shipping rules, then the cheapest rate, as before. The line above the list says how many options still need review, and how many with open orders still need a carrier service. - Same as “…” under an option offers the mapping of an option it looks renamed from. One click takes it. - Use … under an option offers the service you picked by hand for its last three labels (a rate you chose yourself, not the one your rules suggested). One click maps it; nothing is mapped without that click. - Options nobody chose for 30 days are greyed out. At most 200 options are listed; the line above the list says when more were seen. - Shipping → Rules links here and says how many options still need review. ## Map it where you see it You do not have to open Settings to map an option. The customer’s choice is shown where the work happens, and Map… opens the same picker there: - The order page. Each fulfillment starts with “Customer chose …” and what it ships with. The Ship to card repeats it, with Shopify’s delivery promise when there is one. - A new shipment. The carrier account opens on the mapped account. An option nobody mapped yet says so, with Map…. A mapped account that is not connected is said out loud, never switched silently. - The pack station. A line between the order note and the checklist says what the customer chose and what the label uses: mapped, not mapped yet (Map this option), shipping rules decide, not offered for this parcel, or unclear (Shopify combined several rates). It never holds back Fulfil. - Ship all buys the mapped service, else the rate your rules pick, else the cheapest. When the carrier did not offer the mapped service, it leaves that shipment for you to pick its rate. - Floor Mode. The pack screen shows the customer’s choice as a chip. It cannot be mapped there: the label prints at the pack station. Map… is offered to people whose role holds Automation, routing and shipping rules. Everyone else sees the words without the button. ## Find orders by their option On Orders, + Filter → Shipping option lists the orders with a fulfillment that ships under one option, picked from this list. With open statuses only (Open, Unfulfilled, Partially fulfilled) it lists the work still to ship. Add the Shipping option column under Columns to see each order’s option. ## Use an option in a rule Shipping rules and automation rules can test Shipping option: - is, is not and is one of pick options from this list, never typed text. - contains matches part of the option’s name, for example “Express”. Example: Shipping option is “Express before 10:30” → Set priority: High puts those orders first for the 10:30 collection. Note While an order’s option is not known yet (an imported order, or a checkout Floormode has not read), a rule that tests it is skipped and noted on the order’s timeline. It never treats the order as “not Express”. Once Floormode reads the option, the skipped rules are checked again, once, and run if they match. An order already fulfilled or cancelled by then is not checked again. ## See also - [Shipping] (/features/fulfillment/shipping/): rates, labels and the shipping rules. - [Automation] (/features/settings/automation/): the rule cascades this page sits beside. - [Carriers & packaging] (/features/settings/carriers-and-packaging/): connecting carrier accounts. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/carriers-and-packaging/ # Carriers & packaging Carrier accounts, label printers and the box catalog the packing step chooses from. In Floormode, Settings → Shipping & carriers (/settings/shipping) holds the three things that turn a picked order into a parcel somebody collects. ## On this page - Carrier accounts - Try it with the test carrier - Label printers - The box catalog - See also ## Carrier accounts A carrier account is what turns a packed parcel into a bought label. Connect the accounts you actually ship with; [Shipping] (/features/fulfillment/shipping/) then shows every rate across all of them, sorted by price and speed. Freight carriers are configured here too — a ShipEngine LTL account for less-than-truckload, or Uber Freight for full-truckload. Uber Freight is apply-gated: request access first. ## Try it with the test carrier No carrier connected yet? Choose Use the test carrier — here, on the empty shipments list, or at the pack station when a label cannot be bought. It is built in: nothing to sign up for, nothing to type. - Its one service, Test label, costs 0. - Its label is a real PDF you can print and reprint: the ship-to, the order, a TEST-… number, and in its largest type TEST LABEL: NOT VALID FOR SHIPPING. Voiding it only marks it void. - A parcel fulfilled with a test label is fulfilled in Shopify without tracking, even if a number is typed in, and no shipping confirmation goes to the customer — not from Shopify, not from Floormode. Webhooks and Shopify Flow hear nothing of a test label. Trying it on a real order never e-mails a tracking link that leads nowhere. Caution The test carrier never ships anything. Connecting a real carrier turns it off, so a test draft left over is never bought by itself. Turn it on again to make another test label: the real carrier stays the default, and no checkout option or shipping rule can choose the test carrier. ## Label printers Label printing goes through PrintNode. With it connected, a bought label goes straight to the station printer; a picker never touches a file dialog. Note A printer is optional. Without one you download the label as a PDF and print it by hand — slower, but complete. Packaging, carrier and printer are not setup steps; they are one link away on the You’re live screen and under Settings. Bin label printing from the [Bins] (/features/inventory/bins/) tab uses the same connection. ## The box catalog The box catalog is the set of packaging you actually own — each with its dimensions, its empty weight and, where relevant, its cost, in your store’s units: inches, pounds and ounces in a store on imperial units; millimetres, grams and kilograms in a metric one. [Cartonization] (/reference/glossary/#cartonization) at the pack step chooses from this catalog: the cheapest suitable box for the items being packed, split across several where one will not do. Two things make it work well: 1. A complete catalog. A box you use but never entered cannot be chosen. 2. Item dimensions on your products — see [Item dimensions & capacity] (/features/inventory/item-dimensions-and-capacity/). Without any boxes at all, nothing can be cartonized, which is why adding your boxes comes right after going live. ## See also - [Shipping] (/features/fulfillment/shipping/) — where carrier accounts are used. - [Pack] (/features/fulfillment/pack/) — where the box catalog is used. - [The setup flow] (/getting-started/setup-guide/) — the four steps that come before packaging. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/labels-printers-and-scanners/ # Labels, printers and scanners Label artwork, paper and printer calibration, direct printing, and scanning with Floormode. In Floormode, create label artwork once, then choose the paper and printer correction for each print run. Saving a design does not save its printer correction. ## On this page - Set up a printer and medium - Print a PDF or send to a device - Barcode formats - GS1 prerequisites - A code that counts as several units - Check a new setup - Scan with a phone or tablet camera - Can’t scan? Take a photo - Weigh with a USB scale - Install Floormode on a phone or tablet - Carrier pickups - See also ## Set up a printer and medium 1. Open labels from the item list, locations or a receipt. 2. Choose the paper format and label dimensions. Sheet labels have independent left, right, top and bottom margins. Thermal media can contain several labels across the roll. 3. Open the calibration PDF and print at actual size / 100%. Disable the printer driver’s “fit to page” option. 4. Measure the printed rulers and position. Adjust X/Y offset for position and X/Y scale for measured size. Save a profile with a recognizable printer and medium name, such as “Packing desk / 57 × 32 mm”. 5. Print a small sample and scan it with the device used on the warehouse floor. Profile names describe your setup. Direct printing separately selects a discovered PrintNode device. Changing a design keeps the current correction. If another user updates a profile, reload it explicitly to adopt the change. The preview checks occupied space and barcode quiet zones. Rotation keeps the content’s dimensions; a rotation that does not fit is refused with guidance to reduce the element size or enlarge the medium. The final PDF checks actual font and barcode dimensions as well. Small media may fit a short identifier but not a long GS1-128 barcode. GS1 Data Matrix often uses less space. Calibration proof sheets require a medium at least 20 × 20 mm. A legacy label without an explicit design conservatively reserves its entire label area, so some printer offsets are refused. Use a design with suitable artwork padding. ## Print a PDF or send to a device Preview & print PDF opens the authenticated PDF in either standalone or Shopify embedded access. Use the browser/PDF print controls to send it to a printer. Direct printing uses the connected PrintNode account and a discovered device. The submitted PDF, printer and request identity are recorded before the provider call. “Sent” means PrintNode accepted the job; check the device for physical output. A timeout can mean that the provider accepted the job but its answer was lost. Check status and the printer before deliberately creating another attempt. Floormode does not automatically print a second copy after an uncertain result. The history keeps that job as unknown, including after background reconciliation. A confirmed provider refusal is failed. An expired worker also becomes unknown; it does not remain queued indefinitely. Request details report pending, accepted, refused or unknown separately from the background processing state. Generated PDFs for direct printing are limited to 1 MiB. For larger sheets, select fewer labels or use the PDF flow. An old print request never prints again by itself; a new attempt records the previous request when one is supplied. ## Barcode formats Automatic selection recognizes valid EAN-13, UPC-A and EAN-8 check digits and uses Code 128 for other supported printable identifiers. Explicit formats also include Code 39, ITF, UPC-E, QR Code, Data Matrix, PDF417, GS1-128 and GS1 Data Matrix. ITF needs an even number of digits. UPC-E needs the full eight-digit compact code with its check digit. Some scanners expand UPC-E to UPC-A or EAN-13. Configure compact output, or add the exact expanded scanner output as an alternate item barcode. Printing never replaces the stored identifier. ## GS1 prerequisites The scanner reads GS1 codes in every common form: GS1-128, GS1 Data Matrix, GS1 DataBar and GS1 QR, the printed (01)…(17)…(10)… text, and GS1 Digital Link QR codes (https://…/01//10/?17=…, any web address). It reads these application identifiers (AIs): AI Value Handling 00 SSCC of a pallet or parcel Read. Scanned alone where an item is asked for, the floor says to scan the item’s barcode 01 GTIN of the item Finds the item by its barcode or an alternate barcode 02 GTIN of a carton’s contents Finds the item, like 01 10 Lot, up to 20 GS1 characters Capture at receiving; check allocated lot while picking 11, 13 Production and packaging date, YYMMDD Read, not booked 15 Best before, YYMMDD Read as the lot’s date when the code carries no 17; day 00 means month end 17 Expiry, YYMMDD Capture/check as a calendar date; day 00 means month end 21 Serial, up to 20 GS1 characters The unit’s serial for an item that tracks serials; refused on any other item 30 Variable count of items Read, not booked 37 Count of items in the carton Shown at receiving. You still book the units you count, unless the 02 GTIN is a code that counts as several units (below) 310n, 320n Net weight in kg (310n) or lb (320n), one weight; a label stating both is read in kg Read, not booked 330n, 340n Gross weight in kg (330n) or lb (340n), one weight; a label stating both is read in kg Read, not booked Other AIs on a supplier’s label are skipped. A code that is broken, such as a wrong check digit, a cut-off value or a date that cannot exist, is refused, and the floor names the fault. GTIN-13 and GTIN-14 match automatically: a GTIN-14 that starts with 0 finds the item whose barcode is the GTIN-13 (or UPC-A, or EAN-8), and the other way round. You do not need to add the 14-digit GTIN by hand. A case GTIN-14 that starts with 1–8 is the case’s own code and never finds the unit. The whole GS1 payload containing a lot or expiry is not an alternate item barcode. Enable AIM symbology identifier transmission on the scanner: ]C1 for GS1-128 or ]d2 for GS1 Data Matrix. Also configure it to preserve the FNC1 separator between variable-length fields. Keyboard scanners can send ASCII 29 or Ctrl+]. An unmarked long numeric SKU or an ordinary web address is never guessed to be GS1. Repeated AIs are refused. At receiving, enable lot tracking for the warehouse. Scanning fills the lot and expiry fields. Editing them to conflict with the barcode refuses the booking. Expiry-only data still needs a lot number. The current lot ledger uses uppercase keys without surrounding spaces; GS1 lot values requiring a different spelling are refused instead of silently changed. A serial (21) books the unit’s serial number for an item that tracks serials; on any other item the code is refused. Picking checks scanned lot and expiry against the line’s allocated lot before moving stock. A task without an allocated lot cannot verify those attributes. Packing checks no lot, so its item scan refuses GS1 codes that carry a lot or expiry instead of claiming per-lot verification. Its serial step takes a code with a serial (21) whatever else it holds, without checking the lot or expiry. Other workflows without explicit GS1 lot handling also refuse structured booking. Read-only identification retains all supported fields. For receiving-label designs, selecting a GS1 format combines an exact GTIN-14 with the movement’s captured lot and expiry. An explicitly supplied complete GS1 value is printed with its own fields. Month-end day 00 is rendered as the actual last calendar day; the date’s meaning is unchanged. ## A code that counts as several units A supplier’s carton often has its own barcode. On the item page, open Barcodes, add the carton’s code and set Counts as to the units one carton holds, for example a carton of 12. One scan of that code then books 12 units at once: - Receive opens the quantity at 12 instead of what the line still owes. Each further scan of the same carton code adds 12. While filling a bin, each carton scan adds 12 and each unit scan adds 1. - Quick stock starts the quantity at 12, and each further scan of the carton adds 12. - Count opens the total at 12, and each further scan adds 12. You can type over it. The total you confirm replaces the earlier count, as always. - Pick and pack take units: a carton code is not the item there, and the scan says so as for any other code. Moves, transfers and Return to shelf only check the item, since the task carries the quantity. The stock, movements and reservations always count single units. A GS1 label naming the carton’s GTIN in (01) books one carton; its (37) is shown and never multiplied. A label naming the contents (02) with a count (37) fills in the count times the carton’s units, for you to confirm. Only your own codes can count as several units. A code that is also the item’s primary barcode, its SKU, or a code from Shopify or another app always counts as one unit. A carton code is never the code a tap sends, and an item that only a carton code finds is listed under Can’t be scanned. Serial items and items measured in weight, length or volume count every code as one unit. “Counts as” is not the Units per carton in the item’s dimensions, which is shelf capacity only. A GS1 Digital Link web address stored as it reads, as a barcode, an alternate barcode or a SKU, finds its item as stored. ## Check a new setup Print and scan representative identifiers, including the longest SKU, a lot with expiry and a dense matrix code. Confirm the returned identifier and attributes in the intended floor task. Repeat after changing the medium, printer driver, scanner output settings or scaling. PDF and independent decoder tests verify the software output; physical legibility depends on the actual equipment and stock. ## Scan with a phone or tablet camera No scanner at hand? Every floor task can scan with the device’s camera. 1. Open the task in Floor Mode. 2. Tap Scan with camera. Allow the camera when the browser asks. 3. Hold the barcode inside the white frame. A short tick means the camera read it. 4. Floormode answers the scan as it answers a scanner. The camera reads EAN, UPC, Code 128, Code 39, QR and Data Matrix codes. It counts a label once while it stays in view. To scan the same label again, move the camera away for a moment, then back. Tap Light on in a dark aisle if your phone has a flashlight. The camera turns off when you close it or switch to another app. If Floormode may not use the camera, allow it for this site in the browser settings. Inside Shopify admin the camera may be blocked, or the button may not show. Open Floormode in its own browser tab or as the installed app instead. ## Can’t scan? Take a photo A torn, faded or wrinkled label that no scanner reads still prints its code. With Read codes from a photo on (Settings › Picking & floor › Floor Mode, per warehouse, off by default), Floor Mode reads that printed code from a photo. 1. On a bin or item step, open Scan with camera or Type code. 2. Tap Can’t scan? Take a photo, hold the label inside the frame and tap Take the photo. 3. Check the code Floor Mode read, then tap Use A-01-03. Nothing is booked before you tap it. Check it: a code from a photo counts exactly like a typed one. A warehouse that asks for scans still asks a lead wherever it asks one for a typed code, and the desk’s summary of a pick list or parcel says “2 from a photo”. Floor Mode only uses a code that names one bin or one item. When two bins or items look alike (A-01-08 and A-01-0B, a barcode two items share), when the photo shows several codes, or when the bin belongs to another warehouse, it says so and you type the code. A label without a readable code may still show the product’s name. Floor Mode then shows the items that look like it, but never books them: scan or type the item’s code. On Look up and on Today, tapping a bin or an item it found opens it there. A cart slot, a serial number, a lot and a parcel’s seal are never read from a photo. A device without a camera shows no photo button. ## Weigh with a USB scale The pack station can read the parcel weight from a USB scale, so nobody types it. Which scales work: most USB shipping scales that need no extra software, such as Dymo M-series, Mettler Toledo PS-series and Stamps.com scales. Their manuals call them HID or point of sale scales. Which browsers: Google Chrome or Microsoft Edge on a computer. Safari, Firefox, phones and tablets cannot read a scale. They keep the typed weight. 1. Plug in the scale and switch it on. 2. Open a parcel on the pack station. 3. Click Connect scale under the weight field. Pick your scale in the list the browser shows. 4. Put the parcel on the scale. When the weight settles, Floormode fills it in. 5. Click Verify parcel or Save package as usual to keep the weight. Floormode remembers the scale in this browser. Next time it connects by itself. If the scale switches itself off, switch it on again and Floormode reads it again. A weight you typed is never replaced. Floormode shows Use scale weight instead, and you choose. The scale may show grams, kilograms, ounces or pounds. Floormode saves whole grams and shows the weight in the warehouse’s units: “2 lb 12 oz” in a warehouse on imperial units, “1,361 g” in a metric one. Floormode also knows what the items and the box should weigh. When the scale differs by more than 15%, it asks you to check the parcel. You can still go on. This check needs a weight and dimensions on every item. Enter each box’s empty weight under Manage boxes too, or the box counts as weighing nothing. Inside Shopify admin the browser may block the scale. Then the button does not show. Open Floormode in its own browser tab or as the installed app instead. ## Install Floormode on a phone or tablet Installed, Floormode opens straight into Floor Mode, full screen, from the home screen. - iPhone or iPad (Safari): open Floormode, tap Share, then Add to Home Screen. - Android (Chrome): open Floormode, open the menu, then tap Install app or Add to Home screen. The installed app uses your Floormode login, not Shopify admin. Sign in once in the app. It always loads the current version of Floormode, so there is nothing to update. ## Carrier pickups Shipping › Logistics books a carrier’s pickup (collection) at a warehouse, and shows each pickup with its status, number and fee. - Schedule pickup books the day’s open labels of the carrier at the warehouse; for a carrier with an end-of-day close-out it also closes them out. A manifest’s ⋯ menu books that manifest’s parcels. - The fee line says what a pickup costs: USPS is free; UPS shows its price and asks for your Max fee. Booked only if UPS’s quote is within your Max fee. UPS bills its own charge, which can be higher; a higher charge is flagged, never cancelled for you. Contract carriers charge under your contract, if at all. A carrier without a pickup API shows where to book it instead. - Cancel pickup cancels at the carrier; the row changes only on the carrier’s answer. When the carrier does not answer, the row says Cancellation not confirmed: check the carrier, then resolve it as cancelled or still booked. Reschedule cancels and books the same parcels again. - Pickup plans (per warehouse and carrier): When I ask, Regular pickup (the carrier comes on your contract’s daily pickup; nothing is booked) or Book at close-out (USPS: the close-out books the day’s pickup, or adds its parcels to the one already booked while its Collect by time is still 30 minutes away). A plan holds the window, the pickup contact (empty: the Shopify location’s) and where the parcels wait. - Owed by close-out is a booking a close-out made due before the carrier was asked: Book now, Book for another day or Drop it. A pickup the carrier missed is resolved as Not collected, then booked again. Carrier Book Cancel Fee UPS Floormode (live accounts once enabled) Floormode Booked only if UPS’s quote is within your Max fee. UPS bills its own charge; a higher charge is flagged, never cancelled for you. USPS Floormode (live accounts once enabled) Floormode free ShipEngine Floormode Floormode your carrier contract CouriersPlease Floormode CouriersPlease account your contract FedEx, DHL Paket, EasyPost, Sendcloud, Royal Mail, Evri, DPD UK, Australia Post, Aramex AU, GLS, DPD DE, DHL Express, Sendle the carrier’s account the carrier’s account the carrier’s ## See also - [Compatible hardware] (/getting-started/compatible-hardware/) - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Pack stations] (/features/settings/pack-stations/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/customer-notifications/ # Customer emails Choose who sends shipping emails and which parcel updates customers get, and where customers follow their order. In Floormode, Settings → Customer emails has four tabs. Emails decides who sends your customers’ shipping emails and which parcel updates they get. Brand, Words and Sender & page hold your look, your words and your sender address per store, and where customers follow their order — the order page in your store and the block on Shopify’s order status page. With two stores or more, the Store picker in the header chooses whose brand you edit. ## Choose the sender Under Shipment email owner for new orders, choose Shopify (recommended), Floormode or No shipment emails from these flows. Shopify stays the default and sends each fulfillment confirmation with your Shopify email branding. An order’s sender is settled by whichever comes first: its first fulfillment, or the first customer email for it that goes to the email provider (an order-held or backorder notice can come before any parcel). From then on the order keeps that sender; a change of the setting applies to every order whose sender is not settled yet. Order confirmations, invoices, payment changes and financial-only order edits stay with Shopify either way. When Floormode sends, it sends one first-shipment confirmation per order, then the parcel updates you select. Each update names its own parcel: if one parcel is delivered while another is still on its way, a delivered email does not mean the whole order arrived. Two switches pause Floormode’s emails without changing the sender: Email customers as their parcel moves pauses them for every order, and Notify customers, under Advanced at the end of the tab, allows or stops the selected updates (the fold opens by itself while it is off). The order page in your store stays available while they are off. ## Choose parcel updates Under Delivery milestones that email the customer, switch on the updates customers should get: Label created, In transit, Out for delivery, Delivered, Delivery problem, Delivery attempt failed and Returning to sender. More parcels can mean more emails. A repeated carrier update for the same parcel and milestone sends nothing new. Before the parcel ships adds optional notices for orders waiting on stock or production: Order held and Item backordered. Recent notifications lists the latest customer emails and whether they went out. Filter by status, and choose Retry on one that failed. ## The order page in your store Every order has a page inside your own online store, in your theme, at /apps/floormode-tracking. Returns start on the page next to it, /apps/floormode-tracking/r ([Returns → Requests] (/features/returns/requests/)). Shopify forwards these pages to Floormode through its app proxy, so they need the Online Store channel. Customers reach the page from the button in Floormode’s emails, Shopify’s tracking link and the order status page, or find their order with the order number and their email address or postal code. The page shows the order’s items, its parcels with carrier and tracking number, its progress and any return. It never shows the customer’s name, street, postal code, email address, phone number or any amounts. Under Settings → Customer emails → Sender & page: - Order page address shows the address with Copy and Open. - Path in your store follows Shopify’s app proxy path (Settings › Apps › Floormode › App proxy in Shopify). Change it here only after renaming it there. - Link customers to chooses The order page in your store or The carrier’s tracking page. A password-protected or paused store can’t show the order page: link customers to the carrier until the store is open. - Check link opens the saved address as a customer would and says whether customers can reach it. The Order page preview below shows the page in your current brand. ## The block on Shopify’s order status page With Shopify’s customer accounts, Floormode adds a block to the order status page customers see when they are signed in. It shows where the order stands in your warehouse — packed, shipped or waiting, with the reason and the promised day — and links to the order page in your store. It uses the customer’s own Shopify session; no extra sign-in is needed. To place it, open Shopify’s checkout and accounts editor (Settings → Checkout → Customize in Shopify), switch to the order status page and add the app block Floormode order status. Removing the block changes no order or shipment. ## Your brand, words and sender Settings → Customer emails holds what every customer email and page shares, per store: - Brand — the store name in emails, the logo (PNG or JPEG, up to 128 KiB and 2048 pixels per side), its width and position, accent, background and text colours, and corners. The colour check says whether every pairing reads at 4.5:1 or better. - Words — the email introduction, footer and sign-off, the packing slip line, the default language and the support email. - Sender — the From address. Emails go from Floormode’s address under your store’s name until your own domain is verified ([Sending domain] (/features/settings/sending-domain/)). The email preview beside the cards shows your unsaved draft, and nothing is sent from it. ## See also - [Sending domain] (/features/settings/sending-domain/) - [Shipping] (/features/fulfillment/shipping/) - [Returns → Requests] (/features/returns/requests/) - [Backorders & oversell] (/features/inventory/backorders-and-oversell/) Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/settings/sending-domain/ # Your own sending domain Send your customer emails from your own domain, with the DNS records to add and how to stop. Customer emails can leave from an address at your own domain instead of Floormode’s shared sender. You choose the address, add a few DNS records once, and Floormode switches the sender when your domain is verified. ## On this page - What a sending domain does - Choose the address - Add the DNS records - Keep your existing email records - Verification - Until it is verified - Switching back - See also ## What a sending domain does Shipment confirmations and tracking updates show your address as the sender, such as bestellungen@yourshop.com. Replies go to your support address either way. ## Choose the address In Settings → Customer emails → Sender & page, type the From address for the store. Then choose Verify and confirm that Floormode may send the store’s order emails from that domain. Two stores can share one domain. If the domain is your store’s own domain in Shopify, it needs no extra proof. Any other domain gets one verification record first. ## Add the DNS records The Sender card lists the records to add at your DNS provider: the verification record if one is needed, then the sending records. Copy each value exactly, then choose Check again. A DMARC record is recommended too. ## Keep your existing email records The sending records go on their own names (send. and resend._domainkey.). Records the mailbox provider of your main domain uses stay untouched. Keep the records in place after verification. ## Verification Floormode checks when you choose Check again, and when the email service reports a change. Nothing is checked on a timer, so choose Check again after you add the records. If the email service no longer has your domain, the Sender card says so. Choose Check again: Floormode sets the domain up again and lists its new sending records. Your verification record stays as it is. ## Until it is verified Your emails go from Floormode’s address under your store’s name, with replies to your support address. They never stop while the domain waits. The same holds while sending from your own domain is not switched on for your shop yet: the Sender card says so. ## Switching back Clear the From address in Customer emails → Sender & page, then remove the domain. Emails return to the shared sender at once. ## See also - [Customer notifications] (/features/settings/customer-notifications/) Last updated: 18 October 2026 --- Source: https://docs.floormode.app/features/settings/privacy-requests/ # Customer privacy requests What to do when Shopify forwards a customer data request, from the download to marking it completed. Shopify forwards two kinds of privacy requests: a customer asks for their data, or asks for it to be erased. Floormode lists them with a deadline and prepares the export; sending it is your step. ## On this page - Where requests come from - Deadlines - Download the export - Review before you send - Send the response securely - Mark the request completed - Erasure requests - See also ## Where requests come from The customer asks Shopify; Shopify tells every installed app. Requests appear under Settings → Customer privacy with the customer and the date. ## Deadlines Each request shows the date by which a response is due. Requests past their deadline are listed first. ## Download the export The export holds every record Floormode has for that customer: orders, shipments, returns, notes. Choose Download customer data on the request and keep the page open while Floormode collects the records: the JSON file downloads once every part has been read. If the export fails or you choose Stop export, start it again (Download fresh export) for a new complete file. Older closed orders in the [history archive] (/features/settings/history-archive/) are part of the export too. ## Review before you send Read the export before it leaves. Remove anything that belongs to another person, and add data you hold outside Floormode. ## Send the response securely Floormode does not send the export by itself. Deliver it to the requester over a channel you trust, never as a plain attachment to an unverified address. ## Mark the request completed Once the reviewed response has reached the requester, choose Mark securely delivered. The request is recorded as completed with your name and the time. Downloading the file alone does not complete a request, and Floormode sends no e-mail or other message by itself. An empty export still needs a review and a response. ## Erasure requests An erasure removes the customer’s personal details from Floormode’s records while keeping the order history anonymised. It runs by itself once Shopify’s own grace period has passed. A request whose customer was erased shows Customer details erased and cannot be exported again. ## See also - [Settings overview] (/features/settings/overview/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/settings/history-archive/ # History archive Where old closed orders and the stock books go, how an archived order still opens and comes back, and how long each part is kept. Floormode keeps your working data fast by moving what is finished and old out of it, into the history archive. Nothing is lost: an archived order still opens, and the stock books stay downloadable. The archive’s card is under Settings → Customer privacy → History archive. ## On this page - What moves, and when - Opening an archived order - Restore - The books - How long each part is kept - See also ## What moves, and when The archive works at night, between 01:00 and 05:00 in your first warehouse’s time zone: your store’s, unless you set the warehouse’s own, and UTC only when neither is known. It moves from your store’s first night. The card’s first line says what it does for your store: moving, or — only when Floormode support set it so — copying (everything is copied, nothing leaves Floormode yet) or off. Very busy stores can choose Use 21 days on the card: closed orders then move after 21 days, from the next night, and still open, search and restore from Orders. Go back to the automatic days returns the days you had before. Whoever holds the Customer data requests permission can choose it. - Closed orders past your store’s window: fulfilled or cancelled, and last changed in Shopify longer ago than the days the card names. A store with many orders keeps fewer days; a shorter window is announced on the card before it starts. They move with everything that belongs to them: their picks, packs, shipments, cost of goods sold and their own stock movements. - Receipts and counts older than two years, or one year when closed orders stay 45 days or fewer. - The stock books: the stock movements and the cost of goods sold, one part per day, copied two days after the day ends, for every store whatever its age. An order waits while something is still open on it: a change still on its way to Shopify, a task, a staged release, a parcel discrepancy, a label being bought. A document that never ended (a shipment never delivered, a return never closed) holds it at most 90 days more; it then moves with that document’s last state, and its timeline says so. The card names what the orders it keeps here wait on, and the last night’s pass. ### When a change is refused for storage One Floormode account holds about 10 GB. Before a warehouse’s opening import, a stock import that adds new bin positions, a store joining, a store’s location or products being linked, or a longer pack-photo plan, Floormode checks that the account still fits six years ahead. If it would not, nothing changes and the message names the share of the storage it would reach: contact support. ## Opening an archived order An archived order opens at its usual address, read-only, with an Archived on … badge: the items, the customer (while kept), shipments and tracking, and who picked and packed it. Names are read when you open the page, so someone who left your team reads Former team member. To find one, open Orders and use Find an archived order under the list. It shows once older orders are archived, and searches like Shopify does: by order number, customer name or email. Lists that can show closed orders say so in their footer: “Older orders up to … may be archived.” ## Restore Restore on an archived order brings it back into Floormode, for example for a goodwill return after the return window. It needs a role with Edit orders, holds and merges. Floormode reads the order from Shopify again and keeps it for 90 days. A restored closed order runs no automation rule and sends no customer notification again, apart from the label of a return you open for it. Its earlier pick and pack history stays in the archive. A customer’s return restores the order by itself. When a customer starts a return on your store’s returns page and the order is archived but still inside its return window, Floormode brings it back on its own: the customer is asked to try again in a minute, and the return then goes ahead as usual. An order past its return window stays archived, and the customer reads that its return window has ended. An order whose customer data was erased is never restored. ## The books The card lists the books by month, for the year you choose: Stock movements, Cost of goods sold, Lot shipments, Receipts, Counts, Lot receipts and returns, Serial shipments and Stock value at month end. Download gives one month as a compressed CSV file, ready for your accountant. Reading the card and its books needs a role with Analytics, forecasts and stock value. Caution Uninstalling Floormode deletes the archive. With one store, it is deleted at once; in an account with several stores, uninstalling one store removes that store’s archived orders, and the last store’s uninstall deletes the rest. Download the books you must keep before you uninstall. ## How long each part is kept Part Kept An order’s facts: numbers, lines, lots, quantities, shipments 10 years An order’s customer part: name, addresses, email, notes 6 years A lot’s whole trace, live and archived (Shipped earlier → Show archived shipments on its page) 6 years A privacy erasure deletes the customer part at once; the facts stay. The export of a customer data request includes the archived orders it names: every archived copy, its facts and its customer part. An erased customer part is stated as erased. ## See also - [Privacy requests] (/features/settings/privacy-requests/): the requests the archive answers too. - [Lots & serial numbers] (/features/inventory/lots/): a lot’s archived shipments. - [Accounting export] (/features/insights/accounting-export/): the monthly figures built from the books. - [Installation] (/getting-started/installation/): what an uninstall deletes. Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/settings/stores/ # Stores Several Shopify stores of one business in your company's one Floormode — one stock, one floor, each store its own orders. Settings → Stores (/settings/stores) lists the Shopify stores that share your company’s Floormode. They share one stock, one warehouse floor and one team; each store keeps its own orders, its own plan and its own Shopify. Admins see it. One store A one-store Floormode works exactly as before. Settings → Stores lists your one store with Connect another store and the Join your company’s Floormode card, and nothing about stores shows anywhere else until a second store joins. ## On this page - The main store - Connect another store - Start a store - A store’s page - Orders from several stores - Who sees what - When a store leaves - See also ## The main store The store the account was made from is the Main store. Its plan sets the account’s features and its order allowance. If it leaves, the store that joined first becomes the main store. ## Connect another store 1. In this account: Settings → Stores → Connect another store. Tick These stores belong to the same business. and choose Create code. The code has 12 characters and works once, for 15 minutes. “The same business” means one company, or companies of one group that have agreed between them to share their orders, customers and stock here. Floormode cannot check this: by ticking the box you confirm it. 2. In the other store: open Floormode there, then Settings → Stores → Join your company’s Floormode, and enter the code. 3. Read the checks. Floormode shows every check with its verdict. The store must be fresh (no Floormode work of its own yet), have an active plan, sell in the same currency, and fit: at most ten stores in one account, and about 330,000 orders in 30 days across all its stores (fewer when every received line is inspected, or when its stores’ catalogs and stocked bins are large). When the stores together would shorten how long the account keeps closed orders, the preview says so first: older ones open from the archive. Its orders must also have been counted, and it must not still be leaving that account. The preview also lists what that store’s own Floormode settings lose: its people, roles, carrier accounts, rules, templates, saved views, webhooks, app connections and custom domains. 4. Tick the same box and choose Join. Its Shopify orders and products are read again under this account. Nothing in Shopify changes. ## Start a store A joined store sells nothing from your warehouse until you start it. On its page, choose Start: three steps, and nothing is written to the store until the last one. Step What you do Locations Pick which of the store’s Shopify locations ship from which of your warehouses. Products Link each product to the item you already stock. Accept all links the exact matches; Check needs your pick; Leave alone keeps a product out; Bring in Shopify’s count adds one you don’t stock yet. Start Read the preview of the changes, then Start. From then on, every linked product’s number in that store is Floormode’s. ## A store’s page Card What it shows Stock updates Whether Floormode updates this store’s numbers, checked every night. When the store’s numbers differ, Count counts those bins and Re-set sends your numbers again; Re-set asks first, and Keep Shopify’s leaves them as they are. Products Every link, the automatic ones and the ones you accepted, each with Undo. Plan The store’s own plan; one the store will not renew says when it ends. If it ends, that store’s new orders wait for its renewal; its stock keeps updating. Who joined it Who joined the store. Someone the account already knows by the same verified email is the same person, with their role. Anyone else who opens Floormode through a joined store has no role until an Admin gives one (Give a role). When this store leaves What happens to its open orders if it uninstalls Floormode: hold their stock for 14 days (recommended), or put it back at once. ## Orders from several stores - Every order list has a Store filter. Orders and the Queue show each order’s store with its badge under the order number; Pack, Shipments and Returns show a Store column, which Orders, the Queue and Return requests offer under Columns. - Inventory is one shared stock, so it has no store filter. An item’s page shows each store’s number for it. - Two stores can both have an order #1001. Search finds both. On the floor, scanning a number two stores share asks you to scan the pick list or the tote instead. ## Who sees what The stores share one team. Anyone whose role lets them see orders sees the orders and customer details of every store in the account, in the warehouses their role covers; there is no role for one store only. Packers see the delivery address on the label and the packing slip whichever store the order came from, and each packing slip carries its own store’s name. Your customers see nothing of the other stores: every customer page and email belongs to one store, with its own look and sender. ## When a store leaves A store that uninstalls Floormode leaves the account. Its open orders follow When this store leaves: their stock is held for 14 days (recommended) so paid goods can still ship, or put back at once. While it is held, Held orders on its page lists them, each with Back to stock; Put all back now releases them all. A parcel whose fulfilment was on its way to Shopify when the store left shows Unconfirmed: choose Did it ship? and answer what happened at the warehouse. Then Floormode removes the store’s data from the account: its orders, customers, returns, photos, documents and archived orders, and the team members who used only that store. Stock movements, valuation and warehouse history stay, without personal details. If the main store leaves, the store that joined first becomes the main store, and its plan sets the account’s features. ## See also - [Warehouses] (/features/settings/warehouses/) — each warehouse’s Shopify location - [Billing] (/features/settings/billing/) — plans and what they unlock Last updated: 30 October 2026 --- Source: https://docs.floormode.app/features/settings/team/ # Team, roles & floor devices Who works in Floormode, what each role may do, and how floor phones and scanners sign people in. Everyone who works in Floormode is one person on Settings → Team & devices, however they sign in: with their Shopify staff account, with a P&H account in a normal browser tab, or with a PIN or badge on a floor device. ## On this page - People - Roles - What a role decides, and what warehouses decide - Floor devices - Lead approvals - The Team pages - See also ## People Settings → Team & devices → People lists everyone, with their role, their warehouses and how they sign in. - Add floor person adds someone who works only on the floor. They need no email: open their page, make a PIN and, if you like, print a badge. Both are shown once, so write them down or print them then. - Invite emails someone a link to sign in with a P&H account, with their role and warehouses already chosen. You need a P&H account of your own to invite. - Shopify staff who open Floormode from the Shopify admin hold the role set under Defaults → Shopify staff start as until someone gives them another. Automatic means Admin while every connected store has been confirmed as a development store within the last seven days, and Manager otherwise. - Needs a role lists people who signed in with a P&H account that has no Floormode role yet. They can open nothing until someone gives them one. - Removed from your P&H organisation lists people who lost their access there. Deactivate them, or unlink the P&H login. The Shopify store owner who first opens Floormode becomes its first Admin. After that, owning the store gives no extra rights: Admins give and change roles, and the team always keeps at least one active Admin. If your team ever has no Admin left, contact support. ## Roles Admin, Manager and Floor are built in and cannot be changed: Role May do Admin Everything, including integrations, customer data requests, billing, the API, stores and roles. Manager All the desk work and settings, except those six. A Manager adds and invites people as Floor. Floor Floor Mode only: pick, pack, receive, count and move stock. Every desk page sends them to Floor Mode. To make your own role, choose New role and start from a copy of a role, or with nothing ticked; or open a role and choose Duplicate. A Lead, for example, is a copy of Floor with Approve floor exceptions (lead) and Assign and release work for others ticked. Roles are saved in your P&H account, so changing them needs your own P&H account and a role with Create roles and give any role (Admin has it). You can give a role only permissions you hold yourself. A change shows Saving to your P&H account… until it arrives; meanwhile people with the role can do only what both versions allow. ## What a role decides, and what warehouses decide A person’s role decides which pages and actions they can open. Their warehouses decide where they work on the floor and which tasks they can be given, not what they can see at the desk. A Manager with one warehouse still sees every warehouse’s orders on the desk; a picker with one warehouse gets only that warehouse’s work. ## Floor devices Settings → Team & devices → Floor devices → Add device shows a QR code and an 8-character code. On the scanner, phone or tablet, scan the QR code, or open /floor/register and type the code. A code works once, for 10 minutes; New code replaces it. Set up for is Until removed, or Today only: the device stops working at midnight, for a temp or a borrowed phone. Device Who signs in Shared scanner Anyone in the warehouse, with their PIN or badge. Personal phone Only the one person it belongs to. Wall screen Nobody: it shows the wallboard. - A device locks itself after a quiet spell. A new shared scanner starts with the time set under Defaults, a new personal phone with 30 minutes; change one device’s time in its settings on Floor devices. In the ⋯ menu, Lock screen or Not you? Switch person hands a shared scanner to the next person. On a personal phone, Use another phone removes it; a manager then sets up the new one. - After five wrong PINs a device waits 30 seconds, then longer each time. After the fourth wait, a manager unlocks it on Floor devices. - Under Defaults you also choose the PIN length and whether a badge alone signs in or needs the person’s PIN as well. - The built-in Floor role cannot open the wallboard. Tick Open the wallboard on your own copy of Floor to offer it under ⋯ on Today. ## Lead approvals Some floor exceptions, such as shorting a line, need a lead. The lead types their own PIN on the device at that moment; a badge never approves. The lead is recorded on the line. ## The Team pages The Team entry in the navigation shows the day’s people and work, one warehouse at a time: - Today: who is here, who is away, and the work each holds right now. - Plan: who does what, day by day. It appears once Plan days for people is on under Settings → Team & devices → Defaults. - Output: what each person did, for people whose role has See output per person. Defaults sets how many days it shows, or turns it off. It never shows on a floor device or the wallboard. - Shifts: the warehouse’s shifts, who works which, and the days that differ, in the warehouse’s time zone (your store’s, unless you set the warehouse’s own). If Floormode knows no time zone for it yet, the page asks for one first. - Time: hours from the time clock, a month per person, and every entry. Turn the time clock on per warehouse under Settings → Team & devices → Time clock; the warehouse’s Details tab links there too. Note Floormode records who works on what and when. Check the privacy and employment rules where your team works before you introduce it; where staff are represented, they may need to be consulted first. In Germany, a works council may need to agree (§ 87 (1) Nr. 6 BetrVG). In the EEA and the UK, you may need a data protection impact assessment (Art. 35 GDPR). The Team pages name these rules only for a store in those countries. The time clock shows who was on the floor; it is not your legal working-time record unless you decide to use it that way. This is guidance, not legal advice. ## See also - [Standalone access] (/getting-started/standalone-access/): signing in outside the Shopify admin. - [Floor Mode] (/features/floor/overview/): what people do once signed in. - [Queue] (/features/fulfillment/queue/): where work is handed out. - [Team output, plans and time] (/features/settings/team-output-and-time/): output per person, shifts, day plans and the time clock. Last updated: 5 November 2026 --- Source: https://docs.floormode.app/features/settings/team-output-and-time/ # Team output, plans and time Look up and Quick stock on the floor, output per person, shifts, day plans, targets and the time clock. Beside people and roles ([Team] (/features/settings/team/)), Floormode gives the floor its own tools to look up and book stock, and gives leads the Team pages: what each person did, who is on shift, the day’s plan and targets, and the time clock. ## On this page - Look up, Quick stock and My stats - Output per person - Shifts - Day plans and targets - The time clock - Your own records - See also ## Look up, Quick stock and My stats Every floor person scans on Today: a pick list opens as before, a bin or an item opens Look up (what a bin holds, or where an item is, its free units and who needs them), and a packing slip opens its parcel for someone who packs. Without a scanner, ⋯ → Look up & stock → Look up offers Search. Quick stock books units without a task: Put found units into a bin, Take units out with a reason (damaged, sample, internal use, lost, expired, correction), or Move them between bins. Every booking goes through the same rules as the desk: lots, bin limits, “Only this product” and reserved units, which are never taken. The last booking can be undone once while the screen is open; both rows stay on the item’s history. - Move belongs to the built-in Floor role. - Put and Take need Quick stock: put and take units without a task. Managers have it; tick it on your own copy of Floor to give it to the floor. My stats (⋯ → My day) shows a person their own numbers today and this week, never a colleague’s. With Output per person switched off it shows none. ## Output per person Team → Output shows what each person did in one warehouse: lines, units and pick lists picked, the typical pick time and units an hour, orders packed and the typical pack time, units received, count lines and moves. Beside it: parcels per pack station, pick lists per pick profile, and the hours of the week the work was finished. - Typical is the middle value, to within about 5 %: half took less, half more. A pick list confirmed from paper or picked with a single scan has no measurable pick time and is left out of it, and out of units an hour; the page says how many. - Which days: Settings → Team & devices → Defaults sets “Show output per person for” the last 7, 14 (the default), 30 or 90 days, or Off. Lowering it takes effect at once. More than 14 days, and rankings (a rank and an order by any figure), are an Admin’s choice and show the notice Floormode shows on the Team pages again. - Who sees it: people whose role has “See output per person”. Never on a floor device, the wallboard or the API. - It counts the work finished since Output arrived in Floormode; earlier work is not in it. ## Shifts Team → Shifts plans when people work in one warehouse, in its local time: your store’s time zone, unless you set the warehouse’s own. If no time zone is known for it yet, the page asks for one first. Shift times are written in 24-hour form (06:00–14:30), as is the timesheet file. - A shift has a start, an end (after midnight it still belongs to its start day), a break and weekdays. Put a person on a shift from a day on; end it on their last day. - A day off or another shift changes one day, up to 90 days ahead. - Team → Today names who is expected by their shift and not here yet. - A shift plan says when people work; a day plan says what they do. Neither changes the other. ## Day plans and targets Team → Plan says who does what, day by day: for each person and day, up to four areas in order (pick in zone A, then pack at station 2). Turn it on in Settings → Team & devices → Defaults → “Plan days for people”. Nobody planned pulls work from the pool, as before. - What a plan does: on the floor, Today shows the person “Your plan today” first: the plan’s areas in order, its zone or station as the scope. Everything else stays one tap away (“Also open”). A plan never assigns an order and never refuses work. - Who plans: whoever may plan shifts, up to 28 days ahead. Moving someone during today also works with the assign permission. - Shifts and days off come from Team → Shifts and are shown, never edited, in the planner: each day’s shift times and how many people are on shift, and “Off” for a person’s day off. New planning is refused on a day off; copying a week and “Plan from usual areas” leave it empty. A plan saved before the day became off is marked so you can clear it. - Keep plans for 30, 90 (the default) or 365 days: how long plans and team targets stay past their day. Targets (Elevate) add a number to a plan’s picking or packing area: orders picked, parcels packed. A target is guidance: the person sees it and their count on their own device (“Only you see this”), keeps pulling once it is reached, and nothing happens if it is not. Leads with “See output per person” see it on Team → Today. Never a name on the floor or the wallboard, never ranked. - Switching targets on asks you to confirm Floormode’s notice with a checkbox: targets per person are a new evaluation of how people work. They need day plans on and “Show output per person” above 0 days, and pause while either is off. - Team targets (one number per day for the whole team) are always allowed with day plans on Elevate, whatever the per-person switch: the wallboard shows “212 / 420 parcels packed today” and the team’s pace. On a day one person did the work, it shows the count only. - “Split evenly” and “Spread…” divide a team target, or a person who is not in, over the people planned for that work. Nothing is redistributed by itself. ## The time clock Turn the time clock on per warehouse (Settings → Team & devices → Time clock, the warehouse chosen in its header). People then Clock in, take breaks and Clock out & finish on the floor; clocking out ends the day as “Done for today” does. Where people sign in with a badge alone, clocking asks for their own PIN. The time clock shows who was on the floor. It is not your legal working-time record unless you decide to use it that way; check your duties where your team works. In a store in Germany the note ends “check your duties and your works council”. - A forgotten clock-out: an open clock is flagged after the shift and closed for review at the person’s next clock-in or by a lead. Nothing closes it on a timer. - Team → Time shows hours per person and day for a month (worked, breaks, planned, to review) and every entry. Minutes closed for review never count as worked until a lead confirms them. Download the month as a CSV; its first line is the note above. - A lead corrects someone else’s entry with a reason; nobody corrects their own. Every correction stays with the entry. - Hours are never set against output: Team → Output counts work, Team → Time counts hours. - How long: Settings → Team & devices → Defaults → “Keep time records for” 3 to 24 months (24 by default). What Floormode keeps about your team, and for how long: [Floormode’s privacy policy] (https://p-h.solutions/floormode/privacy-policy). ## Your own records Anyone can download their own records — sign-ins, shifts, time records with every correction, presence and output days — as one file from their own page under Settings → Team. An Admin downloads a former team member’s for them. ## See also - [Team] (/features/settings/team/) - [Floor sign-in] (/features/floor/sign-in/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/features/settings/billing/ # Billing Your current Floormode plan, its status, and what each tier unlocks. Settings → Billing (/settings/billing) shows your Floormode subscription: which tier you are on, whether it is active, and what each tier unlocks. ## On this page - What the page shows - Status matters as much as tier - A plan that does not renew - Changing plan - See also ## What the page shows - Your current plan — Essential, Elevate, Enhanced or Enterprise. - Its status — active, active until a date when Shopify will not renew it, or cancelled. - Order allowance — counted releases, the confirmed billing cycle, and any warning, grace deadline or required plan. - What each tier unlocks — so an upgrade decision is made with the list in front of you. Billing goes through Shopify, so the subscription lives with the rest of your Shopify app charges rather than as a separate invoice to reconcile. ## Status matters as much as tier Only an active subscription grants features. Status Effect Active Your tier’s features are unlocked. No plan yet A fresh install. Setup works; new orders are released once Shopify confirms a plan. Cancelled No active plan. Paid feature gates close and new order releases require an active subscription. Test plan · no charge Floormode’s own test plan for development stores: every feature is unlocked and it is never charged. A plan you choose on a development store is a free test charge too, but it keeps that plan’s tier: Essential stays Essential. Caution A cancelled subscription locks the six gated features — automation, reports, pick profiles, cluster picking, FEFO allocation and the external API — until you choose a plan again. Floormode reads your subscription from Shopify’s billing record, which reports an active plan or none. Your data is untouched. Nothing is deleted, no rules are removed, no history is lost. The gates simply close, and reopen when the subscription goes active again. Uninstalling is different: it deletes your warehouse data at once, and reinstalling starts a new, empty setup. In an account of several stores, only the last store’s uninstall does that. See [Uninstalling] (/getting-started/installation/#uninstalling). The core WMS and OMS is included in Essential. Already released fulfillment work, inventory operations, imports and synchronization can continue when an order allowance expires. New releases require the indicated confirmed plan. Subscription status and the allowance grace period are separate; see [how orders count] (/getting-started/subscription-plans/#how-orders-count-and-what-happens-at-the-limit). ## A plan that does not renew A plan can stay Active while Shopify has already scheduled its end. The usual case: you uninstalled Floormode, which cancels the plan, and reinstalled it before the period was over. The billing page then says Your plan does not renew and names the day: Your plan ends on the end of the current billing cycle, or of the trial when no paid cycle has started. Until that day your tier’s features stay on, and new orders keep being released as far as your [order allowance] (/getting-started/subscription-plans/#how-orders-count-and-what-happens-at-the-limit) allows. From that day the store has no active plan, as in Cancelled above. Choose a plan before then to keep releasing orders without a gap. Uninstalling is separate: uninstalling the last connected store deletes your warehouse data at once, even while the plan itself is still active until its end date. ## Changing plan Upgrades and downgrades happen through Shopify’s hosted pricing page: Manage plan in Shopify, or Choose a plan on its card. Shopify asks you to confirm the change, and Floormode verifies the actual current contract before updating access. A scheduled change does not unlock features early. On a development store, Shopify approves any plan as a free test charge. There are no automatic paid upgrades and no per-order fees. Enterprise is listed for up to 40,000 orders a month. ## See also - [Subscription plans] (/getting-started/subscription-plans/) — the full tier comparison. - [Uninstalling] (/getting-started/installation/#uninstalling) — what an uninstall deletes. - [Automation] (/features/settings/automation/) — the Elevate rules engine. - [Cluster picking] (/features/fulfillment/cluster-picking/) — an Enhanced feature. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/overview/ # Floor Mode A full-screen, scanner-first surface for the warehouse floor — no admin chrome, giant tap targets, one job at a time. Floormode’s Floor Mode (/floor) is the screen the people doing the work actually use. No admin chrome, giant tap targets, one job at a time. It is the last nav entry on purpose: opening it leaves the admin behind. The whole shell is replaced by the scanner surface. ## On this page - The five jobs - Where you work, and the ⋯ menu - Scanning with the phone camera - Install it on the phone or tablet - The same work as the office - No search on the floor - Where to next ## The five jobs [Pick] (/features/floor/pick/) One line at a time: scan bin, scan item, confirm quantity. [Production pick] (/features/floor/production-pick/) Pick a work order's components to the staging bin. [Pack] (/features/floor/pack/) Scan every item of the parcel, then box, weigh and verify. [Receive] (/features/floor/receive/) Scan the item, confirm the quantity, scan the putaway bin. [Count] (/features/floor/count/) Scan the bin, scan the item, enter what is really there. ## Where you work, and the ⋯ menu Today starts with where you work: a zone or a station. Someone working zone A opens the app onto zone A’s work and nothing else. Everything else sits behind ⋯ in the top corner of every screen, so the task keeps the screen: - This line and This task — what the job allows right now, such as reporting a bin empty or giving a pick list back. - This device — the screen (Bright, Dim, or follow the device), the text size, whether this device has a scanner, and on a shared scanner who is signed in (Lock screen, or Not you?). A person holding a scanner and a box needs the next job, not a settings page: these few choices are all the floor has. ## Scanning with the phone camera No scanner at hand? Every scan field has Scan with camera. Point the camera at the barcode; a read counts like a scanned code. Hold a label in view and it counts once; move the camera away and back to scan it again. The camera turns off when you close it or leave the screen. The camera reads the common barcodes on items, bins and labels (EAN, UPC, Code 128, Code 39, QR and Data Matrix). Note Inside the Shopify admin the browser may refuse the camera. Then open Floor Mode in its own tab, or install it (below), and allow the camera when the phone asks. ## Install it on the phone or tablet Floor Mode can live on the home screen like an app. On Android, open it in Chrome and choose Install app or Add to Home screen. On an iPhone or iPad, open it in Safari, tap Share and then Add to Home Screen. It opens full screen, straight into the floor, and still signs in with your Floormode login. ## The same work as the office Floor Mode is the same Floormode, drawn for the floor: the same orders, the same pick lists, the same stock — full screen instead of inside the admin. That is why the floor and the office never disagree: a pick confirmed on a tablet in the aisle is the same record the office sees update in the [queue] (/features/fulfillment/queue/), not a copy that catches up later. Floor Mode is also reachable in standalone mode, at its own URL with its own login — which is how warehouse staff who have no Shopify admin account get to it on a shared tablet. ## No search on the floor Caution Floor Mode deliberately has no search box and no ⌘K shortcut. A scanner gun is a keyboard that types fast; if a search overlay could open mid-pick, a barcode scan would open it and swallow the rest of the scan. This is a safety property. ## Where to next - [Fulfillment queue] (/features/fulfillment/queue/) — where floor work is handed out. - [Search everything] (/getting-started/search/) — and why it stops at the floor. - [Zones, stations & staff] (/features/settings/warehouses/) — defining the scopes. - [Wallboard, work area & inspect] (/features/floor/wallboard-work-area-inspect/) — the floor’s other three screens. - [Floor move] (/features/floor/move/) — put away, replenish, move and return to shelf. - [Device sign-in] (/features/floor/sign-in/) — setting up a device, PINs, badges and locks. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/pick/ # Floor pick One line at a time — scan bin, scan item, confirm quantity. Floor pick is the picker’s screen in Floormode (/floor/pick/:id). One line at a time, in route order, with the next bin always on screen. ## On this page - The loop - Route order - When the bin is short - See also ## The loop For every line: 1. Scan the bin — confirms you are where the system thinks you are. 2. Scan the item — confirms you have the right thing. 3. Confirm the quantity — how many you took. Then the screen advances to the next line. There is no list to navigate and nothing to tick off manually; the job in front of you is the only thing on screen. Tip Scanning the bin before the item is what catches the expensive mistake. Two similar SKUs in adjacent bins scan identically as items but sit in different locations — verifying the location first makes picking from the wrong bin a blocked action rather than a mis-ship discovered by a customer. ## Route order Lines come in [pick path] (/reference/glossary/#pick-path) order — zone → aisle → side → bay — so the walk is one pass through the building. Warehouses with bin coordinates get a further-optimised route. You do not choose the order and you cannot skip ahead arbitrarily; the route is the efficiency. ## When the bin is short If the bin does not hold what the system expected, you record a [short pick] (/reference/glossary/#short-pick) rather than hunting for stock or silently taking fewer. That does three things: - The line is marked Picked short instead of quietly under-picking the order. - The discrepancy lands in the [movement ledger] (/features/inventory/adjustments-and-movements/) against that specific bin. - The order surfaces on Home under [Needs attention] (/features/home/needs-attention/) so the office can act. A short pick is information, not a failure. A bin that shorts repeatedly is telling you something a monthly shrinkage figure never would. ## See also - [Batches] (/features/fulfillment/batches/) — the office view of the same batch. - [Production pick] (/features/floor/production-pick/) — the component-picking variant. - [Floor Mode overview] (/features/floor/overview/) — the surface itself. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/production-pick/ # Production pick Pick a work order's components to the staging bin, ready for the build. In Floormode, Production pick (/floor/component-pick/:id) is the fifth Floor Mode job. It looks like a normal pick and ends somewhere completely different: instead of a parcel going to a customer, the picked components go to a [staging bin] (/reference/glossary/#staging-bin), ready to be built. ## On this page - Components, not orders - The loop - Where it ends - See also ## Components, not orders A normal [floor pick] (/features/floor/pick/) pulls the things a customer bought. A production pick pulls the things a work order needs — the components that will be assembled into a finished item. The distinction matters to the numbers behind it. Components picked to staging are no longer freely available, but they have not been shipped either: they are committed to a build that has not happened yet. ## The loop The picker’s loop is deliberately identical to a normal pick — scan bin, scan item, confirm quantity — because it should be. A picker who knows one screen knows both, and the muscle memory carries over. What differs is the destination: instead of a tote heading for the pack station, the components go to the staging bin named on the job. ## Where it ends The picked components sit in staging until the build runs. From the order side, an order waiting on that build shows the hold reason “Waiting for production”, and its progress stepper carries the Waiting stage — the warehouse is not what is late. Note Floormode picks and stages the components; it does not own the build itself. Where Assemblified runs your assembly, the work order that drives this pick lives there, and the two apps coordinate over what has been staged and what has been built. [Integrations → Assemblified] (/integrations/assemblified/) covers that hand-off in full: what the work order announces, what progress is reported back, and what happens when a plan changes or a build is cancelled. ## See also - [Floor pick] (/features/floor/pick/) — the ordinary picking loop. - [Holds] (/features/orders/holds/) — the “Waiting for production” reason. - [Bins] (/features/inventory/bins/) — the staging bin type. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/pack/ # Floor pack Scan every item of the parcel, then box, weigh and verify. Floor pack is the packer’s screen in Floormode (/floor/pack/:id). Everything in the parcel gets scanned before anything gets sealed. ## On this page - The loop - Box, weight and verify - Why every item - See also ## The loop 1. Read the order’s note, when it has one (“Gift: no invoice”): tap Got it before the parcel goes on. 2. Scan every item going into the parcel — one at a time, all of them. Without a scanner, use Scan with camera, or the confirm button where the warehouse allows tapping. 3. Box — the app proposes the box [cartonization] (/reference/glossary/#cartonization) chose; confirm it or override. 4. Weigh — record the actual parcel weight, in the warehouse’s units: − and + step one ounce in a warehouse on imperial units (“2 lb 3 oz”), 50 g in a metric one. 5. Verify parcel — saves the box and the weight. 6. Fulfil — once every required step is done, the job reads Ready to fulfill. The button says what one press does, such as Fulfil + print label where the checklist buys the label first, or Fulfil. The steps after the scan follow the warehouse’s pack checklist (Settings → Packing → Pack checklist): each of Photo, Weigh, Details, Check and Label is off, optional or required there, and the screen shows only the steps that are on. [Pack] (/features/fulfillment/pack/#the-pack-flow-step-by-step) lists every step, what you need before you start, and how the label step changes the fulfil. ## Box, weight and verify The proposed box comes from your [box catalog] (/features/settings/carriers-and-packaging/) and the item dimensions. Overriding is always allowed — the packer holding the goods knows something the dimensions may not. Weight matters because it is what the carrier bills against. A recorded weight that matches reality is the difference between the rate you were quoted and the adjustment that arrives on next month’s invoice. Where the warehouse’s pack checklist has Check set to required, that inspection step runs here as part of the loop. ## Why every item Tip Scanning every item, not a sample, is what makes the wrong thing in the box a physically blocked action rather than a mistake to catch later. The economics are lopsided. Scanning costs a second or two per item. A mis-ship costs a return shipment, a replacement shipment, the original margin, the handling on both, and often the customer. There is no scan rate that is not worth it. ## See also - [Pack] (/features/fulfillment/pack/) — the office view and the job statuses. - [Shipping] (/features/fulfillment/shipping/) — buying the label for a verified parcel. - [Item dimensions & capacity] (/features/inventory/item-dimensions-and-capacity/) — what makes the box proposal good. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/receive/ # Floor receive Scan the item, confirm the quantity, scan the putaway bin. Floor receive is the receiver’s screen in Floormode (/floor/receive/:id): book a delivery in by scanning. The office can book the same receipt at the desk, with Receive on a line in [Receiving] (/features/inventory/receiving/). Both write the same receipt. ## On this page - The loop - Lots and serial numbers - Putaway: in the same pass, or later - Over-receipt and capacity - Finishing the receipt - See also ## The loop 1. Scan the item — identifies what arrived. 2. Confirm the quantity — how many of it. 3. Scan the putaway bin — where it is going. Repeat until the delivery is booked in. The receipt moves from Expected to Being received on the first line and to Received when it is complete. Where the warehouse sends units for waiting orders straight to packing, the screen says so instead of a bin: Take 3 to packing for #1001. [Straight to packing] (/features/inventory/receiving/#straight-to-packing-cross-docking) explains the switch. Where the warehouse receives to a dock, step 3 is a single press instead: Accept 24 books the units into the dock, and the screen says where they go next (“Goes to DOCK-01 · Put away later”, or “Inspect next”). Without a scanner, Receive this on a line under Still expected starts it, where the warehouse allows tapping. ## Lots and serial numbers - A lot-tracked item always asks for its Lot number. Where the item tracks a date, it asks for that too, in the item’s own words, such as Best before or Use by; a lot whose date is required cannot be booked without it. - A serial-tracked item whose serial numbers are recorded at receiving asks for every unit: Scan each unit, one serial number per unit, listed as you go. (An item set to record them at packing asks at the pack station instead.) A serial already in stock, shipped or belonging to another item is refused with the reason. In a warehouse set to Scan only, typing serial numbers instead of scanning them needs a lead’s approval. - A partial carton of serial units: a lead can Accept 6 now for the units scanned so far. See [Lots & serial numbers] (/features/inventory/lots/) for how the office reads them later. ## Putaway: in the same pass, or later With the warehouse’s receiving policy Straight to a shelf, confirming the bin in the same loop means [putaway] (/reference/glossary/#putaway) happens as goods are received. With At the dock, shelved later the goods are booked into DOCK-01 and a putaway task follows; with Check goods first (inspection) they are booked into QC-IN-01, inspected, and the passed units get a putaway task. The policy is set per warehouse ([Receiving] (/features/inventory/receiving/) lists all three). Tip Receiving to a dock and putting away later is where inbound stock goes missing on the floor: it sits on a pallet by the door, not in the bin a picker walks to. Floormode never offers it for sale meanwhile. Goods on the dock or in inspection are on hand, and become sellable once a putaway task brings them to a shelf. Scanning the destination bin as part of receiving skips the dock entirely. Where [Placement] (/features/inventory/placement/) is configured, the screen proposes the home bin rather than making the receiver decide. ## Over-receipt and capacity Two guards apply as you confirm quantities: - Over-receipt tolerance — a per-warehouse policy for how much more than expected the floor may book in before the app pushes back. - Capacity warnings — where the destination location has a capacity set, putaway warns if the delivery will not fit. A location with no capacity set is treated as unlimited, never as zero. Anything received that does not match expectations becomes a [discrepancy] (/reference/glossary/#discrepancy) on the receipt, visible to the office rather than absorbed silently. ## Finishing the receipt ⋯ → Finish receipt closes it. With every line received it says so; with lines still open it asks first, and finishing closes them short. A line whose product is not in your catalogue yet cannot be scanned: Close them short records it as not received, Keep open, tell the office leaves the receipt open for the office to add the product. ## See also - [Receiving] (/features/inventory/receiving/) — the office view and receipt statuses. - [Placement] (/features/inventory/placement/) — the rules behind the proposed bin. - [Item dimensions & capacity] (/features/inventory/item-dimensions-and-capacity/) — where capacity warnings come from. - [Wallboard, work area & inspect] (/features/floor/wallboard-work-area-inspect/#inspect) — passing and rejecting goods received into inspection. - [Floor move] (/features/floor/move/) — the putaway that follows a dock receipt. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/count/ # Floor count Scan the bin, scan the item, enter what is really there. Floor count is the counter’s screen in Floormode (/floor/count/:id). Three steps, and the third one is the whole job. ## On this page - The loop - Blind counting - What happens next - See also ## The loop 1. Scan the bin — confirms which location you are counting. 2. Scan the item — confirms what you are counting. 3. Enter what is really there — the number in front of you. That third step is phrased deliberately. Not “confirm the quantity”, not “is this correct?” — enter what is really there. The screen is asking for an observation, not an agreement. ## Blind counting Where the count is [blind] (/reference/glossary/#blind-count), the counter never sees the expected quantity. Tip This is the difference between counting and confirming. Shown “48” and holding what looks like about 48, almost anyone types 48. The count then confirms the system’s belief rather than testing it — and a bin that has been quietly wrong for months stays quietly wrong. A blind count produces an independent number. It is the only kind worth reconciling against. ## What happens next The counter’s job ends at the number. What happens to it is somebody else’s decision: - Matches — the count closes. - Differs — the count goes to Needs review, not straight into your stock figures. A count goes for review once every bin is done: each item counted, each bin with nothing on the sheet looked into and confirmed empty. If a counter cannot finish, Can’t finish? Send what I have in the ⋯ menu names the bins still open and asks why (out of time, can’t reach a bin, something else). Those bins and items go as not counted, never as zero: their stock stays as it is, and the review shows them first. The approval queue in [Counts] (/features/inventory/counts/) is where someone decides whether the count was right (adjust the system) or wrong (recount). Approving posts a reason-coded adjustment into the [movement ledger] (/features/inventory/adjustments-and-movements/). Separating the two roles is what keeps counting honest: the person holding the goods reports what they see, and nobody is asked to both observe and adjudicate. ## See also - [Counts] (/features/inventory/counts/) — statuses, variances and the approval queue. - [Adjustments & movements] (/features/inventory/adjustments-and-movements/) — where an approved variance lands. - [Bins] (/features/inventory/bins/) — what gets counted. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/move/ # Floor move Put away, replenish, move and return to shelf — one two-step screen: take from a bin, bring to a bin. In Floormode, every task that carries stock from one bin to another opens the same screen: Put away goods from the dock, Replenish a pick bin, Move stock, and Return to shelf what a cancelled pick left behind. The screen has two steps, and the header says which one you are on: Step 1 of 2 · take … and Step 2 of 2 · bring …. ## On this page - Before you start - Step 1: take from - Step 2: bring to - When it does not go to plan - See also ## Before you start Open the task from Today in [Floor Mode] (/features/floor/overview/), or take it in the [Queue] (/features/fulfillment/queue/#other-floor-work). You need a scanner, or Scan with camera. Where the warehouse lets workers confirm by tapping, a phone with This device has no scanner switched on gets confirm buttons instead. ## Step 1: take from 1. Scan the bin the task names under Take from. For a [putaway] (/reference/glossary/#putaway) after a delivery, that is the bin the goods were received into, such as the dock. 2. Scan the item: its barcode or SKU. 3. Scan the lot, when the item is lot-tracked and the task names a lot or the bin holds only lotted units. The screen lists the lots it expects. 4. Count what you took and press Took 24 (your number). Scans made while the number is on screen wait until you confirm it. ## Step 2: bring to 5. Scan the shelf bin under Bring to. Where the task planned a bin, scan that one; where it did not, scan the bin you put the goods in. The scan records the movement, and the screen shows it under Already moved. Where the warehouse allows tapping and the task planned a bin, a Confirm button does the same without a scan; the earlier steps get their own confirm buttons the same way. 6. When units are left on the task, Move the rest starts the next round. A scan of a different sellable bin than the planned one is allowed: the screen says Not the planned bin, and its Confirm button records the movement there. A bin that is not active, or the bin the goods came from, is refused. ## When it does not go to plan Everything below sits behind ⋯: - Only part of it fits: change how many you bring. The rest stays on the task. - Bring it to …: back to the planned bin after you scanned another. - Start again: scan the source bin, or the item, again. - Release this task: give it back to the pool for someone else to take. - Source bin is empty, for a lead: closes the task and flags the bin for a count. A putaway from a delivery cannot be closed this way. If the connection drops while a movement is being recorded, the screen keeps it and offers Retry same movement: the same movement is never booked twice. Leaving before it is confirmed asks first, because the goods in your hand are not booked yet. Tip Return to shelf brings back what a cancelled pick left at the staging bin. Its target is the item’s home bin, or another active sellable shelf; the task closes once every unit is back. ## See also - [Floor Mode overview] (/features/floor/overview/): the other floor jobs and the ⋯ menu. - [Floor receive] (/features/floor/receive/): where putaway tasks come from. - [Placement] (/features/inventory/placement/): how the planned bin is chosen. - [Adjustments & movements] (/features/inventory/adjustments-and-movements/): where every movement is recorded. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/wallboard-work-area-inspect/ # Wallboard, work area & inspect The floor's other three screens — today's work in big numbers for a wall, the zone or station whose work you see, and the inspection of goods a receipt brought in. Beside the five jobs, Floormode’s Floor Mode has three screens of its own: the wallboard for a screen on the wall, Work area for choosing whose work you see, and Inspect for goods that arrive into inspection. ## On this page - The wallboard - Work area - Inspect - See also ## The wallboard The wallboard shows today’s work in numbers readable from across the floor. Open it from ⋯ → Wallboard in Floor Mode, or set up a Wall screen under Settings → Team & devices → Floor devices → Add device: a wall screen shows the wallboard with nobody signed in. - Today’s output: Shipped today, Shipped yesterday, Due today and Late. A late figure is amber and says so in its label, never by colour alone. - Average pack time: today’s average as a clock, the parcels packed today under it, and how many took over 30 minutes and are left out of the average. Team figures only: no person, no station and no ranking reaches the wall. - Open work, one tile per job: receive, pick, pack, ship, count and returns. Under Pick, the work orders whose materials are being picked are named (“Materials for …”). - Team targets [Elevate plan] (/getting-started/subscription-plans/): Team picking and Team packing, done against today’s target (“120 / 300 orders picked today”) and when the team gets there at this pace. The targets are set under Team → Plan, and their day is the warehouse’s. - Ready by profile: how many orders each pick profile has ready. The board updates by itself and says when it last did. Its output and open work count the day by the clock of the screen it runs on, so set a wall screen to the warehouse’s time zone. The built-in Floor role cannot open it; tick Open the wallboard on your own copy of Floor to offer it under ⋯ on Today. A role that can see fulfillment work opens it too. ## Work area Today starts with where you work: a zone, a station, or All work. The row at the top says which (“Zone A”, “Station PACK-01”); Change opens Work area, and so does ⋯ → Work area. 1. Tap All work, a zone or a station. When yours span several warehouses, each tile names its warehouse. 2. Tap Show this work. Today and its lists then show that zone’s or station’s work only. The choice is remembered for you, on every device you sign in on. The row appears once the warehouse has zones or stations: a manager sets them up under the warehouse’s [Zones, stations & staff] (/features/settings/warehouses/#zones-stations--staff). Until then everyone sees all work. ## Inspect With the warehouse’s receiving policy Check goods first (inspection) (Settings → Receiving & stock, the warehouse’s Receiving card), received goods are booked into the inspection bin QC-IN-01, and Today lists Inspect … units for each receipt with units waiting, oldest first. The receipt’s screen lists what is Waiting for inspection. Scan an item, or tap Inspect this; for an item that came in several lots, choose the lot under Which lot is it?. Then: - All pass: every waiting unit of that item passed. Passed units go to the dock, DOCK-01, with a putaway task to bring them to a shelf. - Some failed: say How many failed? and Why did they fail?. The line above the bar says where they go before you confirm, for example “2 go to HOSP-01 · Pass 3, reject 2”. Then Reject … books them. Why they failed Where they go Damaged, Packaging HOSP-01, damaged stock Wrong item, Expired, Other QUAR-01, quarantine One of your own fail reasons QUAR-01, quarantine Other asks What is wrong? in up to 500 characters. Your own fail reasons, such as “Torn seal”, are added on the warehouse’s Receiving card, and so is Photo of failed goods: the inspector then takes a photo before rejecting units, and photos are kept for 90 days. When every unit is judged, the screen says Nothing waits for inspection, and Inspect next opens the next item or Next task returns to Today. Neither passed nor failed units are offered for sale until they reach a sellable shelf. Tip An inspection is per unit, not per parcel: a carton with three good units and two crushed ones is three passes and two rejects. ## See also - [Floor Mode overview] (/features/floor/overview/): the five jobs and the ⋯ menu. - [Floor receive] (/features/floor/receive/): receiving on the floor, before the inspection. - [Receiving] (/features/inventory/receiving/): the warehouse’s receiving policy. - [Team, roles & floor devices] (/features/settings/team/): wall screens and the roles that open the wallboard. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/features/floor/sign-in/ # Floor device sign-in Set up a scanner, phone or tablet as a floor device, sign in with a PIN or badge, hand it to the next person, and what happens after wrong PINs. This page is for the people using Floormode on the floor: how a device is set up, how you sign in on it, and what to do when it locks. A manager adds the device and your PIN first, under Settings → Team & devices; see [Team, roles & floor devices] (/features/settings/team/#floor-devices). ## On this page - Set up the device - Sign in - Hand the device on - Wrong PINs and locks - See also ## Set up the device A manager chooses Settings → Team & devices → Floor devices → Add device, picks the kind of device, and gets a QR code and an 8-character code. Then, on the scanner, phone or tablet: 1. Open Floor Mode. A browser that is not a floor device yet shows This browser is not set up for Floor Mode; choose Set up this device. Or open /floor/register, or scan the QR code with the device’s camera. 2. Scan the QR code with the device’s scanner, which goes straight to the confirmation. Or type the 8-character code and press Check code; the card then also names the warehouse and the device. A code works once, for 10 minutes; if it was refused, ask the manager for a new one. 3. Check the names on the card, then press Make this a floor device (or Make this a wall screen). Use another code starts again. Kind Who signs in Shared scanner Anyone in the warehouse signs in with their PIN or badge. Personal phone Only the one person it belongs to signs in on it. Wall screen Nobody. It shows the warehouse’s figures on its wallboard. A device set up Today only stops working at midnight. A manager can remove a device at any time; it then says This device was removed, and Set up this device again needs a new code. ## Sign in The sign-in screen names the device and its warehouse, and says Enter your PIN or scan your badge. - PIN: type it on the pad. A personal phone asks only for its owner’s PIN: Enter your PIN to unlock your phone. - Badge: scan it with the scanner, or tap the badge key and hold its QR code to the camera. Where your warehouse asks for both, the screen says Badge read · Enter your PIN to finish. - No PIN yet? Ask a manager. A PIN and a badge are shown or printed once, when the manager makes them. On a shared scanner the screen then says Welcome, …, and Start opens your work; if the name is not yours, Not you? goes back to the sign-in. A personal phone shows its welcome once a day and otherwise opens your work straight away. ## Hand the device on Behind ⋯, under This device: - Lock screen: the device goes back to the PIN pad. Type your PIN to carry on. - Not you? Switch person, on a shared scanner: the next person signs in with their own PIN or badge. - Use another phone, on a personal phone: removes this phone. A manager then sets up the new one. A device also locks itself after a quiet spell; the sign-in screen says how long, for example “Locks by itself after 10 minutes without a touch.” ## Wrong PINs and locks You see It means What to do Wrong PIN · Enter it again. The PIN did not match. Type it again. Wait a moment or Too many tries · Wait 30 seconds, then try again. Five wrong PINs within 15 minutes make the device wait 30 seconds. Each further five wrong PINs double the wait. Wait for the countdown, then try again. Locked after wrong PINs · A manager unlocks it under Floor devices. After the fourth wait the device stops taking PINs. Ask a manager to unlock it under Settings → Team & devices → Floor devices. The PIN could not be checked The connection dropped while checking. Try again. Note A lead approves floor exceptions, such as shorting a line, by typing their own PIN on the device at that moment. A badge never approves. ## See also - [Team, roles & floor devices] (/features/settings/team/): adding people, PINs, badges and devices. - [Floor Mode overview] (/features/floor/overview/): what you do once signed in. - [Compatible hardware] (/getting-started/compatible-hardware/): scanners and phones that work. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/integrations/overview/ # Integrations How Floormode divides the work with Logistified and Assemblified — who owns which document, and what changes on your screens. Not available yet The connections to Logistified, Assemblified and Alertified open after Floormode’s approval. Until then each switch under Settings → Apps & API → Apps reads Not available yet and cannot be turned on. Until then nothing travels between the apps, and Floormode runs on its own ([If you run Floormode on its own] (#if-you-run-floormode-on-its-own)). Floormode is one of three apps that can share a warehouse. Each owns a different part of the job, and the split is deliberate: one app owns each document, so nobody has to reconcile two systems that both think they are right. ## On this page - The division of labour - What that means in practice - The pages in this chapter - If you run Floormode on its own ## The division of labour App Owns Typical documents Logistified Procurement — what to buy and from whom [Purchase orders] (/reference/glossary/#purchase-order), suppliers, transfer orders, stocktakes Assemblified Production — what to build and from what [Work orders] (/reference/glossary/#work-order), bills of materials, bundles Floormode The physical warehouse and everything outbound Receipts, bins, picks, packs, shipments, returns Caution Logistified is procurement, not shipping. The name suggests logistics in the delivery sense, and that is the wrong end of the process. Logistified decides what you buy; Floormode does everything physical and everything that goes out of the door to a customer. The rule that follows from the table is worth stating on its own: If it is physical, it happens in Floormode. If it is a commitment — to a supplier, or to a build — it happens in the sibling. A purchase order is a promise to a supplier, so it lives in Logistified. The pallet that turns up against it is physical, so it is received in Floormode. A work order is a plan to build something, so it lives in Assemblified. The components someone walks around the building collecting are physical, so they are picked in Floormode. Customer communication belongs to Floormode too. Neither sibling emails your customers. ## What that means in practice Once the apps are connected, nothing is entered twice. Documents raised in a sibling announce themselves in Floormode as work to do, and Floormode reports back what physically happened: - A purchase order in Logistified becomes an [expected delivery] (/integrations/logistified/) in Floormode receiving, complete with supplier and expected date. - A work order in Assemblified becomes a [production pick] (/integrations/assemblified/) on the floor. - What the floor actually received or picked travels back to the sibling, so the document there stays honest without anyone retyping it. - Goods the sibling owns but Shopify has never heard of — raw materials, sub-assemblies, custom items — are stocked here as [local items] (/features/inventory/local-items/), in real bins, counted like anything else. Messages between the apps are queued and confirmed rather than fired and forgotten. If a sibling is unreachable, the work waits and retries; a switched-off sibling gets nothing — see [Parked and held] (/integrations/parked-and-held/). ## The pages in this chapter [Run Floormode with Logistified and Assemblified] (/integrations/three-apps/) The setup guide: install order, the switches, receiving, work orders, packaging, lots, FEFO and the connection states. [Logistified] (/integrations/logistified/) Purchase orders and transfers arriving as expected deliveries, and receiving progress reported back. [Assemblified] (/integrations/assemblified/) Work orders announcing component picks, staged components, and finished goods coming back into stock. [What changes when connected] (/integrations/what-changes-when-connected/) Screen by screen: what looks different once a sibling is connected, and what stays exactly the same. [Who writes Shopify] (/integrations/who-writes-shopify/) The single-writer rule, why double-writes cause drift, and how to check nobody has been left out. [Bundles and kits] (/integrations/bundles-and-kits/) Picking a kit's components when there is no finished one on the shelf, and how that reads on the order. [Local items] (/features/inventory/local-items/) Raw materials, sub-assemblies and custom items: stocked here, never on Shopify, and always in a bin. [Integration health] (/integrations/health-panel/) Connection status, queued and waiting messages, and the warning that says nobody is writing Shopify. [Parked and held] (/integrations/parked-and-held/) What happens when a sibling is not answering, and why a switched-off one gets nothing. [Activation] (/integrations/activation/) Connecting the apps, what switches itself on, how to verify it, and what stops when you disconnect. [Standalone] (/integrations/standalone/) Floormode without siblings: what works, what stays empty, and what connecting later does not backfill. ## If you run Floormode on its own Everything in Floormode works without either sibling. Expected deliveries can be entered by hand, replenishment exports CSV for any supplier, and holds record a document reference whether or not that document lives in another app. [Standalone] (/integrations/standalone/) is the honest account of which surfaces stay empty until you connect something — and of what connecting later does and does not bring with it. ## See also - [Receiving] (/features/inventory/receiving/) — the screen a purchase order lands on. - [Production pick] (/features/floor/production-pick/) — the screen a work order lands on. - [Subscription plans] (/getting-started/subscription-plans/) — what each tier unlocks. Last updated: 27 October 2026 --- Source: https://docs.floormode.app/integrations/three-apps/ # Run Floormode with Logistified and Assemblified The setup guide for all three apps on one shop — install order, the switches, warehouses, receiving, work orders, packaging, lots and best-before dates, FEFO, who writes Shopify, and what each connection state asks of you. Not available yet The connections to Logistified, Assemblified and Alertified open after Floormode’s approval. Until then each switch under Settings → Apps & API → Apps reads Not available yet and cannot be turned on. The connection steps on this page apply once it opens; until then the three apps run side by side, each on its own. This page is for whoever sets the three apps up on a shop — often a merchant’s developer, on one afternoon. Each app keeps its own job: Logistified buys, Assemblified plans what gets built, Floormode runs the warehouse — every bin, every pick, every receipt. Follow the steps in order; each one says where to click and how to tell it worked. ## On this page - Install the apps - Set up your warehouses and go live - Connect Logistified - Hand receiving over, location by location - Connect Assemblified - Packaging and inserts - Lots and best-before dates - Pick the earliest expiry first - Who updates which Shopify quantity - The connection states - Hamper batches and recall - See also ## Install the apps Install all three on the same Shopify shop, Floormode first. Logistified and Assemblified only connect to a Floormode installed on their own shop, so with Floormode in place the other two can be installed in either order. Each app needs an active plan of its own. Floormode reads the other apps’ install and plan state; it never changes it. ## Set up your warehouses and go live Before you connect anything, Floormode has to be the warehouse of record: 1. In Settings → Warehouses, map each warehouse to the Shopify location it ships from. Documents from the other apps are routed by Shopify location, so a warehouse without a location receives nothing. 2. Set up its bins and its opening stock — the warehouse page’s setup guide walks you through both. 3. Click Go live on the warehouse page. From then on Floormode keeps that location’s Shopify quantities up to date. Connecting Logistified is refused while a receiving warehouse is not live, and an Assemblified work order for a warehouse that is not live is refused too — so this step comes first. ## Connect Logistified 1. In Floormode, open Settings → Apps & API → Apps and switch Logistified on. 2. In Logistified, open Settings → Integrations and switch the Floormode connection on there. 3. Back in Floormode, the status reads Connected, no exchange yet. Raise a small purchase order in Logistified and confirm it: it appears in Inventory → Receiving as an expected delivery, and the status turns Connected. From now on goods are booked in here, and only here. See [Logistified] (/integrations/logistified/) for what travels each way. ## Hand receiving over, location by location Receiving moves to Floormode per Shopify location, through an agreement driven from Logistified’s Settings → Integrations: 1. Prepare. Choose the locations in Logistified. Nothing changes yet; Logistified checks each one and says which are ready. 2. Go live in Floormode. A location is only ready when its Floormode warehouse is live. Logistified names any that are not; go live on their warehouse pages here. 3. Activate. Commit the agreement in Logistified. It is all or nothing: one location that is not ready refuses the whole set, and nothing changes. The Activity tab of Floormode’s Settings → Apps & API then lists every location as received here or received by Logistified. The details are in [Who writes Shopify] (/integrations/who-writes-shopify/#handing-over-one-location-at-a-time). ## Connect Assemblified 1. In Floormode, Settings → Apps & API → Apps: switch Assemblified on. 2. In Assemblified, Settings → Integrations: connect Floormode there. 3. In Assemblified, make a [work order] (/reference/glossary/#work-order) ready to build at a live warehouse’s location. Its components appear on the Floor home as a Production pick, the work order shows on Fulfillment → Production, and the status turns Connected. Caution Build with work orders, not assemble flows. Only a work order tells Floormode what to pick and what comes back. An assemble flow run in Assemblified changes its own numbers and never reaches the warehouse, so your bins and Shopify drift apart. When a build finishes, Floormode books the finished goods at once onto the warehouse’s workbench bin, WO-STAGE-01, and a putaway task brings them to a shelf, as after a delivery to the dock. An output that needs the receiver — serial numbers taken at receiving, or a date Floormode cannot work out — waits on its receipt instead. See [Assemblified] (/integrations/assemblified/) and [Hamper batches and recall] (#hamper-batches-and-recall) below. Assemblified and Logistified also connect to each other, in Assemblified’s Settings → Integrations, so Logistified can forecast the materials your builds use. That link does not involve Floormode. ## Packaging and inserts Boxes, tissue, ribbons and recipe cards are not things you sell, so they should not be Shopify products. Create them in Assemblified as virtual materials and put them on the recipe. Once Assemblified is connected, they arrive in Floormode as [local items] (/reference/glossary/#local-item), ids starting VMAT- — listed under Inventory → Stock → More stock actions → Item setup and recovery. From then on they live in Floormode’s bins like any stock: - Receive them here. A Logistified purchase order for a virtual material arrives in Inventory → Receiving as an expected receipt, like any purchase order: receive the delivery on it. Without a purchase order, use New receipt or a blind receipt. - They are picked with the work order’s components into its staging bin, WO-STAGE-01, and leave stock when Assemblified reports the build that used them, not when the pick completes. - They never appear on Shopify. Nobody writes a Shopify number for them, by design. - Track a batch where it matters. Open the item from Item setup and recovery (its name is a link to the item) and set its Tracking to Lot. Its batches then join the hamper batch’s record below, so a recall reaches them too. Give it a best-before only if the packaging really carries one — an undated box is still traced. Floormode holds their stock once the Assemblified status reads Local stock active. Until then Assemblified keeps its own count. ## Lots and best-before dates Turn lot tracking on for every ingredient that carries a date, and for the finished product too: 1. Open the item’s page and find its Tracking card. 2. Choose Lot — a lot number and date at receive. 3. Set Date on the lot to Best before, and switch on Date is required so nothing is booked in without one. Receiving then asks for the lot number and the date of every delivery, and Inventory → Lots shows each lot with its stock. A GS1 barcode that carries a best-before (15) or an expiry (17) fills the date for you. For the finished product, Floormode sets the batch number and the date itself — see below. ## Pick the earliest expiry first [FEFO] (/reference/glossary/#fefo) is on every plan. Switch on Pick the earliest expiry first for each warehouse in Settings → Warehouses: sales orders then take the lot with the soonest date first, so short-dated stock leaves before it goes out of date. A blocked or expired lot is never picked, FEFO or not. Work-order component picks follow the same rule, packaging included: the pick list names the lot that expires first, and the floor scans it. ## Who updates which Shopify quantity Exactly one app writes each Shopify number. Floormode shows the split in effect right now under Settings → Apps & API → Activity → Who updates Shopify: Quantity Written by Received goods (purchase orders, transfers) Floormode — receiving happens here Sales picks and fulfilments Floormode, always Work-order components Floormode — the warehouse picks them Finished goods: a plain stocked bundle, or one sold only preassembled Floormode — the putaway writes it Finished goods: a dynamic availability or fixed inventory level bundle Assemblified — the number is calculated, not counted Packaging, inserts and other local items Nobody — they are not on Shopify The table names Assemblified or Logistified only while that app is installed on the shop; until then it reads Nobody until … is installed. A row that reads Nobody in red is a gap that needs a live warehouse — see [Who writes Shopify] (/integrations/who-writes-shopify/). ## The connection states Floormode, Logistified and Assemblified use the same words for the same state, and each state carries one sentence saying what to do. On Floormode’s Settings → Apps & API → Apps: Status What it means What to do Not installed The app is not installed on this shop. Install it, then come back here. Not available yet The other app does not offer the connection yet — it opens with that app’s update — so the switch here cannot be turned on (a switch that is already on can still be turned off). Nothing else is needed. The other app tells Floormode when its own page is opened, so opening its Settings → Integrations (Alertified: opening Alertified) checks again. Off Your switch here is off. Switch on to start. Waiting for the other app Your switch is on; the other app’s is not, or it refuses. Open that app’s Settings → Integrations and switch on there (Alertified: open Alertified and switch Floormode on there). Connected, no exchange yet Both switches are on; nothing has travelled yet. Send the first document: a purchase order from Logistified, a work order from Assemblified. Connected A message went through and was confirmed. Nothing. The line shows when the last one arrived. Local stock active Floormode now holds the other app’s local stock. Nothing. Not answering Deliveries are paused after repeated failures. Nothing is lost; Floormode keeps trying. Check connection says whether the app can be reached. Handing back Local stock is being returned to the other app. Wait for the other app to confirm; the switch turns itself off then. Uninstalled The other app was removed from this shop. Switch this off, or reinstall it. ## Hamper batches and recall One batch per work order. When Assemblified reports a finished build, Floormode books the hampers onto the workbench bin under their batch: the work order’s number, for example WO-1042, with its best-before. Set the hamper to Lot with Best before (as above) — a hamper that tracks no lots gets no batch. The best-before is the earliest of its ingredients. A batch is best before the earliest best-before of any ingredient or packaging lot its work order used. Floormode works it out when the hampers are booked. If it later learns that an earlier-dated lot went in — a component picked after the booking, say — the date moves earlier and you get a Batch date moved earlier alert telling you to relabel. A date never moves later, so a printed label is never too optimistic. Tracing works both ways. A batch’s lot page shows Made from: every ingredient and packaging lot that went in. An ingredient’s lot page shows Went into: every batch made from it, with what each still holds. From a batch, Export affected orders and the shipments list name the orders that got it — ingredient → batch → orders. 1. Open the ingredient’s lot and choose Block lot. 2. The dialog lists the hamper batches made from it that still hold stock. Tick Also block the … hamper batches that contain it to block them in the same step, with the same reason. Leave it unticked to block the ingredient alone. 3. Unblocking the ingredient later leaves the batches blocked: a batch may contain a second blocked ingredient. Unblock each one from its own page. The putaway task then brings the hampers to a shelf and asks which lot it moves: scan or type the batch number as it stands, WO-1042, without a leading #. If another lot of the hamper already carries the work order’s number (booked by hand before, say), Floormode refuses the booking: rename that lot in Floormode, then complete the run again. A hamper whose date is required but cannot be worked out — a use-by, or a best-before with no dated ingredient — waits on its receipt instead, where the receiver books it with the date. Not yet The best-before is not written to your Shopify product yet, so your theme cannot show it. Expiry warnings appear in Floormode’s alerts, not by e-mail. ## See also - [Activation] (/integrations/activation/) — what switching on and off does, and handing local stock back. - [Who writes Shopify] (/integrations/who-writes-shopify/) — the single-writer rule and the per-location handover in full. - [Local items] (/features/inventory/local-items/) — packaging, materials and sub-assemblies in your bins. - [Integration health] (/integrations/health-panel/) — the counters behind the status line. - [Warehouses] (/features/settings/warehouses/) — the Shopify location mapping and the warehouse policies. Last updated: 27 October 2026 --- Source: https://docs.floormode.app/integrations/logistified/ # Logistified Purchase orders and transfers arriving as expected deliveries, receiving progress reported back, and counts exported as stocktakes. Logistified is procurement. It owns suppliers, what you buy and the paperwork of buying it. It does not touch a physical box — the moment goods exist in your building, they are Floormode’s. The connection exists so that neither app has to be told twice: a [purchase order] (/reference/glossary/#purchase-order) raised there becomes work here, and what the floor actually receives goes back there. ## On this page - Purchase orders become expected deliveries - Receiving them - What goes back to Logistified - Revisions and cancellations - Transfer orders - Counts exported as stocktakes - Moving between the apps - See also ## Purchase orders become expected deliveries When a purchase order in Logistified reaches a confirmed state for a location Floormode receives at, it announces itself here as an [expected receipt] (/reference/glossary/#expected-receipt) — no rekeying, no CSV. What arrives with it: Document The purchase order’s number and name, so the dock and the office use the same reference Supplier Who it is coming from, visible on the receipt without opening Logistified Expected date When it is due, so you can see what is landing this week Lines Product, SKU and ordered quantity Destination Which of your warehouses it is for The receipt’s Source column reads “Logistified purchase order” rather than “Entered by hand”, so at a glance you can tell announced work from work someone typed in. Note Announcing is not receiving. A purchase order landing here books nothing and changes no stock number. It creates the expectation and the work; the goods only count when someone physically books them in. ## Receiving them Go live in every receiving warehouse before you connect: the switch refuses otherwise, because Logistified stops updating received quantities the moment it is on. Identically to any other delivery. There is no separate integration workflow to learn: the [Floor receive] (/features/floor/receive/) job scans the item, confirms the quantity and scans the putaway bin, exactly as it does for a receipt you created yourself. Everything Floormode does with a delivery still applies — putaway to real bins, lot and expiry capture where you use them, over-receipt tolerance, discrepancies, and partial receipts. A purchase order that arrives across three pallets on three days is three receipts against one document, and each is booked when it lands. Caution When the connection is on, receiving happens here and only here. Logistified’s own receiving step is deliberately switched off — there is exactly one place goods are booked in, so the two apps can never disagree about what arrived. ## What goes back to Logistified Two different things, at two different times, and the distinction is the useful part: - Progress, while receiving is underway. As the floor books lines in against an open receipt, Logistified’s copy of the purchase order updates — how many units are in, how many lines disagree with the plan, and a link straight to the receipt. Somebody in the office watching the purchase order sees it filling up without ringing the warehouse. - Totals, when the receipt completes. Closing a receipt sends the confirmed figures, which is what Logistified’s records are actually built from. Those totals are always running totals for the whole document, never “and another twelve”. A second delivery reports the full quantity received so far. It is the detail that makes a re-sent message harmless: a total that arrives twice is the same total, while an increment that arrives twice is a wrong number nobody can trace back. Note Logistified records these, it does not push them to Shopify. Once connected, writing received quantities to Shopify is Floormode’s job — see [Who writes Shopify] (/integrations/who-writes-shopify/). Later still, Logistified is told when those units are genuinely confirmed in Shopify, so its on-order figures wind down against reality rather than against an assumption. ## Revisions and cancellations Purchasing changes its mind; the connection expects it. - A revision rewrites the part you have not yet received. Quantities already booked in are never touched, never reduced, and never un-received. If a line is cut below what already landed, the outstanding remainder simply becomes zero and the excess is recorded as an over-receipt rather than becoming a negative expectation. - A cancellation closes whatever is still outstanding. Units already booked in stay booked in — they are in your bins, and no message from another app can change that. - A later, larger revision can arrive as an additional delivery against the same document, netted against what earlier receipts already booked, so nothing is announced twice. Out-of-order messages are refused rather than applied. If an older revision turns up after a newer one, Floormode declines it and says so — nothing changes, which is the correct outcome. ## Transfer orders Transfers between your own locations work the same way as purchase orders, from both ends: - Arriving — a transfer bound for one of your warehouses announces itself as an expected delivery, with the source location on it, and is received exactly like a purchase order. Its Source reads “Logistified transfer”. - Leaving — confirming that the outbound leg has left the source warehouse tells Logistified the stock is genuinely in transit. That is a status signal rather than a quantity: the units were counted when they were picked. ## Counts exported as stocktakes Approving a cycle count in Floormode exports it to Logistified as a stocktake, so its records reflect the count. This is reporting only, by design. Floormode has already corrected the bins and already written the new availability to Shopify. Logistified records what you counted; it must not — and does not — re-apply those quantities on top. ## Moving between the apps A receipt created from a Logistified document carries the document’s identity, so the two views of the same delivery are one click apart: Logistified’s purchase order links to the exact Floormode receipt that booked the goods in. ## See also - [Receiving] (/features/inventory/receiving/) — the office view of what is arriving. - [Floor receive] (/features/floor/receive/) — where goods are actually booked in. - [Who writes Shopify] (/integrations/who-writes-shopify/) — what changes about inventory writing when you connect. - [Replenishment] (/features/insights/replenishment/) — deciding what to reorder in the first place. Last updated: 24 August 2026 --- Source: https://docs.floormode.app/integrations/assemblified/ # Assemblified Work orders announcing component picks, staged components, progress reported back, and finished goods returning to stock. Assemblified is production. It owns recipes, work orders and the decision to build. It does not walk around your building collecting parts — that is picking, and picking is Floormode’s. The connection turns a build plan into warehouse work, and reports back what the warehouse actually managed to supply. ## On this page - Work orders become production picks - What the picker sees - What goes back to Assemblified - When the plan changes or the build is cancelled - Finished goods coming back - What you can see about production - See also ## Work orders become production picks When a [work order] (/reference/glossary/#work-order) in Assemblified is ready to build at a location Floormode picks for, it announces the components it needs. Those appear on the Floor home as a Production pick section, and open as a [Production pick] (/features/floor/production-pick/) job. The job names the work order and lists its materials, which come in three kinds: Kind On the floor Ordinary stocked parts Picked normally, pointed at the best bin holding stock Sub-assemblies Parts your production makes rather than buys. Real, binnable and pickable here — but they do not exist on Shopify and are never pushed to it Non-stocked lines Things on the recipe that never sit in a bin — a licence, an instruction. Shown so the plan reads completely, picked by nobody Note Quantities can be fractional. A recipe calling for 1.5 metres or 0.25 kg is a normal work order, not a rounding error, and the floor is asked for exactly that. ## What the picker sees Deliberately, the same loop as any other pick: scan the bin, scan the item, confirm the quantity. A picker who knows the ordinary pick knows this one. Two things differ: - Where it ends. Components go to a work-order [staging bin] (/reference/glossary/#staging-bin), not a pack station. They are no longer freely available, but they have not shipped either — they are committed to a build that has not happened yet. - What “short” means. If a component cannot be supplied, the picker records a shortage and it is reported to the work order. Nothing is silently re-allocated — the shortfall is production’s decision to make, not the warehouse’s. The picker finishes with either “Components staged” or “Staged with shortages”, and in the second case is told how many lines were reported back. ## What goes back to Assemblified Progress, at the three moments that matter to somebody planning a build: Report Means Picking The floor has started on your work order Staged Everything requested is staged and ready to build Short The pick closed with lines that could not be supplied This is what lets Assemblified stop a build run from starting before its parts are physically staged, rather than discovering it at the assembly workbench. Caution If the connection is switched off, the pick still works — but nobody is told. The goods are staged and the pick is recorded here, and Floormode says so plainly on the completion screen rather than pretending the message went out. See [Parked and held] (/integrations/parked-and-held/). ## When the plan changes or the build is cancelled Both are handled, and both protect work already done: - A revised plan reconciles the lines not yet picked against the new plan. Anything already picked and staged stays exactly as it is. - A cancelled work order closes the pick batch and clears it off the floor, so nobody keeps collecting parts for a build that is not happening. Components already staged for it walk back to the bins they were picked from, on their own. Only when Floormode cannot tell where a unit came from — or the staging bin is missing — does the batch wait on the Production tab for a supervisor to resolve it, which returns the materials the same way. ## Finished goods coming back When a build completes, the finished goods come back to Floormode to be put away into real bins, arriving as a receipt whose Source reads “Assemblified work order”. They are put away like any other goods, and from that moment they are ordinary pickable stock. The interesting question is who tells Shopify about them, and the answer depends on the kind of bundle — Assemblified says which on every batch, so the two apps never both write and never both stand down. The receipt itself tells you which happened, in plain words: Assemblified owns the Shopify write — putaway does not push. or Assemblified deferred the Shopify write to Floormode — putaway pushes these units. [Who writes Shopify] (/integrations/who-writes-shopify/) has the full split per bundle type. Once the goods are in bins, Floormode reports back what was put away, so Assemblified’s picture of finished stock matches your shelves. ## What you can see about production The Production tab under Fulfillment shows a pipeline with one row per work order, tracking it across the stages the warehouse can witness: announced, picking, staged, in production, awaiting putaway, and put away. The stage is derived from the freshest evidence Floormode has — the announcement, the pick’s own progress, and the finished goods arriving — so a delayed status message never moves a work order backwards on screen. Assemblified remains the home of the build itself: recipes, scheduling, and the detailed production status live there, and every pipeline row links across for that view. What you get in Floormode is the warehouse half, complete: what has been asked of the floor, what the floor has staged, what it could not supply, and what has come back. ## See also - [Production pick] (/features/floor/production-pick/) — the floor job in detail. - [Bundles and kits] (/integrations/bundles-and-kits/) — the other half of Assemblified’s recipes, on customer orders. - [Holds] (/features/orders/holds/) — the “Waiting for production” reason. - [Bins] (/features/inventory/bins/) — the staging bin type. Last updated: 23 October 2026 --- Source: https://docs.floormode.app/integrations/what-changes-when-connected/ # What changes when connected Screen by screen — what looks different once Logistified or Assemblified is connected, and what stays exactly the same. 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] (/features/floor/receive/) job. You can still create expected deliveries by hand while connected. The two coexist. ## Floor Mode [Production picks] (/reference/glossary/#production-pick) only exist when Assemblified is connected. - Standalone — the Floor home shows picking, packing, receiving and counting. There is no production section. - Connected — a Production pick 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 bin] (/reference/glossary/#staging-bin) rather than a pack station, 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] (/integrations/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 hand] (/reference/glossary/#on-hand), [committed] (/reference/glossary/#committed), [available] (/reference/glossary/#available), [incoming] (/reference/glossary/#incoming) — 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] (/features/inventory/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] (/integrations/who-writes-shopify/) question to answer for them — the push is refused rather than merely skipped. ## Counts Approving a cycle count exports it to Logistified as a stocktake, 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] (/integrations/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] (/integrations/who-writes-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] (/integrations/logistified/) — the purchasing side in full. - [Assemblified] (/integrations/assemblified/) — the production side in full. - [Standalone] (/integrations/standalone/) — the same comparison from the other direction. Last updated: 25 October 2026 --- Source: https://docs.floormode.app/integrations/who-writes-shopify/ # Who updates Shopify The single-writer rule, why two writers cause drift and zero writers are worse, and how to hand over receiving one location at a time. Shopify holds one number for how many of a thing you have at a location. Exactly one app may write it — the [single-writer] (/reference/glossary/#single-writer) rule. Everything on this page, from connecting Floormode to handing over a location, follows from that sentence. ## On this page - Why exactly one - What happens when you connect - The split, flow by flow - Handing over one location at a time - What happens at locations you did not hand over - Goods with no Shopify number at all - The warning that needs a human - See also ## Why exactly one Two apps writing the same number do not average out — they overwrite each other. Each writes what it believes, the last one wins, and the number drifts away from your shelves in a way no report can reconstruct. Caution Two writers is loud. Zero writers is silent — and that is the dangerous one. With two writers, a location double-counts and somebody notices within the hour. With zero, everything looks perfect: goods arrive, the bins are right, the ledger is right, the receipt is right. Shopify’s number simply stops moving, and nothing anywhere warns you. This is why the [health panel] (/integrations/health-panel/) exists and why it leads with this one check. ## What happens when you connect Connecting Logistified hands over received goods, because receiving now physically happens in Floormode. Logistified stops writing received quantities at that moment. For that not to leave a hole, the switch refuses while a receiving warehouse is not live and names the warehouses with a Go live link. Go live there first; then the switch goes on. Note Switching the connection back off does not take a warehouse out of live. That is deliberate: with no sibling connected, Floormode keeping Shopify’s quantities updated is the correct standalone posture, and connecting never changed it in the first place. ## The split, flow by flow Settings shows a Who updates Shopify table — the split in effect right now, given what you have connected. In summary: Flow Written by Received goods (purchase orders, transfers) Floormode when Logistified is connected — receiving happens here Sales picks and fulfilments Floormode, always, in every configuration Work-order component decrements Floormode — we pick the components, so we report them Finished goods — plain stocked bundle Floormode — Assemblified stands down and our putaway writes it Finished goods — sold only preassembled Floormode — the bundle is a real thing in a real bin Finished goods — dynamic availability bundle Assemblified, always — the number is a computed capacity, not a stock level Finished goods — fixed inventory level bundle Assemblified, always — it is a constant it maintains for you Sub-assemblies, raw materials, custom items Nobody, by design — these are [local items] (/features/inventory/local-items/) and have no Shopify number to write The last two rows of Assemblified ownership are worth understanding rather than memorising: those bundle types have numbers that are calculated, not counted. Floormode never writes them in any configuration, because a warehouse count is the wrong input for a figure that is not a warehouse fact. If any row ever reads Nobody where it should not, that is the silent gap — and the panel shows it in red. ## Handing over one location at a time Most merchants do not want to move every location on the same afternoon. If you run several, receiving can be handed to Floormode location by location — [delegating] (/reference/glossary/#delegation) one at a time — and the rest stay exactly as they are. The handover is a three-step agreement, driven from Logistified: 1. Prepare — propose which locations Floormode should receive at. Nothing changes: no stock moves, no setting flips, no receiving behaviour is altered. It is a dry run you can repeat as often as you like while you decide. 2. Readiness check — each proposed location is checked and answered individually, so you find out what is wrong before anything commits. A location is not ready when: - it has no active Floormode warehouse mapped to it, or the Shopify location is not one this shop knows; - two warehouses map to the same Shopify location, which would put two writers on one number from inside Floormode alone; - the app can no longer write to Shopify for this shop at all. 3. Commit — the proposal becomes the live agreement, all or nothing. If a single location in the set is not ready, the whole commit is refused and nothing changes — you are never left half-migrated. On success, receiving moves to Floormode for exactly those locations, and their warehouses become inventory writers in the same action. You can also release the agreement later, which withdraws it and returns the shop to the shop-wide setting. Note Until you commit, nothing changes. A shop that has never committed an agreement stays on the older shop-wide behaviour, byte for byte — the connection switch decides receiving for every location, exactly as before. An existing shop-wide setting is never silently reinterpreted as “all locations are handed over”. That guess would be wrong for precisely the multi-location merchants this exists for, so it is never made. ## What happens at locations you did not hand over They carry on as they were: Logistified keeps receiving there. That is the point of doing this per location. Concretely, once an agreement is live, a delivery announced for a location you did not hand over is refused, clearly and permanently — not queued, not retried, not half-applied. The refusal names the location, says that Logistified still receives there, confirms that nothing was applied, and tells you what to do about it: add the location to the agreement and commit it. The refusal is deliberate. Quietly accepting it would mean booking goods in at a site Floormode does not run, and writing a Shopify number that another app is still writing. Cancellations are the one exception: a cancellation is always accepted, so an expected delivery raised before a handover can always be tidied up afterwards. The Logistified row in the health panel lists every location in the agreement — received here or received by Logistified — so “who receives where” is a list you can read rather than a thing you infer. ## Goods with no Shopify number at all Everything above is about a number Shopify holds. [Local items] (/features/inventory/local-items/) — Assemblified raw materials and sub-assemblies, Logistified custom items — have no such number, because they are not Shopify products. Shopify has never heard of them and never will. That makes the single-writer question moot for them, and it is worth being precise about why: it is not that Floormode declines to write them, it is that the push is refused for local items at the point it would happen. No setting can turn it on and no future connection can cause one to appear in your storefront inventory. This is the row that reads Nobody and is supposed to. But there is still an ownership question, and it has a different answer: Shopify stock ownership is decided per location, by the agreement. Local stock ownership is decided per item, by the connection. With the connection active, the sibling ready for it, and the per-location agreement committed, Floormode becomes the physical truth for that app’s local items: - Assemblified stops consuming its own raw materials when a build completes, and shows the quantities Floormode reports instead. A work order’s components are physically picked here. - Logistified stops moving its own custom items when something is received, and shows Floormode’s figures instead. Its purchase-order paperwork still tracks how much of the order has landed — that part is unchanged — but the stock number itself comes from here. Caution Nothing is inferred. Floormode does not take over local stock because a sibling looks new enough, because a message parsed, or because a connection succeeded. The sibling has to say it is ready, explicitly, and the agreement has to be committed. Until both are true the sibling keeps moving its own stock — because guessing here means two systems each consuming the same unit. If you are not connected, none of this happens. Logistified and Assemblified behave exactly as they always have, keeping their own local quantities. There is no partial state where they have half stopped. Warehouses with no Shopify location mapped are the one blind spot: their local units are real and pickable here, but they are invisible to the sibling, because there is no honest place to put them on the other side. ## The warning that needs a human One situation is reported to you rather than fixed automatically. If a warehouse still writes inventory to Shopify but is not handed over for receiving, the panel says: …: still live on Shopify although Logistified receives there. Floormode leaves that to you. The reasoning matters. “Writes inventory to Shopify” is not only a receiving flag — it also covers sales picks, counts and adjustments, and sales picks are Floormode’s in every configuration. Switching it off because a receiving agreement changed would break something nobody asked to change. So it is surfaced for a person to decide, in Settings → Warehouses. ## See also - [Integration health] (/integrations/health-panel/) — where the table and the warnings live. - [Warehouses] (/features/settings/warehouses/) — the “Writes inventory to Shopify” flag itself. - [Activation] (/integrations/activation/) — connecting, and what it switches on. - [Local items] (/features/inventory/local-items/) — the goods with no Shopify number, and how they are stocked. - [Logistified] (/integrations/logistified/) — the receiving flow this governs. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/integrations/bundles-and-kits/ # Bundles and kits Picking a kit's components when there is no finished one on the shelf — stock first, then parts, and how it reads on the order and at the pack station. A [kit] (/reference/glossary/#kit) is sold as one thing and made of several. That creates a question for Floormode every time one is ordered: does the picker fetch a finished kit off the shelf, or fetch the parts? When Assemblified is connected, Floormode knows what a kit is made of and can answer that question per order line — [expanding] (/reference/glossary/#kit-expansion) the kit into its parts only when it needs to — rather than forcing you to choose one policy for ever. ## On this page - Where the recipe comes from - Stock first, then components - Kits that must never be broken up - How it reads on the order - How it reads at the pack station - When components run short - See also ## Where the recipe comes from The bill of materials — the recipe — lives in Assemblified. Floormode asks it what a given product is made of and remembers the answer, so allocating an order never waits on a round trip to another app. If the recipe is not yet known, the order is not guessed at: Floormode requests it, allocates what it can from finished stock in the meantime, and expands properly once the answer arrives. ## Stock first, then components The rule is finished kits first, components for the remainder. It is worth spelling out because it is the behaviour merchants most often expect and most rarely get: Note An order for 5 of a kit, with 2 finished ones on the shelf, produces: - 2 allocated from the finished kits, picked as the kit itself, and - 3 worth of components, picked as parts. One order line, two kinds of picking, no human decision required. This matters because the alternative policies are both wrong some of the time. Always picking finished kits leaves orders short while the parts sit on a shelf. Always picking components breaks up finished goods you deliberately assembled ahead of demand. Doing stock first and expanding only the shortfall is the only version that never destroys work you have already done. Two details follow from it: - A kit is only as buildable as its scarcest part. If the recipe needs three of a component and you have enough for two kits’ worth, two is what expands — the rest goes short. - Components are never stolen from a bundle’s own bin neighbours. Reserved units are tracked down to the bin and batch, so expanding one order’s kit cannot quietly consume stock another order already had claimed. ## Kits that must never be broken up Some products are only ever sold pre-assembled — a gift set that must arrive boxed, something that needs a qualified person to build it. Assemblified marks those, and Floormode honours it. For those, the finished-stock pass still runs, but the shortfall does not expand. Whatever cannot be filled from finished kits goes to backorder with a “Waiting for production” hold instead, because the honest answer is “someone has to build one”, not “send the parts”. ## How it reads on the order Expansion is visible, not silent. On the order’s fulfilment view: - Component reservations appear indented under the line they came from, marked as a component of the ordered bundle — so the parts never look like things the customer ordered separately. - The line carries a summary badge counting what was assembled rather than picked whole — for the example above, “3 built from components”. - Parts of a recipe that are not stocked items — instructions, a licence, anything that exists on the recipe but never in a bin — are shown as not stocked and allocate nothing. They appear so the recipe reads completely, not because anyone must fetch them. ## How it reads at the pack station The packer sees the parent — the thing the customer bought — with its components listed beneath and a per-bundle quantity, plus a note explaining why the parts are there: This bundle was picked as its parts — there was no finished one on the shelf. That sentence exists because without it the pack station looks like a picking error. The packer needs to know the parts are the product, and how many of each go into one. ## When components run short If a component cannot be found in the quantity needed, the shortfall behaves like any other shortage: the units become a backorder and the order takes a “Waiting for production” hold. The picked components stay reserved — they are not released back to general stock, because they are already spoken for. The order’s progress stepper shows the Waiting stage, which is the correct signal: the warehouse is not behind, the build is. ## See also - [Assemblified] (/integrations/assemblified/) — where the recipes and work orders live. - [Production pick] (/features/floor/production-pick/) — picking components for a build, which is a different job from this one. - [Holds] (/features/orders/holds/) — the “Waiting for production” reason. - [Backorders & oversell] (/features/inventory/backorders-and-oversell/) — what a shortfall becomes. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/integrations/health-panel/ # Integration health Connection status, message counts, receiving ownership and the warning that says nobody is writing Shopify inventory. Floormode’s 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 → Apps & API, on the Activity tab beside the connection switches’ Apps tab. ## On this page - Why this screen exists - Connection status - What each connection has done - Receiving ownership - Nobody is writing Shopify inventory - Who updates Shopify - What to do when something is waiting - See also ## 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: 1. The switch is off and nobody remembers turning it off. 2. They stopped talking to us — or, which looks identical and has the opposite fix, they are talking and we keep refusing them. 3. We stopped talking to them — messages are piling up unsent. 4. Nobody is writing Shopify inventory — the silent one. Note The panel makes one promise explicitly, because a health screen that flatters itself is worthless: Nothing here is ever deleted to make a number look better — a message that was never delivered stays counted. ## 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] (/integrations/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] (/integrations/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. Caution The switch refuses while a receiving warehouse is not live, so seeing this alert means the gap appeared afterwards — a warehouse linked later, or its Shopify updates switched off by hand. Nothing else in the app will tell you: receiving keeps working perfectly and Shopify’s number quietly stops moving. 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: 1. Rate limited — do nothing. It is a pause, not a failure, and it does not consume a delivery attempt. 2. 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. 3. Failed — the other app rejected the message or the attempt errored. Check that the sibling is installed with an active plan. 4. 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. 5. Never delivered — permanent. The sibling’s records are behind by that many messages and will not catch up on their own. ## See also - [Parked and held] (/integrations/parked-and-held/) — the failure states in detail. - [Who updates Shopify] (/integrations/who-writes-shopify/) — the rules behind the table. - [Activation] (/integrations/activation/) — connecting, and verifying it worked. - [Warehouses] (/features/settings/warehouses/) — where a warehouse goes live. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/integrations/shopify-updates/ # Updates from Shopify How orders, products and inventory changes reach Floormode, what the status line means, and how to recover a lost update. Shopify tells Floormode about new orders, edited products and changed quantities. Each update is applied in order; the Shopify updates tab on Settings → Apps & API shows what arrived and what is still being processed. ## On this page - How Shopify updates reach Floormode - Reading the status line - When an update fails - Recovering a lost update - What recovery cannot restore - When Shopify slows Floormode down - See also ## How Shopify updates reach Floormode Shopify sends an update for every change; Floormode also imports pages of data when you install and when it re-checks. An update counts as done once it is processed, not when it arrives. ## Reading the status line Inbound from Shopify shows how many updates are queued, processing, applied in the last 24 hours, retrying, and failed. Zero failed is the normal state. ## When an update fails A failed update is listed with its reason. Fix the cause (usually a Shopify location that is not linked to a warehouse), then click Retry. Nothing is applied twice. ## Recovering a lost update When the original update is no longer available, Floormode can fetch the current record from Shopify and process that instead. Enter the Shopify ID from the failed update and a short reference; the request is kept in the audit trail under your name. ## What recovery cannot restore Recovery uses Shopify’s current state. A hold that was placed and lifted in between, or a quantity that changed again since, is not replayed as history. ## When Shopify slows Floormode down Shopify limits how fast an app may call it. Floormode waits and retries by itself; the panel shows when the next attempt is due. Nothing is lost. ## See also - [Integration health] (/integrations/health-panel/) - [Activation] (/integrations/activation/) Last updated: 23 October 2026 --- Source: https://docs.floormode.app/integrations/webhooks/ # Webhooks Tell your own systems what happens on the floor, as it happens — signed messages to your endpoints, with every delivery shown. Webhooks send a signed message to an address of yours each time something you picked happens on the floor. Your ERP, a chat channel or a tool like Zapier, Make or n8n can react at once, without asking Floormode every few minutes. The messages follow [Standard Webhooks] (https://www.standardwebhooks.com/). You will find them in Settings → Apps & API → Webhooks. Like the [REST API] (/rest-api/overview/), they work on every plan. ## On this page - Add an endpoint - Events - Only some warehouses or stores - The signing secret - Deliveries - Not delivered - Switched off - Replay, Send again, Send a sample - Event feeds - See also ## Add an endpoint Click Add endpoint, paste an https:// address, pick the events and click Add endpoint. An account can have up to 10 endpoints. Floormode only sends to public addresses. An address on a private or local network is refused, before it is saved and again before every message. Your system should respond 2xx within 10 seconds. ## Events The events come in seven groups: Orders, Fulfilment, Shipping, Inventory, Returns, Warehouse and Alerts. Open a group to tick single events, or use Select group. Each event says in one sentence when it is sent, and search finds an event by its name or its API name (order.allocated). The [event catalogue] (/integrations/events/) shows what each one carries, with an example. Lot expired is sent once a lot, when it has expired at every warehouse that holds it. A lot with nothing on hand or in transit is not announced: the notice is for stock you can act on. Stock booked into a lot after its notice (a return, a transfer arriving) is not announced again. Messages about the same order arrive in the order they happened, and each carries a sequence number. Every message has an id (webhook-id): if one ever arrives twice, skip it. A message carries ids, short ids, order, warehouse and store names, statuses and counts. It never carries a customer’s name, email, address or phone, nor a note someone typed. Your system reads the details through the REST API with its own access. ## Only some warehouses or stores Open Only some warehouses or stores to receive events from some warehouses or stores only. Leave a field empty to receive from all of them. An event that has no warehouse (or no store) is never sent while that filter is set, and the event list greys it out and says why. ## The signing secret When you add an endpoint, Floormode shows its signing secret (whsec_…) once. Copy it now: Floormode keeps only a locked copy and cannot show it again. Your system checks the webhook-signature header with it, so it knows each message came from Floormode. Make a new secret (in the endpoint’s ⋯ menu) shows a new one, once. For 24 hours every message carries both signatures, so your system can switch over at its own pace. Making yet another new secret inside those 24 hours stops the oldest one at once. ## Deliveries An endpoint’s page lists every event it was sent, newest first: - Pending: waiting to be sent, or held while the endpoint is off. - Retrying: your system did not accept it; Floormode tries again, on growing intervals, for up to 3 days. - Delivered: your system responded 2xx. - Failed: refused, or no try left. Send again sends it once more. Search by event or by an order’s name. Floormode keeps events for 5 days. A page reads back a stretch of that time; Load older reads further back, and the line under the list says how far it has checked. ## Not delivered When events could not be delivered before Floormode stopped keeping them, the list shows one Not delivered row with the period. Nothing is lost on your side silently: read what changed in that period through the [REST API] (/rest-api/overview/). ## Switched off You can switch an endpoint off in its ⋯ menu. Floormode switches it off by itself, and says why, when: - 20 deliveries in a row were refused; - the address responded 410 Gone; - no delivery succeeded for 3 days; - the address points to a private or local network. Switch on… asks where to start: Send what is still kept sends every event since it stopped (oldest first, then new ones), From now sends only new events. When the address itself was the fault, Edit address… comes first. ## Replay, Send again, Send a sample - Replay from… sends every kept event since a time again, oldest first. - Send again sends one failed delivery again. - Send a sample sends a test message, marked "test": true. Replayed and resent events keep their ids (webhook-id), so your system can recognise an event it already has. Note Messages to your endpoints never hold up Floormode’s own updates to Shopify. A slow endpoint only waits its turn. ## Event feeds An event feed lets an agent or a script read events through the API at its own pace, with no address of its own for Floormode to call. Choose a feed over an endpoint when nothing of yours is always online, or when an [AI agent] (/rest-api/connect-an-ai-agent/) does the reading. Open the Event feeds tab and click Add feed. Give it a name, pick the events and, if you want, Only some warehouses or stores, then choose where it starts: - From now reads only events from this moment on. - From the oldest kept event starts with what Floormode still keeps. Floormode keeps 5 days of the events an endpoint or feed receives. Events from before any endpoint or feed listened, or from while this feed had expired, were never kept, so no feed can read them. Feed added shows the Feed URL. Copy it into your agent or script. It is an address, not a password: every read needs the reader’s own API login, and each reader sees only the events its own role and warehouses may see. A reader without access to orders reads no order events from the same feed. A feed expires 30 days after its last read. The list shows Last read for each feed, and a badge when a feed ends within 7 days or has expired. Renew gives it 30 more days from now. Copy feed URL and Delete feed are in the row’s ⋯ menu. An account can have up to 10 feeds. ## See also - [REST API] (/rest-api/overview/) — read the details a message points to. - [Integration health] (/integrations/health-panel/) — the other apps Floormode talks to. - [Shopify Flow] (/integrations/flow/) — the same events as triggers for your Flow workflows. Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/events/ # Event catalogue Every event Floormode can send to a webhook, what it carries and an example. Every event a [webhook] (/integrations/webhooks/) can subscribe to. Each message is a Standard Webhooks envelope (id, type, version, timestamp, sequence, subject, scope, test, truncated) around the event’s data below. A message never carries a customer’s name, e-mail, address or phone. An [event feed] (/integrations/webhooks/#event-feeds) gives each reader only the events its own role may read: each event below names the permission its readers need. ## Orders ### Order put on hold hold.applied · version 1 · filters: store Floormode put an order on hold in Shopify. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string holdId string hold string reason string ```json { "holdId": "holdIntents_01JCV4W6Y8A0C2E4G6J8L0N2Q4", "hold": "#HOLD-00007", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "reason": "fraud_risk" } ``` ### Order address changed order.address_changed · version 1 · filters: store An order’s delivery address changed. The address itself is never sent. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string addressVersion number ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "addressVersion": 3 } ``` ### Order created order.created · version 1 · filters: store A new order arrived from the store. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string channel string lines number units number ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "channel": "shopify", "lines": 3, "units": 5 } ``` ### Order allocated order.allocated · version 1 · filters: warehouse, store Stock was reserved for an order at a warehouse. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string lines number units number complete boolean ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "lines": 3, "units": 5, "complete": true } ``` ### Order completed order.completed · version 1 · filters: store Every item of an order was fulfilled. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string parcels number warehouses array warehousesCapped boolean ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "parcels": 2, "warehouses": [ "Main warehouse" ], "warehousesCapped": false } ``` ### Rule matched automation.rule_matched · version 1 · filters: store One of your order rules with “Send an event” matched an order. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string ruleId string rule string trigger string occurrenceKey string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "ruleId": "automationRules_01JCV9C3D4E5F6G7H8J9K0LMNP", "rule": "Rush the VIP orders", "trigger": "order_created", "occurrenceKey": "" } ``` ### Order late order.deadline_missed · version 1 · filters: warehouse, store An order passed its fulfil-by time, or the end of its packing day, and has not shipped. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string dueKind string dueAtMs number minutesLate number warehouseId null or string warehouse null or string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "dueKind": "fulfill_by", "dueAtMs": 1762610531483, "minutesLate": 42, "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse" } ``` ### Order assigned to a warehouse order.warehouse_assigned · version 1 · filters: warehouse, store Shopify assigned an order’s fulfillment order to one of your warehouses, or moved it to another. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string fulfillmentOrderId string previousWarehouseId null or string previousWarehouse null or string split boolean ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "fulfillmentOrderId": "fulfillmentOrders_01JCV6R2S4T6V8X0Z2B4D6F8H0", "previousWarehouseId": null, "previousWarehouse": null, "split": false } ``` ### Order deallocated order.deallocated · version 1 · filters: warehouse, store Stock reserved for an order at a warehouse was given back. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string reason string units number ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "reason": "cancelled", "units": 5 } ``` ### Order backordered order.backordered · version 1 · filters: warehouse, store An order is waiting for stock: it reserves itself when the stock arrives. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string fulfillmentOrderId string shortLines number shortUnits number episodeBegan boolean edgeId string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "fulfillmentOrderId": "fulfillmentOrders_01JCV6R2S4T6V8X0Z2B4D6F8H0", "shortLines": 1, "shortUnits": 2, "episodeBegan": true, "edgeId": "01JCV6Q8ZK3M2W1Y4T5R7N9PQB" } ``` ### Backorder resolved order.backorder_resolved · version 1 · filters: warehouse, store A backordered order is fully reserved again: stock arrived, or the order or its warehouse changed. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string fulfillmentOrderId string units number edgeId string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "fulfillmentOrderId": "fulfillmentOrders_01JCV6R2S4T6V8X0Z2B4D6F8H0", "units": 2, "edgeId": "01JCV7A1B2C3D4E5F6G7H8J9KM" } ``` ### Order cancelled order.cancelled · version 1 · filters: store An order was cancelled and Floormode closed its work. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string workStage string releasedAllocations number ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "workStage": "picking", "releasedAllocations": 1 } ``` ### Order hold released hold.released · version 1 · filters: store A hold Floormode put on an order in Shopify was released. It can arrive without hold.applied (a hold withdrawn before Shopify confirmed it). Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string holdId string hold string reason string ```json { "holdId": "holdIntents_01JCV4W6Y8A0C2E4G6J8L0N2Q4", "hold": "#HOLD-00007", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "reason": "fraud_risk" } ``` ## Fulfilment ### Packing finished pack_job.completed · version 1 · filters: warehouse, store A packer finished a parcel. Feed readers need: See orders and customers or See pick, pack and shipping work or Pack, buy and print labels at the pack station. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string packJobId string packJob string trackingNumber null or string packingDetails array packingDetails[].label string packingDetails[].value boolean or number or string or null packingDetails[].unit null or string packingDetails[].line null or string packingDetails[].key string packingDetailsCapped boolean ```json { "packJobId": "packJobs_01JCV6ZT4N8R2K5M7Q9S1V3X5Z", "packJob": "#PK-00117", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "trackingNumber": "1Z999AA10123456784", "packingDetails": [ { "key": "custom.seal", "label": "Seal", "value": "S-48213", "unit": null, "line": null }, { "key": "custom.weight", "label": "Weight", "value": 1.2, "unit": "lb", "line": null } ], "packingDetailsCapped": false } ``` ### Order fulfilled order.fulfilled · version 1 · filters: warehouse, store Shopify confirmed the fulfillment Floormode created for one parcel. Feed readers need: See orders and customers. Field Type orderId string order null or string shopifyOrderId null or string warehouseId string warehouse null or string packJobId string packJob string trackingNumber null or string shopifyFulfillmentId null or string ```json { "packJobId": "packJobs_01JCV6ZT4N8R2K5M7Q9S1V3X5Z", "packJob": "#PK-00117", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "trackingNumber": "1Z999AA10123456784", "shopifyFulfillmentId": "4412345678901" } ``` ### Wave released wave.released · version 1 · filters: warehouse A wave was released to the floor. Feed readers need: See pick, pack and shipping work or Plan picking: batches and waves. Field Type warehouseId string warehouse null or string waveId string wave string tasks number fulfillmentOrders number ```json { "waveId": "waves_01JCVE5F6G7H8J9K0L1M2N3P4R", "wave": "W-0193", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "tasks": 6, "fulfillmentOrders": 120 } ``` ### Wave closed wave.closed · version 1 · filters: warehouse A wave was closed: its open tasks went to the floor’s continuous work. Feed readers need: See pick, pack and shipping work or Plan picking: batches and waves. Field Type warehouseId string warehouse null or string waveId string wave string tasksReleased number ```json { "waveId": "waves_01JCVE5F6G7H8J9K0L1M2N3P4R", "wave": "W-0193", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "tasksReleased": 2 } ``` ### Pick list started pick_batch.started · version 1 · filters: warehouse A picker booked the first pick of a pick list. Feed readers need: See pick, pack and shipping work or Pick (orders and production). Field Type warehouseId string warehouse null or string pickBatchId string pickBatch string method string orders number lines number units number ```json { "pickBatchId": "pickBatches_01JCVF6G7H8J9K0L1M2N3P4Q5S", "pickBatch": "#PB-00042", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "method": "batch", "orders": 20, "lines": 64, "units": 120 } ``` ### Pick list completed pick_batch.completed · version 1 · filters: warehouse Every line of a pick list was picked or reported short. Feed readers need: See pick, pack and shipping work or Pick (orders and production). Field Type warehouseId string warehouse null or string pickBatchId string pickBatch string method string orders number lines number units number linesPicked number linesShort number unitsPicked number durationMs null or number ```json { "pickBatchId": "pickBatches_01JCVF6G7H8J9K0L1M2N3P4Q5S", "pickBatch": "#PB-00042", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "method": "batch", "orders": 20, "lines": 64, "units": 120, "linesPicked": 62, "linesShort": 2, "unitsPicked": 118, "durationMs": 1260000 } ``` ### Pick short pick_line.shorted · version 1 · filters: warehouse, store A picker found fewer units in a location than the pick asked for. Feed readers need: See pick, pack and shipping work or Pick (orders and production). Field Type warehouseId string warehouse null or string variantId string sku null or string item string pickLineId string pickBatchId string pickBatch string orderId null or string order null or string shopifyOrderId null or string bin null or string expected number picked number ```json { "pickLineId": "pickLines_01JCV8B2C3D4E5F6G7H8J9K0LM", "pickBatchId": "pickBatches_01JCVF6G7H8J9K0L1M2N3P4Q5S", "pickBatch": "#PB-00042", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "bin": "A-01-02", "expected": 3, "picked": 1 } ``` ## Shipping ### Label bought shipment.label_purchased · version 1 · filters: warehouse, store A shipping label was bought for a parcel. Feed readers need: Shipping labels, manifests, pickups, freight or Pack, buy and print labels at the pack station. Field Type orderId string order null or string shopifyOrderId null or string shipmentId string shipment string warehouseId null or string warehouse null or string carrier string service string trackingNumber null or string cost null or number currency null or string ```json { "shipmentId": "shipments_01JCV7A1B2C3D4E5F6G7H8J9KM", "shipment": "#SHP-00042", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "carrier": "ups", "service": "UPS Ground", "trackingNumber": "1Z999AA10123456784", "cost": 7.45, "currency": "USD" } ``` ### Parcel delivered shipment.delivered · version 1 · filters: warehouse, store The carrier delivered a parcel. Feed readers need: Shipping labels, manifests, pickups, freight or Pack, buy and print labels at the pack station. Field Type orderId string order null or string shopifyOrderId null or string shipmentId string shipment string warehouseId null or string warehouse null or string carrier string service string trackingNumber null or string ```json { "shipmentId": "shipments_01JCV7A1B2C3D4E5F6G7H8J9KM", "shipment": "#SHP-00042", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "carrier": "ups", "service": "UPS Ground", "trackingNumber": "1Z999AA10123456784" } ``` ### Delivery problem shipment.exception_reported · version 1 · filters: warehouse, store The carrier reported a delivery problem: an exception, a failed attempt or a return to sender. Feed readers need: Shipping labels, manifests, pickups, freight or Pack, buy and print labels at the pack station. Field Type orderId string order null or string shopifyOrderId null or string shipmentId string shipment string warehouseId null or string warehouse null or string carrier string service string trackingNumber null or string trackingStatus null or string exceptionAtMs number ```json { "shipmentId": "shipments_01JCV7A1B2C3D4E5F6G7H8J9KM", "shipment": "#SHP-00042", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "carrier": "ups", "service": "UPS Ground", "trackingNumber": "1Z999AA10123456784", "trackingStatus": "failed_attempt", "exceptionAtMs": 1762610531483 } ``` ### Label voided shipment.label_voided · version 1 · filters: warehouse, store A bought shipping label was voided. Feed readers need: Shipping labels, manifests, pickups, freight or Pack, buy and print labels at the pack station. Field Type orderId string order null or string shopifyOrderId null or string shipmentId string shipment string warehouseId null or string warehouse null or string carrier string service string trackingNumber null or string refund string ```json { "shipmentId": "shipments_01JCV7A1B2C3D4E5F6G7H8J9KM", "shipment": "#SHP-00042", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "carrier": "ups", "service": "UPS Ground", "trackingNumber": "1Z999AA10123456784", "refund": "pending" } ``` ### Parcel in transit shipment.transit_started · version 1 · filters: warehouse, store The carrier scanned a parcel for the first time. Feed readers need: Shipping labels, manifests, pickups, freight or Pack, buy and print labels at the pack station. Field Type orderId string order null or string shopifyOrderId null or string shipmentId string shipment string warehouseId null or string warehouse null or string carrier string service string trackingNumber null or string firstScanAt number ```json { "shipmentId": "shipments_01JCV7A1B2C3D4E5F6G7H8J9KM", "shipment": "#SHP-00042", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "carrier": "ups", "service": "UPS Ground", "trackingNumber": "1Z999AA10123456784", "firstScanAt": 1762610531483 } ``` ### Manifest closed manifest.closed · version 1 · filters: warehouse A carrier manifest was closed: its parcels are announced to the carrier. Feed readers need: Shipping labels, manifests, pickups, freight. Field Type warehouseId string warehouse null or string manifestId string manifest string carrier string date string parcels number ```json { "manifestId": "manifests_01JCV9D4E5F6G7H8J9K0L1M2NP", "manifest": "#MAN-00014", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "carrier": "ups", "date": "2026-11-08", "parcels": 214 } ``` ## Inventory ### Count found a difference count.variance_found · version 1 · filters: warehouse A stock count found quantities that differ from what was expected. Feed readers need: See stock, products and movements or Plan counts and accept count differences or Count. Field Type warehouseId string warehouse null or string countTaskId string count string countedLines number varianceLines number varianceUnits number ```json { "countTaskId": "countTasks_01JCV5K7M9P1R3T5V7X9Z1B3D5", "count": "#CT-00031", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "countedLines": 40, "varianceLines": 2, "varianceUnits": -3 } ``` ### Lot blocked lot.blocked · version 1 · filters: none A lot was blocked: nothing from it is picked or sold. Feed readers need: See stock, products and movements. Field Type lotId string lot string variantId string sku null or string item string reason null or string units number openOrders number openOrdersCapped boolean ```json { "lotId": "lots_01JCT1C2D3E4F5G6H7J8K9M0NP", "lot": "L-2026-114", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "units": 24, "openOrders": 3, "openOrdersCapped": false, "reason": "quality_hold" } ``` ### Lot unblocked lot.unblocked · version 1 · filters: none A blocked lot was released: it is picked and sold again. Feed readers need: See stock, products and movements. Field Type lotId string lot string variantId string sku null or string item string reason null or string units number openOrders number openOrdersCapped boolean ```json { "lotId": "lots_01JCT1C2D3E4F5G6H7J8K9M0NP", "lot": "L-2026-114", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "units": 24, "openOrders": 3, "openOrdersCapped": false, "reason": "quality_hold" } ``` ### Count approved count.approved · version 1 · filters: warehouse A stock count was approved and its differences booked. Feed readers need: See stock, products and movements or Plan counts and accept count differences or Count. Field Type warehouseId string warehouse null or string countTaskId string count string stocktakeId null or string countedLines number varianceLines number varianceUnits number ```json { "countTaskId": "countTasks_01JCV5K7M9P1R3T5V7X9Z1B3D5", "count": "#CT-00031", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "stocktakeId": null, "countedLines": 40, "varianceLines": 3, "varianceUnits": -4 } ``` ### Stocktake signed off stocktake.signed_off · version 1 · filters: warehouse A stocktake was signed off: every sheet is approved or cancelled. Feed readers need: See stock, products and movements or Plan counts and accept count differences. Field Type warehouseId string warehouse null or string stocktakeId string stocktake string countDate string sheets number binsCounted number binsNotCounted number differenceLines number differenceUnits number ```json { "stocktakeId": "stocktakes_01JCVA1B2C3D4E5F6G7H8J9K0M", "stocktake": "#ST-00002", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "countDate": "2026-11-08", "sheets": 24, "binsCounted": 850, "binsNotCounted": 0, "differenceLines": 9, "differenceUnits": -12 } ``` ### Stock adjusted stock.adjusted · version 1 · filters: warehouse An item’s stock in a location was adjusted, by a person or by Floormode; the reason says which. Feed readers need: See stock, products and movements. Field Type warehouseId string warehouse null or string variantId string sku null or string item string movementId string bin string delta number reason null or string onHandAfter number ```json { "movementId": "stockMovements_01JCVB2C3D4E5F6G7H8J9K0L1N", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "bin": "A-01-02", "delta": -2, "reason": "damaged", "onHandAfter": 38 } ``` ### On hand changed stock.on_hand_changed · version 1 · filters: warehouse An item’s units on hand in a warehouse changed: received, shipped, adjusted, counted, returned or transferred. Feed readers need: See stock, products and movements. Field Type warehouseId string warehouse null or string variantId string sku null or string item string movementId string delta number onHandAfter number cause string ```json { "movementId": "stockMovements_01JCVB2C3D4E5F6G7H8J9K0L1N", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "delta": -1, "onHandAfter": 37, "cause": "ship" } ``` ### Adjustment awaiting approval adjustment_request.submitted · version 1 · filters: warehouse An adjustment above your approval limit waits for a second person. Feed readers need: See stock, products and movements. Field Type warehouseId string warehouse null or string variantId string sku null or string item string adjustmentRequestId string adjustmentRequest string bin string delta number reason string value number currency null or string ```json { "adjustmentRequestId": "adjustmentRequests_01JCVC3D4E5F6G7H8J9K0L1M2P", "adjustmentRequest": "ADJ-00012", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "bin": "A-01-02", "delta": -10, "reason": "damaged", "value": 84.5, "currency": "USD" } ``` ### Lot expired lot.expired · version 1 · filters: none A lot passed its expiry date at every warehouse that holds it. Floormode no longer allocates or sells it. Feed readers need: See stock, products and movements. Field Type variantId string sku null or string item string lotId string lot string expiresOn string units number ```json { "lotId": "lots_01JCT1C2D3E4F5G6H7J8K9M0NP", "lot": "L-2026-114", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "expiresOn": "2026-11-08", "units": 24 } ``` ## Returns ### Return requested return.requested · version 1 · filters: store A customer asked for a return, in the returns portal or in Shopify. Feed readers need: See returns. Field Type orderId string order null or string shopifyOrderId null or string source string returnRequestId null or string returnRequest null or string shopifyReturnId null or string return null or string units number unitsComplete boolean reasons array value null or number currency null or string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "source": "portal", "returnRequestId": "returnRequests_01JCV3R5T7V9X1Z3B5D7F9H1K3", "returnRequest": "#RMA-00091", "shopifyReturnId": null, "return": null, "units": 1, "unitsComplete": true, "reasons": [ "wrong_item" ], "value": 19.99, "currency": "USD" } ``` ### Return received return.received · version 1 · filters: warehouse, store The warehouse received a customer return. Feed readers need: See returns. Field Type returnReceiptId string receipt string orderId null or string order null or string shopifyOrderId null or string returnId null or string warehouseId string warehouse null or string units number reasons array conditions array ```json { "returnReceiptId": "returnReceipts_01JCV2P4R6T8V0X2Z4B6D8F0H2", "receipt": "#RET-00012", "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "returnId": "1234567890", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "units": 1, "reasons": [ "wrong_item" ], "conditions": [ "sellable" ] } ``` ### Return approved return.approved · version 1 · filters: store A return request was approved. Feed readers need: See returns. Field Type orderId string order null or string shopifyOrderId null or string returnRequestId string returnRequest string resolution string units number currency string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "returnRequestId": "returnRequests_01JCV3R5T7V9X1Z3B5D7F9H1K3", "returnRequest": "#RMA-00091", "resolution": "refund", "units": 1, "currency": "USD" } ``` ### Return denied return.denied · version 1 · filters: store A return request was denied. Feed readers need: See returns. Field Type orderId string order null or string shopifyOrderId null or string returnRequestId string returnRequest string resolution string units number currency string ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "returnRequestId": "returnRequests_01JCV3R5T7V9X1Z3B5D7F9H1K3", "returnRequest": "#RMA-00091", "resolution": "refund", "units": 1, "currency": "USD" } ``` ### Return refunded return.refunded · version 1 · filters: store A return was refunded. Feed readers need: See returns. Field Type orderId string order null or string shopifyOrderId null or string returnRequestId string returnRequest string resolution string units number currency string amount null or number ```json { "orderId": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "order": "#1001", "shopifyOrderId": "5512345678901", "returnRequestId": "returnRequests_01JCV3R5T7V9X1Z3B5D7F9H1K3", "returnRequest": "#RMA-00091", "resolution": "refund", "units": 1, "currency": "USD", "amount": 19.99 } ``` ## Warehouse ### Receipt completed receipt.completed · version 1 · filters: warehouse A receipt was completed: its goods are booked into stock. Feed readers need: Purchase orders and receipts (desk) or Receive and put away deliveries. Field Type warehouseId string warehouse null or string receiptId string receipt string source string lines number units number discrepancyLines number ```json { "receiptId": "receipts_01JCVG7H8J9K0L1M2N3P4Q5R6T", "receipt": "#RC-00007", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "source": "manual", "lines": 12, "units": 480, "discrepancyLines": 1 } ``` ### Receipt cancelled receipt.cancelled · version 1 · filters: warehouse A receipt was cancelled before its goods were booked. Feed readers need: Purchase orders and receipts (desk) or Receive and put away deliveries. Field Type warehouseId string warehouse null or string receiptId string receipt string source string ```json { "receiptId": "receipts_01JCVG7H8J9K0L1M2N3P4Q5R6T", "receipt": "#RC-00007", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "source": "manual" } ``` ### Location blocked bin.blocked · version 1 · filters: warehouse A location was blocked: nothing in it is planned or picked. Feed readers need: See stock, products and movements or Warehouses, layout, bins, zones, stations or Plan counts and accept count differences. Field Type warehouseId string warehouse null or string binId string bin string cause null or string units number items number ```json { "binId": "bins_01JCVH8J9K0L1M2N3P4Q5R6S7V", "bin": "A-01-02", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "units": 40, "items": 2, "cause": "damaged" } ``` ### Location unblocked bin.unblocked · version 1 · filters: warehouse A blocked location was released: it is planned and picked from again. Feed readers need: See stock, products and movements or Warehouses, layout, bins, zones, stations or Plan counts and accept count differences. Field Type warehouseId string warehouse null or string binId string bin string cause null or string units number items number ```json { "binId": "bins_01JCVH8J9K0L1M2N3P4Q5R6S7V", "bin": "A-01-02", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "units": 40, "items": 2, "cause": "damaged" } ``` ### Transfer started transfer.started · version 1 · filters: warehouse A transfer’s goods left the source warehouse. Feed readers need: See stock, products and movements or Transfers between warehouses or Use Floor Mode, clock in and out, own shifts. Field Type transferId string transfer string fromWarehouseId string fromWarehouse null or string toWarehouseId null or string toWarehouse null or string lines number units number ```json { "transferId": "warehouseTransfers_01JCVJ9K0L1M2N3P4Q5R6S7T8W", "transfer": "#TR-00012", "fromWarehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "fromWarehouse": "Main warehouse", "toWarehouseId": "warehouses_01JA3C4D5E6F7G8H9J0K1M2N3P", "toWarehouse": "Second warehouse", "lines": 8, "units": 96 } ``` ### Transfer completed transfer.completed · version 1 · filters: warehouse A transfer was completed at its destination. Feed readers need: See stock, products and movements or Transfers between warehouses or Use Floor Mode, clock in and out, own shifts. Field Type transferId string transfer string fromWarehouseId string fromWarehouse null or string toWarehouseId null or string toWarehouse null or string lines number units number ```json { "transferId": "warehouseTransfers_01JCVJ9K0L1M2N3P4Q5R6S7T8W", "transfer": "#TR-00012", "fromWarehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "fromWarehouse": "Main warehouse", "toWarehouseId": "warehouses_01JA3C4D5E6F7G8H9J0K1M2N3P", "toWarehouse": "Second warehouse", "lines": 8, "units": 96 } ``` ### Refill completed replenishment.completed · version 1 · filters: warehouse A refill moved stock from reserve to a pick location. Feed readers need: See pick, pack and shipping work. Field Type warehouseId string warehouse null or string variantId string sku null or string item string taskId string fromBin null or string toBin null or string units number toBins array (optional) toBins[].binId string toBins[].bin null or string toBins[].units number toBinsCapped boolean (optional) ```json { "taskId": "tasks_01JCVD4E5F6G7H8J9K0L1M2N3Q", "warehouseId": "warehouses_01JA2B3C4D5E6F7G8H9J0K1M2N", "warehouse": "Main warehouse", "variantId": "variants_01JB8X9Y0Z1A2B3C4D5E6F7G8H", "sku": "MUG-BLU-12", "item": "Travel mug · Blue", "fromBin": "R-03-01", "toBin": "A-01-02", "units": 24, "toBins": [ { "binId": "bins_01JCVD7Q8R9S0T1V2W3X4Y5Z6A", "bin": "A-01-02", "units": 24 } ], "toBinsCapped": false } ``` ## Alerts ### Alert raised alert.raised · version 1 · filters: store Floormode raised an alert: a late order, a shortage, a failing connection. Feed readers need: Analytics, forecasts and stock value. Field Type alertId string alertType string ref null or object ref.type string ref.id string ref.name string orderId null or string (optional) severity string ```json { "alertId": "48213", "alertType": "sla_breach", "severity": "warning", "ref": { "type": "order", "id": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "name": "#1001" }, "orderId": null } ``` ### Alert resolved alert.resolved · version 1 · filters: store An open alert ended: its cause is gone, or a newer alert replaced it. Feed readers need: Analytics, forecasts and stock value. Field Type alertId string alertType string ref null or object ref.type string ref.id string ref.name string orderId null or string (optional) cause string ```json { "alertId": "48213", "alertType": "sla_breach", "ref": { "type": "order", "id": "orders_01JCV6Q8ZK3M2W1Y4T5R7N9PQA", "name": "#1001" }, "orderId": null, "cause": "order_fulfilled" } ``` --- Source: https://docs.floormode.app/integrations/flow/ # Shopify Flow Start your Shopify Flow workflows when Floormode buys a label, packs or fulfills a parcel, a parcel is delivered or runs into a problem, a count finds a difference, an order goes on hold or a return is received. Shopify Flow runs your own automations: tag an order, send an email, post to a chat. Floormode adds its own triggers to Flow, so a workflow can start when something happens on your floor. Flow is free in Shopify and Floormode’s triggers work on every Floormode plan. ## On this page - The Floormode triggers - Build a workflow - What a trigger carries - When a workflow did not run - A workflow can rarely run twice - See also ## The Floormode triggers In the Flow editor, choose Select a trigger and search for Floormode: Trigger Starts when Shipping label purchased Floormode bought a shipping label for an order Parcel packed A packer finished a parcel and handed it on for fulfillment Parcel fulfilled Shopify confirmed the fulfillment Floormode created for a parcel. Once per parcel Shipment delivered The carrier delivered a parcel. Once per shipment Shipment delivery exception The carrier reported a problem, such as a failed delivery attempt or a return to sender. Again if a new problem follows after the parcel was moving again Count variance found A submitted count does not match the stock on record Order put on hold A hold became active on an order Return received The goods of a customer return arrived and were checked at your warehouse. Once per receipt; goods that came back without an order start no workflow Only orders from your Shopify store start a trigger that names an order. ## Build a workflow 1. Open Shopify Flow and create a workflow. 2. Select a Floormode trigger. 3. Add a condition if you want one, then an action, for example Add order tags or Send internal email. 4. Turn the workflow on. Floormode starts the trigger from then on. Things that happened before you turned the workflow on do not start it later. If Flow says it could not turn the workflow on, wait a moment and turn it on again. ## What a trigger carries Every trigger except Count variance found carries the order, so a workflow can read and change it with Flow’s order actions. Each also carries a few fields you can use in conditions and messages: Trigger Fields Shipping label purchased Order name, Shipment, Carrier, Service, Tracking number Parcel packed, Parcel fulfilled Order name, Parcel, Warehouse, Tracking number Shipment delivered, Shipment delivery exception Order name, Shipment, Carrier, Tracking number Count variance found Count, Warehouse, Counted lines, Variance lines, Variance units Order put on hold Order name, Hold, Hold reason Return received Order name, Receipt, Warehouse, Units A field Floormode does not know yet, such as a tracking number on a parcel without one, is empty. A trigger never carries a customer’s name, email, address or phone; a workflow reads those from the order. ## When a workflow did not run Floormode sends each trigger in the background, behind its updates to Shopify, so a workflow can start a little after the event. When Shopify is busy, Floormode waits and tries again by itself. A trigger that could not be sent is listed in Settings → Apps & API → Shopify updates, under Failed updates to Shopify, with the trigger and its order. Fix the cause, then click Send again. ## A workflow can rarely run twice Shopify Flow cannot tell whether it already received a trigger. Floormode therefore sends a trigger again when it is not sure the first try arrived, for example when Shopify did not answer in time. In that rare case a workflow runs twice. Flow’s run history shows both runs. Caution In the failed updates list, a trigger marked Shopify may already have started these workflows may have run already. Sending it again runs its workflows a second time. Use conditions in your workflow (for example, skip an order that already has your tag) where a second run would matter. ## See also - [Webhooks] (/integrations/webhooks/): the same events, sent to an address of yours. - [Updates from Shopify] (/integrations/shopify-updates/): the other direction. Last updated: 8 October 2026 --- Source: https://docs.floormode.app/integrations/parked-and-held/ # Parked and held What happens to messages when a connected app is not answering, and why a switched-off app gets nothing. Two apps talking to each other will eventually fail to. When the app on the other side of a Floormode connection is not answering, the message waits somewhere you can see it. When you switch a connection off, nothing is sent to that app at all. ## On this page - Queued, then confirmed - The states a message can be in - Held while the other app is not answering - Switching a connection off - The one case that is genuinely lost - Refusals, and why they are different - Duplicates - Messages the other app sends while it is off here - See also ## Queued, then confirmed Nothing is sent and forgotten. Every message to a connected app is written down first, sent second, and marked delivered only when the other app confirms it applied it. That ordering is the whole reliability story. A message can never be lost because the app crashed after sending it — the record was made before the attempt, so a message that never got a [confirmation] (/reference/glossary/#delivery-confirmation) is still sitting there waiting to be retried. ## The states a message can be in The [health panel] (/integrations/health-panel/) counts each connection’s outbound messages by state: State What it means Queued Written down, waiting its turn Sending An attempt is in flight right now Delivered The other app confirmed it applied it Held [Parked] (/reference/glossary/#parked-message) — the other app is not answering, or Shopify is rate limiting us. Releases itself Rate limited The other app said “not now” — a pause, not a failure Failed The other app rejected it, or the attempt errored Never delivered Held so long it was given up on. Permanent Rate limited deserves a note. When a connected app asks Floormode to slow down, that is a normal, healthy response to a busy moment — not an error. A pause does not count against a message’s retry attempts, so being throttled can never, by itself, cause a message to fail. The panel says as much: nothing is lost — a rate limit does not spend a delivery attempt. ## Held while the other app is not answering If the other app is down or cannot be reached, messages for it are held, in order, and the panel shows them as Held with the age of the oldest one. Floormode retries one message every so often and sends the whole backlog the moment one gets through, in the order it was produced. A Shopify rate limit is handled the same way. Neither needs you. ## Switching a connection off A switched-off app gets nothing: Floormode writes no message for it and keeps no backlog. Your own records stay here (the count, the receipt, the alert on your alert list). Switching it on starts fresh. From then on new work is sent; nothing from the time it was off is sent later, and anything still held from before is marked as not sent. Two exceptions always go out: the notice that the connection was switched off, and the return of the other app’s local stock. ## The one case that is genuinely lost There is a limit, and it is documented rather than hidden. While an app is not answering, its connection can hold up to 500 messages. Past that, the oldest are given up on. They move to Never delivered, a visible state, never a silent deletion, and the panel says so: 68 messages never delivered. The other app is missing that data. Caution Never delivered is permanent. 500 messages cover an outage of a working day. A non-zero count means the other app’s records are behind and will not catch up on their own. ## Refusals, and why they are different A refusal is not a failure of delivery — the message arrived and was understood, and Floormode declined to apply it. Refusals come back with a reason, and they are counted separately as Rejected. The refusals a merchant actually meets: Refusal Why Fix The location is not one Floormode receives for Nothing here should book goods in at a location you have not handed over Map or delegate the location, then have the sibling resend The document has already been updated to a newer version An out-of-order revision would undo a newer plan Nothing — it is correct, and nothing changed The document has no physical lines There is nothing to receive Nothing — informational The document has grown too large to revise safely Rewriting it would re-announce units already in a bin Split the document in the sibling The distinction the panel is careful about: “they have stopped talking to us” and “they are talking and we keep refusing them” look identical from the warehouse floor and have opposite fixes. That is why Received, Rejected and Last message are three separate numbers rather than one health light. ## Duplicates Every message carries an identifier that is unique to the thing it describes. If the same message arrives twice — a retry after a confirmation went missing, a sibling replaying its own queue — the second copy is recognised and ignored, not applied again. Reports that travel the other way are built the same way round: they carry running totals rather than increments. A second delivery against a purchase order reports the full quantity received so far, not “two more”. A total that arrives twice is harmless; an increment that arrives twice is a wrong number nobody can trace. ## Messages the other app sends while it is off here A switched-off connection holds both directions. Documents the other app sends (a purchase order, a transfer) are not applied while the switch is off. The other app keeps them and sends them again; they land once you switch the connection on. Its exits always land: it leaving, it releasing receiving back to itself, and its confirmations of work Floormode already did. See [Activation] (/integrations/activation/) for what else switching off does and does not undo. ## See also - [Integration health] (/integrations/health-panel/) — where all of these numbers live. - [Activation] (/integrations/activation/) — connecting and disconnecting. - [Needs attention] (/features/home/needs-attention/) — where failed actions surface on Home. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/integrations/activation/ # Activation Connecting a sibling app, what switches itself on, how to verify it works, and what does and does not stop when you disconnect. Not available yet The connections to Logistified, Assemblified and Alertified open after Floormode’s approval. Until then each switch under Settings → Apps & API → Apps reads Not available yet and cannot be turned on. This page describes how connecting works once it opens; Floormode runs on its own until then. Connecting takes one switch. Knowing what that switch does — and what it deliberately does not undo — takes this page. ## On this page - What you need first - Connecting - What switches itself on - Verifying it works - Handing over receiving per location - Disconnecting - Handing local stock back - See also ## What you need first Two things, and the connection needs both: 1. 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. 2. 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. 3. 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] (/features/settings/warehouses/) before you connect, not after. ## Connecting 1. Open Settings → Apps & API and find the Apps card. 2. 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. 3. 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. 4. 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] (/integrations/three-apps/#the-connection-states) 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] (/features/inventory/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] (/integrations/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. Caution Switching off is not a pause button. What happens here while a connection is off (counts, receipts, alerts) is not sent later. Your records here are complete; the other app’s are not. Switch off when you mean to stop the connection. 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] (/features/inventory/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] (/reference/glossary/#handback), 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 → Apps & API 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. Caution The switch stays on until the other app confirms. This looks like the click did not work, and it is deliberate: the quantities travel over the same connection, so switching it off at that moment would hold up the very message the handover is waiting for. The switch is frozen and labelled “Handing back” until the confirmation lands, and then it turns itself off. The sequence, once started: 1. 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”. 2. 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. 3. 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”. 4. 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. Note A handback states every item in one message, and there is a ceiling on how many that can be — 500 per app. Beyond it the handback refuses to start rather than send half the warehouse: the switch stays on, nothing is frozen, and the refusal says so. If you are near that size, raise it before you plan a disconnection. ## See also - [Integration health] (/integrations/health-panel/) — how to tell a working connection from a dead one. - [Parked and held] (/integrations/parked-and-held/) — what happens to messages while a connection is off. - [Standalone] (/integrations/standalone/) — what connecting later does and does not backfill. - [Local items] (/features/inventory/local-items/) — the goods a handback returns, and the worklist that starts them off. - [Warehouses] (/features/settings/warehouses/) — the Shopify location mapping you need first. Last updated: 27 October 2026 --- Source: https://docs.floormode.app/integrations/standalone/ # Floormode on its own What works without the sibling apps, which surfaces stay empty, and what connecting later does and does not backfill. 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] (/integrations/who-writes-shopify/) 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 receipt] (/reference/glossary/#expected-receipt) 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] (/features/floor/production-pick/) job only ever appears when a [work order] (/reference/glossary/#work-order) 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] (/integrations/bundles-and-kits/). - 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] (/features/inventory/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] (/features/insights/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] (/features/orders/holds/) 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] (/features/inventory/local-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] (/integrations/who-writes-shopify/), and check the [health panel] (/integrations/health-panel/) once you have connected. ## See also - [Activation] (/integrations/activation/) — the connect flow itself. - [What changes when connected] (/integrations/what-changes-when-connected/) — screen by screen. - [Replenishment] (/features/insights/replenishment/) — the CSV path that works with any supplier. Last updated: 25 October 2026 --- Source: https://docs.floormode.app/integrations/carriers/aramex/ # Aramex Floormode books Aramex labels on your own Aramex account: within your country (Overnight Parcel) and abroad (Priority, Value and Economy Parcel Express), with cash on delivery. Floormode books Aramex labels on your own Aramex account: within your country (Overnight Parcel) and abroad (Priority, Value and Economy Parcel Express), with cash on delivery. ## On this page - What you enter - What Floormode books - Test labels first - See also ## What you enter Field Where you find it User name the e-mail address of your aramex.com login with API access Password that login’s password Account number your Aramex shipping account number (digits), on your contract or in your aramex.com account Account PIN the PIN Aramex issued with the account (digits) Account entity the three-letter code of your Aramex office, for example JNB (Johannesburg) or CPT Account country your account’s two-letter country, for example ZA 1. Ask your Aramex account manager to enable the Shipping Services API for your login, and for the account number, PIN and entity if you do not have them. 2. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → Aramex and enter the six fields. ## What Floormode books - One parcel per label, prepaid by your Aramex account, to the customer’s door. - At home: Aramex Overnight, priced by Aramex for your account. - Abroad: Priority, Value and Economy Parcel Express, each priced by Aramex; a route Aramex does not serve with a product is not offered. The parcel carries its customs lines (HS code, value and origin of each product), and duties are paid by the recipient. Aramex builds the commercial invoice from those lines: print it from Aramex’s portal and put it with the parcel. - Cash on delivery: the amount and currency you enter for the order. Floormode shows the amount Aramex confirmed it will collect. Aramex pays the cash out to your account under your account’s cash-on-delivery agreement. - An insured value, when you enter one. - The label as a PDF, and tracking from Aramex’s updates. Not offered: cancelling a label in Floormode (Aramex’s API has no cancellation; ask Aramex), pickups, returns and dangerous goods. ## Test labels first Aramex runs a test system (ws.dev.aramex.net) with a public test account in its Shipping Services API manual; ask Aramex for test credentials of your own, connect them as a test account, and test labels cost nothing. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/aramex-au/ # Aramex Australia Floormode books Aramex Australia (formerly Fastway) parcels on your own Aramex account, through the myFastway API. Floormode books Aramex Australia (formerly Fastway) parcels on your own Aramex account, through the myFastway API. ## On this page - What you enter - What Floormode books - See also ## What you enter Field Where you find it Client ID and secret myfastway.com.au → Administration → API Keys → Create Key ## What Floormode books - One parcel per label within Australia, with its weight and its three sides, at your account’s price. - Parcels leave from your account’s own pickup address in myFastway (the API takes no other sender). - A 4 × 6 inch PDF label. - Deleting a consignment before its first scan. Aramex has no test system for the API: every consignment Floormode books is a real one. A consignment made by mistake can be deleted before its first scan. Not offered: satchels, returns, delivery options such as Authority to Leave, parcels abroad and dangerous goods. Pickups: Book pickups in your Aramex account; a regular pickup is a contract option. See [Carrier pickups] (/features/settings/labels-printers-and-scanners/#carrier-pickups). ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/internetmarke/ # Deutsche Post Internetmarke Floormode buys Deutsche Post postage (Internetmarke) for letters, large letters and the Warensendung, and prints it as a PDF. Floormode buys Deutsche Post postage (Internetmarke) for letters, large letters and the Warensendung, and prints it as a PDF. Every stamp is paid from your Portokasse, Deutsche Post’s prepaid postage account, at the moment Floormode buys it. Internetmarke is for letters posted in Germany. It is offered only for shipments from a warehouse in Germany: elsewhere it is never the default and cannot be chosen. ## On this page - What you enter - What a stamp costs - Which product a letter gets - What has no tracking - Printing - Cancelling a stamp - Not possible - If a purchase is unclear - See also ## What you enter Field Where you find it API key and API secret developer.dhl.com → My Apps → your app, once Deutsche Post has given it Internetmarke access and the app subscribes to the Products API Portokasse e-mail and password the login you use for the Portokasse on deutschepost.de (the password has at most 22 characters) Print format number the Internetmarke print format you print on. If the number is wrong, connecting lists the formats your Portokasse offers What is printed an address label with the postage, or the postage only, for envelopes that already carry the address 1. Register a Portokasse on deutschepost.de if you have none. It is free. 2. In the DHL developer portal (developer.dhl.com), create an app and request access to the Deutsche Post INTERNETMARKE API for it. Add the Products API (Post & Parcel Germany) to the same app too: Floormode reads the prices there. The app shows the API key and secret. 3. Sign in to the Portokasse and approve the app once, under Meine Daten → Geschäftsanwendungen. Until you do, Deutsche Post refuses the login. 4. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → Deutsche Post Internetmarke and enter the values. Connecting checks the login, the print format and the price list. It never buys a stamp. If the app lacks the Products API, connecting says so. ## What a stamp costs Floormode asks Deutsche Post’s price list for each product’s current price and shows it as the rate. Buying the label pays exactly that amount from the Portokasse. If the Portokasse holds less, Floormode refuses before anything is bought: top it up on deutschepost.de first. Floormode never tops it up. Prices from Deutsche Post’s list (PPL 6.0, valid from 1 July 2026), within Germany: Product Up to Price Standardbrief 20 g, 23.5 × 12.5 × 0.5 cm €0.95 Kompaktbrief 50 g, 23.5 × 12.5 × 1 cm €1.10 Großbrief 500 g, 35.3 × 25 × 2 cm €1.80 Maxibrief 1,000 g, 35.3 × 25 × 5 cm €2.90 Maxibrief up to 2,000 g 60 × 30 × 15 cm €5.10 Warensendung (goods only) 1,000 g, 35.3 × 25 × 5 cm €2.70 + Einschreiben Einwurf + €2.35 + Einschreiben + €2.65 The rate always shows the price Deutsche Post names on the day. ## Which product a letter gets - Add the envelopes you use to your boxes (Settings → Shipping & carriers → Carriers & printing), with their size and empty weight, and record each item’s length, width and thickness. Floormode chooses the envelope the item fits, and offers every product that takes that envelope by size and weight, envelope included. - Without a chosen envelope, Internetmarke offers no rate: the shipment says so, and you ship that order with another carrier or add the envelope. - Asking for a signature books Einschreiben. - Within Germany only. Deutsche Post’s international letters carry documents, not goods, so Floormode does not offer them for an order. Send goods abroad with another carrier (DHL’s Warenpost International takes small items). - The Warensendung is for goods only, sealed, with no written message, and takes up to four working days. ## What has no tracking - A plain letter has no tracking. Its stamp has no number Floormode could pass on, so the order is fulfilled without a tracking link. - Einschreiben Einwurf and Einschreiben have a tracking number. Floormode passes it to Shopify with a link to Deutsche Post’s tracking page. - Floormode cannot refresh the status of a letter: Deutsche Post offers no tracking API for Internetmarke. ## Printing Deutsche Post renders the stamp as a PDF in the print format you chose: plain A4 sheets, label sheets, a label printer roll, or straight onto an envelope. Floormode prints that PDF as it comes, through your label printer (PrintNode), like any other label. ## Cancelling a stamp Voiding the label asks Deutsche Post to refund the unused stamp. Deutsche Post books the refund to the Portokasse later, once it is sure the stamp was never posted. ## Not possible - No test mode. Deutsche Post has no test host; every stamp Floormode buys is real and paid. There is no sample label for this carrier. - Postcodes. Internetmarke prints five-digit postcodes only, as Germany’s are; an address with another postcode is refused before anything is bought. - International letters (documents only), postcards, Dialogpost, press products, the Rückschein and cash on delivery. ## If a purchase is unclear If Deutsche Post does not answer a purchase, Floormode looks it up by its order number once. If that does not tell, the shipment asks you to check that order in the Portokasse before buying again. Floormode never buys the same stamp twice on its own. When you record a stamp you found there, enter its franking id (and the tracking number of an Einschreiben): a plain letter has no tracking number. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/dhl-paket-de/ # DHL Paket DE Floormode books DHL Paket labels on your own DHL business contract (Post & DHL Geschäftskundenportal) from a warehouse in Germany: DHL Paket and DHL Kleinpaket within Germany, to the customer's… Floormode books DHL Paket labels on your own DHL business contract (Post & DHL Geschäftskundenportal) from a warehouse in Germany: DHL Paket and DHL Kleinpaket within Germany, to the customer’s door, a Packstation or a Postfiliale, and, with your international billing numbers, DHL Paket International and Warenpost International abroad. ## On this page - What you enter - DHL Kleinpaket - Packstation and Postfiliale - What Floormode refuses, and why - The point search - When DHL’s answer is unclear - Prices and cancelling - See also ## What you enter Field Where you find it Shipping API key and secret developer.dhl.com → My Apps → your app with the Parcel DE Shipping API GKP system username and password Geschäftskundenportal → a system user allowed to ship (live accounts only) DHL Paket billing number Geschäftskundenportal → contract data: 14 characters, procedure 01 DHL Kleinpaket billing number (optional) the same contract data: 14 characters, procedure 62 (digits 11–12) Contract estimates what each product costs you; DHL’s API returns no price Open Settings → Shipping & carriers → Carriers & printing → Connect carrier → DHL Paket DE. To update an account, use Update credentials and re-enter your keys with the new numbers. ## DHL Kleinpaket DHL’s small parcel within Germany. With its billing number and estimate on the connection, Floormode offers it beside DHL Paket when the parcel: - weighs at most 1 kg, - has a known box between 10 × 7 × 0.1 cm and 35.3 × 25 × 8 cm (DHL’s own limits), and - goes to a door or a Packstation (DHL takes no Kleinpaket to a Postfiliale). A box Floormode does not know the size of always goes as DHL Paket, so Ship all never buys a Kleinpaket on weight alone. A Kleinpaket can enclose a DHL return label like a DHL Paket. ## Packstation and Postfiliale Customers address a DHL station the way DHL asks: - Packstation: “Packstation 598” in an address line and their DHL Postnummer (6–10 digits) in the other line, or after their name, or after the station (“Packstation 598 1234567890”). - Postfiliale or DHL Paketshop: “Postfiliale 518” (or “Filiale 518”, “DHL Paketshop 518”), with the Postnummer in the same places. Floormode reads this from the order’s shipping address, so the shipment shows the station as its point (“Packstation 598 · 10115 Berlin”) and the label goes to it. You can also pick a station on the shipment: Find points searches DHL’s Packstations and post offices near the address. The Postnummer always comes from the order; the label never shows it in the name. A Postfiliale without a Postnummer. DHL then needs the customer’s e-mail to tell them the parcel is waiting. Floormode passes it only when you turn on Pass the customer’s e-mail to DHL Paket DE on the connection (Settings → Shipping & carriers → Carriers & printing); it is off until you do. With the switch off, such a label is refused with that sentence before anything is sent to DHL. Rating such a parcel shows your estimate with the note “DHL checks the Postfiliale delivery when the label is bought.” ## What Floormode refuses, and why Each before anything is sent to DHL: - A Packstation without a Postnummer. A Packstation opens only with the customer’s DHL account. Add the Postnummer to the shipping address’s other line. - Two different Postnummern in one shipping address: the refusal names where they are (for example “address line 2 and the name”); keep one. - Another carrier for a station order shipped from Germany. “This order goes to a DHL Packstation; ship it with DHL Paket.” Only DHL delivers to its stations; another carrier’s label comes back. Through Sendcloud, EasyPost or ShipEngine, only their DHL Paket services are offered for such an order. A store shipping from outside Germany is not refused by this rule. - A station abroad: DHL delivers to Packstations and post offices in Germany only. - A Packstation box over 75 × 60 × 40 cm: ship to the door or a Postfiliale. - A point picked without its kind (through the API): pick the DHL point again. ## The point search The desk’s Find points uses DHL’s Location Finder – Unified API. Add it to your DHL API app at developer.dhl.com (My Apps → your app → add the API; it is free and self-service). Until you do, the search answers “Add Location Finder – Unified to your DHL API app at developer.dhl.com.” Labels to a station the order names work without it. ## When DHL’s answer is unclear DHL sometimes answers a purchase with an error page or an error that still names a shipment number. Floormode then cannot tell whether a label exists, so it keeps the purchase open instead of freeing it for a second label: 1. The shipment gets a Label bought but not recorded exception naming DHL’s shipment number when DHL gave one. 2. Look the number (or the order) up in the Geschäftskundenportal. 3. Settle it on the shipment: record the label DHL made, or mark that no label exists. Only then can it be bought again. ## Prices and cancelling DHL’s API prices nothing: each rate shows your contract estimate, and DHL’s invoice decides. A label can be cancelled until DHL’s daily close-out. Pickups: Book the Abholauftrag in your DHL business customer portal; a regular pickup at an agreed location is a DHL contract option. See [Carrier pickups] (/features/settings/labels-printers-and-scanners/#carrier-pickups). ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/fastway-za/ # Fastway (South Africa) Floormode books Fastway labels on your own Fastway account in South Africa, to the customer's door. Floormode books Fastway labels on your own Fastway account in South Africa, to the customer’s door. Fastway’s Portal API runs on the ShipLogic platform, the same as The Courier Guy’s, so the two connect and work the same way, each with its own key. ## On this page - What you enter - What Floormode books - Tracking updates - Your first label - See also ## What you enter Field Where you find it API key portal.fastway.co.za → Settings → API Keys 1. Sign in to your Fastway portal (portal.fastway.co.za). A Fastway key works only for Fastway’s portal, not for another ShipLogic courier’s. 2. Open Settings → API Keys and create a key. 3. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → Fastway and enter the key. ## What Floormode books - One parcel per label within South Africa, from a South African address with its four-digit postcode. - To the door: the service levels your account has (for example Economy), priced in rand with VAT as Fastway quotes them. A declared value insures the parcel. - The waybill as a PDF. Fastway texts and e-mails the recipient, so the order needs the customer’s mobile number or e-mail. - Cancelling a label before the parcel is collected: Fastway reverses the charge. A collected parcel cannot be cancelled. - Tracking, from Fastway’s statuses. The tracking link on the order opens Fastway’s own tracking page (portal.fastway.co.za/track). Not offered: pickup points and lockers (Fastway’s API lists none), cash on delivery (Fastway’s API has none), returns, satchel rates, opt-in extras such as early-bird delivery, and international parcels. ## Tracking updates Refresh on a shipment reads the latest status from Fastway. For status changes that arrive on their own, each connected Fastway account has its own private tracking address: add it in your Fastway portal under Settings → Webhook subscriptions, for tracking events. To get it, open Settings → Shipping & carriers → Carriers & printing, find the account and press Copy address beside Tracking address (it needs Settings access). Treat the address like a password: anyone who has it can send status updates for this account. Fastway does not sign its updates, so the address is their only proof. Reconnecting the account keeps the same address. ## Your first label Fastway has no test system, so a Fastway account in Floormode is a live one: every label it books is real and charged. Book your first label for a parcel that really ships, or cancel it before Fastway collects the parcel, and Fastway reverses the charge. To try the whole flow first, use Floormode’s built-in test carrier. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/gls-de/ # GLS Floormode books GLS labels on your own GLS contract, in Germany, Austria, Belgium, France or Ireland. Floormode books GLS labels on your own GLS contract, in Germany, Austria, Belgium, France or Ireland. In each of these countries GLS uses the same booking system (ShipIT), so the connection asks the same things everywhere. ## On this page - What you enter - What Floormode books - ParcelShop and ParcelLocker delivery - When GLS’s answer is unclear - Test labels - See also ## What you enter Field Where you find it GLS country The country of your GLS contract. Parcels leave from there; for a second country, connect that country’s GLS account as well. API key and API secret GLS developer portal (dev-portal.gls-group.net) → My Apps: create an app with Authentication v2, ShipIT-Farm v1 and Track And Trace V1. GLS Contact ID From your GLS contract. Ask your GLS contact to link your app to it (in France: GLS France’s IT client support). Contract estimate per parcel (EUR) What you expect to pay per parcel. GLS’s API gives no prices, so Floormode shows this estimate. ## What Floormode books - One parcel per label, from a warehouse in your GLS country, within that country and to the EU (BusinessParcel and EuroBusinessParcel). - A PDF label. - Cancellation, until GLS has scanned the parcel. - Tracking, on GLS’s own tracking page and in Floormode. - ShopReturn labels, returning to a warehouse in your GLS country. GLS bills them only when the customer sends the parcel. - ParcelShop and ParcelLocker delivery (GLS ShopDeliveryService), see below. Not offered: parcels that need a customs declaration, other extra GLS services (FlexDelivery, Express), dangerous goods, and the GLS countries with their own systems (the Netherlands, Spain, Italy, Hungary, Romania, Slovakia, Czechia, Slovenia and Croatia). ## ParcelShop and ParcelLocker delivery A parcel goes to a GLS ParcelShop or ParcelLocker instead of the customer’s door when the order names the shop’s GLS ParcelShop ID (a checkout widget writes it into the order, for example as glsParcelShopId), or when you type the ID on the shipment. Orders that ship to a pickup point aren’t booked with GLS. When Shopify’s ship-to is the pickup point itself, Floormode can’t check the shop against GLS’s own list. Ship such an order with another carrier, or book it in GLS’s portal and type its tracking number when you fulfil. A ParcelShop ID on an order that ships to the customer’s home still books: GLS delivers to the shop and keeps the home address as the customer’s. - The ID. GLS writes it as GLS_DE-2760238818: the country, then the shop’s number. Floormode sends that form as it is. A bare number that starts with GLS’s country code (276 Germany, 040 Austria, 056 Belgium, 250 France, 208 Denmark, 616 Poland, 442 Luxembourg) gets its prefix. Any other ID is refused before GLS is asked. - Same country. GLS delivers only to a ParcelShop in the customer’s country. - No ParcelShop search. Type the ID under Pickup point on the shipment. You find it in GLS’s ParcelShop finder. GLS routes the parcel by that ID; if GLS can’t route to it, check the ID, or ship to the customer’s door. - The customer’s e-mail. GLS needs it to tell the customer that the parcel is waiting. Floormode passes it only when Pass the customer’s e-mail to GLS is on for the connection (Settings › Shipping & carriers). While it is off, a ParcelShop label is refused before any call. - Your contract must include GLS ShopDeliveryService. If it does not, GLS refuses the label and Floormode shows GLS’s words. - Weight and size. Floormode checks only the limits GLS publishes for delivery to a shop: from France 30 kg, 130 cm long and 170 cm length + width + height within France, 20 kg abroad; from Belgium 31.5 kg, 200 × 80 × 60 cm and a girth of 300 cm. For Germany, Austria and Ireland GLS publishes no such limit, so GLS decides when you buy the label. GLS’s International ShopDeliveryService reaches ParcelShops in Germany, Austria, Belgium, Croatia, Denmark, Spain, France, Finland, Hungary, Italy, Luxembourg, the Netherlands, Poland, Portugal, Czechia, Slovakia and Slovenia (GLS France, 2022). Which of them your contract reaches is GLS’s answer. ## When GLS’s answer is unclear GLS refuses a label it cannot make with a short, documented message, which Floormode shows. Any other answer (a blank page, an error page, a timeout) may still have created a parcel. Floormode then keeps the shipment as “purchasing” and opens an exception: check GLS’s portal for the parcel, then record its label or mark that none exists. ## Test labels GLS’s sandbox sends nothing to GLS’s network, so a sandbox label never ships. Connect with Sandbox on to try Floormode before your first real label. Pickups: Book pickups with GLS; a regular pickup is a GLS contract option. See [Carrier pickups] (/features/settings/labels-printers-and-scanners/#carrier-pickups). ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/inpost/ # InPost Floormode books InPost labels on your own InPost organisation in Poland: to a Paczkomat® parcel locker, or by courier to the door, with cash on delivery in złoty. Floormode books InPost labels on your own InPost organisation in Poland: to a Paczkomat® parcel locker, or by courier to the door, with cash on delivery in złoty. For InPost in the United Kingdom, connect InPost UK instead: it is a different InPost API with its own keys. ## On this page - What you enter - What Floormode books - Test labels first - See also ## What you enter Field Where you find it API token Parcel Manager (manager.paczkomaty.pl) → My account → API → ShipX API → Generate Organisation id the same page, beside the token (digits) 1. In Parcel Manager, fill in your company and invoice details under My account → Data; InPost generates API access only once both are complete. 2. Open the API tab and generate a token for the ShipX API. 3. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → InPost and enter the token and the organisation id. ## What Floormode books - One parcel per label within Poland. - Paczkomat® locker: the order’s locker (the one your customer chose at checkout, or one you pick from the nearest lockers). Floormode chooses the locker size (A, B or C) from the package’s sides, so pack into a saved package with its size. InPost texts and e-mails the pickup code, so the order needs the customer’s mobile number and e-mail. Floormode passes the e-mail only when you turn on Pass the customer’s e-mail to InPost Poland on the connection (Settings → Shipping & carriers → Carriers & printing); it is off until you do. - Courier: to the customer’s door, with the package’s sides and weight. - Sender: your warehouse, with the e-mail of your organisation’s contact person (Parcel Manager → My account → Data). With no contact e-mail, InPost prints your organisation’s own sender details instead. - Cash on delivery in PLN; a courier parcel with cash on delivery is insured for at least the amount collected, as InPost requires. - An A6 PDF label. InPost prices the label on your contract; Floormode shows the price InPost charged once the label is bought. - Cancelling a label InPost has not bought yet. A bought label stays in Parcel Manager. Not offered: returns, Allegro services and dispatch orders. ## Test labels first Connect a test organisation from InPost’s test Parcel Manager (sandbox-manager.paczkomaty.pl): top up its virtual funds in the Payments tab, and test labels cost nothing. InPost’s test system shows no tracking. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/packeta/ # Packeta Floormode books Packeta (Zásilkovna) labels on your own Packeta e-shop account: to a Packeta pickup point or a Z-BOX, with cash on delivery. Floormode books Packeta (Zásilkovna) labels on your own Packeta e-shop account: to a Packeta pickup point or a Z-BOX, with cash on delivery. ## On this page - What you enter - What Floormode books - Testing without a label - See also ## What you enter Field Where you find it API key client.packeta.com → Client support → API password and key (16 characters) API password the same page (32 characters) Sender label (optional) client.packeta.com → Senders; only if your account has more than one sender 1. Register an e-shop account at client.packeta.com and wait for Packeta to approve it for sending; Packeta checks new accounts before their first parcel. 2. Copy the API key and the API password from the client section. 3. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → Packeta and enter the values. ## What Floormode books - One parcel per label to a Packeta pickup point or Z-BOX in Czechia, Slovakia, Hungary, Romania or Poland, up to 15 kg: the order’s point (the one your customer chose at checkout, or one you pick from the nearest points). - Cash on delivery in the point’s currency, and the parcel’s value, which Packeta insures. - Packeta tells your customer the parcel has arrived, so the order needs their e-mail or phone number. - An A6 PDF label. - Cancelling a packet before it is handed over. Not offered: home delivery through Packeta’s partner carriers. ## Testing without a label Packeta has no test system, so every packet Floormode creates is a real one. Floormode refuses a packet it cannot describe (a missing point, phone or weight) before it calls Packeta, and Packeta’s own refusals are shown in its words; a packet you created by mistake can be cancelled until it is handed over. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/pargo/ # Pargo Floormode books Pargo orders on your own Pargo account in South Africa: to one of Pargo's pickup points (a shop near your customer), or to the customer's door. Floormode books Pargo orders on your own Pargo account in South Africa: to one of Pargo’s pickup points (a shop near your customer), or to the customer’s door. ## On this page - What you enter - What Floormode books - Tracking updates - Test labels first - See also ## What you enter Field Where you find it API username the e-mail address Pargo set up for API access (Pargo issues it on request) API password the password Pargo issued with it Warehouse code (optional) the code of the warehouse location Pargo stored for your account; empty = your default location 1. Ask Pargo (pargo.co.za, or your account manager) for API credentials. Pargo issues staging credentials for testing and production credentials for live orders. 2. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → Pargo and enter the username and the password. 3. If Pargo stores more than one warehouse location for you, enter the code of the one this Floormode warehouse ships from. ## What Floormode books - One parcel per label within South Africa, from the warehouse location Pargo holds for your account. - To a Pargo point: the point your customer chose at checkout (Pargo’s map widget names it, for example pup1234), or one you pick from the nearest points. Points at capacity are not offered. - To the door: the customer’s address, with the parcel’s weight and sides. - Prices in rand, when Pargo has turned on its quotation service for your account (ask Pargo); without it the label is booked at your contract price. - The order label as a PDF. If Pargo has not made it yet, Floormode keeps the order and says the label is missing; print it from Pargo’s portal. - Tracking, from Pargo’s order events. Not offered: cash on delivery (Pargo collects cash only in Egypt), an insured value, returns, and cancelling an order (ask Pargo support). Pargo issues one sign-in token at a time for your username: if Floormode reports that Pargo still holds a valid token, try again within the hour. ## Tracking updates Refresh on a shipment reads the latest status from Pargo. For status changes that arrive on their own, each connected Pargo account has its own private tracking address: send it to Pargo support, who register it for your account. To get it, open Settings → Shipping & carriers → Carriers & printing, find the account and press Copy address beside Tracking address (it needs Settings access). Treat the address like a password: anyone who has it can send status updates for this account. Pargo does not sign its updates, so the address is their only proof. Reconnecting the account keeps the same address. ## Test labels first Connect the staging credentials Pargo gave you as a test account: staging orders are never delivered and cost nothing. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/postnl/ # PostNL Floormode books PostNL labels on your own PostNL business account: to the door or to a PostNL point, within the Netherlands. Floormode books PostNL labels on your own PostNL business account: to the door or to a PostNL point, within the Netherlands. ## On this page - What you enter - What Floormode books - Test labels first - See also ## What you enter Field Where you find it API key MijnPostNL Zakelijk → API keys (or ask your PostNL account manager) Customer code your PostNL contract, four letters (e.g. ABCD) Customer number your PostNL contract, up to eight digits 1. Request an API key at developer.postnl.nl → Request API key, with your customer number; PostNL sends a test key and a live key. 2. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → PostNL and enter the values. ## What Floormode books - One parcel per label within the Netherlands, up to 23 kg. - Standard parcel to the customer’s door. - Pick up at a PostNL point: the order’s point (the one your customer chose at checkout, or one you pick from the nearest points); PostNL e-mails your customer when it is ready, so the order needs their e-mail. Floormode passes it only when you turn on Pass the customer’s e-mail to PostNL on the connection (Settings → Shipping & carriers → Carriers & printing); it is off until you do. - A PDF label, pre-announced to PostNL when it is made. Not offered: returns, cash on delivery, Belgium and other countries. PostNL’s newest shipment and return interfaces are open only to selected customers so far; Floormode moves to them when PostNL opens them. ## Test labels first Connect your test key to use PostNL’s test system: test labels are never delivered and cost nothing. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/purolator/ # Purolator Floormode buys Purolator labels on your own Purolator account. Floormode buys Purolator labels on your own Purolator account. ## On this page - What you enter - What Floormode books - Test labels first - See also ## What you enter Field Where you find it Key and key password E-Ship Web Services registration (eship.purolator.com); Purolator e-mails the development key Account number Your Purolator billing account number Activation key (user token) Only for a Platform key: the activation key Purolator gives you with it (below). Leave it empty for your own account’s key 1. Register for E-Ship Web Services at eship.purolator.com. Purolator e-mails a development key at once. 2. Ask Purolator to activate your production key; it stays inactive until Purolator has reviewed your account. 3. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → Purolator and enter the values. ### A Platform key and its activation key Purolator issues some web-services keys as a Platform key. A Platform key works only together with its activation key, which Purolator gives you with the Platform key; ask your Purolator representative if you do not have it. Enter it as Activation key (user token); Floormode stores it encrypted and sends it with every call. Without it, Purolator refuses a Platform key, and Floormode says so and points you to this field. A key you registered for your own account has no activation key: leave the field empty. ## What Floormode books - One parcel per label within Canada: Purolator Ground, Express, Express 10:30 AM and Express 9 AM. - A 4 × 6 inch thermal PDF label. The street must start with its civic number (for example 1234 Main Street, or 5-1234 Main Street with a unit). - Voiding a shipment on the day you created it. Not offered: shipments to the US and abroad, returns, options and pickups. ## Test labels first A test account uses Purolator’s development system with your development key; its labels cannot be shipped. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/royal-mail/ # Royal Mail and Parcelforce Floormode books Royal Mail labels on your own Royal Mail account. Floormode books Royal Mail labels on your own Royal Mail account. Connect it one of two ways: choose the connection first, then fill in its fields. ## On this page - What you enter - What Floormode books - Parcelforce - Return labels (Tracked Returns) - See also ## What you enter Click & Drop (most shops): Field Where you find it API key Click & Drop → Settings → Integrations → Add a new integration → Click & Drop API Royal Mail Shipping API (Online Business Account customers who send 100+ items a day): Field Where you find it Client ID and secret Pro Shipping → API Credentials. The secret is shown once. Shipping account ID Pro Shipping → Shipping Accounts (the account holding your OBA number and posting location) Shipping location ID Pro Shipping → Shipping Locations. Needed for the day’s manifest. For both: an estimate in pounds for each service you use. Royal Mail’s API gives no prices, so Floormode shows your estimate and offers only the services you priced. Your Royal Mail invoice decides the price. Optional: the client ID and secret of Royal Mail’s Tracking API, if you want Floormode to refresh tracking. ## What Floormode books - One item per label, sent from Great Britain. - Letters, large letters and parcels: Royal Mail 24 and 48, 1st and 2nd Class, Tracked 24 and 48, Special Delivery Guaranteed by 1pm, International Standard and International Tracked. Parcelforce: see below. - Signed For when an order needs a signature (24, 48, 1st and 2nd Class). Special Delivery is always signed. - Parcels abroad with their customs form (CN22 / CN23), duties paid by you (DDP) or the customer, and your IOSS number for EU orders. - The day’s manifest (close-out). Good to know: - Click & Drop returns the label only to OBA accounts. Otherwise Floormode creates the order, and you print its label in Click & Drop. - Royal Mail manifests by account, not by parcel: the day’s manifest takes every label of the account (or its shipping location) not yet manifested, also ones made outside Floormode. A Click & Drop account with several carriers (Royal Mail and Parcelforce) is manifested in Click & Drop: Royal Mail refuses one manifest for both. - Click & Drop can’t cancel a label through the API. Delete the order in Click & Drop and don’t post the label. The Shipping API cancels a label until it is manifested. ## Parcelforce Parcelforce Worldwide is part of Royal Mail. Its own expressLink connection closed at the end of 2025: a Parcelforce contract now sits on your Royal Mail Online Business Account, and you book it through the same two connections. - Click & Drop: express24 and express48 within the UK. - Shipping API: globalexpress, globalpriority Europe and globalpriority Rest of World abroad, each with its customs form or commercial invoice. Floormode offers globalpriority Europe for the European countries of Royal Mail’s rate card and Rest of World for the rest. Neither globalexpress nor globalpriority Rest of World goes to the United States. - Up to 30 kg a parcel, one parcel a label, at most 1.5 m long (and abroad 3 m in length and girth). The customer pays duties and taxes (DDU). A parcel that asks for duties you pay, an IOSS number or a signature is not offered Parcelforce. - Enter an estimate for each Parcelforce service you use, as for Royal Mail’s. Not offered for Parcelforce: the UK services through the Shipping API (express10, expressAM, express24, express48 and express48large: Royal Mail has not published their API codes), europriority, irelandexpress and IOSS or duties you pay on globalpriority Europe (they need a commercial invoice uploaded before the manifest), signature, age checks, Saturday delivery and enhanced compensation. ## Return labels (Tracked Returns) - Opens once confirmed: Royal Mail return labels open once Floormode has confirmed Royal Mail’s Tracked Returns answers. Until then your shop sends return labels, and Floormode never asks Royal Mail for one. - Through the Shipping API v4 only: a Click & Drop account makes no return label. - Turn on Tracked Returns on your Royal Mail contract on the connection: Royal Mail makes return labels only for Online Business Accounts with Tracked Returns 24 or 48 on the contract. - Royal Mail Tracked Returns 48 by default, or 24, from a customer in Great Britain (not Jersey, Guernsey or the Isle of Man) to your return warehouse. - A PDF label, a QR code your customer shows at a Post Office or Royal Mail Customer Service Point (they print the label there), or both. Royal Mail receives your customer’s name and address only. - Charged when created: Floormode never makes a second label on its own. You can void a label until your next Royal Mail close-out. Not offered: dangerous goods, age checks, insurance (consequential loss). Pickups: Book collections in Click & Drop (up to 5 days ahead); daily collections are a Royal Mail contract option. See [Carrier pickups] (/features/settings/labels-printers-and-scanners/#carrier-pickups). ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/the-courier-guy/ # The Courier Guy Floormode books The Courier Guy labels on your own Courier Guy account in South Africa: to the customer's door, or to a Pudo locker, a Courier Guy counter or a partner pickup point. Floormode books The Courier Guy labels on your own Courier Guy account in South Africa: to the customer’s door, or to a Pudo locker, a Courier Guy counter or a partner pickup point. Fastway runs on the same platform (ShipLogic) and connects as its own carrier: see [Fastway] (/integrations/carriers/fastway-za/). ## On this page - What you enter - What Floormode books - Tracking updates - Test labels first - See also ## What you enter Field Where you find it API key portal.thecourierguy.co.za → Integrations → API Keys → Create 1. Sign in to your Courier Guy portal (portal.thecourierguy.co.za). Since May 2026 The Courier Guy’s keys work only for its own portal, not for another ShipLogic courier’s. 2. Open Integrations → API Keys and create a key. 3. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → The Courier Guy and enter the key. ## What Floormode books - One parcel per label within South Africa, from a South African address with its four-digit postcode. - To the door: the service levels your account has (for example Economy, Priority), priced in rand with VAT as The Courier Guy quotes them. A declared value insures the parcel. - To a locker or pickup point: the point your customer chose at checkout, or one you pick from the nearest points. The Courier Guy takes no declared value on a pickup-point parcel. - The waybill as a PDF. The Courier Guy texts and e-mails the recipient, so the order needs the customer’s mobile number or e-mail. - Cancelling a label before the parcel is collected: The Courier Guy reverses the charge. A collected parcel cannot be cancelled. - Tracking, from The Courier Guy’s statuses. Not offered: cash on delivery (The Courier Guy’s API has none), returns, opt-in extras such as early-bird delivery, and international parcels. ## Tracking updates Refresh on a shipment reads the latest status from The Courier Guy. For status changes that arrive on their own, each connected Courier Guy account has its own private tracking address: add it as a webhook in your Courier Guy portal. To get it, open Settings → Shipping & carriers → Carriers & printing, find the account and press Copy address beside Tracking address (it needs Settings access). Treat the address like a password: anyone who has it can send status updates for this account. The Courier Guy does not sign its updates, so the address is their only proof. Reconnecting the account keeps the same address. ## Test labels first Register a free sandbox account at tcg-sandbox.shiplogic.com/register (it needs a South African mobile number), create an API key under Integrations → API Keys, and connect it as a test account. Sandbox rates are demo prices, and the sandbox gives no international quotes. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/ups/ # UPS Floormode books UPS labels on your own UPS shipper account. Floormode books UPS labels on your own UPS shipper account. You connect it by signing in on UPS’s own page: Floormode never sees your UPS password or app secrets. ## On this page - Connect - What Floormode books - Return labels - See also ## Connect 1. Open Settings → Shipping & carriers → Carriers & printing → Connect carrier → UPS. 2. Enter your six-character UPS shipper account number. It must be linked to the UPS profile you sign in with. 3. Choose UPS Ground Saver only once UPS has enabled it on your account. 4. Connect with UPS opens UPS’s sign-in page; Floormode is connected when you come back. ## What Floormode books - One parcel per label within one country (no customs), with the parcel’s length, width and height. - UPS’s services for your account’s country, rated at your account’s prices. UPS Ground Saver (less than 1 lb, and 1 lb or greater) within the US, when it is on. - A PDF label, and the thermal label beside it. - Voiding an unused label, and tracking. ## Return labels Floormode makes UPS Print Return Labels for your returns, on the RMA, on the returns page and in the background label work. They are free until posted: UPS charges the return shipping “when the package is actually shipped”, and there is no per-label fee for a printed return label. - Services by the return address’s country: in the US UPS Ground (the default), 3 Day Select, 2nd Day Air and Next Day Air; in the UK and in Germany UPS Standard. UPS takes none of Next Day Air Saver, 2nd Day Air A.M. or Ground Saver for a return, so they are not offered. - Within one country. A return from abroad is outside UPS’s reach in Floormode: the customer sends that parcel themselves. - The return parcel size. UPS needs the parcel’s three sides. Enter your usual return box once in Settings → Returns → Return labels; the label dialog takes another size for one return. Without a size the returns page says you send the label. - The customer’s name and address go on the label. - A PDF the customer prints. A label whose PDF did not arrive shows Reprint, which takes the PDF from UPS again. An unused return label costs nothing and needs no void. ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/integrations/carriers/usps/ # USPS Floormode buys USPS labels on your own USPS business account and pays them from your Enterprise Payment Account (EPA), at your commercial prices. Floormode buys USPS labels on your own USPS business account and pays them from your Enterprise Payment Account (EPA), at your commercial prices. ## On this page - What you enter - What Floormode books - Return labels - Test labels first - See also ## What you enter Field Where you find it Consumer key and consumer secret developers.usps.com → Apps → your app CRID (Customer Registration ID) USPS Business Customer Gateway → your business profile MID (Mailer ID) Business Customer Gateway → Mailer ID; six or nine digits Payment account (EPA) Business Customer Gateway → Payment Account (Enterprise Payment Account number) 1. Sign in at developers.usps.com with your USPS business account and add an app; it shows the consumer key and secret. 2. Ask USPS to enable the Labels API for the app (USPS calls this the label access request). 3. In Floormode, open Settings → Shipping & carriers → Carriers & printing → Connect carrier → USPS and enter the values. ## What Floormode books - One parcel per label within the US: USPS Ground Advantage, Priority Mail and Priority Mail Express. - A 4 × 6 inch PDF label. USPS needs the parcel’s length, width and height, so pack into a saved package with its size. - The day’s SCAN form (PS Form 5630) when you close out: one scan at the Post Office accepts every label on it. - Cancelling an unused label. A label already on a SCAN form gets a refund request instead, which USPS decides. - Signature Confirmation or Adult Signature Required, and insurance in US dollars (up to $500, or above). Not offered: letters and flats, and international mail. ## Return labels Floormode makes USPS return labels for your returns, on the RMA, on the returns page and in the background label work. They are free until posted: USPS charges a return label only when it scans the parcel (USPS Returns). - Services: USPS Ground Advantage Return (the default), Priority Mail Return and Priority Mail Express Return. Pick another one on the label dialog, or as the default in Settings → Returns → Return labels. - A label, a QR code, or both. Besides the PDF, USPS makes a Label Broker QR code: the customer shows it at a participating Post Office and USPS prints the label there. With Prefer a QR code on, the returns page offers both and links USPS’s Post Office finder. USPS’s Label Broker terms are between you and USPS and apply when you use the QR code. - Within the US only. A return from a US territory (Puerto Rico, Guam, the US Virgin Islands, American Samoa, the Northern Mariana Islands) or from a military or diplomatic address (APO, FPO, DPO) needs a customs form, which Floormode does not send: the customer sends that parcel themselves. - The customer’s name and address go on the label. Two steps before the first label: 1. Enrolled in USPS Returns. USPS makes return labels only for a Mailer ID enrolled in USPS Returns (USPS Ship). Once USPS has enabled it, turn on Enrolled in USPS Returns on the USPS connection. Until then the returns page says you send the label, and the label dialog names the step. 2. The return parcel size. USPS needs the parcel’s length, width and height. Enter your usual return box once in Settings → Returns → Return labels; the label dialog takes another size for one return. A parcel over 70 lb or 108 inches in length and girth is refused by name before anything is sent. Reprint. A label whose file did not arrive shows Reprint on the RMA. USPS reprints a return label as a PDF, at most three times and only on the day it was made (Central time); after that, create a new label. An unused return label costs nothing. ## Test labels first Connect a test account to use USPS’s test environment. USPS opens labels there only after you e-mail your consumer key to USPS (“Authorize CAT App”); test labels cost nothing and cannot be mailed. Pickups: Carrier Pickup is free: Floormode books, cancels and (with a plan) books it at close-out, for the next pickup day; live accounts once USPS has enabled pickups for Floormode. See [Carrier pickups] (/features/settings/labels-printers-and-scanners/#carrier-pickups). ## See also - [Carriers and packaging] (/features/settings/carriers-and-packaging/) - [Labels, printers and scanners] (/features/settings/labels-printers-and-scanners/) Last updated: 18 November 2026 --- Source: https://docs.floormode.app/rest-api/overview/ # REST API The external REST API — one authenticated door to every operation the app itself runs, with a live explorer and a downloadable OpenAPI 3.1 document. Floormode exposes its operations over HTTP at /api/v1. It is not a separate, thinner copy of the app — the API and the app run the same operations, so anything the interface can do, an integration can do, and neither can drift ahead of the other. ## On this page - What the API is - Authenticating - Requests - Responses and errors - Limits - Discovering the surface - Changes - See also ## What the API is Orders, allocations, picking, packing, shipments, receiving, returns, inventory movements, counts, replenishment, analytics — the same operations and the same vocabulary the app’s screens use. Each operation says whether it reads or writes. Two properties are worth knowing before you build anything against it: - Operation names are the API. orders_list is the operation id in REST, the method app.orders.list an agent calls over the MCP server (the first _ becomes a dot), and the handler name inside the app. One operation, three doors. - The tenant comes from your credentials, never from the URL. There is no shop or account parameter anywhere in the surface. A token identifies exactly one company’s Floormode, and a request can only ever reach that company’s data. Plan The API is open on every plan, also before a plan is chosen, so a system or an agent can set a store up from its first day. A few operations need a plan of their own (automation rules and reports need Elevate, cluster picking Enhanced); they are marked x-min-plan in the OpenAPI document, and a call on a lower plan is answered 403 with {"code": "plan_required", "requiredPlan": …}. ## Authenticating Every request carries a bearer token: ```http GET /api/v1/orders?status=unfulfilled HTTP/1.1 Host: your-app-domain Authorization: Bearer ``` Two token types are accepted. External integrations and agents use a WorkOS OAuth access token — discovery metadata is published at /.well-known/oauth-protected-resource (RFC 9728), so a standards-aware client can find the authorization server on its own. The embedded app uses its Shopify session token. A request with neither is answered 401. ## Requests GET and DELETE operations take their input from the query string; POST, PUT and PATCH take a JSON body. Query values are coerced against each parameter’s declared type before validation, so ?limit=25 reaches a numeric field as the number 25, and ?includeArchived=true reaches a boolean as true. Arrays accept a repeated parameter (?ids=a&ids=b) or a JSON array. One behaviour deserves its own paragraph, because it is deliberately stricter than most APIs: a query parameter the operation does not declare is refused, not ignored. ```json { "error": "Unknown query parameter(s): stat. orders_list accepts: status, cursor.", "code": "unknown_parameter", "unknown": ["stat"], "accepted": ["status", "cursor"] } ``` Silently dropping stat=open would return the whole unfiltered list with a 200 — a wrong answer wearing a correct answer’s clothes. The refusal names what the operation does accept, so one round trip fixes a typo. ## Responses and errors A success is always wrapped: ```json { "data": { "orders": [], "cursor": null } } ``` A failure is always {"error": ""}, plus a code whenever the refusal is one the app classified. Branch on code, never on the message text — messages are written for people and will be reworded. code HTTP Means invalid_input 400 A domain precondition the operation checked unknown_parameter 400 A query parameter the operation does not declare unauthorized 401 No usable identity plan_required 403 The account’s plan does not include this forbidden 403 Authenticated, but the wrong kind of caller for this operation not_found 404 The addressed record does not exist conflict 409 A state or uniqueness conflict — the write cannot be applied as asked payload_too_large 413 The write would exceed a storage ceiling rate_limited 429 The store’s calls for this minute are used up — wait and send it again internal 500 Our bug An input that does not fit the operation’s schema is the one error without a code: it is answered 400 with {"error": "Invalid input", "issues": [...]}, the schema’s own list of what failed. A 409 usually carries guidance in its message: it is how the API says “this order is already packed” or “use the component-pick operation for a kit line” rather than failing opaquely. ## Limits Each store can make 60 calls a minute through the API. Every REST operation call that passes validation counts, and so does every MCP execute (its first app.* call uses that one; each further call counts) and every code search (search({ code })); the catalog (GET /api/v1), the rest of search, MCP’s docs and the app’s own screens do not. A call past the limit is answered 429 with a Retry-After: 60 header and "code": "rate_limited" (over MCP: RATE_LIMITED). Nothing was run, so wait the minute and send the same call again. An MCP connection (one person, one agent app) can also send 120 requests a minute to /mcp, every request counted, search included. Past it the request is answered 429 with Retry-After: 60 and a JSON-RPC error whose data.code is RATE_LIMITED ("scope": "connection"); it did not run. ## Discovering the surface GET /api/v1 returns the machine-readable catalog — every operation with its method, path, minimum plan and input JSON Schema, straight from the running app. It needs a token but no plan, so a client can see the whole surface before its plan allows every call. The same information, as a static document you can point tooling at: [API explorer] (/rest-api/explorer/) Browse every operation, its parameters and its responses, with ready-made code samples. [OpenAPI 3.1 document] (/openapi/rest-v1.json) rest-v1.json — generated from the app's own registry. Feed it to your client generator. The document is regenerated from the registry on every change, so an operation that exists in the app exists in the document, with the same description the app carries. It cannot go stale without the app’s build failing. ## Changes The API follows the app: an operation that changes shape changes it for every door at once, and there is no compatibility layer. Recent changes, November 2026: - MCP: the tools are search, execute and docs (describe_api and run are gone; docs searches these pages). An execute that makes one call spends one of the store’s calls, not two. search({ query }) takes plain words or a whole question, with typos and merchant words (“label”, “stock”, “RMA”) understood. - Topics: every operation belongs to one of thirteen topics (orders, fulfillment, shipping, receiving, inventory, returns, layout, catalog, customers, people, integrations, reports, account). The catalog (GET /api/v1) names each entry’s topic, this document marks each operation with x-topic and groups its tags by topic (x-tagGroups), and MCP’s search answers the topics first and lists one with search({ topics: ["inventory"] }), page by page (cursor). The runtime discovery tag is discovery (it was catalog, which the catalog picker’s operations share). October 2026: - MCP: describe_api without input answers an index of every method, reads apart from writes. describe_api({ namespaces: ["orders"] }) declares those namespaces with their input and return types, and describe_api({ search: "short stock" }) the methods whose name or description holds every word. The server’s instructions carry the index instead of the whole declaration. - picking_create_batch no longer takes filter, and its input is strict: a call that still sends filter: "singles" is answered 400 (Invalid input, with the schema’s issues). Cut single-item orders with a pick profile instead (the Singles template: units = 1) and pass its profileId. Without foDocIds the batch takes the oldest ready orders first, and before it does it re-plans up to ten reservations that went stale (a lot that expired, a bin that is no longer allocatable). - picking_create_batch holds an explicit selection to the batch size too: max, else the profile’s order count, else 20. A selection with more ready orders is answered 409 selection_too_large (with max and ready) and nothing is batched; it is never cut short. - Pick profiles (Elevate): pick_profiles_list, _preview, _create, _update, _archive, _restore and _reorder under /picking/profiles. picking_queue and picking_list_batches take profileId; orders_recent_tags (GET /orders/tags) suggests the tags and priorities to write conditions with. - picking_queue_exclusions gains stale: orders that wait for a fresh reservation. - orders_work_queue’s tag matches like an automation rule (case, surrounding spaces and accent composition do not matter) and is answered 409 tags_indexing for the minute after an update that re-derives the order tags. - A shipment rate’s amount and currency can be null: in shipments_get (shipment.rates[], shipment.chosenRate, shipment.purchaseRate) and in the shipments_list rows. null means a service on your own carrier contract that Sendcloud returned no price for, so the carrier’s invoice decides. A label bought on such a rate is recorded with cost: null and currency: null. Code that adds up amount must skip the null ones. September 2026: - setup_guide_status is now setup_status (GET /setup), and answers four steps instead of six. - settings_set answers { ok: true, value } on success and { ok: false, reason: "warehouses_not_live", detail, warehouses, capped } when the Logistified switch is refused; inventoryWriterCutoverRequired is gone. - picking_queue_exclusions gains unmapped and takes warehouseId optionally. - The setting names openingStockSkipped and printerSetupSkipped no longer exist and are answered 400. ## See also - [REST quickstart] (/rest-api/quickstart/) — a token, a list, a safe change and the errors, step by step - [Connect an AI agent] (/rest-api/connect-an-ai-agent/) — the same operations through Claude, ChatGPT or another MCP client - [API explorer] (/rest-api/explorer/) — the interactive reference - [Subscription plans] (/getting-started/subscription-plans/) — what each plan includes - [Integrations] (/integrations/overview/) — how Floormode talks to the sibling apps - [Webhooks] (/integrations/webhooks/) — have Floormode call your system when something happens, and how to verify each message Last updated: 6 November 2026 --- Source: https://docs.floormode.app/rest-api/quickstart/ # REST quickstart Get a token, read a list, make one change safely and read the errors — Floormode's external REST API in four steps. Four steps from nothing to a working Floormode integration: get a token, read a list, make one change that is safe to send twice, and read what an error says. The [REST API] (/rest-api/overview/) page has the full rules, the [API explorer] (/rest-api/explorer/) every operation. ## On this page - Get a token - Read a list - Make a change safely - Read the errors - See also ## Get a token Every request carries Authorization: Bearer : an OAuth access token of a Floormode person whose role includes Use the API and AI agents (REST, MCP). The token can do what that person can do, and nothing more. To give an integration less than your own access, invite a person for it with a narrower role in Settings → Team & devices. Where to get the token is published: Terminal window ```bash curl https://prod.floormode.app/.well-known/oauth-protected-resource ``` ```json { "resource": "https://prod.floormode.app/mcp", "authorization_servers": ["https://"], "bearer_methods_supported": ["header"] } ``` Point any OAuth library at that document: it finds the sign-in, registers its client, and signs the person in once in a browser (authorization code with PKCE). Ask for the resource above. The same token works on /api/v1 and on the MCP server. Access tokens are short-lived; let your library renew them with its refresh token. ## Read a list Open orders that are short of stock, two at a time: Terminal window ```bash curl "https://prod.floormode.app/api/v1/orders/queue?allocationState=short&limit=2" \ -H "Authorization: Bearer $TOKEN" ``` A success is always { "data": … }. A list answers a page of rows, whether the list was cut (capped), and a cursor for the next page: ```json { "data": { "rows": [ { "_id": "orders_01K8C4Z3W9V7RS2A6J3QPMB5EN", "shopifyOrderId": "6253011468585", "name": "#1038", "allocationState": "short", "shortSkuCount": 1, "ageMs": 93600000 } ], "capped": true, "cursor": "1761036000000:orders_01K8C4Z3W9V7RS2A6J3QPMB5EN" } } ``` Each row carries more fields than shown here; the explorer lists them. For the next page, send the same request with &cursor=, until cursor is null. Pass the cursor back as it came; never build one. Query values are read as their declared type, so limit=2 is the number 2. A parameter the operation does not have is refused with 400 unknown_parameter, which names the ones it accepts. ## Make a change safely Put an order on hold because its address is incomplete: Terminal window ```bash curl -X POST "https://prod.floormode.app/api/v1/holds/apply-for-orders" \ -H "Authorization: Bearer $TOKEN" \ -H "Content-Type: application/json" \ -d '{ "shopifyOrderIds": ["6253011468585"], "reason": "address_issue", "note": "Street number missing", "requestKey": "7c4f0a52-2f0e-4c1e-9a41-0b8f6c2d1e33" }' ``` ```json { "data": { "applied": 1, "skipped": [] } } ``` requestKey is your own key for this one change, for example a new UUID. Keep it when you send the request again after a timeout: - the same key with the same body answers the first answer again, and nothing happens twice; - the same key with a different body is refused: ```json { "error": "This request key was already used for a different request. Use a new key.", "code": "conflict", "details": { "code": "idempotency_key_reused" } } ``` Operations that take a key say so in the explorer (requestKey or idempotencyKey). For one without a key, read before you send it again: for example, after a lost answer to picking_create_batch, list the open batches with picking_list_batches first. ## Read the errors An error is { "error": "", "code": "" }, and details.code when Floormode names the exact reason. Branch on the codes; the sentence is written for people and may change. A request whose input does not fit the operation’s schema (a missing field, a wrong type, limit=0) is the one error without a code: it is answered 400 with the schema’s own list of what failed. ```json { "error": "Invalid input", "issues": [ { "origin": "number", "code": "too_small", "minimum": 1, "inclusive": true, "path": ["limit"], "message": "Too small: expected number to be >=1" } ] } ``` HTTP code Means 400 none, issues instead The input does not fit the operation’s schema 400 unknown_parameter A query parameter the operation does not have 400 invalid_input The values fit, but Floormode refused them; the sentence says why 401 none No token, or one that is not valid for Floormode 403 plan_required The operation needs a higher plan (it names requiredPlan) 403 forbidden The person may not do this; details.code is permission_required 404 not_found The record does not exist 409 conflict The change cannot be applied as asked; the sentence says why 429 rate_limited The store’s 60 calls for this minute are used up; send it again after Retry-After Note A 409 is an answer, not a failure of ours: “this order is already packed” or “use a new key”. Change the request; sending the same one again gets the same answer. ## See also - [Connect an AI agent] (/rest-api/connect-an-ai-agent/): the same operations through an AI client - [REST API] (/rest-api/overview/): requests, responses, limits and changes in full - [API explorer] (/rest-api/explorer/): every operation with its inputs - [Webhooks] (/integrations/webhooks/): have Floormode call your system when something happens Last updated: 19 November 2026 --- Source: https://docs.floormode.app/rest-api/connect-an-ai-agent/ # Connect an AI agent Let an AI agent such as Claude, ChatGPT or Cursor read your orders and stock, and do work for you, with your own access. An AI agent can answer questions about your warehouse and do work for you: “which orders are stuck, and why?”, “where is order #1042?”, “start the morning’s batches”. It connects to Floormode’s MCP server, signs in as you, and can never do more than you can. ## On this page - What you need - Connect - What you approve - Taking access back - Read only - What the agent can do - Set up a store - How the agent finds its way - Three examples - Read events - When something goes wrong - See also ## What you need - A Floormode person whose role includes Use the API and AI agents (REST, MCP). Administrators have it. - An AI client that can add a remote MCP server. Claude calls it a connector, other clients a custom integration or an MCP server. Floormode speaks the current MCP version, 2026-07-28, and the earlier 2025-11-25 and 2025-06-18, so newer and older clients all connect. ## Connect 1. In your AI client, add a remote MCP server with this address: ```text https://prod.floormode.app/mcp ``` 2. The client opens Floormode’s sign-in in your browser. Sign in with your P&H account. If you belong to more than one workspace, choose your store’s. 3. Approve the client. The next section says what the approval screen asks for. 4. Ask your question in the chat. ## What you approve The approval screen comes from the sign-in page of your P&H account, not from Floormode’s own pages, and its words are general. What you grant is narrower than it may sound: - Floormode’s API for the workspace you chose: that one store’s Floormode, not your Shopify admin or any other app. - As you, within your role. The client reads and changes what your role allows, nothing more, and every call is checked against your role as it is at that moment. A change it makes shows in the history under your name. - For as long as you leave it connected. The screen asks to keep access: the client stays signed in without asking you each time, until you take the access back. The screen may call the client unverified and warn about it. Most AI clients register themselves with the sign-in page when you add the server, and nobody can vouch for the publisher of a client that registered itself, so the page says so. The warning is about the client app, not about Floormode, and it changes nothing about what the client may do. Approve it only when you have just added the server yourself, in a client you trust. ## Taking access back - In Floormode, one app at a time: Settings → Apps & API → Webhooks & API → Connected apps lists every app someone on your team connected, who connected it and when it was last seen. Revoke takes effect at once: the app’s next request in this workspace is refused, until an administrator chooses Allow again. An administrator (Integrations, webhooks, Flow, domains) does this for any app of the team; it stops the app in this workspace only. When you revoke an app you connected yourself, the connection in your P&H account ends too, in every workspace. - In your AI client: remove the server (the connector). The client stops calling Floormode. - For the whole person, at once: open the person the agent signs in as under Settings → Team & devices and choose Deactivate, or take Use the API and AI agents (REST, MCP) out of their role. The agent’s next call is refused, whatever the client still holds. ## Read only In the same Connected apps list, set an app to Read only: it may then read everything its person may read, and every change it tries is refused with agent_read_only, at once and whatever the person’s role allows. Same as the person gives it the person’s own rights back. Read only never gives an app more than its person has. The approval screen does not offer the choice: AI clients register themselves, and such a client gets the same sign-in scopes as any other, so the limit is set in Floormode after you connect. ## What the agent can do - It works as you. Every read and every change is checked against your role, as in the app. A change it makes shows in the history under your name. - It can change data. Holds, stock adjustments and pick batches are writes. Ask the agent to say what it will do before it does it. - Less than your own access. For an agent that only reads, set it to Read only (see [Read only] (#read-only)). For a narrower set of writes, invite a person for it in Settings → Team & devices (for example agent@yourshop.com), give that person a role with only what the agent needs plus Use the API and AI agents (REST, MCP), and sign in as that person when you connect; deactivating that person takes the agent’s access back without touching yours. - Limits. Your store can make 60 calls a minute through the API, agents included. Each execute counts as one call, which its first call inside uses; each further call inside counts one more, and so does each code search (below); looking things up with search or in the help pages with docs counts none. One execute stops after 30 seconds or 200 calls. Apart from the store’s calls, each connected agent can send 120 requests a minute, every request counted, looking things up included, so an agent that used up the store’s calls can still find its way and plan the next step. The agent can read these limits with search({ context: true }). ## Set up a store An agent can set a new store up with you, on any plan and before you choose one. It follows Home’s setup steps: 1. Warehouses from your Shopify locations: setup_status lists the locations, shopify_locations_refresh reads them fresh from Shopify, warehouses_create_from_locations makes the warehouses. 2. Shelves: locations_generate_grid or bins_create. 3. Stock: inventory_opening_import brings in Shopify’s numbers. If the store import stalled or failed, sync_import_start runs it again; sync_job_get shows how it goes. 4. Go live: warehouses_go_live starts a check of Shopify’s numbers against Floormode’s. Read the outcome with warehouses_cutover_history. If the only differences are counts made in Floormode, the attempt names a countedDigest; the agent calls warehouses_go_live again with it to set Shopify to your counts. Going live cannot be undone, so ask the agent to tell you before it does it. 5. Packing, boxes and the team: warehouses_update (the pack checklist), boxes_create, people_invite. 6. The test order: you place it in Shopify; setup_first_order shows where it stands while it is picked and packed. store_facts_get gives the agent your store’s time zone and units, and floor_devices_list, printnode_scales_list and customerPages_health show what is set up already. Some steps stay yours: installing Floormode, approving the agent, choosing your plan in Shopify, typing a carrier’s or PrintNode’s key into Floormode’s own dialog, and pairing a floor device. ## Ship a parcel An agent can ship a parcel the way the desk does: 1. Draft: shipments_create_draft opens a shipment for the order. 2. Rates: shipments_rate asks the carrier. The answer names the default your shipping rules or the customer’s checkout option chose. shipments_service_points lists pickup points and lockers near the customer, for carriers that have them. 3. Buy one label: shipments_buy_label with a rateId. A label costs money, so the agent shows you the rate and asks you to confirm before it buys. Calling it again asks you to confirm again, and never buys a second label: it answers the label already bought. If the carrier refused, never answered, or the label could not be saved, the answer says what happened to the money and what to do next. If the carrier never answered, shipments_lookup_purchase asks the carrier whether the label exists. 4. The label file: shipping_document_link answers a download link for a label, customs form or manifest. The link works for 10 minutes without signing in, so the agent can download the file or give you the link. The file itself never goes through the agent’s chat. 5. Void: shipments_void_label cancels a label at the carrier, after you confirm. A label already voided is not cancelled twice. Booking a pickup, closing out a manifest, freight quotes and printing are not open to agents yet. ## How the agent finds its way This part is for the curious and for developers; the agent does it by itself. The server offers three tools: search and execute, which the agent uses in three steps (find, read the details, execute), and docs, which searches these help pages. - search finds what the agent can call. - Topics: without input it answers how to use it and the API’s topics, the same areas the [API explorer] (/rest-api/explorer/) groups by: orders, fulfillment (picking and packing), shipping, receiving, inventory, returns, layout (warehouses, bins, zones), catalog, customers (tracking pages, customer e-mails, privacy requests), people, integrations (stores and sync), reports and account. search({ topics: ["returns"] }) lists one topic’s methods; a long list comes in pages, and its cursor fetches the next one. - Find: search({ query: "which orders are ready to pick?" }) answers a short list of candidates, best first: each method’s name, its topic, what it does in one line, whether it reads or writes, the permission and plan it needs, and whether the agent may run it here (allowed: false names why not). Plain words and whole questions both work (“create batch”, “stocktake”, “How do I buy a label for order #1042?”), and so do typos and a merchant’s own words: “label” finds shipments, “stock” inventory, “RMA” return requests. The search ranks by each method’s name, purpose, inputs and their values, permission and the skills that use it. topics, namespaces, kind ("query" for reads, "mutation" for writes) and limit narrow the list. - Details: search({ names: ["picking.queue"] }) answers the exact methods asked for, with their inputs and answers as TypeScript, including the fields of each list row. - Who am I here: search({ context: true }) answers the store the agent is connected to, your role, the store’s plan, your permissions and the limits. - Search with code: for questions across many methods, the agent writes JavaScript over the whole list of methods: search({ code: 'return catalog.methods.filter((m) => m.topic === "fulfillment" && m.irreversible).map((m) => m.name);' }) answers every fulfillment change that cannot be undone. The code sees only that list, with each method’s topic, inputs, permission and whether the agent may run it: no store data and no network. Each code search counts as one call. - search({ index: true }) lists every method by name, under its topic. - Skills: step-by-step recipes for common tasks: find stuck orders, cut a pick batch safely, receive a purchase order, adjust or move stock, count a bin, handle a return, check shipping problems, read the day’s numbers, and more, at least one for every topic. search({ skills: true }) lists them and search({ skill: "create-a-pick-batch" }) reads one. A search names the skills that use its first methods. Clients that load skills from a server (the MCP skills extension) find the same recipes there. - execute runs the JavaScript the agent writes, in a sandbox with no network. The agent calls app..(input) and returns what it found. Several calls fit in one run. - docs searches these help pages live: docs({ query: "how does wave picking work" }) answers the best passages, each with its page, its section and a link to it. The agent reads them to explain a screen or a setting, or to learn how a workflow goes before it looks for the methods. Answers stay small and whole. One answer holds up to 24,000 characters by default (execute({ code, maxChars }) raises it). A bigger answer is refused with its shape (its fields, how many rows, capped and cursor), and the agent asks again for fewer fields or rows. Floormode never cuts rows off an answer quietly: a list says capped: true when more rows exist, and its cursor fetches the next page. Answers as data. Clients on MCP 2026-07-28 also receive each answer as data (structuredContent), in the shape each tool’s output schema describes. Refusals say how to fix the call. Beside the readable message, a refused call names the method, the field and the rule it broke, the permission or plan it needs, whether trying again can help, and the next step. A call the agent’s client cancels stops before its next step; the steps it already took stay done. A method’s name is the operation’s name in the [API explorer] (/rest-api/explorer/) with its first _ turned into a dot: orders_work_queue is app.orders.work_queue, and pick_profiles_list is app.pick.profiles_list. ## Three examples What the agent writes for three questions, and what the answer looks like. You never write this code yourself. ### Which orders are stuck, and why? ```js const { groups } = await app.dashboard.needs_attention(); const short = await app.orders.work_queue({ allocationState: "short", limit: 5 }); const missing = await Promise.all( short.rows.map(async (order) => { const { gaps } = await app.orders.allocation_gaps({ shopifyOrderId: order.shopifyOrderId }); return { order: order.name, missing: gaps.map((gap) => `${gap.missingQty} × ${gap.sku ?? gap.title}`), }; }), ); return { attention: groups.map(({ kind, reason, count }) => ({ kind, reason, count })), missing, }; ``` ```json { "attention": [ { "kind": "on_hold", "reason": "address_issue", "count": 2 }, { "kind": "short_allocation", "reason": null, "count": 3 } ], "missing": [ { "order": "#1038", "missing": ["2 × MUG-BLUE"] }, { "order": "#1041", "missing": ["1 × TEE-M-BLACK", "1 × TOTE-NAT"] } ] } ``` ### Where is order #1042? ```js const { hits } = await app.search.global({ query: "#1042" }); const order = hits.find((hit) => hit.type === "order" && hit.label === "#1042"); if (!order) return "No order #1042."; const { entries } = await app.orders.journey({ shopifyOrderId: order.id }); return entries.slice(-4).map(({ atMs, kind, subject, detail }) => ({ at: new Date(atMs).toISOString(), kind, subject, detail, })); ``` The journey lists every step oldest first: reserved, picked, packed, label bought, shipped in Shopify, the carrier’s tracking. The last steps say where the order stands. ```json [ { "at": "2026-10-21T09:12:40.000Z", "kind": "packed", "subject": "PACK-1", "detail": null }, { "at": "2026-10-21T09:13:05.000Z", "kind": "label_bought", "subject": null, "detail": "1Z999AA10123456784" }, { "at": "2026-10-21T09:13:09.000Z", "kind": "shipped_in_shopify", "subject": "UPS", "detail": null }, { "at": "2026-10-21T16:40:00.000Z", "kind": "tracking", "subject": "in_transit", "detail": "Louisville, KY" } ] ``` ### What’s short? ```js const { rows, totalShortfallUnits } = await app.inventory.backlog_shortfall({ limit: 10 }); return { totalShortfallUnits, items: rows.map(({ sku, title, demand, available, shortfall, incoming, suggestedOrderQty }) => ({ sku, title, demand, available, shortfall, incoming, suggestedOrderQty, })), }; ``` demand is what open orders owe and available what the bins hold; shortfall is the difference. incoming is already on its way, so suggestedOrderQty is what is left to order. ```json { "totalShortfallUnits": 9, "items": [ { "sku": "MUG-BLUE", "title": "Mug, blue", "demand": 12, "available": 6, "shortfall": 6, "incoming": 2, "suggestedOrderQty": 4 }, { "sku": "TOTE-NAT", "title": "Tote bag, natural", "demand": 5, "available": 2, "shortfall": 3, "incoming": 0, "suggestedOrderQty": 3 } ] } ``` ## Read events An agent can follow what happens on the floor through an event feed (Settings → Apps & API → Webhooks → Event feeds): it reads new events when it wants, with nothing of yours online. Copy the Feed URL from the feed and give it to the agent. The loop: 1. Read a page: REST GET /api/v1/events?feed=feed_… (with after once it has a cursor), or MCP await app.events.list({ feed: "feed_…", after }). 2. Handle the page’s rows, oldest first. Each row is a [Standard Webhooks] (/integrations/webhooks/) event body; skip an id it already handled. 3. Keep the answer’s cursor. The next read passes it as after. 4. Wait retryAfterMs: 0 while more is waiting, longer once it is caught up. The loop (a sketch: handle and sleep are the agent's own) ```js let after; for (;;) { const page = await app.events.list({ feed: "feed_…", ...(after ? { after } : {}) }); for (const event of page.rows) handle(event); after = page.cursor; await sleep(page.retryAfterMs); } ``` What to know: - Its own access. Each read sees only the events the agent’s own role and warehouses may see. The answer’s readable.withheld names the events it may not read, and why. - Gaps. A gap in the answer names a period the feed may have missed: the events were older than Floormode keeps (5 days), or the feed had expired. A read from the past, or a feed that starts at the oldest kept event, reads only what Floormode kept. Events from before any endpoint or feed listened, or from while this feed had expired, were never kept, and a read from the past names no gap for them. To fill a gap, read the details through the API. - The cursor is opaque. Keep it as it came: it is not signed, and changing it only misleads the agent itself. A cursor that is not one, that points past the newest event, or that names a later end than the feed has is refused (cursor_invalid). - Limits. A page holds at most 100 events and 1 MB. Feed reads have their own limits, 30 a minute per agent and feed and 120 a minute per store, and never use the store’s 60 calls a minute. Cloudflare counts them per location, so treat them as a guard and follow retryAfterMs. - Life. A feed lives 30 days after its last read, so an agent that reads keeps it alive. A read of an expired feed is refused (feed_expired): an administrator renews it. - Sequence numbers show how much happened in your store, not what happened. ## When something goes wrong The agent says Means Do It has to sign in again and again The sign-in did not reach your store’s workspace Sign in with your P&H account, and choose your store’s workspace if asked organization_required The sign-in chose no workspace Connect again and choose your store’s workspace when asked agent_read_only The app is set to Read only An administrator sets it to Same as the person in Connected apps, if it should change data agent_revoked The app was revoked in this workspace An administrator chooses Allow again in Connected apps, if it should have access The approval screen calls it unverified The client registered itself when you added the server Approve it if you added the server yourself just now; see [What you approve] (#what-you-approve) plan_required The operation needs a higher plan (the refusal names it) Choose that plan in Settings → Billing, or leave that step out permission_required Your role does not include the API Ask an administrator to add Use the API and AI agents (REST, MCP) to your role RATE_LIMITED (answered 429, "scope": "connection") The agent sent more than 120 requests this minute Wait a minute and go on with fewer, larger steps. The refused request did not run RATE_LIMITED The store’s 60 calls for this minute are used up Wait a minute, then go on in smaller steps. The refused call did not run. The refusal says how many calls of the same request had finished before it and how many were still running: those may have been done, so check before asking again INVALID_INPUT or CONFLICT Floormode refused the call and said why The agent reads the reason and can correct the call ... is not a function The agent guessed a method name Ask it to look the name up with search({ query: "…" }) OUTPUT_TOO_LARGE The answer was bigger than the agent’s budget The agent asks again for fewer fields or rows, or a bigger maxChars Caution Cutting a pick batch takes a requestKey: one key per batch the agent means to cut, kept when it asks again. Asked again with the same key and the same arguments, Floormode answers the first batch and cuts no second one; the same key with other arguments is refused with idempotency_key_reused. Without a key, an agent that lost the answer must look at the open batches before it asks again, or it cuts a second batch from the next orders in the queue. ## See also - [REST quickstart] (/rest-api/quickstart/): the same API for your own code - [REST API] (/rest-api/overview/): authentication, errors and limits in full - [API explorer] (/rest-api/explorer/): every operation with its inputs - [Standalone access & your team] (/getting-started/standalone-access/): inviting people and their roles Last updated: 11 November 2026 --- Source: https://docs.floormode.app/rest-api/explorer/ # API explorer Browse every operation in Floormode's external REST API — parameters, schemas, responses and copy-ready code samples. Every operation below is generated from Floormode’s own operations registry, so this page describes what the API actually does today. Start with the [REST API overview] (/rest-api/overview/) for authentication, the response envelope and the error codes; the raw document is at [/openapi/rest-v1.json] (/openapi/rest-v1.json). Interactive API explorer: [OpenAPI document] (/openapi/rest-v1.json) --- Source: https://docs.floormode.app/reference/glossary/ # Glossary Every warehouse term Floormode uses, defined in one sentence. Floormode’s warehouse vocabulary, defined once. Terms that appear inline elsewhere in these docs link back to this page. Where a plain-English name exists, the app uses it — see [Plain-English names] (/getting-started/plain-english-names/) for what got renamed and what was deliberately kept. ## Available Also known as: Available quantity On 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. ## Available to promise Also known as: ATP What you can genuinely commit to a customer right now, taking existing reservations into account. Floormode spells this out rather than using the industry abbreviation. ## B-stock Also known as: Grade B A returned item fine to sell but not as new (worn, opened or with its tags removed), which Floormode holds in its own bin, BSTK-01, so it is never sold as new by mistake. ## Backorder Also known as: Backordered, Back order An order waiting on stock that could not be reserved. When stock arrives, it is reserved for the orders waiting on it, which are then picked and packed as usual. ## Bin Also known as: Location, Bin location A specific place stock sits. Every bin has a type — receiving, quality check, quarantine, bulk, pick, packing, staging or returns — which tells the app how to treat what is in it. ## Blind count Also known as: Blind counting A count where the counter never sees the expected quantity, so the number they report is genuinely independent rather than a confirmation of what the system already believed. ## Blind receipt Also known as: Blind receiving Receiving where the expected quantity stays hidden from the receiver, so what gets booked in is what was actually in the box rather than what the delivery said. ## Cartonization Also known as: Box selection Choosing the cheapest suitable box for an order from your box catalog, using item dimensions — and splitting into several boxes where one will not do. [anchor: multi-order-picking] ## Cluster picking Also known as: Multi-order picking, Multi-order Picking several orders in one walk, each order in its own slot on the cart, so the sorting happens at the shelf instead of at a sort wall afterwards. ## Committed Also known as: Committed quantity, Reserved for orders Units already promised to open orders and therefore no longer freely sellable, even though they are still on the shelf. ## Cycle count Also known as: Cycle counting, Count Counting a few bins at a time, continuously through the year, instead of shutting the warehouse for an annual stocktake. ## Days of cover Also known as: Days of supply How many days the stock you have left will last at the rate the product has been selling. ## Delegation Also known as: Delegated location, Location delegation, Delegate Handing one specific location’s receiving and inventory writing to Floormode, so a merchant can move locations across one at a time instead of switching the whole shop at once. ## Delivery confirmation Also known as: Confirmed delivery, Acknowledgement The receipt a connected app sends back to say it applied a message — which is what lets Floormode show a queue as genuinely delivered rather than merely sent. ## Discrepancy Also known as: Variance Any difference between what the system expected and what was physically found — on a receipt, at a bin during picking, or in a count. ## Disposition Also known as: Dispositions The decision about where a returned unit goes once it has been graded: back to sellable stock, into damaged and quarantine, or written off. ## Expected receipt Also known as: Receipt, Inbound delivery A delivery you are waiting on. It moves from expected, through being received, to received as the floor books it in line by line. ## FEFO Also known as: First expired first out, Expiry-first picking First expired, first out: allocating the shortest-dated stock first so perishable goods leave before they expire. A per-warehouse policy on every plan. ## Floor Mode Also known as: Floor The full-screen, scanner-first surface for warehouse staff: no admin chrome, giant tap targets, one job at a time, and no search box a scanner gun could trigger. ## Fulfillment Also known as: Fulfillments The part of an order that one warehouse ships together. An order split across two sites has two fulfillments; each carries its own lines, shipments and state. ## Handback Also known as: Handover, Handing back, Handed back, Hand back, Handing over local stock The controlled exit taken when a connection is switched off: Floormode freezes the local stock, sends the exact quantities back to the owning app, and only releases them once that app confirms it has them. ## Hold Also known as: On hold, Blocked A deliberate block on an order, recorded with a reason, a note and usually a reference to the document being waited on. A hold is a decision, not a failure. ## HS code Also known as: Tariff number, Harmonized System code The customs code that classifies a product, kept on the product in Shopify; every item of a parcel that needs a customs declaration needs one. ## Incoming Also known as: Incoming quantity, Inbound quantity Units on an expected receipt that has not fully arrived — stock you have coming but cannot pick yet. ## Kit Also known as: Bundle, Kits and bundles A product sold as one item but made of several components. Selling a kit consumes its components, which is why a kit’s availability depends on the scarcest part rather than on a stock figure of its own. ## Kit expansion Also known as: Bundle expansion, Expanded kit, Kit expansion on orders Turning a kit ordered by a customer into the component lines the floor actually picks, so a picker is told to fetch real things on real shelves rather than a product that never sits in a bin. ## Local item Also known as: Local items, Not on Shopify, Virtual material, Raw material, Sub-assembly, Custom item A good you stock and move in Floormode that does not exist on Shopify — an Assemblified raw material or sub-assembly, or a Logistified custom item — recognisable by an id starting VMAT-, ASM- or CSTM-. ## On hand Also known as: On-hand, On hand quantity The units physically in the building right now, whether or not they are already promised to an order. ## Oversell Also known as: Overselling Selling beyond what is on hand. Deliberate oversell is a per-warehouse switch that is off by default; accidental oversell usually means a warehouse is not linked to a Shopify location. ## Pack job Also known as: Pack task One parcel’s worth of work at the pack station: scan every item, choose the box, record the weight, and verify before a label is bought. ## Parked message Also known as: Parked, Parked messages, Parked delivery, Parked deliveries A message to a connected app that is held, in order, while that app is not answering, and sent once it answers. It is visible, never a silent loss. A switched-off app gets no messages, so nothing is parked for it. ## Pick batch Also known as: Batch, Pick list A set of lines one picker walks in one trip, sorted into pick-path order so the building is crossed once rather than repeatedly. ## Pick path Also known as: Pick sequence, Walking route The order bins are walked in — zone, aisle, side, bay — which is what turns a list of lines into an efficient single pass through the warehouse. ## Placement Also known as: Slotting Deciding which bin each product lives in, so the fastest sellers sit closest to packing. Warehouse software traditionally calls this slotting. ## Production pick Also known as: Component pick Picking a work order’s components to a staging bin so they are ready to be built, rather than picking finished goods for a customer. ## Purchase order Also known as: PO, Purchase orders An order placed on a supplier — the document in Logistified that names the supplier, the lines and the expected date, and which appears in Floormode receiving as the delivery to book in. ## Putaway Also known as: Put away Moving received goods from the receiving area to the bin they belong in. With the receiving policy Straight to a shelf it happens during receiving; with a dock policy a putaway task follows the receipt (after the inspection, where the policy inspects). A work order’s finished goods that Floormode books onto the workbench bin WO-STAGE-01 get a putaway task too; an output that needs the receiver (serial numbers, or a date Floormode cannot work out) is received on its receipt instead. ## Reorder point Also known as: Reorder level The stock level that should trigger a new purchase order, so the delivery lands before you sell the last unit. ## Replenishment Also known as: Replenish, Top-up, Refill Topping up a pick bin from reserve stock before it runs empty, as a Replenish task the floor works. ## Restocking fee A share of a returned item’s price kept back from the refund for handling it, never charged on an exchange or a faulty item, nor in the EU, EEA and UK to a customer who cancels within 14 days. ## Return request Also known as: RMA, Return merchandise authorization A customer’s request to send something back, before you approve it and it becomes a return. Warehouse software traditionally calls this an RMA. ## Safety stock Also known as: Buffer stock The buffer held underneath the reorder point to absorb a late supplier or an unusually good week without going to zero. ## Saved view Also known as: Saved views, View tab A list’s filters, sort and columns kept under a name: only you see it, unless you tick Share with everyone in this shop when you save it. ## Short pick Also known as: Short, Shortage When a bin does not hold what the system expected. Recording it (Report short) marks the line Picked short and posts the discrepancy against that specific bin, rather than quietly under-picking the order. ## Single writer Also known as: Single-writer rule, Inventory writer, Shopify writer The rule that exactly one app may write a given location’s inventory back to Shopify, because two apps writing the same number overwrite each other and the stock figure drifts. ## Slot Also known as: Cart slot One numbered place on a pick cart, such as CART-1-03, where cluster picking puts one order’s units. ## Staging bin Also known as: Staging A bin holding goods marshalled for a next step — components waiting for a build, or parcels waiting for despatch — rather than stock available to pick. ## Tote Also known as: Totes One container a picker carries for a batch, without slots, whose orders are sorted at the pack station. ## Unexpected return Also known as: Blind return, Unauthorised return A parcel that comes back without a return request or a Shopify return announcing it, received like any return. ## Unplaced item Also known as: Unplaced items, Unplaced, Placing, Opening quantity A local item the connected app has told Floormode about that has no bin here yet — it cannot be received, picked or counted until you place it by entering its opening quantity into a bin. ## Value deduction Part of a returned item’s refund kept back because it came back worth less than it was sold for, set as a percentage on a return grade and never applied to a faulty item. [anchor: release] ## Waves Also known as: Wave, Release, Wave picking A group of orders released for picking together (Release wave), instead of every order reaching the floor as soon as it is paid. ## Work order Also known as: Work orders, Build order An 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. Last updated: 19 November 2026 --- Source: https://docs.floormode.app/reference/lifecycles/ # Lifecycles Every state an order, a shipment and a return can be in, in the words the app shows, and what comes next. Floormode names each state the same way on every screen. This page lists them in order, with what each means and where it can go next. ## On this page - An order - A shipment - A return - See also ## An order The order’s page shows where the order stands as a row of steps. An order normally moves left to right through Open → Reserved → (Waiting) → Picking → Packed → Fulfilled. The other states stop the row. State Means Next Open Read from Shopify; nothing reserved yet. Reserved, or Not enough stock Reserved Stock is reserved in bins for the order’s fulfillments. Picking Waiting Held while goods are made or on their way; the step names the document, such as a purchase order. Only shows for those holds. Picking, once the goods are in and the hold is released Picking Pick work is running on the floor. Packed Packed Packed and handed to a shipment. Fulfilled Fulfilled Every fulfillment is closed. — Not enough stock Some lines could not be reserved. Reserved, once stock arrives On hold Someone held it with a reason. Back on the row when released On hold outside Floormode Held in the Shopify admin or by another app. Release it there. Back on the row when released Releasing hold Released; waiting for Shopify to confirm. Back on the row Nothing to ship Closed in Shopify with nothing left to send. — Cancelled Cancelled in Shopify. — Beside it, the Orders list shows Shopify’s own Status: Unfulfilled, Partly fulfilled, Fulfilled, On hold, Scheduled or Restocked, or Cancelled. Why an order is not moving is its Blocked reason; see [Why isn’t this order pickable?] (/features/orders/why-not-pickable/). ## A shipment A shipment is one parcel and its label, on Fulfillment → Shipping and the order’s page. State Means Next Draft The parcel exists; no rates yet. Rates ready, Buying label…, Label voided Rates ready Rates were fetched; nothing bought. An address change sends it back to Draft. Buying label…, Draft, Label voided Buying label… The label is being bought from the carrier. Label bought, or Rates ready if the purchase did not go through Label bought The label exists and can be printed. In transit, Delivered, Delivery problem, Refund pending, Label voided In transit The carrier has scanned it. Delivered, Delivery problem, Refund pending, Label voided Delivery problem The carrier flagged it: a failed attempt, an address problem, a return to sender. In transit, Delivered, Refund pending, Label voided Refund pending You asked to void the label; the carrier has not confirmed. If the parcel is scanned meanwhile, it goes back to its tracking state. Label voided, or back to tracking Delivered The carrier delivered it. Final. — Label voided The label was taken back, or a draft was discarded before any label existed. Final. — Some carriers cannot take a label back; see [Shipping] (/features/fulfillment/shipping/#rates-and-labels). ## A return A return starts as a request, from the customer’s returns page or entered by you. These are the request’s states on Returns → Requests. State Means Next Requested The customer asked; waiting for your decision. Approved, Declined, Cancelled Approved Agreed; the customer can send it back. Received, Cancelled Received The goods arrived and were graded on a return receipt. The money or exchange is still owed. Refunded, Credited or Exchanged Refunded, Credited, Exchanged Resolved by what the customer asked for: money back, store credit, or an exchange order. A filter calls all three Resolved. — Declined You said no. — Cancelled Withdrawn. — An exchange creates a draft order in Shopify with the customer’s address. When there is no address to copy, the request says so: add the address to the draft before you send it. The return itself, as Shopify tracks it on Returns → Shopify returns, reads Requested, Open, Closed, Declined or Cancelled. A return receipt, where the goods are graded, is Open, then Received or Cancelled. ## See also - [Why isn’t this order pickable?] (/features/orders/why-not-pickable/): the reasons an order stops. - [Pack] (/features/fulfillment/pack/#pack-job-statuses): the pack job’s states. - [Shipping] (/features/fulfillment/shipping/): rates, labels and voids. - [Returns overview] (/features/returns/overview/): requests, returns and receipts. Last updated: 30 October 2026 --- Source: https://docs.floormode.app/reference/url-map/ # URL map Where every pre-overhaul Floormode link now lands — old bookmarks and links in old emails keep working. Every pre-overhaul Floormode URL redirects to its new home. Bookmarks, links in old emails and support hand-offs all keep working. ## On this page - Old links and where they land - The current routes - Nothing quietly falls back to home - See also ## Old links and where they land Old link Now /picking, /tasks, /fulfillment/tasks /fulfillment/queue /packing /fulfillment/pack /shipping /fulfillment/shipping /waves /fulfillment/waves /fulfillment/release /fulfillment/waves /inbound /inventory/receiving /inventory/adjustments /inventory/movements /slotting /inventory/placement /return-requests /returns/requests /analytics /insights/reports /forecast /insights/replenishment /automation /settings/orders/rules /routing /settings/orders/routing a warehouse’s ?tab=settings its ?tab=details /onboarding, /notes / (the setup guide on Home) Detail links carry their identifier across too — an old /picking/:id lands on /fulfillment/batches/:id, an old /packing/:id on /fulfillment/pack/:id, and an old /inbound/:id on /inventory/receiving/:id. You never lose the record you were pointing at. ## The current routes A part written with : stands for the record’s own identifier, as it appears in the address bar when you open that record. Section Pages Home / Orders /orders, an order /orders/:order, merge groups /orders/merges and one group /orders/merges/:group Fulfillment /fulfillment/queue, /fulfillment/batches, /fulfillment/pack, /fulfillment/shipping, /fulfillment/production, /fulfillment/waves; a pick batch /fulfillment/batches/:batch, a pack job /fulfillment/pack/:job Inventory /inventory/stock and an item /inventory/stock/:item, /inventory/receiving and a receipt /inventory/receiving/:receipt, /inventory/counts and a count task /inventory/counts/:task, /inventory/movements, /inventory/lots and a lot /inventory/lots/:lot, /inventory/serials and a serial /inventory/serials/:serial, /inventory/transfers and a transfer /inventory/transfers/:transfer, /inventory/bins, /inventory/placement, item setup /inventory/local-items Returns /returns/requests, /returns/all and a return /returns/:return, /returns/receipts and a receipt /returns/receipts/:receipt Insights /insights/reports, /insights/replenishment, /insights/stock-value, /insights/alerts Team /team/today, /team/plan, /team/output, /team/shifts, /team/time Settings /settings/warehouses and a warehouse /settings/warehouses/:warehouse (its map …/map, its zones, stations & staff …/work-areas), /settings/stock, /settings/picking, /settings/packing, /settings/shipping (its tabs …/printing, …/rules, …/checkout-options), /settings/orders (its tabs …/rules, …/routing), /settings/returns, /settings/customer-emails (its tabs …/brand, …/words, …/sender), /settings/privacy, /settings/apps, /settings/stores and a store /settings/stores/:store (starting it …/start), /settings/team and a person /settings/team/people/:person, /settings/team/roles and a role /settings/team/roles/:role, /settings/team/devices, /settings/team/time-clock, /settings/team/defaults, /settings/billing Floor Mode /floor, the wallboard /floor/board, choosing where you work /floor/scope; picking /floor/pick/:batch, production picking /floor/component-pick/:batch, packing /floor/pack/:job, receiving /floor/receive/:receipt, inspecting /floor/inspect/:receipt, a move /floor/move/:task, counting /floor/count/:task; a transfer’s pick, return and receipt /floor/transfers/:transfer/pick, …/return, …/receive; setting up a floor device /floor/register, signing in /floor/pin Customer-facing in your store: /apps/floormode-tracking — the order page, and /apps/floormode-tracking/r — its returns Clicking a nav entry lands on that section’s first tab: /inventory opens /inventory/stock, /fulfillment opens /fulfillment/queue, /team opens /team/today and /settings opens /settings/warehouses. Someone whose role cannot open a page lands on the first one they can. ## Nothing quietly falls back to home Note A URL that matches nothing shows a proper “Page not found” with a link home — it does not quietly drop you on the dashboard. Silently redirecting an unknown URL to home is a small kindness that costs a lot: you cannot tell a typo from a removed feature, and a broken link in a support email looks like it worked. ## See also - [Finding your way around] (/getting-started/finding-your-way-around/) — the eight places. - [Plain-English names] (/getting-started/plain-english-names/) — why the names changed. Last updated: 19 November 2026