Which conditions can an order automation use to decide which orders it acts on?

An order automation can check the order’s sales channel, tags, financial status, source integration, fields, and metadata, and a fulfillment order’s building. The conditions you can pick depend on the trigger. Fulfillment Ready automations do not offer conditions.

• Sales Channel: is, is not, is any of, or is none of. Use it to limit an automation to one sales channel.
• Order Tags: include all of, include any of, exclude all of, match exactly, is empty, or is not empty. A tag must match exactly, including capital letters.
• Financial Status: Paid, Partially paid, Pending, Authorized, Partially refunded, Refunded, or Voided.
• Order Source Integration: the integration the order came from, or blank.
• Order Dynamic Field: compares an order field, such as Order number, Status, Ship-to email, Units, Shipping cost, or Expected ship date, with a value. It is available on Order Created and Order Approved.
• Order Metadata: looks up a property in the order data the source system sent, by its path, such as note_attributes for Shopify. It checks whether the property exists, equals a value, or contains text, or whether a list has an item with a given field value or matching several fields.
• Building: Fulfillment Created only. It checks the fulfillment order’s building.
• Fulfillment Shipping Address: Fulfillment Created only. Check country code, state, city, postal code, or address lines. Comparisons ignore case and use the fulfillment’s address override when present, otherwise the order’s address.

Conditions sit in groups. In each group, choose Any or All. Groups are joined with And. Each action can also have its own conditions, so one automation can treat orders differently by tag, for example by giving one action an Order Tags condition and another action the opposite condition.

When an order does not match the automation’s conditions, Endless does not record a run.