{"title":"How fulfillment stations work","slug":"how-fulfillment-stations-work","url":"https://support.storeconnect.com/articles/how-fulfillment-stations-work","url_markdown":"https://support.storeconnect.com/articles/how-fulfillment-stations-work.md","subtitle":null,"summary":"Understand the records behind POS fulfillment stations, the order in which an item is routed to a station (overrides, mappings, availability, fallback, and load balancing), how station tickets move through the prep lifecycle, and what operators see on a screen.","type":"Help_Documentation","video_url":"","keywords":"fulfillment station routing, routing order, register override, category mapping, station availability, fallback station, station group, load balancing, weighted least connections, station ticket, prep lifecycle, status flow, requested, preparing, ready for pickup, primary station, covered station, fallback recipient, degraded station, station ticket history","last_modified":"2026-11-11T01:38:25+0000","body_markdown":"Use this topic to understand what happens behind [POS fulfillment stations](pos-fulfillment-stations): which records hold the setup, how each item on an order is routed to a station, how a station ticket moves through its prep stages, and what operators see on a screen. Read it before you [configure station routing](pos-fulfillment-station-routing), or when a ticket goes somewhere you did not expect.\n\n## The records involved\n\nFive objects hold the configuration, and one field on the fulfillment records the result.\n\n| Object | What it holds |\n|--------|---------------|\n| [Fulfillment Category](fulfillment-category-object-reference) (`s_c__Fulfillment_Category__c`) | One record per prep concept, such as Hot Food, Wine, or Cocktails |\n| [Product Fulfillment Category](product-fulfillment-category-object-reference) (`s_c__Product_Fulfillment_Category__c`) | Links a product to one or more categories |\n| [Fulfillment Station](fulfillment-station-object-reference) (`s_c__Fulfillment_Station__c`) | One record per preparation area, attached to an outlet |\n| [Fulfillment Category Station](fulfillment-category-station-object-reference) (`s_c__Fulfillment_Category_Station__c`) | Maps a category to a station, giving the outlet-level default route |\n| [Register Fulfillment Category Station](register-fulfillment-category-station-object-reference) (`s_c__Register_Fulfillment_Category_Station__c`) | Sends a category to a specific station for one register, overriding the outlet default |\n| [Shipment](shipment-object-reference) (`s_c__Shipment__c`) | The fulfillment itself. `s_c__Fulfillment_Station_Id__c` records which station the ticket was routed to |\n\nBecause a station ticket is a Shipment, anything you can report on for a Shipment you can report on for a station ticket.\n\n## How an item reaches a station\n\nRouting runs once for each item. On a regular order it runs when the order is fulfilled. With open orders on, it runs on every **Submit** for the newly submitted items, and again at checkout for anything not yet routed. Once a fulfillment exists, its station is fixed until an operator moves the ticket.\n\nVirtual products are excluded before routing starts. A virtual product such as a fixed-price bundle's wrapper is not a fulfillable good, so it never resolves to a station and never enters a fulfillment. An unrouted virtual item is expected, not a fault.\n\nEvery other item is routed individually, in this order.\n\n1.  **Register override.** If the order-taking register has a **Register Fulfillment Category Station** record that sends the item's category to a station at this outlet, that station wins.\n2.  **Outlet mapping.** Otherwise the outlet's category-to-station mapping decides. If a category maps to more than one station, the station with the oldest **Created Date** wins. This tiebreaker is deliberately stable, so adding a newer station never silently re-routes an existing configuration.\n3.  **Products in several categories.** Candidates are pooled across all of the product's categories and the same oldest-record tiebreaker picks one. An item always routes to exactly one station and is never split across stations.\n4.  **No mapping.** The item is left unassigned. Nothing is lost and no error is raised.\n\nAn item always routes within its own outlet. Stations in other outlets are never used, even when a register override points at one.\n\n### Availability\n\nA station is only routed to if it can actually take work. Routing skips a station that is `disabled` or `degraded`. An active station's register must also be online, meaning its heartbeat has been received in the last five minutes, and must have an open shift, unless the station's **Offline Behavior** is `accept`.\n\nA station group is never evaluated directly. It is evaluated through its children.\n\n### Fallback\n\nWhen the chosen station cannot take work, routing follows that station's **Fallback Station** and re-checks availability there. The chain is capped at five hops so a misconfigured loop cannot run forever.\n\nIf no available station is found anywhere along the chain, the item stays assigned to the station originally chosen rather than disappearing. A visible ticket an operator can act on is better than a lost one, and the station's own banner explains why tickets are landing there.\n\n### Load balancing across a station group\n\nSet **Parent Station** on two or more stations to make them children of a group. Items routed to the group are spread across the children rather than handled by the group itself.\n\nThe pick uses weighted least connections: each child's outstanding ticket count is divided by its **Weight**, and the child with the lowest result takes the item. Only the ratio of weights matters, so `100` and `200` behave the same as `1` and `2`. Fulfillments in a terminal state (`complete`, `delivered`, `shipped`, `returned`, `received`, `cancelled`) do not count toward the outstanding total.\n\nThe spread happens across fulfillments and orders, not within one. Loads are counted once per fulfillment, so every item in a fulfillment that routes to the group goes to the same child.\n\nUnavailable children are skipped. If none are available, the group's own fallback chain is followed.\n\nGroup parents are invisible to operators. They are excluded from the cover picker, the degrade and cover actions, and the register lists on the outlet stations board. Staff always interact with the children.\n\n### Grouping into tickets\n\nItems are grouped by stock location and station, so each unique combination becomes its own fulfillment.\n\n- Items at the same location going to different stations produce separate tickets.\n- Items at different locations produce separate tickets even when they share a station.\n\nShipping charges are grouped exactly as they were before stations existed.\n\n## The prep lifecycle\n\nA station ticket advances through a fixed progression: `requested` → `preparing` → `ready_for_pickup` → `complete`. Operators see these as **Requested**, **Preparing**, **Ready**, and **Completed**.\n\nEach station chooses which of those stages it uses, using the **Status Flow** field on the station. The order never changes and `requested` and `complete` are always the endpoints, so the field only records which stages are active.\n\nThree example configurations, to show the range. Yours can be any combination of the four stages:\n\n| Example setup | Stages | Status Flow value | Effect |\n|---------------|--------|-------------------|--------|\n| A retail counter tracking pick and pack | Four | Leave empty, or select all four | The default. Tickets step through every stage |\n| A quick-service counter | Three | `requested;ready_for_pickup;complete` | Skips **Preparing** |\n| A bar, where a drink is poured and handed over | Two | `requested;complete` | A requested ticket finishes in one tap |\n\nAn empty or unrecognized value falls back to the full flow, so a station can never end up unable to advance or complete a ticket. A ticket sitting at a stage the flow omits always advances forward to the next configured stage ahead of it, so no ticket is ever stranded.\n\nAn operator can also advance part of a ticket. Selecting some of the lines splits those lines onto a new ticket at the next status and leaves the rest on the original, so whatever is finished can go out while the rest is still being prepared. In a kitchen that might be sending the side dish ahead of the main; at a trade counter it might be releasing the items that are in stock while one is still being fetched.\n\n## What operators see on a screen\n\nThree surfaces expose stations in the POS. The **Stations** sidebar entry appears automatically once the current outlet has at least one fulfillment station record. The others are opt-in and an admin adds them, as described in [Set up station tickets on a register](pos-station-tickets-at-a-register).\n\n| Surface | Scope |\n|---------|-------|\n| **Stations** | The stations this device is responsible for, plus a combined ticket feed |\n| **Operations** | Every register in the outlet, plus an **Inactive stations** group for stations with no register |\n| Home grid cards | Shortcuts such as **Cover a station**, and live cards for individual stations |\n\nAt any moment a station has one of three relationships to the device looking at it.\n\n- **Primary** — the station's **Register** is this device's register. Its permanent home.\n- **Fallback recipient** — the station is degraded and its fallback lands on one of this device's primary stations, so this device is receiving its tickets. Every device derives this the same way.\n- **Covered** — an operator on this device chose to also handle this station. This is local to the device, and other devices do not see it.\n\nOperators flip a station between **Active** and **Degraded** themselves, using **Degrade station** and **Restore station**. `disabled` is set by an admin and is structural. Status changes sync and are safe to make offline: the local view updates immediately and the change is applied when connectivity returns.\n\nFor the staff-facing side of all this, see [work station tickets](work-fulfillment-station-tickets) for advancing and splitting tickets, and [monitor stations across the outlet](monitor-outlet-stations) for covering a colleague's station and moving stations between registers.\n\n## How long a device keeps tickets\n\nA device keeps every station ticket it has synced. Nothing is deleted, so opening an old order on the device still shows how it was fulfilled, and a device that has been in service for months holds months of tickets. Three consequences follow.\n\n- **Station screens show open work plus a tail of recent history.** A station's lists and the **Stations** overview show every ticket still outstanding, plus a short tail of recently finished ones, rather than everything ever routed there. Nothing that is still waiting is ever hidden. To find an older finished ticket, open its order from the **Orders** list.\n- **Printing speed does not depend on history.** Auto-print reads only the work still live at the stations it prints for, so a device set up this morning prints as quickly as one that has run for a year. The one exception is the count on a home grid station card, which still counts everything ever routed to that station and grows slower as the device ages. The station detail screen and the searchable ticket workspace also read the whole history.\n- **A first sync pulls the outlet's ticket history.** A newly set-up device, or one whose data has been cleared, downloads the outlet's tickets before it is fully up to date. This is a one-off cost at setup and does not affect printing speed afterwards. See [POS storage, sync, and device administration](pos-storage-sync-and-administration)."}