Starting with API version 2026-04, a tags field is available on all discount types. The Admin API lets you add, update, and remove tags so you can label, group, and organize discounts.
There was no way to categorize discounts, so they were managed manually with code names like "SUMMER_2025_VIP" or custom naming conventions. Cross-cutting grouping was difficult.
All discount types now expose a tags field, and you can add, update, and remove tags via the Admin API. Discounts can be bundled and handled by tag.
summer-sale etc.) are examples to aid understanding and are not listed in the article.
tags A tags field has been added to all discount types, allowing uniform labeling regardless of type.
Tags can be added, updated, and removed through the Admin API.
Provided as a way to efficiently label, group, and organize discounts.
Whether tags can be viewed or edited on the Shopify admin discount screen is not documented. This article is an Admin API announcement.
Whether queries or filtering by tag are supported, and the syntax, are not documented. The article only states that discounts can be organized.
The maximum number of tags, allowed characters, specific mutation names, and field types are not documented. Check the Admin API documentation.
| Aspect | Before (prior to 2026-04) | After (API 2026-04 and later) |
|---|---|---|
| Discount classification | Naming-dependent Managed manually with code names and ad hoc conventions | tags Classified with structured labels |
| Grouping | Difficult to group across types | By tagcan be bundled together |
| API operations | No tags field available | add / update / remove Supported |
| Scope | — | All discount types |
| UI and search support | — | Not documented Check the documentation |
The tags field is available from 2026-04. Older API versions don't have the field at all, so you must first bump the API version you're calling.
tags is available for any discount type — automatic discounts, discount codes, free shipping, etc. There's no note about specific types being unsupported.
Whether tags is visible depends on the API version you call. Bump your app/integration to 2026-04 or later before checking the schema.
tags was added across all discount types. You don't need to branch by type — the same tags-handling logic can be reused horizontally.
Add, update, and remove are all available. You can design tag management as CRUD and easily wire it into sync flows from external systems.
The release says you can "organize" discounts, but there's no mention of query filtering by tag. If you plan to design around tag-driven listing, verify support in the docs first.
Tags are free-text labels. Shopify doesn't assign meaning to them, sodefine a cross-team tag naming convention up front — campaign ID / season / owner / status, etc.Otherwise things go sideways fast. The docs don't list limits or allowed characters either, so confirm those and bake them into your convention.
campaign:◯◯ season:2026-q2 and from then on, always attach a tag at issuance time.ext-id:◯◯ and reconcile/update both sides via API sync.ext-id: etc. are now standardized. Tag-based search support isn't documented, so verify in the docs upfront if you need filter queries.status:to-review expiring-soon tags to discounts matching given conditions (and remove them when no longer applicable), making operational status visible at a glance via tags.