---
title: "Troubleshoot fulfillment stations"
source: https://support.storeconnect.com/articles/troubleshoot-pos-fulfillment-stations
type: article
format: markdown
site: StoreConnect Support — product and developer documentation for StoreConnect
site_index: https://storeconnect.com/llms.txt
docs_index: https://support.storeconnect.com/llms.txt
note: Append .md to any page or article URL on this site to get its Markdown form.
---
# Troubleshoot fulfillment stations

Station problems are quiet by design. Routing never raises an error, so an item that cannot be routed is left unassigned and a docket that cannot print is simply not printed. Work by symptom, and check the data on the [Shipment](shipment-object-reference) record rather than relying on what the screen shows.

## Start here

Make these two checks first, because together they tell you which half of this article you need.

1.  **Is a fulfillment template selected on the device?** Go to **Settings**, then under **Printers** select **Printer templates**, then **Fulfillment template**. Nothing prints on a device with no template selected, and nothing warns you, so this is worth ruling out before anything else.
2.  **Does the fulfillment carry a station?** Open the **Shipment** record in Salesforce and check **Fulfillment Station**. A blank value is a routing problem. A populated value with a blank **Auto Printed At** is a printing problem. That split tells you which half of this article to read.

## The item routed nowhere

**Symptom:** the fulfillment exists but **Fulfillment Station** is blank, and no ticket appears on any station screen.

Check these in order.

1.  **Does the product have a fulfillment category?** A product with no **Product Fulfillment Category** record routes as unassigned.
2.  **Is the category mapped to a station at this outlet?** A **Fulfillment Category Station** record is needed per outlet. A mapping that exists at one outlet does not apply at another.
3.  **Is the product virtual?** A virtual product, such as a fixed-price bundle's wrapper, is never routed. That is expected. Check the components instead.
4.  **Did the order have a register and a source outlet?** Routing needs both, so an order missing either one routes nothing. The fulfillment is still created, with **Fulfillment Station** blank.

Run a report on fulfillments where **Fulfillment Station** is blank to see the whole pattern rather than one case. A single product points at a missing category; a whole category points at a missing mapping.

## The ticket landed at the wrong station

**Symptom:** the ticket printed, but at a station you did not expect.

| Likely cause | How to confirm |
|--------------|----------------|
| A register override is in play | Check for a **Register Fulfillment Category Station** on the order-taking register for that category |
| The category maps to more than one station | The station with the oldest **Created Date** wins. Look for a duplicate **Fulfillment Category Station** record |
| The product is in several categories | Candidates are pooled across all of them and one station is picked. An item is never split |
| The chosen station was unavailable | The fallback chain took over. Check the intended station's **Status**, its register's shift, and its **Offline Behavior** |
| The category maps to a group | The group spreads work across its children, so the child that takes an item varies by load |

:::note
An override pointing at a station in a different outlet is ignored, and the outlet default is used. An override pointing at a station in the right outlet that is unavailable is still honored, and the fallback chain then runs from there. Routing does not fall back to the outlet mapping in that case, so check the override station's own fallback.
:::

## The ticket appears on screen but no docket printed

**Symptom:** the ticket is on the station screen, **Auto Printed At** is blank on the **Shipment** record.

Work through these on the device that should have printed it.

1.  **No fulfillment template selected.** Select one under **Settings**, **Printer templates**, **Fulfillment template**.
2.  **No receipt printer set up.** The automatic cycle does not run at all on a device with no receipt printer.
3.  **The printer is not connected.** In browser POS, a warning banner appears on the station details screen, the ticket workspace, and the printer settings page. Select **Reconnect** to re-approve the printer. A Star mPOP always needs this after being unplugged, because it reports no USB serial. A printer that reports a serial reconnects by itself.
4.  **The station is not this device's responsibility.** A device only auto-prints for its own primary stations, and for covered stations with auto-print switched on. Check the station's **Register**.
5.  **The station has no register.** A station with **Register** blank never auto-prints anywhere until it is assigned, or until a device covers it and switches auto-print on.
6.  **All of the station's assigned printers are offline.** Nothing is dispatched and the ticket stays unprinted. A network printer cannot be polled, so the failure only surfaces when a print is attempted, after an attempt of up to two minutes.
7.  **An earlier print never finished.** Each printer has its own queue, but a device runs only one print cycle at a time. A stuck print holds up every new ticket on that device, for every printer, until it is abandoned and logged as failed after about two minutes. Each further ticket for the stuck printer adds another wait, and a station assigned two printers stalls on both when one of them is stuck. If dockets have slowed or stopped across a whole device, look for one printer that is off or unreachable.
8.  **The printer profile could not be determined.** A banner on the printer settings page says so. Set the profile to match the hardware.

