Set up station tickets on a register
On this page
Use this process to set up each tablet or register that runs or supervises fulfillment stations. You select the template that station tickets print with, set up how staff open the station screens, and choose which printer each station’s tickets print on. Which station an item goes to is set separately, by station routing.
Most of these settings are set per device, so two terminals at the same outlet are set up separately. A kitchen terminal and a bar terminal, for example, each get their own template and printers. The action items in Step 2 are the exception, because they apply to every register in the org.
Before you start
- Fulfillment stations and category mappings exist for the outlet. See Configure POS fulfillment station routing.
- Each station’s Register field is set to the register that will run it.
- Each device that prints tickets has a receipt printer connected.
Step 1: Select the station ticket template
A device prints no station tickets until you select a fulfillment template on it, and the POS gives no warning when one is missing.
- On the register, select Settings in the sidebar.
- Under Printers, select Printer templates, then Fulfillment template.
- Select a template. StoreConnect includes Example Fulfillment Template, which prints the station name, the order date and reference, the customer, and the items routed to that station, with bundle components indented.
- Select Run test print to print a sample ticket and check the layout.
To build your own template, create a POS Print Template record with Context set to fulfillment and Printer type set to receipt, then select it in step 3. The template receives three variables:
| Variable | Contents |
|---|---|
current_station |
The station the ticket belongs to, with name and display_name |
current_order |
The order the ticket came from |
current_items |
Only the items routed to this station, as fulfillment items |
Use a receipt template for station tickets. A document template produces a PDF for Run test print, but real station tickets do not print with it. The POS still marks those tickets as printed, so the never-printed report does not catch them. See POS print templates for the full templating reference.
:::warning The template’s Printer type controls which printers you can assign to a station. If you change the type on a template that is in use, printer assignments that no longer match are dropped, and those stations print to the device’s default printer. :::
Step 2: Set up access to station screens
Staff work stations from three screens on the device: the list of this device’s stations, each station’s ticket board, and an outlet-wide board for managers. This step sets up how staff open them.
| Entry point | Opens | Who uses it | Setup |
|---|---|---|---|
| Stations in the sidebar | This device’s stations, with waiting counts and a combined ticket feed. Selecting a station opens the station’s details screen, with the tickets, status, fallback, printers, and the categories that route to it | Staff working a station | None. It appears automatically on any register whose outlet has at least one fulfillment station, as long as the store uses the default sidebar menu |
| Operations in the sidebar | The outlet-wide board: every register in the outlet with its stations and live counts for each status | Managers and supervisors | Add the Operations sidebar entry |
| Home grid cards | Shortcuts to the outlet-wide board, one station, or one station’s tickets | Whoever you set up the home grid for | Add home grid cards |
If staff only work their own stations, the automatic Stations entry is enough, and you can go to Step 3. Add the Operations entry or home grid cards when managers need to see the whole outlet, or when staff need a quicker way into a particular station.
:::note You cannot limit station screens to particular staff or devices. Anyone who can open a station screen can degrade a station, cover another station, move tickets, and reprint, with a confirmation dialog for each. Action items sync to every register in the org, so the Operations entry and home grid cards appear on every register, including registers at outlets with no stations. :::
For how staff use these screens during service, see work station tickets and monitor stations across the outlet.
Add the Operations sidebar entry
:::warning
A sidebar_main_menu action group replaces the default sidebar menu entirely. Home, Orders, the automatic Stations entry, and every other default entry disappear unless you add them to the group as well. A Stations item you add yourself appears on every register, including registers at outlets with no stations.
:::
- Go to the POS Action Groups list and open the group with the Identifier
sidebar_main_menu. If there is none, create the action group with that identifier and a Type ofList, and add an item for each default entry you want to keep. -
Add a POS Action Item (
s_c__Pos_Action_Item__c) with Parent Action Group set to this group, and these values:Field Value Display Name OperationsIcon radarType actionAction nav:outlet_stations - Sync the device.
Operations now appears in the sidebar of every register.
Add home grid cards
- Go to the POS Action Groups list and open the group with the Identifier
home. If there is none, create the action group with that identifier and a Type ofGrid. If the outlet has a quicklist product category, ahomegroup replaces the quicklist product grid on the home screen. -
For each card, add a POS Action Item with Parent Action Group set to this group, and the values for that card:
Display Name Action Params The card opens Manage stationsopen:outlet_stationsNone The outlet-wide board Cover a stationstation:cover:pickerNone A list of stations to take over on this device Your stationsopen:fulfillment_stationsNone This device’s stations, the same screen as Stations in the sidebar The station’s name open:fulfillment_stations:recordstation_id=<station sfid>One station’s details screen The station’s name open:station_fulfillmentsstation_id=<station sfid>One station’s ticket board - Sync the device.
For example, a card for the hot station’s tickets has the Display Name Hot station, the Action open:station_fulfillments, and the Params station_id=a1B5g00000XyZAbEAN.
A card with the action open:fulfillment_stations:record shows the station’s live name, status, and routing, for example Hot station [Degraded] → Cold station.
Use nav: for sidebar items and open: for home grid cards. With nav:, the new screen replaces the current one. With open:, Back returns staff to the screen they came from.
Choose how a ticket board opens
A ticket board card (open:station_fulfillments) accepts three more parameters:
viewsets the arrangement the board opens in. See the table below.statusesis a comma-separated list of the statuses to show, fromrequested,preparing,ready_for_pickup, andcomplete.sortisfield:direction, where the field isupdatedorstatus.
Without these parameters, the board opens as a grid showing requested,ready_for_pickup tickets, sorted by status.
view |
The board | Can staff switch it? |
|---|---|---|
grid (the default) |
A grid of ticket cards | Yes, to any of the first four arrangements |
rail |
One row of cards that scrolls sideways | Yes, to any of the first four arrangements |
double-rail |
Two stacked rows that scroll sideways | Yes, to any of the first four arrangements |
flex-grid |
A board where each card keeps its natural height | Yes, to any of the first four arrangements |
rows |
One line per ticket, with thumbnails and a status label | No |
list |
A compact table of tickets | No |
Use rows for a mounted screen where staff should not change the arrangement. The home grid card shows a preview of the arrangement the board opens in.
:::note
You cannot attach a POS View to a station ticket board, including the list arrangement, so the six arrangements above are the only layout options. You can still change colors, sizing, and card density with Style Blocks. See POS layouts.
:::
Step 3: Assign printers to individual stations
Each station prints to the device’s default printer unless you assign it a different one. When a device has more than one printer of the template’s printer type, assign each station the printer where its tickets should print. With network printers, one tablet can print tickets for several stations, each on its own printer.
- On the register, open Stations in the sidebar and select the station.
- Open the station’s action menu and select Assign printers.
- Check each printer the station should print to. The device’s default printer is labeled Default.
- Close the picker.
The station’s details screen now lists the assigned printers in the Printer box (Printers when there is more than one). If you check more than one printer, every ticket prints on each of them, for example on a preparation bench and at the counter where orders are handed over.
What to know about printer assignments:
- They are stored on the device. Assignments do not sync. Another register covering the same station keeps its own assignments.
- To clear an assignment, uncheck every printer. The station then prints to the device’s default printer. There is no separate clear option.
- Assign printers only appears when there is a choice. It shows on a device with two or more connected printers of the template’s type, for stations this device runs or is covering. It does not show for group parents or for degraded or disabled stations.
- You cannot select a disconnected printer. It shows with a Not connected label. A printer that is already assigned, and the default printer, stay selectable so you can always remove an assignment.
- A removed printer falls back to the default. If an assigned printer is removed, or no longer matches the template’s printer type, the assignment is dropped, and the station prints to the default printer.
Telling identical printers apart
The POS tells printers apart by serial number, so you can assign two printers of the same model to different stations.
The POS does not let you add a second USB printer of the same make and model when neither reports a serial number, because the two cannot be told apart. Printers that report a serial number are not affected.
To check that a printer was identified, go to Settings > Manage hardware, select the printer, and check the Manufacturer, Model, and Serial number rows. A row shows Not detected when the value could not be read.
:::note The POS never prints a ticket on a printer it was not sent to. If an assigned printer is not connected, or cannot be told apart from an identical one, that copy is not sent anywhere else.
If every printer assigned to a station is offline, the ticket stays unprinted, and it prints automatically when a printer reconnects, as long as the ticket is still open. Do not reprint it by hand, or the station gets two copies. If only some of the assigned printers are online, the POS marks the ticket printed once one copy prints and does not send the offline printer’s copy later. Reprint by hand if that copy is needed. :::
Use one device to print for several stations
You can print tickets for several stations from one device, so the printing hardware is in one place.
- On the device that will print, connect a printer for each station.
- In Salesforce, set each station’s Register to this device’s register.
- On the device, use Assign printers to give each station its own printer.
Make this device the only register named on these stations. A station’s own register always prints the station’s tickets, and you cannot turn this off. If a station’s Register is set to another device, both devices print and the station gets two copies.
If a station cannot have a register, leave Register blank and set Offline Behavior to accept. Then cover the station on the printing device and select Auto-print new tickets. With Offline Behavior set to pass and no register, the station is unavailable and its tickets go to its fallback station.
Each station’s tickets print in the order they were placed. If two stations share a printer, their tickets print one after another, in no guaranteed order. A ticket that failed to print earlier prints first on the next attempt, and a print that was delayed can come out of order.
:::warning If the printing device goes offline, no station gets a ticket. Check the never-printed report every shift, whichever setup you use. :::
Example: configuring the restaurant devices
This example continues the restaurant from Configure POS fulfillment station routing.
| Device | Stations it runs | Fulfillment template | Printer assignments |
|---|---|---|---|
Kitchen tablet |
Hot station, Cold station |
Selected | Each station assigned the printer beside it |
Bar front tablet |
Bar front station |
Selected | None, so it uses the device default |
Bar back tablet |
Bar back station |
Selected | None, so it uses the device default |
Cellar tablet |
Wine Tasting Cellar |
Selected | None, so it uses the device default |
Host tablet |
None | Not needed | None |
Server A, Server B, Server C handhelds |
None | Not needed | None |
Only the Kitchen tablet needs printer assignments, because it is the only device with two receipt printers. The handhelds take orders and never print tickets, so they need neither a template nor a printer.
If you add the Operations sidebar entry so a manager can see the whole outlet, it also appears on the handhelds.
When a device is set up correctly, its Stations screen lists its own stations, a new order routed to one of them prints a ticket without anyone touching the screen, and the station’s Printer box names the printer the ticket printed on.
Was this article helpful?
Thanks for your feedback! It helps us improve our docs.