Automatically Tag Orders & Customers
Streamline your B2B workflows by letting tags assign themselves. The Auto Tag module labels customers or orders automatically when a Shopify event happens and your conditions match, so your pricing, access and marketing segments stay up to date without manual work.
How to Set Up Auto Tag Rules
Section titled “How to Set Up Auto Tag Rules”The rule page has three cards: Rule, When (the event and the conditions) and Actions. A Make Auto Tags live card at the top shows the setup checks and a Live (or Not live yet) badge.
1. Enable & Begin Configuration
Section titled “1. Enable & Begin Configuration”- Go to B2B customers > Auto Tags and switch the module on.
- Click Add rule.


2. Basics
Section titled “2. Basics”- Give your rule a name (for example “Big Orders Tagger”).
- Set it to Enable or Disable (you can configure it now and turn it on later).
- Choose one Event that triggers the rule:
| Event | Fires when |
|---|---|
| Customer created | A customer signs up through the registration form chosen in the rule |
| Order created | An order is placed |
| Order paid | An order is paid |
| Order fulfilled | An order is fulfilled |
| Order canceled | An order is canceled |
With Customer created, choose the form in Registration form so the fields of that form become available as conditions.


3. Conditions
Section titled “3. Conditions”Choose whether the record must match all conditions or any condition, then add condition rows (Field, operator, Value). Click Add another condition for more rows.
Customer created rules can check:
- Default Field: Display Name, Email, First Name, Last Name. On a multi-step form only Email is offered.
- Custom Field: any field of the selected registration form (for example Company, Country, City or your own questions).
- Operators: Contains, Does not contain, Is equal to, Is not equal to. For Country you can type the name (
United States) or, with Is equal to / Is not equal to, the 2-letter code (US).

Order event rules can check:
| Group | Fields |
|---|---|
| Customer account | Display name, Email, Customer tags, Order item, Total spent |
| Customer shipping address | City, Country, Province, Postcode |
| Customer billing address | City, Country, Province, Postcode |
| Product info | Product name, Sku |
| Order info | Number of products, Order quantity, Order amount, Order weight, Total amount of paid orders, Total number of paid orders, Total weight of paid orders |
- Text fields use Contains, Does not contain, Is equal to, Is not equal to; Sku also offers Starts with, which matches if any line item’s SKU starts with your value.
- Number fields use Is equal to, Greater than and Less than.
- Total amount of paid orders, Total number of paid orders and Total weight of paid orders (Order created and Order paid rules only) use
>,<,>=,<=and a period: within 1, 7, 15, 30, 45 or 60 days.

Order weight condition (order events only)
On Order created, Order paid, Order fulfilled, and Order canceled rules, the Order info group includes Order weight (the total weight of the order) next to Order quantity and Order amount.
- Select Order weight as the field.
- Select an operator: Is equal to, Greater than, or Less than.
- Enter the value, then pick its unit in the Weight unit dropdown next to it:
g,kg,lb, oroz(defaultg).

The app converts your value and the order’s total weight to the same unit before comparing, so a rule set in kg works for a store that records product weights in lb.
Total weight of paid orders condition (Order created and Order paid only)
Tag customers by how much they buy by weight, for example a Tier-1000kg tag once a customer has bought 1,000 kg in 30 days.

- Select Total weight of paid orders as the field.
- Pick the period (within 30 days, for example) and an operator:
>,<,>=or<=. - Enter the value and pick its unit:
g,kg,lboroz.
The app adds up the weight of the customer’s orders that were fully paid in that period (the period counts from the payment date). Orders refunded after being paid in full still count. The tag is added on the order that reaches the threshold.
4. Actions
Section titled “4. Actions”Add one or more action rows; click Add another action for more. The actions depend on the event:
| Event | Available actions |
|---|---|
| Customer created | Add customer tag, Add customer note, Mark customer as tax exempt |
| Order events | Add customer tag, Remove customer tag, Add customer note, Add order note, Add order tag, Remove order tag |
For tag actions, enter one or more tags separated by commas, for example wholesale,vip.

Click Save. The rule runs the next time its event happens.
Backfill Tags to Existing Data
Section titled “Backfill Tags to Existing Data”Apply a rule to your past customers and orders:
- On the Auto Tags page, click Apply to existing customers.
- The page has two sections:
- Apply a rule to existing customers or orders: choose Existing customers or Existing orders, pick the rule in Rule, then click Apply tags.
- Remove customer/order tags: choose Customer tags or Order tags, use Select tags to pick the tags to remove, then click Remove tags. This removes the tags only; your rules are not changed.
- The job runs in the background with a progress banner, so you can keep using the app. When it finishes, the banner shows how many records were updated and lists any failures with the reason.


Auto Tag History
Section titled “Auto Tag History”Every tagging action is recorded, so you can check what was applied and when.
- On the Auto Tags page, click History.
- Switch between Customers with tag updates and Orders with tag updates.
- Each row shows the customer or order, the Rule, Added Tags, Removed Tags, Updated Time and Updated by. Page through the list or sort it to find a record.
Use it to confirm a rule fired, to see which rule tagged a customer or order, and to spot rules that match more records than expected.

Export Rules
Section titled “Export Rules”On the Auto Tags page, open More actions > Export. It opens a page with an Export button that downloads your rules as a CSV. Because a rule can have several conditions and actions, the file uses one row per condition/action pair, so one rule can span several rows. The Export history list on that page lets you download recent exports again.

Use Cases & Examples
Section titled “Use Cases & Examples”- Tag high-value customers: Event Order paid, condition Order amount Greater than 500, action Add customer tag
high-value. - Classify partners at sign-up: Event Customer created, form Wholesale Registration Form, condition Email Contains
@partner.com, action Add customer tagpartner. Your Custom Pricing or BSS B2B Lock rules for thepartnertag then apply right away. - Tag by country from the registration form: Event Customer created, form Wholesale Registration Form, condition Country Is equal to
US, action Add customer tagus-wholesale. - Clean up on cancellation: Event Order canceled, action Remove order tag
priority.
- Auto TagsAuto Tags adds tags to customers and orders automatically based on rules you set, so you can segment buyers and trigger workflows without manual work.
- B2B Portal: One Storefront Page for Your B2B CustomersTurn on the B2B Portal to give signed-in B2B customers one storefront page for their account with you. Set it up, add the links and see what customers see.
- Registration FormsRegistration Forms let wholesale buyers apply for an account, so you can review, approve and tag them before they see your B2B prices.