Once the cause is fixed, the held ticket prints by itself the next time the POS runs the print cycle, as long as the ticket is still open. There is no timer. The cycle runs only when something happens on the device: when a USB printer reconnects, when the printer or template settings change, when the POS reloads, and when a ticket changes or syncs on the device. To print the held ticket straight away, reload the POS. Nothing needs re-fulfilling. Do not reprint it from the ticket detail while it waits: a manual reprint does not count as the automatic print, so the station gets a second docket when the cycle runs.

:::warning
Do not rely on a held ticket printing itself when a printer comes back. A ticket completed before it printed never prints by itself, and a ticket can sit unprinted with nothing on screen drawing attention to it, which is how an order gets missed. Run a report on **Shipment** where **Fulfillment Station** is not blank and **First Printed At** is blank, and check it during and after every shift. That report is the only thing that catches this reliably.
:::

## A docket printed on the wrong printer

**Symptom:** two printers on one device, and dockets come out of the wrong one.

1.  Open each station's details screen and read its **Printer** box (**Printers** when there is more than one). It shows the printers that station's dockets currently route to, or the default when it has no printers assigned.
2.  If a station reads `Not configured`, no printer of the template's type is set up on the device. This does not check whether a printer is connected. It also reads `Not configured` when no fulfillment template is selected.
3.  Confirm the printers can be told apart. Go to **Settings**, **Manage hardware**, then each printer, and check the **Serial number** row. `Not detected` means the printer could not be uniquely identified, and two identical units cannot be reliably assigned to separate stations.
4.  Check that the template's **Printer type** still matches the assigned printers. An assignment that no longer matches the type is dropped, and the station falls back as described below.

### Where a station prints when its printer assignment is gone

An assigned printer that has been removed, or that no longer matches the template's printer type, is dropped from the station. The station then prints to:

1.  The printer marked **Default** on that device, if there is one.
2.  Otherwise the first eligible printer set up on the device, which is not something an operator can predict.

Mark one printer as **Default** on every device that prints dockets. Without one, removing a printer sends a station's dockets somewhere arbitrary rather than somewhere known.

Remember that printer assignments are stored on the device, not on the station. Another device covering the same station has its own assignments, or none.

## The same docket printed twice

**Symptom:** two identical dockets for one ticket.

- **Two devices printed at the same instant.** Auto-print is deduplicated across devices through **Auto Printed At**, but a brief sync window can let two devices that both auto-print the ticket each print it. An occasional second docket is expected.
- **A station is assigned more than one printer.** The same docket prints on every printer assigned to the station. That is intended. Uncheck the printer you do not want.
- **Someone reprinted it.** Compare **First Printed At** with **Last Printed At** on the **Shipment** record. Different values mean a reprint, and **Last Printed Register** names the device. A reprint taken while the ticket was still waiting for the automatic print does not stop that print, so the station gets both.
- **A covering device has auto-print switched on.** Both the primary and the covering device can print. Select **Stop auto-printing tickets** on the covering device.
- **A slow print was abandoned and retried.** A print that does not finish within about two minutes is treated as failed, so nothing is stamped and the automatic cycle prints the ticket again. If the printer did in fact produce the first docket late, you get two. A printer that regularly takes this long is usually on a congested network or short of paper.

## A moved ticket did not print at its new station

