Brand, GTIN and MPN completion

What it is

As part of Optimal WooCommerce Schema, AISA fills in brand and a product identifier (GTIN or MPN) when they are missing from the Product node — fields Google increasingly treats as required in many retail categories. The correct schema.org key is chosen automatically by GTIN length (gtin8, gtin12, gtin13, gtin14 or generic gtin).

Where to find it

Runs automatically when Optimal WooCommerce Schema is enabled (Settings → WooCommerce). There is no separate screen — the values are read from your existing product data.

Requirements & tier

Requires WooCommerce. Brand and identifier must exist somewhere in the product data; AISA does not invent them. No AI cost.

How to use

1. Enable Optimal WooCommerce Schema.
2. Set your product brand via a brand taxonomy (product_brand, Perfect Brands, YITH) or a brand/marca attribute.
3. Set the identifier in WooCommerce's native GTIN field (_global_unique_id, 8.5+), a common custom field (gtin/ean/barcode), an attribute, or _mpn as a fallback.
4. AISA reads the first available source and adds it to the Product node.
5. The right gtin key is picked by digit length; MPN is used only if no GTIN is found.

Questions people ask

• Where does the brand come from? A brand taxonomy first, then a brand/marca attribute.
• Which GTIN sources are checked? WooCommerce native _global_unique_id, then custom fields (gtin/ean/barcode), then attributes.
• What if there is no GTIN? AISA falls back to MPN if present.
• How is gtin8 vs gtin13 decided? By the number of digits in the value.
• Will it overwrite an existing brand/GTIN in the schema? No — it only fills when those fields are empty.

Troubleshooting

If no brand appears, make sure a supported brand taxonomy or a brand/marca attribute is actually assigned. If no identifier appears, put the value in the native GTIN field or a recognized custom field/attribute — AISA never fabricates an identifier.

Related

Optimal WooCommerce Schema · Variant product schema · WooCommerce value pills.