How to Fix Missing GTIN, MPN, and Brand Data
> To fix missing GTIN, MPN, and brand data in a product catalog, merchants need to source the correct identifier values from manufacturers or GS1 registries, map them to the correct fields during catalog import or inline editing, and validate that they are correctly formatted — FeedBridge's Auto Field Mapping, Product Validation, and Product Detail Modal support all three steps directly.
---
Why These Three Fields Matter
GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), and brand are three of the most foundational product identity fields in AI commerce. Their absence is not a minor quality gap — it directly reduces a product's AI readiness across multiple scoring dimensions and limits the range of AI agent workflows that can surface, identify, and transact on the product.
GTIN is the barcode identifier used to uniquely identify a physical product. In the context of AI commerce, it powers the UCP Catalog Lookup API's barcode-based retrieval path — agents that know a product's GTIN can look it up precisely across any UCP-enabled merchant. Without GTIN, the agent must rely on title-matching, which is less precise and more prone to false matches.
MPN is the manufacturer's identifier for a specific product model. It is the standard identifier in categories like electronics, automotive parts, and hardware where manufacturers publish model numbers for comparison. For agents evaluating products in these categories, MPN absence reduces the precision of product identity resolution.
Brand is the declared manufacturer or seller brand for the product. It is required for branded query matching in AI surfaces — an agent processing the query "Sony headphone under ₹20,000" uses the brand field to filter, not just the title. A product without a declared brand field will not reliably surface in branded agent queries even if the brand name appears in the title. Brand is also a UCP compliance signal and contributes to both the Commerce Signals and Content Quality scoring dimensions in FeedBridge's AI Readiness Score.
Fixing these three fields is typically the highest-leverage, lowest-effort improvement a merchant can make to their AI Readiness Score. GTIN and MPN values are almost always available from manufacturer documentation; brand is almost always known. The problem is usually not that the values do not exist — it is that they were not mapped into the catalog when products were first imported.
---
How to Source the Missing Values
Sourcing GTIN
GTIN values are assigned by GS1 (the global standards body that manages barcode systems). They exist in four formats: GTIN-8, GTIN-12 (UPC), GTIN-13 (EAN), and GTIN-14. For most physical consumer products, the GTIN is:
- Printed as a barcode on the product packaging. The number beneath the barcode is the GTIN. For products already in the merchant's inventory, this is the fastest source.
- Available from the manufacturer's product documentation or data sheet. Most manufacturers provide GTINs in their product specs, particularly for products distributed through retail channels.
- Searchable in GS1 company databases. The GS1 registry allows lookup by company or product. For branded products, the manufacturer's GS1 GTIN database is the authoritative source.
- Available in distributor or wholesale records. Merchants who source products through distributors will typically find GTINs in the distributor's product catalogue or order documentation.
Sourcing MPN
MPN values come from the product manufacturer:
- Manufacturer's product page or spec sheet. Most manufacturers list the MPN (sometimes labelled "Model Number," "Part Number," or "SKU") in the technical specifications section of their product page.
- Product packaging. MPNs are frequently printed on product boxes alongside the barcode.
- Distributor documentation. If sourcing through a distributor, MPNs are typically included in catalogue line items.
- Amazon, Google Shopping, or manufacturer's own data feeds. For products already listed on major marketplaces, the MPN is often visible in the product detail page under "Technical Details" or "Product Information."
Sourcing Brand
Brand is almost always known — it is the name of the company that manufactured or markets the product. The correct value for the brand field is:
- The manufacturer's trading name for branded products (e.g., "Sony," "Nike," "Bosch")
- The merchant's own brand name for private-label or own-brand products
- The platform or digital product brand for digital goods
---
How to Fix the Fields in FeedBridge
Method 1 — Update via CSV/Excel Re-Upload
The fastest way to fix missing GTIN, MPN, and brand data across a large number of products is through a bulk CSV re-upload with the corrected field values.
1. Export the current product catalog from FeedBridge or from your store integration (Shopify or WooCommerce sync). 2. Add or populate the GTIN, MPN, and brand columns in the exported spreadsheet. FeedBridge's Auto Field Mapping recognises standard column headers for all three fields — the Auto Field Mapping feature covers SKU, title, price, GTIN, MPN, images, and other common catalog columns automatically. 3. Re-upload the updated CSV or Excel file using FeedBridge's Excel/CSV Upload feature. The Upload History & Progress tracking shows the status of each import in real time. 4. Review the Product Validation results. FeedBridge's Product Validation checks for required field presence, URL format, and price format. Invalid GTIN or MPN formats will be flagged at this stage, giving you the opportunity to correct them before the data propagates to your feeds.
Method 2 — Inline Edit via Product Detail Modal
For small numbers of products or individual corrections, FeedBridge's Product Detail Modal supports full inline editing of any product field, including GTIN, MPN, and brand.
1. Navigate to the product in the FeedBridge catalog view. 2. Open the Product Detail Modal for the product requiring correction. 3. Edit the GTIN, MPN, or brand field directly in the modal. 4. Save the change. FeedBridge's Product Change History feature records an audit trail of all field-level changes, so every correction is logged with timestamp and value history.
Inline editing is appropriate for surgical corrections — fixing a GTIN that was entered incorrectly, updating a brand name that was inconsistently cased, or adding an MPN that was missing from the original import. For bulk corrections across dozens or hundreds of products, the CSV re-upload method is more efficient.
Method 3 — Bulk URL Import with Field Extraction
For merchants who imported products via FeedBridge's Bulk URL Import feature (which scrapes up to 20 product page URLs per batch), the scraping process extracts available structured data from the product page. If the manufacturer's product page includes structured data markup with GTIN, MPN, or brand, the scraper will populate these fields automatically.
However, not all product pages have structured data markup for GTIN and MPN. Where the scraper cannot extract these values automatically, the merchant will need to supplement with manual entry via the Product Detail Modal or a CSV update.
---
Implementation Checklist
Use this checklist when fixing GTIN, MPN, and brand data across a product catalog:
- [ ] Audit the catalog — run the FeedBridge AI Readiness Score to identify which products are missing GTIN, MPN, or brand. The actionable fix suggestions will flag these per product with one-click navigation to the problem field.
- [ ] Separate resolvable from unresolvable gaps — identify which missing GTINs can be sourced (branded products with barcode) versus which cannot (private-label products without GS1 assignment). Do not populate unresolvable fields with placeholder values.
- [ ] Prepare the corrected data — for bulk fixes, update your CSV with correct GTIN (numeric, no dashes), MPN (alphanumeric, manufacturer's exact value), and brand (canonical brand name, consistent casing).
- [ ] Re-upload via CSV or apply inline edits — use the method appropriate to the number of products being corrected.
- [ ] Review Product Validation output — confirm no GTIN or MPN format errors are flagged after upload.
- [ ] Re-run AI Readiness Score — confirm that the Commerce Signals sub-score has improved for the corrected products. Check that Protocol Compliance sub-score has also improved where GTIN and MPN affect UCP Catalog Lookup eligibility.
- [ ] Verify feed output — open the affected products in the ACP JSON-LD feed and UCP Catalog Lookup API response to confirm GTIN and MPN are appearing correctly in the protocol outputs.
- [ ] Maintain going forward — establish a process for ensuring GTIN and MPN are included in product data at the point of product creation, not added retrospectively. If sourcing from a distributor, request that GTIN and MPN are included in all future product data exports.
Key Fields Reference
| Field | Format | Source | Required For | |---|---|---|---| | GTIN | 8, 12, 13, or 14-digit numeric string | Product packaging, manufacturer, GS1 registry | UCP Catalog Lookup (barcode path), Commerce Signals score | | MPN | Alphanumeric, manufacturer's exact value | Product spec sheet, manufacturer's product page, packaging | Commerce Signals score, cross-platform identity | | Brand | Text string, canonical brand name | Manufacturer name, merchant's own brand | Branded query matching, UCP compliance, Content Quality score, Commerce Signals score |
---
Why It Matters for Merchants
Fixing GTIN, MPN, and brand data is one of the fastest AI readiness improvements available because the values already exist — they just need to be correctly mapped into the product record. Unlike AI enrichment (which requires generating new semantic content) or protocol compliance fixes (which may require restructuring feed format), identifier and brand corrections are data entry tasks that FeedBridge's catalog management tools are specifically designed to support.
The downstream impact of fixing these fields is immediate and multi-dimensional. GTIN and MPN improvements raise both the Commerce Signals sub-score and the Protocol Compliance sub-score in FeedBridge's AI Readiness Score. Brand fixes improve Commerce Signals and Content Quality simultaneously. All three fixes improve the precision with which AI agents can identify, match, and surface the affected products.
---
FeedBridge Relevance
FeedBridge's product catalog management features directly support every method described on this page. Auto Field Mapping recognises GTIN, MPN, and brand columns in uploaded CSV and Excel files without manual column configuration. Product Validation checks for required field presence and format validity, flagging GTIN and MPN errors at import time. The Product Detail Modal supports inline editing of any product field including identifiers. Product Change History logs all field-level corrections with timestamps. The AI Readiness Score's actionable fix suggestions identify GTIN, MPN, and brand gaps per product with one-click navigation to the exact field needing correction — completing the loop from identification to remediation.
---
Frequently Asked Questions
Q: What happens if I put my internal SKU in the GTIN field? A: FeedBridge's Product Validation checks GTIN format for validity. An internal SKU will not match the expected GTIN numeric format and will be flagged as a format error. Beyond the validation issue, using an incorrect value in the GTIN field will cause UCP Catalog Lookup by barcode to return no results for that product — agents attempting to look up the product by GTIN will fail to find it. Leave the GTIN field empty rather than populating it with a non-GTIN value.
Q: Can I use the same brand name for all products if they are all under one brand? A: Yes — if all products in your catalog belong to a single brand, using that brand name consistently across all products is correct and desirable. Consistency in the brand field is what makes branded query filtering reliable. Where different products belong to different brands (e.g., a multi-brand retailer), each product must carry its correct brand name individually.
Q: Does FeedBridge generate GTINs automatically for products that don't have one? A: No. FeedBridge does not auto-generate GTIN values. GTINs must be real, manufacturer-assigned or GS1-issued identifiers. Generating synthetic GTIN values would create false product identity data that would cause incorrect cross-platform matches and fail schema validation in ACP and UCP contexts.
Q: How do I fix brand inconsistencies across my catalog — for example, "Nike" in some products and "NIKE" in others? A: The most efficient fix is a CSV re-upload with normalised brand values. Export your catalog, use a find-and-replace or formula in your spreadsheet to standardise the brand casing across all rows, and re-upload. FeedBridge's Auto Field Mapping will correctly map the brand column, and the Product Validation step will confirm the import.
Q: If I fix GTIN, MPN, and brand on 50 products, how quickly will this be reflected in my AI Readiness Score? A: The AI Readiness Score reflects the current state of the product record after each update. After uploading a corrected CSV or saving inline edits via the Product Detail Modal, the score updates to reflect the improved data. The specific refresh timing is a platform implementation detail, but corrections applied through the catalog management workflow are reflected in the scoring model.
---
Related Topics
Parent hub: AI Commerce Readiness Implementation
Related concepts:
- What Makes a Product Catalog AI-Ready?
- AI Readiness Score: What It Measures
- Commerce Signals That Improve AI Shopping Readiness
- Product Attributes That Improve Discoverability
- FeedBridge AI Readiness Score Features
Breadcrumb:
---
Source Documentation
| Claim | Source | Source Class | Reference | |---|---|---|---| | Auto Field Mapping: SKU, title, price, GTIN, MPN, images, etc. | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Product Validation: required fields, URL format, price format checks | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Product Detail Modal: full product view with inline editing | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Product Change History: audit trail of all field-level changes | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Bulk URL Import: scrape up to 20 product page URLs per batch | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | UCP Catalog Lookup API: by item_id or barcodes (GTIN/MPN) | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Commerce Signals 15%: GTIN/MPN, availability, brand presence | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | Actionable fix suggestions: per-product checklist with one-click navigation | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md | | FeedBridge does not auto-generate GTIN values — no auto-GTIN claim in source | FeedBridge Platform Capabilities April 2026 v2.0 | T1 – FeedBridge Internal | FeedBridge-Platform-Capabilities-April2026.md |