This is intended. Auto-print fires once per ticket and a move does not reset **Auto Printed At**, which stops moves and sync churn causing reprint storms.

Open the ticket at its new station and select **Reprint**. A manual reprint moves **Last Printed At** and never touches **Auto Printed At**.

## Switching auto-print on did not print the waiting tickets

Also intended. Switching **Auto-print new tickets** on for a covered station sets a starting point: the created date of the newest ticket already on the device for that station, or the moment you switched it on if there are none. Only tickets created after that point print automatically, so the existing backlog is deliberately left alone rather than dumped to the printer. A ticket created earlier that had not yet synced to the device still prints, because it is newer than anything the device held.

This applies to covered stations only. On a station's own register there is no starting point, so every open ticket that has never auto-printed prints.

Reprint the waiting tickets by hand from their ticket detail.

## The Stations entry is missing from the sidebar

The entry appears automatically once the current outlet has at least one **Fulfillment Station** record.

1.  Confirm a station record exists and that its **Outlet** is the outlet this register belongs to.
2.  Run a sync on the device, then check again. The entry follows the synced data, so it is missing until the station reaches the device.
3.  If your store uses a custom sidebar action group, confirm the group still includes the item. Authoring your own group for an identifier replaces the app default completely.

**Operations** and the home grid cards are opt-in and never appear by themselves. Add them as described in [Set up station tickets on a register](pos-station-tickets-at-a-register).

## A station is not taking any work

**Symptom:** new tickets go to the fallback while the station looks fine. If the whole fallback chain is unavailable, they stay on the station that was first picked, so tickets are never lost.

Check in this order, because status dominates.

1.  **Status.** A `degraded` or `disabled` station is skipped. Operators set `degraded` and can clear it with **Restore station**. `disabled` is set in Salesforce.
2.  **Register heartbeat.** A station's register must have reported in within the last five minutes. A register that has not is treated as offline, and its stations are unavailable even with an open shift. Recovery needs the register to reconnect, or a manual ticket move.
3.  **Open shift.** With **Offline Behavior** set to `pass`, the station is unavailable when its register has no open shift. Start a shift, or set the field to `accept`.
4.  **Register assigned.** A station with **Register** blank and **Offline Behavior** set to `pass` is always unavailable for direct routing. Set it to `accept`, or assign a register with an open shift.

The banner on the station details screen names a degraded or disabled status, and a register with no open shift (`this station's register is offline`). It says nothing about a register that has stopped checking in, or a blank **Register** with `pass`, so check those two yourself.

## A group station is missing from the POS

Group parents are deliberately invisible to operators. A station with children never appears in the cover picker, the degrade and cover actions, or the register lists on the **Operations** board. Staff work with the children instead. Map categories to the group; expect to see only the children.

## Nothing prints from an Android tablet

1.  **The printer was not discovered.** Open **Settings**, **Set up hardware**, **Receipt**, and check the picker. If the list is empty, confirm the tablet and printer are on the same Wi-Fi, and that the app has the Nearby devices permission (Location on Android 10 and 11) with Location turned on.
2.  **The printer has no reachable address.** The alert reads `Printer has no reachable address; re-run printer discovery.` Remove the printer and discover it again.
3.  **The connection type was not recorded.** The alert names LAN, USB, and Bluetooth as the options. Run discovery again so the connection is stored with the printer.
4.  **You are looking for an offline warning.** The Android app does not show one. It has no way to poll a network printer, so a failure surfaces as an alert at print time instead. The ticket is not marked printed, so it prints on the next cycle. There is no timer: a cycle runs when a ticket changes or syncs, a printer reconnects, or a printer, template, or auto-print setting changes. A busy outlet gets one about every minute through the regular sync, but on a quiet device the ticket waits until something happens, so reload the POS to print it straight away.
5.  **It is a document printer.** Those are managed in the tablet's own Android print settings, not in StoreConnect.

See [Print station tickets over the network](pos-station-network-printing) for the full setup.

## A ticket is stuck and cannot be advanced

