Guide : Microsoft Shopping & Bing Merchant Center

Ce que Microsoft Merchant Center (formerly Bing Merchant Center) is, how free Product Listings and paid Shopping Campaigns fonctionner, and how its feed spec differs from Google's.

Première publication : 3 juil. 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues

Microsoft Merchant Center (MMC) — the platform formerly appelé Bing Merchant Center — is the free hub à l’intérieur Microsoft Advertising où vous créer a store and submit a product feed. Un feed drives les deux free Product Listings on the Bing Shopping tab and paid Microsoft Shopping Campaigns, exactly comme Google Merchant Center on the Bing/Copilot side. The naming is a mess (Bing → Microsoft on les deux the outil and the surface), and the feed spec is fermer to Google's but pas identical: Microsoft's API listes ~13-14 required-for-insert fields with réel country-conditional rules (mandatory shipping pour Germany, mandatory apparel sizing pour FR/DE/UK/US), an identifierExists flag, and a schema that's a deliberate superset — it accepts a raw Google feed and silently ignores Google-only fields, qui is pourquoi the Google-import outil 'simplement fonctionne.' Paid Shopping Campaigns span 90+ countries (far plus que the free-listings rollout footprint, a courant myth). In 2026 Microsoft made store nom/domain edits self-serve, shipped Product Explorer, and made MMC feeds UCP-ready — repositioning MMC as the product-data foundation pour Copilot's agentic shopping and checkout, si or pas vous run paid ads. Its Shopping Campaign reports (product dimension, partition, and search-query performances) cover paid delivery seulement — ils don't mesurer free-listing visibility — and conversion tracking runs on the même UET/goals/attribution-window model as the rest of Microsoft Advertising, so expect some discrepancy contre Google Analytics or Google Ads by design, pas by bug.

TL;DR — MMC is the Bing/Copilot-side Merchant Center: un feed drives free Product Listings and paid Microsoft Shopping Campaigns. Naming is a rename mess (Bing → Microsoft on les deux the outil and the surface). The feed spec is fermer to Google’s but pas identical — Microsoft’s API listes ~13-14 required-for-insert fields, with shipping mandatory pour Germany and sizing mandatory pour apparel in FR/DE/UK/US, an identifierExists flag, and a schema that’s a deliberate superset que accepts a raw Google feed and silently ignores Google-only fields (pourquoi the Google-import outil fonctionne). Paid Shopping Campaigns and free-product surfaces have différent market footprints, so vérifier the current country liste and program eligibility plutôt que assuming un implies the autre. Shopping Campaign reports mesurer paid delivery seulement, pas free-listing visibility, and conversion tracking runs on Microsoft’s standard UET/attribution model — so some discrepancy contre Google Analytics/Ads is normal.

Evidence for this claim Microsoft Shopping campaigns use products from a Microsoft Merchant Center store catalog to create product ads. Scope: Paid Microsoft Advertising shopping campaigns; free-listing availability is separate and market-dependent. Confidence: high · Verified: Microsoft Advertising: Product ads Evidence for this claim Microsoft publishes a product resource schema with required and market-specific shopping-feed fields. Scope: Microsoft Shopping Content API; field requirements can vary by target market and category. Confidence: high · Verified: Microsoft Advertising: Products resource

Ce que MMC is, and how it relates to Shopping Campaigns

Microsoft Merchant Center is the store-and-catalog couche; Microsoft Shopping Campaigns are the paid ads que draw from it. Microsoft’s propre API docs put the relationship plainly:

Evidence for this claim Microsoft Shopping campaigns use products from a Microsoft Merchant Center store catalog to create product ads. Scope: Paid Microsoft Advertising shopping campaigns; free-listing availability is separate and market-dependent. Confidence: high · Verified: Microsoft Advertising: Product ads

“A Microsoft Shopping campaign enables vous to advertise the products from votre Microsoft Merchant Center store product catalog. Product ads from a Microsoft Shopping campaign inclure details à propos de the product, an image, and optional promotional text.” — Microsoft Advertising, Product Ads

