The product is good, the photography strong and the budget ready. Yet the ad shows the wrong variant, a vague title or a price that no longer matches the page. The customer does not see the integration behind it. They see a promise that changes after the click.
A feed is a structured source of product information, delivered through a file, integration or API. A catalog is the collection of products used by the platform. Having a catalog does not itself mean the data is complete, current or ready for promotion.
The quality of product data is part of the customer’s experience and campaign preparation.
From a technical record to an intelligible offer
In Merchant Center, Google uses product data to match queries and for certain advertising formats. Missing, incorrect or contradictory information can cause eligibility limitations, rejections or misleading impressions. Google Merchant Center: product data specifications
An internal label such as “Model 218 B” may work for stock management. It tells someone looking for an extendable oak table very little. Internal organization and a useful product description serve different purposes.
We do not bridge that gap by stuffing the title with popular terms. We select the real features that help identify the product, taking into account its category and the destination’s rules. An irrelevant term can attract an expectation that the product does not meet.
The same product, two representations
The following example is fictional and concerns a furniture store. We assume the dimensions and features exist in its range.
| Field | Unclear version | Verifiable version |
|---|---|---|
| Title | Table 218, super offer | Extendable oak table, 160-220 cm, natural finish |
| Variant | One entry for all colors | The natural variant has its own identifier and image |
| Image | Photo showing a different finish | Photo of the selected product and finish |
| Availability | “In stock,” copied from an old export | Current status from a verified source |
Google requires titles to identify the product accurately and match the landing page, including relevant variant differences. The title field is not a place for unrelated promotional copy. Google Merchant Center: title requirements
The internal code does not explain the product.
Example of information that can help identify a variant.
IN THE STOCK SYSTEM
Model 218 B. The team knows what the code represents.
FOR THE BUYER
Extendable oak table, 160-220 cm, natural finish. Features must be accurate.
Fictional example, not NOT MORE. results or forecasts.
The change is not just cosmetic. It makes it easier to understand which product is being sold and whether it meets the buyer’s needs. The commercial result remains to be evaluated; a clearer title does not guarantee demand or profit.
A product photo doesn’t always do a banner’s job
A catalog’s main image may be used in a format where the platform shows the title, price and other information separately. Adding the same elements to the photo can reduce clarity or break that destination’s rules.
Merchant Center’s main-image guidance generally excludes promotional text, watermarks and borders: the image should represent the product. Check current requirements and any exceptions. At the time of this edition, Google announces a 500 × 500 pixel minimum from 31 January 2027 and recommends images of at least 1,500 × 1,500 for different formats. Google Merchant Center: image requirements
These rules do not automatically transfer to all images in all campaigns. A photo for the catalog, a demonstration of use and a communication material may have different roles. That is why asset preparation starts with strategy and destinations, not one export used everywhere.
The product’s identity must hold throughout the journey
A stable identifier lets systems refer to the same product record. Describe variants according to category and platform requirements. Use commercial identifiers such as GTIN correctly where applicable; never invent them just to fill a field.
There is another important link: the product in the website event and the product in the catalog. If the identifiers do not match, some uses of the data may be affected. This is checked for the specific integration, including variants and changes to the ecommerce platform.
Check the same product variant throughout.
Check data consistency alongside when each source was last updated.
SOURCE
What system sets the price and stock?
CATALOG
What version of the data has been transmitted?
PAGE
What does the customer see for the selected option?
ORDER
What product and conditions does the purchase confirm?
Illustrative framework. Application depends on the project’s context and data.
Prices can change between updates and stock can sell quickly. Rather than promising perfect synchronization every second, establish the authoritative source, an appropriate update frequency and a way to detect and correct differences.
Eligibility does not make a product a spending priority
A product may meet the technical requirements and still be a weak choice for promotion at that moment: limited stock, insufficient margin, difficult delivery or unsuitable seasonal demand.
We look at catalog health and commercial priorities separately. Grouping products by useful criteria can help analysis, but the criteria depend on the business. A high-priced product does not automatically leave a large contribution. A category with many orders can also bring high return or support costs.
In the furniture example, in-stock and made-to-order tables may need different delivery explanations. Strategy decides how to present and promote them. The feed needs to support those choices with accurate information.
Who is responsible for what?
Data may come from the inventory system, the ecommerce platform and separate edit files. If each team assumes someone else will fix a problem, it can keep affecting the ads.
It is worth clarifying who validates the product, who maintains integration, who follows up on diagnostics and who decides commercial priorities. A manual correction in the advertising platform can be overwritten by the next import if the source is not repaired.
For the customer, all these responsibilities come down to one simple thing: finding on the page what they understood from the ad. Consistency reduces unnecessary questions and provides a better basis for choice.
How we work at NOT MORE.
Start with the offer, priority categories and how the products are managed. Connect the catalog review with creative work, campaigns and the experience after the click. Then prioritize changes by their likely impact and dependencies.
Sometimes the main problem is an integration. Sometimes what is missing is the right images or a commercial decision about what is worth promoting. Expertise means identifying these differences before asking for more budget.
Product data, integration and promotion each have an owner
The client holds and confirms commercial information about products, variants, prices and stock. NOT MORE. can prepare materials, configure the catalog and implement or repair the integration included in the project. Together with the providers managing the systems, we check how information travels from its source to the ad and page.
For ongoing work, we establish who monitors errors, who corrects the source and who adjusts promotion when a product can no longer be sold on the advertised terms. Reporting can connect data problems to distribution and the buyer’s experience.