Product Tag Actions
Product Tag Actions in Arigato allow you to automatically add tags to products based on specific attributes such as title, price, inventory, vendor, and more. These actions are designed to be used within workflows triggered by events like Product Created, Product Updated, or manual runs.
The legacy "Tag product by attributes" action has been deprecated and replaced with individual, more flexible tag actions. Existing workflows using the legacy action will continue to function, but we recommend migrating to the new actions for improved control and clarity.
Actions
- Tag by Keyword
- Tag by Product Type
- Tag by Taxonomy Category
- Tag by Product Vendor
- Tag by Product Variant Options
- Tag by Quantity
- Tag by Price
- Tag by Weight
- Tag on Sale
- Tag by Template
- Tag by Collection
How Tag Actions Work
Each Product Tag Action evaluates a specific attribute and applies tags when conditions are met. These actions are evaluated independently, meaning a product can receive multiple tags from different actions in the same workflow.
When using prefixes or suffixes, the final tag is dynamically constructed using the product's attribute value. Formatting (such as lowercase or hyphenation) is applied before the prefix or suffix.
prefix: type_+Shirts→type_shirtssuffix: _vendor+Nike→nike_vendor
Most attribute-based tag actions behave as a synchronization:
- If a product matches the rule, the tag is added.
- If a product no longer matches the rule, the tag is automatically removed.
This ensures that tags always reflect the current state of the product as attributes change over time.
⚠️ Important: Use a Prefix or Suffix to Prevent Unintended Tag Removal
If no prefix or suffix is configured, the action evaluates against all existing product tags. During synchronization, any tags that do not match the current rules may be removed.
This can lead to unintended tag cleanup, especially if your products already use tags for merchandising, filtering, or integrations.
Best practice: Always use a unique prefix or suffix (e.g., type_, vendor_, auto_) to ensure only tags managed by this action are synchronized, while all other tags remain untouched.
Configuring the Action
To use Product Tag Actions in your workflow:
- Navigate to your workflow in Arigato.
- Add a trigger such as Product Created or Product Updated.
- Click Add Action.
- Select one of the Product Tag Actions.
- Configure the fields based on the selected action type.
- Save and enable the workflow.
You can add multiple tag actions within the same workflow. Each action runs independently and can apply different tags based on its conditions.
Available Actions & Configuration
Tag by Keyword
Adds a tag when specific keywords or phrases are found in the product title or description.
| Field Name | Description | Example |
|---|---|---|
| Search in | Select whether to search the product title, description, or both. | Title & Description |
| Tag | The tag to apply when a match is found. | summer |
| Keywords or phrases | Comma-separated list of keywords (not case-sensitive). | beach, summer, vacation |
Note: Tag by Keyword is an add-only action and does not remove tags if conditions are no longer met.
Tag by Product Type
Adds a tag based on the product's custom product type.
| Field Name | Description | Example |
|---|---|---|
| Tag prefix / suffix | Optional text added before or after the product type. | type_{{product_type}} |
| Format | Controls formatting (lowercase, hyphenated, etc.). | lower_hyphen |
Tag by Taxonomy Category
Adds a tag based on the Shopify taxonomy category.
| Field Name | Description | Example |
|---|---|---|
| Tag prefix / suffix | Optional text added to the category value. | cat_{{category}} |
Tag by Product Vendor
Adds a tag based on the product vendor.
| Field Name | Description | Example |
|---|---|---|
| Tag prefix / suffix | Optional text added to the vendor name. | vendor_{{vendor}} |
| Format | Formatting options (lowercase, hyphen, etc.). | lower |
Tag by Product Variant Options
Adds tags for each variant option in the format Name:Value.
| Field Name | Description | Example |
|---|---|---|
| Tag prefix / suffix | Optional text added to each variant option. | opt_{{option}} |
Tag by Quantity
Adds a tag when inventory falls within defined ranges.
| Field Name | Description | Example |
|---|---|---|
| Tag | Tag applied when range matches. | low-stock |
| Min quantity | Minimum value (inclusive). | 0 |
| Max quantity | Maximum value (inclusive). | 10 |
Tag by Price
Adds a tag when product price matches defined ranges.
| Field Name | Description | Example |
|---|---|---|
| Tag | Tag applied when range matches. | premium |
| Min price | Minimum price (inclusive). | 100 |
| Max price | Maximum price (inclusive). | 500 |
Tag by Weight
Adds a tag based on product weight ranges.
| Field Name | Description | Example |
|---|---|---|
| Tag | Tag applied when range matches. | heavy |
| Min weight | Minimum weight. | 1 |
| Max weight | Maximum weight. | 5 |
| Unit | Measurement unit (g, kg, oz, lb). | kg |
Tag on Sale
Adds a tag when the product price is lower than the compare-at price.
| Field Name | Description | Example |
|---|---|---|
| Tag | Tag applied when product is on sale. | sale |
Tag by Template
Adds a tag based on the assigned product template.
| Field Name | Description | Example |
|---|---|---|
| Tag prefix / suffix | Optional text added to template name. | tpl_{{template}} |
Tag by Collection
Adds a tag when a product belongs to a specified collection.
| Field Name | Description | Example |
|---|---|---|
| Collection name | Name of the collection to match. | Summer Collection |
| Match type | Choose "contains" or "equals". | contains |
| Tag | Tag applied when condition matches. | summer |
Example Configuration
This example workflow automatically tags products based on multiple attributes:
| Step | Configuration |
|---|---|
| Trigger | Product Updated |
| Action 1 | Tag by Product Type → type_{{product_type}} |
| Action 2 | Tag by Price → premium (100 - 500) |
| Action 3 | Tag by Quantity → low-stock (0 - 10) |
If a product's attributes change, tags are automatically synchronized to reflect the current state.
Troubleshooting & Usage Tips
Tags are unexpectedly removed: This commonly occurs when no prefix or suffix is used. Add a unique prefix/suffix to ensure only managed tags are updated.
Tags are not being added or removed: Ensure your workflow uses a trigger like Product Updated so conditions can be re-evaluated.
Keyword matches not working: Verify keywords match the product content and check for formatting differences.
Inventory-based tags not updating: Confirm inventory tracking is enabled.
Sale tag not applied: Ensure the compare-at price is higher than the current price.
Duplicate tags: Shopify ignores duplicate tags automatically.
Credit Cost
Each Product Tag Action incurs a cost of one Action Credit on Lite plans and is unlimited on Unlimited plans.
Custom Actions
Combine multiple Product Tag Actions to build structured, automated tagging systems. Using prefixes or suffixes ensures safe synchronization and prevents unintended changes to unrelated tags.
When migrating from the deprecated "Tag product by attributes" action, recreate each rule as a separate action for better control and maintainability.