The même feed aussi powers free Product Listings — the organic, unpaid side — so paid and free are two outcomes of un catalog, pas two separate setups. That’s the même “one feed, free and paid” model Google Merchant Center runs; the mechanics on the free side visibly followed Google’s template quand Bing launched les in 2020.

The naming history, une fois

Parce que a réel chunk of search volume ici is personnes trying to map an old nom to a nouveau un:

  • Bing Merchant Center → Microsoft Merchant Center (the outil).
  • Bing Shopping → Microsoft Shopping (the consumer surface — the Shopping tab and shopping modules in Bing, Edge, and Copilot).
  • Microsoft Advertising is the platform que contient Merchant Center.

Même system, renamed. Si a competitor’s guide encore dit “Bing Merchant Center,” it’s describing today’s MMC.

Free Product Listings vs. paid Product Ads

Free Product Listings launched on the Bing Shopping tab in August 2020 — the US premier, with the UK, Canada, Australia, France, and Germany named as near-term rollout markets. Existing Microsoft Shopping Campaigns advertisers were auto-enrolled: leur already-approved product offers were opted into free listings with aucun separate action. Nouveau (non-advertiser) merchants had to créer an MMC store, submit a feed, and obtenir products approved — the même feed-and-approval pipeline que powers paid. Merchants who don’t vouloir organic placement peut turn free listings off in the store’s settings. (Microsoft’s original announcement blog now renders as a JavaScript shell I couldn’t pull clean text from, so I’m relaying ces specifics from Moteur de recherche Land’s contemporaneous coverage and Moteur de recherche Roundtable plutôt que quoting Microsoft directement.)

Setting up an MMC store

Microsoft’s API docs décrire the official workflow: in the Microsoft Advertising web app, ouvrir Outils > Microsoft Merchant Center, click Créer store and provide the store details; créer a product catalog and submit the feed via FTP/SFTP or le contenu API; grab votre store’s unique system identifier; alors, si vous vouloir paid, créer a Microsoft Shopping campaign (Product Ads, “Setup Microsoft Merchant Center”). Domain verification runs via Bing Webmaster Outils, and store creation goes via a manual editorial examiner — secondary sources commonly cite up to à propos de five business days, though Microsoft doesn’t pin an exact SLA in the docs I pourrait vérifier, so treat que number as practitioner-reported.

The MMC feed spec — and how it differs from Google

Ce is où MMC earns its propre article. La plupart competing content hand-waves with “title, price, image, availability” or repeats a incorrect “6 required fields” claim. Microsoft’s réel Products resource API référence listes closer to 13-14 fields requis pour insert, selon category and country.

Core requis fields

Requis pour insert per Microsoft’s schema: availability, brand, channel (Local or Online), condition, contentLanguage (a 2-letter ISO 639-1 code from a pris en charge liste that’s narrower que Google’s), gtin, imageLink, link, mpn, offerId, price, targetCountry, and title — plus the conditional fields ci-dessous.

Country-conditional requirements (the highest-value, least-covered facts)

Two rules routinely surprise personnes reusing a Google feed. Microsoft states les directement:

“REMARQUE: Shipping is requis si the target country is DE (Germany); sinon, it’s optional.” — Products resource

“Ce field is requis pour tout Apparel & Accessories products quand targeting: France, Germany, United Kingdom, and United States.” — Products resource, sizes

So a feed that’s fine targeting the US peut generate warnings or rejections the moment vous ajouter Germany or commencer selling apparel into the UK.

The identifierExists flag

Microsoft’s identifierExists flag indique the system si votre product carries gtin, mpn, or brand identifiers:

“A Boolean valeur que determines si the product offer specifies the gtin, mpn, or brand identifiers. The par défaut is vrai. Définir to faux si vous ne faites pas specify tout three of the identifiers.” — Products resource, identifierExists