- **Its stage is not in the station's Status Flow.** A ticket sitting at a stage the flow omits always advances forward to the next configured stage ahead of it, so it should still have a button. If it does not, the station's flow has not synced yet.
- **It is already complete.** A completed ticket is terminal and shows no advance button.
- **It has only one line.** **Select items** only appears on a ticket with more than one line, counting lines with the same product name as one. Use the footer button.
- **A save failed.** An error banner appears and the ticket stays open so it can be retried. Check connectivity and try again.

## An older finished ticket is not on the station screen

Station screens show the tickets still outstanding plus a short tail of recently finished ones, not everything ever routed to the station. The ticket has not been lost. Open its order from the **Orders** list, where every fulfillment and its station are still shown. See [how long a device keeps tickets](how-fulfillment-stations-work#how-long-a-device-keeps-tickets).

## Prevention

- Run the whole plan in [Test fulfillment stations](test-pos-fulfillment-stations) in a sandbox before every go-live and after any change to categories, stations, or templates.
- Give every station a **Fallback Station** unless you have decided its tickets should stay put when it is degraded.
- Set a report on fulfillments with a blank **Fulfillment Station** and check it weekly. It catches new products added without a category.
- Name printers after where they physically are, so whoever assigns one to a station picks the right unit.
- Mark one printer as **Default** on every device that prints dockets, so a dropped assignment falls back somewhere known.
- Keep a report on **Shipment** where **Fulfillment Station** is not blank and **First Printed At** is blank, and check it every shift. A ticket that never printed is invisible on the POS, so this report is what stops an order being missed.

---

## Follow StoreConnect

- [Email Newsletter](https://storeconnect.com/c/lp-newsletter)
- [LinkedIn Newsletter](https://www.linkedin.com/build-relation/newsletter-follow?entityUrn=7444956928444862464)
- [YouTube](https://www.youtube.com/channel/UCngKdP2x8l1wcbAKW3tvU8g)
- [LinkedIn](https://www.linkedin.com/company/storeconnect)
- [X / Twitter](https://x.com/storeconnecthq)

## Popular Links

- [Partners](https://storeconnect.com/partners)
- [Become a Partner](https://storeconnect.com/become-a-partner)
- [News](https://storeconnect.com/articles/news)
- [Events](https://storeconnect.com/articles/events)
- [Feature Comparison](https://storeconnect.com/how-we-compare)
- [Download a free trial](https://appexchange.salesforce.com/appxListingDetail?listingId=a0N3A00000FMkeKUAT)
- [Book a Demo](https://storeconnect.com/contact)

## Documentation

- [Help documentation](https://support.storeconnect.com/help-documentation)
- [AI agents](https://support.storeconnect.com/ai)
- [Videos & tutorials](https://support.storeconnect.com/videos-tutorials)
- [Developer reference](https://support.storeconnect.com/developer-reference)
- [Release notes](https://support.storeconnect.com/release-notes)
- [Troubleshooting](https://support.storeconnect.com/troubleshooting)
- [Trust Center](https://trust.getstoreconnect.com/)
- [Status Page](https://status.storeconnect.com/)

## Contact

- info@getstoreconnect.com
- US +1 415 745 3230
- AUS +61 2 8365 2308

100 S Ashley Dr, Suite 600-2461
Tampa FL 33602-600 USA

Level 22, Sydney Place
180 George Street
Sydney, NSW, 2000, AUS

## Machine-readable

- [Site index for agents](https://storeconnect.com/llms.txt): curated map of the StoreConnect site in llms.txt format
- [Documentation index for agents](https://support.storeconnect.com/llms.txt): full technical and product documentation map

Every page and article on this site has a Markdown rendering: append `.md` to its URL.

Continue in Markdown: [Help documentation](https://support.storeconnect.com/help-documentation.md) · [Developer reference](https://support.storeconnect.com/developer-reference.md) · [Videos & tutorials](https://support.storeconnect.com/videos-tutorials.md) · [Release notes](https://support.storeconnect.com/release-notes.md)

---

StoreConnect Support — https://support.storeconnect.com/articles/troubleshoot-pos-fulfillment-stations