Skip to main content

How to Identify Post-Purchase Upsell Orders in Shopify

Learn how to reliably tag and identify orders that include a Nosto Post-Purchase Upsell, using Shopify Flow.

Kat Andres avatar
Written by Kat Andres
Updated over 2 weeks ago

Why Order Identification Matters

Tracking which orders included a Post-Purchase upsell lets you filter, report, and automate follow-up actions, which can be critical for fulfillment accuracy and performance analysis. Shopify does not provide a native “upsell” marker, so you need to create a tagging process that fits your workflow.

How to Tag Upsell Orders Using Shopify Flow

Shopify Flow is our recommended way to tag Nosto Post-Purchase Upsell orders automatically. The logic is based on order edits: when a customer accepts an upsell, Shopify edits the original order immediately after payment.

Steps to Create a Tagging Workflow

The following outlines a high-level Shopify Flow that could be used to automatically tag orders edited.

  1. Open Shopify Flow

    • Go to Apps in your Shopify admin, then Shopify Flow

  2. Create a New Workflow

    • Start with the trigger: Order Created.

  3. Add a Condition: Order Edited

    • Add a condition that checks if the order “edited” property is true.

      • Logic: If the order has been edited after creation, continue.

  4. Add Action: Tag Order

    • Action: Add order tags.

    • Enter a tag that works for your operations, e.g. Nosto Upsell.

  5. Save and Activate

    • Name your workflow (e.g. “Tag Nosto Upsell Orders”).

    • Turn it on and test by placing a live order with a Nosto Post-Purchase Upsell.

Example Order Tagging Flow - Shopify Flow

👉 Shopify does not indicate who or what caused an order edit. Any app or manual change made after order creation can trigger this workflow - not just Nosto upsells.

Recommendation:

Test your workflow carefully. You may want to refine your conditions (e.g., check for an increased order total or added product lines). The perfect setup depends fully on your needs and workflows, and can't be defined by Nosto.

Did this answer your question?