AI Search
Google updated Merchant Center product ID documentation on April 8, 2026, clarifying that duplicate IDs across multiple accounts will not trigger disapprovals.
Google updated its Google Merchant Center documentation on April 8, 2026, adding a clarification that using the same product IDs across multiple Merchant Center accounts is acceptable and will not result in duplicate product disapprovals. The change, described as minor by industry observers, has nonetheless drawn attention from feed specialists who say it resolves a question that merchants operating across borders have quietly struggled with for some time.
Emmanuel Flossie, a Google Shopping Specialist and Google Ads Diamond Product Expert who runs the feed management consultancy FeedArmy, published a video on April 8, 2026, breaking down what the documentation change does and does not mean. The video, posted to the FeedArmy YouTube channel, had accumulated 93 views within two days of publication. According to Flossie, the update amounts to a formal acknowledgement of something that was always technically permissible in specific cross-border scenarios – but had never been stated directly in Google’s official product attribute documentation.
“Note that using the same IDs across multiple Merchant Center accounts is acceptable and won’t result in duplicate products disapprovals,” the updated documentation states, according to the FeedArmy video transcript. The sentence is new. Nothing else in the core product ID specification changed.
The product ID attribute, also known as the id attribute, is the unique identifier merchants assign to each product in their feed. It is used throughout the advertising system – from feed submission and Shopping ads to dynamic remarketing and campaign targeting. Consistency in these identifiers matters because Google Ads remarketing relies on matching product IDs between Merchant Center feeds and website tags to serve specific products in dynamic ads.
The existing documentation already prohibited reusing an ID for different products within the same target country or language. That rule remains in place. What the new sentence addresses is a separate scenario: a merchant with two distinct Merchant Center accounts, each targeting a different country, who uses the same product ID in both. Until now, no documentation explicitly confirmed whether this practice was safe or whether it might trigger a duplicate product flag.
Flossie’s assessment is that the update was driven by merchant confusion. According to his analysis, Google does not typically notify the industry about small policy clarifications of this kind – and the fact that the company added this sentence suggests enough merchants were asking about it to make the documentation update worthwhile. “Most likely they have had lots of questions regarding this,” Flossie noted in the video transcript, adding that Google “does not share any updates with anybody regarding policy updates that are rather small.”
The practical context for this clarification is the structure that large retailers and international e-commerce operators use to manage product feeds across multiple countries. When a merchant targets a single country from a single top-level domain – for example, a .com site serving US customers – they typically manage a single Merchant Center account. Product IDs are unique within that account, and there is no cross-account duplication question to resolve.
The situation changes when the same merchant expands internationally using country-specific domains. A retailer targeting the UK and France with separate top-level domains – .co.uk and .fr – needs separate Merchant Center accounts, because Merchant Center does not allow multiple country-specific top-level domains within a single standard account. Alternatively, merchants can create an advanced account and add sub-accounts for each target country.
In both structures, the merchant almost certainly manages a single content management system or product database at the back end. That CMS assigns product identifiers, and those identifiers are the same regardless of which country the product is being listed in. The result is identical product IDs appearing in two or more separate Merchant Center accounts. The April 8 documentation update explicitly states this is acceptable.
According to Flossie, there is a practical preference worth noting. Using a single domain targeting multiple countries consolidates domain ranking signals onto one URL rather than spreading them across multiple country-specific domains. Merchants using separate top-level domains for each country trade that consolidation for localized branding – and end up needing the multi-account structure the new documentation addresses.
The new sentence in the documentation addresses cross-country scenarios. It does not – and explicitly cannot – justify operating multiple Merchant Center accounts targeting the same country with the same products. That practice falls under a separate part of Google’s policy framework: the abuse of ad network policy.
According to the video transcript, Flossie addressed this distinction directly. “If you have one country, let’s say the UK, you have two websites selling the same exact product or even other products, that is considered abuse of ad network because you’re taking an unfair advantage.” The consequence of violating this policy is account suspension.
Google Shopping duplication tactics have been a recurring compliance concern. In December 2025, Flossie published a separate analysis warning that a strategy circulating on LinkedIn – creating multiple product variants with different titles and images to capture additional Shopping ad positions – violated the same abuse of ad network framework. That warning followed LinkedIn posts that had accumulated more than 1,100 comments from marketing professionals expressing interest in the tactic.
The distinction matters because the April 8 update could, on a superficial reading, be misinterpreted as opening a path to multi-account product duplication within a single market. The FeedArmy video was partly designed to prevent that misreading. The line between a permitted cross-country architecture and a prohibited same-country duplication scheme runs directly through this clarification.
A pattern has emerged in how Google handles small but consequential updates to Merchant Center documentation. The company does not send notifications to merchants when it makes minor additions to attribute specifications. Feed specialists and Google Shopping experts who monitor documentation changes closely catch these updates; most merchants do not.
This dynamic has been observed across several recent Merchant Center changes. Google’s out-of-stock buy button rulewas tightened in March 2026, requiring merchants to grey out rather than hide the buy button on unavailable product pages – a change with significant technical implications that did not arrive via direct merchant notification, but was surfaced by Flossie in a YouTube video on March 19, 2026. Similarly, Google’s automatic import feature was documented in January 2026 to be falling nine to ten days behind its stated 24-hour update cycle – a discrepancy with direct consequences for remarketing campaigns that merchants discovered through third-party analysis rather than platform alerts.
The April 8 product ID clarification fits this pattern. The change is small. Its practical scope is limited to a specific multi-country account structure. But for the merchants it applies to – international retailers managing separate Merchant Center accounts per country-specific domain – it removes an ambiguity that may have generated unnecessary support requests or cautious workarounds.
The April 8 update arrives against a background of sustained changes to how Google structures and enforces product data standards. In January 2026, Google announced that merchants using multi-channel product strategies – selling the same item both online and in physical stores – would need to use separate product IDs when attributes like price, availability, or condition differed between channels, with enforcement beginning in March 2026. That change was significantly larger in scope, affecting all retailers managing omnichannel inventory through Merchant Center.
The multi-channel product ID split, announced on January 6, 2026, represented a structural change to how Google processes product data. The April 8 update, by contrast, is a clarification that removes confusion without changing underlying requirements. Both involve the same id attribute. The contrast illustrates how a single field in a product feed can carry different compliance implications depending on which dimension of the merchant’s operation is under consideration – online versus in-store, single-country versus multi-country, one account versus several.
Product ID consistency matters well beyond basic feed management. The id attribute is the linking mechanism between Google Ads remarketing tags on a merchant’s website and the product records in Merchant Center. When a shopper views a product on a merchant’s website, the remarketing tag records which product ID was viewed. When that person subsequently browses other websites or searches Google, the system matches the stored ID against the merchant’s feed to display the correct product in dynamic ads. Mismatches between feed IDs and website tag IDs cause remarketing to break down entirely – serving generic ads or failing to match user behavior to specific products.
This dependency was highlighted in January 2026 when Flossie documented that Merchant Center’s automatic import feature was assigning product IDs differently from the IDs used in website structured data, creating mismatches that undermined dynamic remarketing campaigns. The episode showed how product ID integrity cascades through advertising operations far beyond the feed itself.
For merchants considering international expansion through Google Shopping, the April 8 clarification has a practical implication for account architecture decisions. The two main structural options are a single advanced Merchant Center account with sub-accounts for each country, or independent Merchant Center accounts per country. Either way, if the merchant’s back-end CMS assigns consistent product identifiers across markets – the norm for any system managing a unified catalog – the same IDs will appear in multiple accounts. The updated documentation confirms this does not create a compliance problem.
Sub-accounts under an advanced account function similarly to separate accounts for feed management purposes. Each sub-account targets a specific country, holds its own feed, and operates within its own compliance perimeter. The parent advanced account provides administrative oversight across all sub-accounts but does not merge the product data. A product appearing in the UK sub-account and the French sub-account with the same ID is not, under the April 8 clarification, a duplicate.
The question of whether to use a single domain or separate top-level domains for international targeting is separate from the Merchant Center account structure question. According to Flossie’s analysis in the video, a single domain consolidates ranking signals, while separate top-level domains enable country-specific branding and localization. The Merchant Center account structure follows the domain decision: a single domain can be managed from one account targeting multiple countries; separate top-level domains require separate accounts or sub-accounts.
The April 8 documentation update is the latest in a sequence of Merchant Center changes that have kept feed specialists busy in early 2026. March 2026 alone saw Google make Merchant Center for Agencies generally available in the United States and Canada on March 11, giving digital marketing firms a single dashboard to manage multiple client accounts from one login. On March 6, a documented incident showed an agency closure wiping a client’s Merchant Center accountentirely – deleting all feeds, feed rules, supplemental feeds, and account links including Google Ads, Google Analytics, and PayPal connections. The account was restored within 24 hours following a contact form submission to Google, but the episode exposed structural vulnerabilities in how agencies retain access to client accounts after relationships end.
Flossie – who documented that incident, the automatic import delays in January, the buy button change in March, and now the product ID clarification in April – has become one of the most consistent public sources for Merchant Center policy changes that do not receive formal merchant notifications. His FeedArmy channel, which had approximately 4,550 subscribers as of April 8, 2026, according to the YouTube page captured in the source material, functions as an informal monitoring service for Google Shopping policy developments.
The LinkedIn post amplifying the April 8 video drew reactions from five users including Arpan Banerjee, and posed a pointed question: why did Google feel the need to add this sentence now? The answer Flossie offered – accumulated merchant questions – is plausible, though Google has not provided a rationale for the timing.
What is clear is that the documentation change is narrow in scope, applies to a specific and legitimate multi-country account architecture, and does not alter the rules governing single-market operations. Merchants running one website in one country with one Merchant Center account are unaffected. Those managing international catalogs across country-specific domains and multiple Merchant Center accounts now have explicit documentation confirming that shared product IDs across those accounts will not trigger duplicate product flags.
Who: Google, through an undisclosed update to its official Merchant Center product attribute documentation. Emmanuel Flossie, founder of FeedArmy and a Google Ads Diamond Product Expert, documented and explained the change in a video published April 8, 2026.
What: Google added a sentence to its product ID attribute documentation stating that using the same product IDs across multiple Merchant Center accounts is acceptable and will not cause duplicate product disapprovals. The update applies specifically to merchants managing separate accounts for different countries or using sub-accounts under an advanced Merchant Center account for multi-country targeting. It does not change the prohibition on operating multiple accounts for the same country or target market, which remains a violation of the abuse of ad network policy and can result in account suspension.
When: The documentation update and the FeedArmy video explaining it were both published on April 8, 2026. A LinkedIn post by Flossie amplifying the video appeared approximately two days later.
Where: The change appears in the official Google Merchant Center Help Center documentation under the product ID (id) attribute specification. The FeedArmy YouTube channel and LinkedIn served as the primary discovery and dissemination channels, as Google did not issue a formal notification to merchants.
Why: The most probable explanation, offered by Flossie, is that Google received enough merchant inquiries about whether shared product IDs across multi-country accounts would trigger duplicate disapprovals to justify a documentation clarification. The update addresses an ambiguity that existed for international retailers using country-specific top-level domains and separate Merchant Center accounts or sub-accounts – a legitimate and common architecture for cross-border e-commerce operations.
Your go-to source for digital marketing news. Get the latest updates from Google, Meta, Amazon, and The Trade Desk. Stay informed on ad tech innovations, programmatic trends, and policy changes.
