Retently records where every Shopify order was placed and turns it into two order properties you can filter on:

They behave like any other Shopify order property. You can target a survey campaign with them, and you can also use them to slice your reporting, so you can compare how your retail customers rate you against your online ones. Both are collected automatically. If your Shopify orders already reach Retently, there is nothing to enable.

Wherever you open the Attributes filter, both properties appear in the property menu under the SHOPIFY PROPERTIES group:

Two things to keep in mind. In the campaign builder, Shopify properties are offered on transactional campaigns only, since those are the ones tied to an order. And the Contacts and Outbox pages do not offer them, because both list contacts and sent surveys rather than orders.

These properties are available on ecommerce accounts.

You need Shopify order data in your account. If you already run Shopify surveys, you have it, and the channel and location values are being collected for you.

If you are just getting started, open your transactional survey campaign, go to the Trigger section, copy the webhook URL and follow the Shopify setup guide. From the moment the webhook is live, Retently collects the order channel and store location on every incoming order.

The value comes straight from Shopify's order source, so it is the same wording Shopify uses:

To use it, add a filter, select Order channel, choose a condition and pick a value. It is a text property, so it accepts the standard text conditions (is, is not, contains, and the rest).

The value dropdown fills in with the channels Retently has already seen on your survey responses, so a new account may show an empty list. You do not have to wait for it. The field accepts typed input (Select or type), so you can enter a value now and it will match as soon as responses arrive. Point of sale orders are always pos, so that is a safe value to type before your first in store response.

Use is not when you want the inverse group. Order channel is not pos covers everyone who did not buy in a store.

Add a filter, select Store location, choose is or is not, then pick a location from the dropdown. Store location supports those two conditions only.

Every location Retently has received an in store order for appears in the list automatically. You do not need any survey responses first, and you do not need to paste an ID. Locations you have named show their name, and any location you have not named yet shows its raw Shopify location ID.

One exception: the Trend builder still lists locations by their raw ID rather than their name. The filter works the same way, it just shows the ID.

Renaming a location never breaks an existing filter. Retently always stores the underlying location ID and only shows the name, so saved filters, exports and the API keep working after a rename.

Raw location IDs like 79793553577 are impossible to tell apart, especially once other people work in the account. Give each one a name once and it will show up everywhere the ID used to.

The table lists every location Retently has ingested orders for, sorted by order volume, with an Orders count and a Last order time. Those two columns are how you recognize an unfamiliar ID: the location with hundreds of recent orders is your busy storefront, and the one with two orders from three months ago is the pop up.

Clearing a name is allowed. The location then shows as its raw ID again.

If the account has no in store orders yet, the page tells you so. Locations appear on their own once the first Shopify point of sale order arrives.

If you want to confirm which Shopify location an ID belongs to:

Copy that ID and match it against the Location ID column on the Retently Store locations page, then name it accordingly.