Skip to main content
The routing strategy decides, for each order line, which station(s) it goes to.
There can be only one active strategy per store. Activating a new one automatically deactivates the others for that store.

​
Default vs custom mappings

  • Production required = No in Store settings.
  • One ASSEMBLY station + one screen.
  • Active routing (empty mappings); item mappings are not used because there is no prior production.
If there is no mapping for an item_type, the line goes to fallback (ideally a production station, not assembly).

​
Decision order

  1. Routing (layer 1): picks candidate production stations by item_type + fallback.
  2. Station rules (layer 2): channel, service type (DINE_IN, DELIVERY…), item types — can reject the line.
  3. Distribution (layer 3): if several production candidates remain, picks one according to the mode.
  4. Convergence (runtime): when production advances, the ticket appears in ASSEMBLY/DISPATCH according to gates and convergence distribution; there, channel/service station filters apply.
Layer 2 example: routing sends an item to GRILL, but the station has Exclude channels: UBER_EATS → that line is not shown on the grill even though the mapping includes it.

​
How production routing works

Line routing (layers 1–3) applies only to production stations:
  1. Reads the line’s item_type.
  2. Looks for a mapping (production stations only in the form).
  3. If no match → fallback stations (your default station).
  4. Applies station rules (channel, service, item).
  5. If several candidates → distribution.
Assembly and dispatch do not take part in these steps. They receive the ticket when the matching production is completed (convergence), not because you put BURGER → ASSEMBLY in a mapping.

​
Distribution modes (when 2+ candidate stations)

If the mapping has a single station, the distribution mode does not change the result.

​
Multi-station example

Stations: Screens: Routing strategy — production only in mappings: Convergence (outside mappings): when the lines in GRILL/FRY complete, the ticket appears in ASSEMBLY and then DISPATCH according to convergence distribution and those stations’ channel/service rules.
Routing editor with item_type mappings and distribution

​
Create the strategy

1

Open the routing form

KDS → Routing → Create (/kds/admin/routing/new).
2

Choose store and name

For example, “Default routing”.
3

Simple kitchen

One KITCHEN station, fallback = KITCHEN, no mappings, Active.
4

Advanced kitchen

Mappings only to production stations; convergence distribution if there are ASSEMBLY/DISPATCH stations; fallback = default production station.
5

Save

In the routing list you can see the active strategy card and a conceptual station ↔ screen map. Next: Peripherals, printing and validation.