Setup
No setup or toggle inside EasyScan is needed. Every shop with EasyScan installed gets these triggers automatically. In Shopify Flow, create a new workflow and search the trigger picker for "EasyScan" to find any of them by name. Available on every plan.
The trigger definitions are available to installed stores, but the underlying EasyScan action must be available on the store’s plan and successfully occur—for example, purchase-order workflows require Advanced or Pro.
Available triggers
EasyScan Order picked — fires when a pick log is created
EasyScan Order packed — fires when a pack log is created
EasyScan Order fulfilled — fires when a fulfilment log is created
EasyScan Order checked — fires when a check log is created
EasyScan Order ready for pickup — fires when an order is marked ready for pickup
EasyScan Purchase order created — fires when a purchase order is created
EasyScan Purchase order ordered — fires when a purchase order is marked ordered
EasyScan Purchase order received — fires when a purchase order is fully received
EasyScan Purchase order closed — fires when a purchase order is closed
Data available to your workflow
Order triggers (picked, packed, fulfilled, checked, ready for pickup) pass Shopify's own order reference, plus "Processed by" — the name or email of the EasyScan user who did it, blank if unknown.
Purchase order triggers pass plain fields instead — purchase order number, status, supplier, total quantity, received quantity (where relevant), and Processed by. Purchase orders live only in EasyScan, so there's no Shopify resource to reference.
Purchase-order triggers also provide Line items, with SKU, ordered quantity, received quantity and the numeric Shopify variant ID for each included line. Received quantity includes accepted plus rejected units; do not treat it as the quantity added to sellable inventory.
Use the line-item list in your Flow actions when passing PO information to another system. Check the list’s total-count/truncation information before treating it as the complete order. A Flow action requiring a Shopify global variant ID needs the numeric ID converted to that format.
Good to know
Delivery is at-most-once: if Shopify's receive call fails ambiguously (for example, a timeout), EasyScan won't retry that trigger, to avoid running your workflow twice. A Flow delivery failure never blocks or delays the underlying EasyScan action itself.