custom_label_2
The third custom label slot. Typically used for inventory or seasonality flags.
Also known as: custom label 2
Channel support
| Channel | Status | Field name | Notes |
|---|---|---|---|
| Google Merchant Center | Optional | custom_label_2 | — |
| Meta Commerce Manager | Optional | custom_label_2 | — |
| TikTok Shop | Not supported | — | — |
| Pinterest Catalog | Optional | custom_label_2 | — |
| Amazon | Not supported | — | — |
| Bing Merchant Center | Optional | custom_label_2 | — |
Why it matters
After ROAS (label 0) and margin (label 1), inventory or seasonality is often the third most useful dimension. Encoding it as a label lets you build product set rules like 'pause delivery on items with custom_label_2 = low-stock'.
`custom_label_2` is commonly used for inventory or seasonality state. Inventory in particular maps well here because the data is feed-refresh-cadence rather than real-time — slow enough to be a useful "tier" rather than a transactional flag. Items tagged "low-stock" can have campaigns pause delivery (preserves margin on the limited remaining stock); items tagged "overstock" can get aggressive bidding (clear inventory faster).
For pure inventory state, the values that work: in-stock (default, no tag), low-stock (under N days of cover), overstock (over M days of cover). The thresholds vary by category — apparel might consider 7 days low-stock and 60 days overstock; consumables might use 14 days and 30 days. The label is a tier, not a precise count, which is why it works at feed cadence rather than needing real-time API updates.
For seasonality, the same slot works for season codes (AW26, SS27). Items get tagged with the season they belong to, and campaigns can scope to current-season items only. This is especially useful for fashion catalogs where last-season inventory should be promoted differently from current-season inventory.
Format rules
-
Free-form string, max 100 characters
Applies to: Google Merchant Center, Meta Commerce Manager, Pinterest Catalog, Bing Merchant Center
Valid examples
low-stock Inventory urgency flag
AW26 Season code
Common mistakes
yes Boolean-style values are too coarse to be useful
Related fields
custom_label_1 The second custom label slot. Identical to `custom_label_0` at the system level — the convention is to use it for a different segmentation dimension.
Read morecustom_label_3 The fourth custom label slot. Often used for promotional or campaign flags.
Read moreavailability Whether the product can be bought right now. Channels suspend out-of-stock items from delivery automatically — provided the field actually flips when stock hits zero, which is the operational problem most catalogues quietly carry.
Read moreFAQ
Is custom_label_2 the right place for stock-level data?
It's a common choice. The constraint is that custom labels update at feed-refresh cadence, not real-time. For real-time stock levels, use `availability` and `inventory_quantity` directly.
Last reviewed: 26 May 2026
Why wait? Start free.
See your products rewritten in 60 seconds. Add a card only when you go live.
- Start free, no card: import your catalogue and run the feed audit
- 10 free AI credits to see your product titles rewritten
- Go live with a 7-day free trial of Growth ($29/mo) or Pro ($49/mo)
- Pay-as-you-go AI credits after the free 10, from $5