Merchant Center catalog operations workshop / 5 MIN READ
Connect the certification attribute to the exact certified product
Create a certification evidence record linking the sold model to an applicable supported scheme and verified reference.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-07
A certification-looking code is not evidence that the listed variant holds that certification. Establish the authority, scheme and exact product match before encoding a compliance-related claim.
What you will leave with: Create a certification evidence record linking the sold model to an applicable supported scheme and verified reference.
Use this when
- A supplier provides energy-label or other certification data for catalog export.
- A feed warning requests certification information or an automatic match appears incorrect.
Not legal advice, certification issuance, a product-safety assessment or permission to infer compliance from a family resemblance.
Establish applicability before populating the field
Google's certification documentation describes supported schemes and subattributes including authority, name and, depending on the scheme, code or value. It also notes that certification information may be added automatically from product identifiers. Verify the current scheme, country and product requirements rather than assuming every certificate fits the attribute.
Ask the compliance or product-information owner which scheme applies to the exact offer and target market. Keep legal applicability separate from platform support. A field being optional in a general specification does not establish that the business has no labeling obligation, and a valid-looking schema does not establish regulatory compliance. Catalog staff should transmit approved evidence, not make the underlying certification decision.
Match the evidence to the actual model and configuration
Obtain the authoritative record or manufacturer-supplied evidence appropriate to the scheme. Compare model number, relevant variant details and the product identifier with the sold item. Similar model names can cover different capacities, generations or regional configurations with different certified characteristics.
Record the evidence source, retrieval date, responsible owner and any stated validity or replacement information. Do not copy a code from a visually similar product or from a competitor's listing. A public registry reference may be useful evidence, but a search result alone is not a completed identity match. Resolve discrepancies with the qualified owner and keep unresolved records out of the approved certification mapping.
Encode the supported scheme without flattening its meaning
Maintain authority, scheme name, identifier and any required value as distinct fields. Follow the current format for the actual source type. Avoid concatenating a supplier's free-text certificate description into a single field and hoping the platform interprets it. Validate allowed combinations and duplicate entries before release.
Keep separate claims separate. An energy-efficiency classification does not establish product safety, repairability or universal environmental superiority. Do not expand the meaning in a title or description simply because a certification attribute is present. If the product has several legitimate certifications, verify each supported representation and its own evidence rather than treating one document as proof of every badge in the marketing material.
Inspect processed claims and maintain evidence changes
After processing, compare the displayed or stored certification with the approved mapping, including any automatic enrichment. An unexpected value can originate from an identifier mismatch rather than the certification file itself. Trace both possibilities before overwriting fields. A correction should address the cause and preserve the accurate product identity.
Review the record when the model, supplier documentation, scheme or target market changes. Keep replacement and discontinued model evidence distinguishable so a new version does not inherit an obsolete claim. Escalate apparent withdrawal or conflicting certification information to the qualified owner before further publication. The acceptance result is a traceable, correctly scoped data representation; it is not a new certification, a legal opinion or a guarantee of platform eligibility.
Make the reasoning concrete.
A fictional appliance seller receives one energy-label reference for a model family containing several capacities. Its importer copies that code to every variant because the brand and series name match.
Apply the family reference broadly
Opening: Use the same code for all similar models.
Hypothesis: Every row has a populated certification field.
Risk: Some offers may assert a certification that belongs to a different configuration.
Verify exact model evidence
Opening: Match each sold configuration to its authoritative scheme record before approving the mapping.
Hypothesis: The submitted claim remains tied to the actual product.
Risk: Unresolved variants require supplier or compliance-owner follow-up.
The team verifies model-specific evidence and checks the supported scheme fields. It investigates automatic matches as well as manual submissions and does not infer broader safety or environmental claims.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Applicability
Which qualified owner confirms the scheme and target-market relevance?
Identity
Does the evidence name this exact model and configuration?
Reference
What authoritative record supports the submitted code or value?
Encoding
Are authority, name and conditional subattributes represented correctly?
Lifecycle
Which evidence change requires correction or withdrawal review?
Watch for the wrong conclusion.
- Copying a certification across a model family without checking variants.
- Treating platform schema validity as proof of legal compliance.
- Expanding an energy classification into an unsupported general environmental claim.
Your next action
Validate one certification mapping against the exact sold model and record its evidence and review owner.
Sources & scope
Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.
- Google Merchant Center: Certification →Primary platform documentation · Supports: Supports scheme-specific certification subattributes, supported certification scope and possible automatic enrichment from identifiers. Evidence matching and compliance-owner controls are original editorial analysis.