EasyScan SKU & Barcode

EasyScan SKU & Barcode

Integrations

Troubleshooting Shopify Flow triggers for EasyScan

Fix the most common problems when sending EasyScan events to Klaviyo or another app through Shopify Flow.

Last updated on 13 Nov, 2026

EasyScan can start a Shopify Flow workflow when an order is picked, packed, fulfilled or checked. Most problems we see are not with the trigger itself but with how the workflow reads the order, so this article covers the variables to use and the mistakes that make data go missing.

New to the triggers? Start with the article "Shopify Flow triggers for EasyScan".

Step 1: Use the right variables

EasyScan's order triggers pass Shopify's own order, so you can use any order variable Flow offers. The ones merchants ask for most:

  • Customer email: {{order.customer.email}}

  • Customer first name: {{order.customer.firstName}}

  • Customer last name: {{order.customer.lastName}}

  • Order name, for example #1042: {{order.name}}

  • Order status page link: {{order.statusPageUrl}}

  • Who did it in EasyScan: choose "Processed by" under the EasyScan trigger in Flow's variable picker. It is blank when EasyScan can't tell which user did the action.

Pick variables from Flow's "Add a variable" picker rather than typing them, so the spelling is exact.

Step 2: Check your JSON for a trailing comma

If your event arrives in Klaviyo (or another app) but its properties are empty, look at the last line of your properties block. A comma after the final property makes the whole block invalid, and Flow sends the event without it. There is no error message.

Every property line ends with a comma except the last one. If your final line reads "email": "{{order.customer.email}}", with a comma at the end, delete that comma.

Step 3: Test with a real order, not the Test button

Flow's "Test your workflow" button runs with sample data, not a real EasyScan event, so customer fields can come through empty even when your workflow is set up correctly.

To test properly, turn the workflow on, then pick, pack or fulfil a real or test order in EasyScan. Open the workflow's recent runs in Flow to see exactly what was sent.

Good to know

  • Line items are a list. A single variable can't print them all, so use a loop in the field where you build your message, and test it on a real order with more than one item.

  • Each event is sent once. If Shopify does not confirm it received the event, EasyScan does not send it again, so your workflow never runs twice for the same action.

  • Purchase order triggers send plain fields (number, status, supplier, quantities and line items) because purchase orders live in EasyScan, not Shopify.

Having trouble with this process? Contact support at https://506.io/support

Was this page helpful?
Previous

EasyScan Affiliate Program FAQ

Next

Please contact us through the EasyScan app for further support