Microsoft is softer que Google ici: au lieu de hard-disapproving on manquant identifiers, it warns. Per the même doc, MMC renvoie warnings si vous don’t specify the gtin, mpn, and brand identifiers quand ils devrait be connu — the offer is accepted, but you’re told to fix it. (Ce is the même identifier hygiene que feed optimization covers on the Google side.)

Fields Microsoft garde but ignores (pourquoi a Google feed “just works”)

The genuinely distinctive fact nothing sinon in the SERP calls out: Microsoft’s schema is a deliberate superset of Google’s. Several fields exist purely so a Google-formatted feed doesn’t break on import — Microsoft accepts les and alors fait nothing with les:

“MMC ne fait pas utiliser the additional images; ce field is inclus pour Google compatibility.” — Products resource, additionalImageLinks

The même doc marks adwordsGrouping, adwordsLabels, destinations, taxes, and validatedDestinations as Google-compatibility-only aussi. That’s the technical raison the Google Merchant Center feed-import outil (originally launched in 2018, per Moteur de recherche Land) fonctionne sans field-by-field remapping: vous pouvez drop a raw Google Shopping feed in and the Google-only fields silently no-op. Ce que doesn’t carry over cleanly is the country-conditional stuff ci-dessus — the DE shipping and FR/DE/UK/US sizing rules — plus MMC’s propre identifier handling.

Regional inventory (an MMC fonctionnalité with aucun 1:1 Google nom)

Microsoft has a Regional products resource pour differentiated pricing/availability by region — essentially undocumented in consumer-facing SEO content:

“Utiliser the regional products resource to manage region definitions and regional product offerings in votre Microsoft Merchant Center store (MMC).” — Regional products resource

Remarque the country liste pour regional inventory is narrower que the general targeting liste — don’t conflate the two:

“Pris en charge countries/regions: US, CA, BR, GB, FR, DE, HU, CH, NL, AU, NZ, IN, ID, MY” — Regional products resource, countryCode

”Is Bing Shopping available in my country?” — kill the myth

A myth floats autour que Bing Shopping reaches seulement a handful of English-speaking countries. Que conflates the narrower free Product Listings rollout footprint (US premier, alors UK/Canada/Australia/France/Germany) with the far broader paid Microsoft Shopping Campaigns footprint, qui per Microsoft’s propre docs spans 90+ countries — Albania via Zimbabwe (Product Ads country availability). Si a blog post indique vous it’s six countries, it’s describing the incorrect liste.

What’s nouveau in 2026

Two dated changements faire ce a “read the 2026 version” topic:

  • Self-serve store nom and domain edits (March 2026). Microsoft enabled modification votre store nom and domain à l’intérieur Merchant Center sans prise en charge intervention — nom changements go via editorial examiner pendant que ads garder running sous the existing approved nom; domain changements exiger ownership verification avant taking effect. Ce reverses the still-repeated competitor claim que a store nom “can’t be changed after creation” (Moteur de recherche Land, surfaced publicly by independent PPC commentator Navah Hopkins).
  • Product Explorer (June 2026). Microsoft ajouté a unified catalog view à l’intérieur Merchant Center — a searchable catalog, performances tracking, and eligibility-gap identification, initially pour advertisers with fewer que 100 000 SKUs (Microsoft Advertising blog, Bhuvesh Arora).

MMC and agentic/AI commerce (Copilot Checkout, UCP)

Ce is the biggest chose competing content misses. As of 2026, Microsoft has repositioned MMC from “the Shopping-tab feed pipeline” to the product-data foundation pour Copilot’s shopping and checkout — si or pas vous run paid ads.

Microsoft’s framing on its Agentic Commerce page is que the foundation of agentic commerce is trusted product truth, and it draws a clean line entre two mechanisms: product feeds primarily enable discovery (products showing up in AI réponses), pendant que the Universal Commerce Protocol enables transactions (checkout and post-purchase actions à l’intérieur AI experiences comme Copilot). It’s explicit que the merchant stays the merchant of record — Copilot ne fait pas become the merchant of record — and que, today, Microsoft ne fait pas prendre a commission or affiliate fee (Microsoft Advertising, Agentic Commerce). (I’m paraphrasing plutôt que quoting parce que que page renders via JavaScript and I seulement have it via an extraction réussir — vérifier the exact wording contre the live page avant treating quelconque of it as a verbatim quote.)

