Channel checks need five pieces of product data that WooCommerce does not all have. The field map, under WooCommerce ÔåÆ Channel Readiness ÔåÆ Fields, says where Pro reads each one. Use it when the data already lives somewhere else, such as a feed plugin’s fields, so you do not type it twice.
The five fields
| Field | Default source | Other sources | Where the default source keeps it |
|---|---|---|---|
| GTIN | WooCommerce | Custom field, Attribute | WooCommerce’s own “GTIN, UPC, EAN or ISBN” field on the Inventory tab (meta key _global_unique_id) |
| MPN | Pro | Custom field, Attribute | Pro’s MPN field on the Inventory tab, and on each variation (meta key _sit_wcpg_pro_mpn) |
| Brand | WooCommerce | Attribute, Custom field | WooCommerce’s Brands taxonomy (product_brand) |
| Condition | Pro | Custom field, Attribute | Pro’s Condition field on the Inventory tab (meta key _sit_wcpg_pro_condition) |
| Google product category | Pro | Custom field | Pro’s Google product category field on the Inventory tab (meta key _sit_wcpg_pro_google_category) |
Pro also adds the No identifier exists checkbox (meta key _sit_wcpg_pro_no_identifier), for products that have no GTIN and no MPN, such as custom or handmade items.
Pro’s fields sit in a Channel data group on the Inventory tab, after the GTIN field. A field you map to a custom field or an attribute is no longer shown there, because its value now comes from elsewhere.
Condition falls back to the store default (set on the Fields tab, “new” unless you change it) when a product has none.
Sources
- WooCommerce / Pro: the field shown above.
- Custom field: a post meta key, such as one a feed plugin writes. Letters, digits,
_ - : ., up to 64 characters. The same key is read on variations. - Attribute: a product attribute’s slug, such as
pa_brandorbrand. The first value is used; for brand, any value counts.
When you click Publish in the product editor, Pro judges what you typed, not what was saved before, provided the editor posts the value under the same name as the meta key. A field posted under a different name is judged on its saved value until the product has been saved once. See limits.md.
The GTIN uniqueness check searches WooCommerce’s GTIN or the mapped custom field. A GTIN kept in an attribute is checked for format but not for duplicates.
Meta keys used by common feed plugins
Each key below was read from that plugin’s source code, at the version shown, on 2026-11-12. Plugins change their storage between versions; check yours before mapping. A plugin or field that is missing here could not be confirmed from source.
| Plugin (version checked) | GTIN | MPN | Brand | Condition | Same name in the editor form? |
|---|---|---|---|---|---|
| Google for WooCommerce / Google Listings & Ads (3.10.0) | _wc_gla_gtin | _wc_gla_mpn | _wc_gla_brand | _wc_gla_condition | No: the form posts gla_[] names, so the saved value is judged |
| Facebook for WooCommerce (3.7.6) | fb_gtin | fb_mpn | fb_brand | fb_product_condition | Yes, for MPN, brand and condition |
| CTX Feed (8.0.44) | woo_feed_gtin | woo_feed_mpn | ÔÇö (a taxonomy, not a meta key) | ÔÇö | Yes, on the product |
Notes:
- CTX Feed stores a variation’s values under different keys (
woo_feed_gtin_var,woo_feed_mpn_var). Pro reads the product’s mapped key on variations too, so CTX Feed’s variation GTINs and MPNs are not seen. Keep variation GTINs in WooCommerce’s own GTIN field. - Facebook for WooCommerce writes
fb_gtinonly from an attribute you map in its settings; its product form has no GTIN field. A GTIN mapped tofb_gtinis therefore judged on its saved value. - WooCommerce 9.1 and later has a GTIN field of its own. If a feed plugin can read it, leaving GTIN on the default source avoids a second copy.