> For the complete documentation index, see [llms.txt](https://docs-shpf.bsscommerce.com/b2b-wholesale-solution/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-shpf.bsscommerce.com/b2b-wholesale-solution/customer-management/auto-tags/automatically-tag-orders-and-customers.md).

# 🏷️ Automatically Tag Orders & Customers

Streamline your B2B workflows by letting tags assign themselves. The **Auto Tag** module automatically labels customers or orders when certain conditions are met—saving you time and giving you deeper insights into buyer behavior.

## 🔧 How to Set Up Auto Tag Rules

**1. Enable & Begin Configuration**

* In **Customer Management**, enable the **Auto Tags** feature.
* Then go to **Configuration** and click **Add rule** to start building a tagging rule.

**2. Define General Info**

* Give your rule a **name** (e.g. “Big Orders Tagger”).
* Choose whether the rule is **enabled** or **disabled** (you can configure it now and turn it live later).
* Under **Events**, select one trigger event from options like:

  * **Customer Created** (when a new customer account is created)
  * **Order Created**
  * **Order Paid**
  * **Order Fulfilled**
  * **Order Cancelled**

  If you pick **Customer Created**, you can optionally tie the rule to a specific registration form.

**3. Set Conditions**

Decide **what exactly triggers** the tag.

* **Field**: Choose which field to inspect (e.g. Email, Order Amount, etc.).
* **Operator**: Options include “Contains”, “Does not contain”, “Equals”, “Greater than”, “Less than”.
* **Value**: Enter the specific text or number for comparison.

Examples:

* Tag all new customers whose **email contains** “company.com”.
* Tag orders with **amount greater than** 20,000.

**4. Define Tagging Action**

What happens when the rule matches?

* **Add Tag**: Attach a tag (e.g. “Big Order”) to the order or customer.
* **Remove Tag**: Optionally remove an existing tag if it no longer applies.

You decide which entity is tagged (the order, the customer, or both).

***

## 🔄 Backfill Tags to Existing Data

Once your rule is published, you can immediately apply it to your **past orders and customer records**:

* Use **Apply to previous customers & orders**
* Choose a rule and hit **Submit**, and the system will tag all existing records that meet the rule’s conditions
* You can also **remove tags** in bulk using the same interface

***

## 📋 Use Cases & Examples

* Tag orders over $20,000 with “Big Order” so you can filter or trigger special workflows
* Tag customers whose emails contain your business domains to auto-classify “Partner” accounts
* Automatically remove tags if a condition no longer holds

{% hint style="info" %}
If you have problems using the feature, feel free to reach us at [**support-sbc@bsscommerce.com**](mailto:support-sbc@bsscommerce.com) or [**Live Chat**](https://go.crisp.chat/chat/embed/?website_id=9f64b5a9-1a02-4190-93b8-8ef56b19f740)**.**
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs-shpf.bsscommerce.com/b2b-wholesale-solution/customer-management/auto-tags/automatically-tag-orders-and-customers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.