Flows can do the routine pick ticket work for you: make tickets in batches, print them at the right time, email a ticket to a store, and move an order that was picked short to a location that has everything. This page covers the pick ticket triggers and actions and the two ready-made recipes.
ℹ️ Before you start: pick tickets are set up under Picking → Printing & settings. Each location has its own switch to turn pick tickets on, a Make tickets choice, a printer (through PrintNode) and a Print tickets: automatically, on these days and hours switch. Flows work with those settings, not around them.
How the settings and flows fit together
| Setting (Picking → Printing & settings) | What it means for flows |
|---|---|
| Make tickets: when an order is paid | Tickets are made for you. Use Pick ticket created to print or email each one |
| Make tickets: when the order is in ShipStation | Tickets are made once the order reaches ShipStation |
| Make tickets: only from the orders list and flows | Nothing is made automatically. Use Create pick tickets on a schedule, or the orders list |
| When tickets print: Scheduled | A flow with Print unprinted pick tickets on a schedule does the printing |
| When tickets print: Manual | Print unprinted pick tickets and Print the pick ticket skip their runs and print nothing |
| Orders in one go | The most orders one Create pick tickets step takes in one run |
| Emails per flow run, Emails per hour | Limits for Email the pick ticket |
Triggers
| Trigger | Fires when |
|---|---|
| Pick ticket created | A ticket is made for an order at a location: automatically, from the orders list, or by a flow |
| Pick ticket picked | Every line of a ticket is picked or marked short |
| Pick ticket short | A picker marks at least one line short |
| Pick ticket voided | A ticket stops being valid: the order was cancelled, moved, held or shipped elsewhere |
Fields you can use in conditions and messages: Ticket number, Order number, Order, Location, Channel, Ship service, Status, Lines and Units. Pick ticket events carry no customer name or address.
Actions
| Action | Does |
|---|---|
| Print the pick ticket | Sends the ticket that started the flow to its location’s printer. Start the flow with Pick ticket created. A ticket already printed, or voided, is not printed. Fails if the location has no printer |
| Email the pick ticket | Emails the ticket that started the flow, as a PDF, to the addresses you type (Email these addresses, up to 10). Subject defaults to “Pick ticket … for order …”. The PDF shows the order number, items, bins and quantities, never the customer’s name or city, even when your printed tickets do |
| Create pick tickets | Makes tickets for the orders ready to pick at one Location (paid, open, not yet picked), oldest first. At most limits the orders per run; the most is your Orders in one go setting. Orders that already have a ticket are left alone |
| Print unprinted pick tickets | Sends every ticket that has not printed yet to its location’s printer, oldest ship-by first. Locations takes location codes, comma-separated; leave it empty for every location with pick tickets on. At most: 200 per run by default, 500 at most. A ticket is only ever queued once |
| Create the pick ticket for one order | Makes one order’s ticket at one Location, whatever that location’s Make tickets choice. An order already shipped, cancelled or refunded is skipped with the reason; an existing ticket is returned as it is |
| Move a short order to a location that has it | See below |
Choose Location from the list; it cannot be built from a field. Both Print actions need PrintNode connected.
Move a short-picked order
Move a short order to a location that has it handles a ticket picked short.
- Start the flow with Pick ticket picked.
- Add a condition with + Only if… → + Custom and type
trigger.payload.short == true, so it only runs for short tickets. - Add the action Move a short order to a location that has it and give it a name under Save result as, for example
r. - Add an If / else on the saved result’s Needs a card field being yes, with Add a task card in its Yes lane. Use + Field to put the step’s results (such as What happened (a plain sentence), Products short and Order number) in the card.
What the action does:
- If another location with pick tickets on has the whole order in stock (if several do, the one first in your location priority), the order moves there and a pick ticket is made there. It prints by that location’s Print tickets: automatically switch; when that is off, the Printing result says to print it by hand.
- Otherwise it moves nothing and sets Needs a card: no location has it all, only a split would work, a label is already bought, it is a pickup order, or the order was already moved once.
- It never splits an order, never changes stock, and moves an order automatically at most once.
ℹ️ Note: The flow starts only when the picker finishes the ticket (Finish: mark Picked). Marking a line short does not finish the ticket on its own.
💡 Tip: If the order was already in ShipStation, its ShipStation ship-from warehouse needs to follow the move. Check with ILLUMA support that your account has the flow that updates ShipStation when an order’s location changes before you activate this one.
The full table of what the step decides, and the results it gives, is in Flow recipes.
💡 Tip: You can also send the result to a Microsoft Teams channel with Send a notification. See Notifications, email & webhooks.
Ready-made recipes
Under Flows → From template, in Fulfillment:
- Store: print and email each new pick ticket. For a store that gets an order now and then. Choose the Store and type Email these addresses. When a ticket is made there, it prints on the store’s printer and is emailed as a PDF. Set that store to Make tickets: when an order is paid.
- Warehouse: create and print picks on a schedule (needs scheduled flows). For a busy warehouse that picks in batches. Choose the Warehouse and how often (Every 1h, 2h, 3h or 4h). It makes tickets for the orders ready there, then prints them. Set that warehouse to Make tickets: only from the orders list and flows. It only runs once scheduled flows are switched on for your account.
Both recipes are created in Shadow. Check their runs on Flows → View runs, then click Activate.
ℹ️ Note: On the warehouse recipe, Test run (shadow) shows what it would make and print without doing it. Once the flow is Active, Run now makes and prints tickets straight away. The store recipe starts from Pick ticket created, so it is tested on real tickets in Shadow, not with Run now. See Flow basics.
📸 Screenshot placeholder: Flows → From template with the “Store: print and email each new pick ticket” form open: the Store dropdown, the Email these addresses box and Start as set to Shadow. Use a test location and address.