In April 2026, Microsoft made U.S. prise en charge pour Universal Commerce Protocol (UCP) feeds généralement disponible à l’intérieur Merchant Center, with Target named as an early partner (PPC News Feed). I’m pas going to re-explain UCP ici — the mechanics live in the Universal Commerce Protocol article in the ai-commerce cluster; ce piece seulement nécessite to establish MMC’s role in it.

The important nuance: vous don’t besoin MMC to sell via Copilot Checkout. Microsoft’s January 2026 Copilot Checkout announcement is clair que MMC isn’t a hard requirement — but its propre guidance frames MMC feeds as ce que informs organic Copilot results, and it reiterates que the merchant stays the merchant of record, owning the transaction, customer données, and relationship (Microsoft Advertising blog, Copilot Checkout and Brand Agents). So MMC is the visibility lever pour AI shopping même outside classic Bing search — qui is exactly pourquoi 2026 is a bon temps to définir it up.

Shopping Campaign reports and conversion tracking

Un gap worth closing: ce que vous pouvez en réalité mesurer, and où the numbers won’t match autre platforms.

Reporting is paid-only. Microsoft’s Reporting API has a dedicated “Product Ads” report family pour Microsoft Shopping Campaigns — ProductDimensionPerformanceReportRequest, ProductPartitionPerformanceReportRequest, ProductPartitionUnitPerformanceReportRequest, ProductMatchCountReportRequest, and ProductSearchQueryPerformanceReportRequest (Report Types — Microsoft Advertising API). Ces break performances out by product category, custom étiquette, product partition, and the search requêtes que triggered votre ads — genuinely utile pour tuning a campaign. Ce que ils don’t do is tell vous anything à propos de free Product Listings visibility: every un of les is scoped to Shopping Campaign (paid) delivery données. There’s aucun equivalent first-party report pour free-listing impressions or clicks in ce API — a réel measurement gap worth knowing à propos de avant vous go looking pour un.

Conversion tracking runs on Microsoft’s standard UET stack, the même mechanism utilisé à travers tout of Microsoft Advertising, pas something Shopping-specific. Vous install a Universal Event Tracking (UET) tag, define conversion goals, and définir a conversion window per goal (anything from 1 minute to 90 days; 30 days by par défaut). Microsoft’s par défaut attribution is dernier ad click — the la plupart recent ad click avant the conversion obtient the credit — though it aussi supports data-driven attribution, qui splits credit à travers the contributing keywords/clicks (How fait conversion tracking fonctionner? — Microsoft Advertising).

Don’t be surprised quand ces numbers don’t match Google Analytics or Google Ads. Microsoft’s propre conversion-tracking FAQ walks via pourquoi some discrepancy is attendu, pas a bug: separate UET vs. Google tag installs, différent conversion windows or goal definitions entre platforms, différent unique-vs-all counting settings, Microsoft’s propre cross-device attribution (qui Google Analytics handles differently), and the fact que Microsoft doesn’t currently filter out tester, fraudulent, or duplicate conversions. Si votre numbers are off, vérifier ceux five choses avant assuming the tracking is broken.

Où ce sits in the cluster

Ce is the Bing/Microsoft-specific counterpart to the Google Merchant Center hub and the generic feed optimization deep dive — it owns what’s en réalité différent à propos de MMC. Pour the star-ratings side à travers les deux engines, voir the product examiner feeds piece in ce cluster; pour disapprovals and Microsoft’s three-tier enforcement model, voir the disapprovals piece. The broader ecommerce SEO pillar ties the merchant-center cluster to product pages, category pages, and site structure.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.