Generate Microsoft / Bing Merchant Center-ready product data for Bing Search, Microsoft Edge, Microsoft Start, Outlook, the LinkedIn Audience Network, and Bing Copilot. Central starts from the product data you have, verifies the facts, and prepares the output with review states before it ships.
The Microsoft Advertising error you've seen before. Title over the 70-character cap. Missing Microsoft Shopping category. Image under the 1200×1200 recommended size. Promotional language in the title. Central catches the same checks Bing Merchant Center runs — in your record, before submission.
Title cap, promotional language, image resolution, Microsoft category mapping, MPN-or-GTIN coverage — all enforced in the canonical record, so the Microsoft Advertising diagnostics report stays empty.
Microsoft Advertising's required attributes — plus the common recommended ones — checked against your verified record, with the source that backed each value and the readiness state per field.
Title length (70 ch cap), GTIN format, MPN coverage, image resolution, Microsoft Shopping category mapping, condition, availability — every check Bing Merchant Center runs at submission time, run first in Central.
Same shape as the Microsoft Advertising submission flow — but every check runs in Central first, against the verified record, before Bing Merchant Center ever sees it.
Paste a shop URL, upload a CSV, or connect a catalog. Central maps your fields to Microsoft Advertising's expected attributes and shows which ones are filled and which are missing.
Title 70-character cap, MPN required when no GTIN, Microsoft Shopping taxonomy, image resolution, promotional language — every Bing Merchant rule runs locally. Disapprovals surface here, not at submission.
Channel Studio drafts titles inside the 70-character cap, descriptions, highlights, and attributes from verified facts. Merchant values stay in control for prices, stock, identifiers, URLs.
Bing Merchant-ready XML or TXT. Schedule re-exports, push by URL, or sync directly. Review states ride along, so unsupported claims never enter the feed.
The same Le Creuset SKU. Sparse import on the left. The Microsoft / Bing Merchant Center XML feed entry on the right — required fields filled, title trimmed to the 70-character cap, identifiers validated, one claim held.
<?xml version="1.0" encoding="UTF-8"?> <feed channel="Bing Merchant Center"> <item> <g:id>SIG-RND-26-CER</g:id> <!-- Title trimmed to Bing 70-char cap --> <title>Le Creuset Signature Round Dutch Oven, 26 cm, Cerise</title> <description>Enameled cast iron, oven-safe to 260 °C, induction-compatible.</description> <link>https://shop.le-creuset.eu/p/sig-rnd-26-cer</link> <g:image_link>/products/signature-round-26.jpg</g:image_link> <g:brand>Le Creuset</g:brand> <g:mpn>21177260671</g:mpn> <g:gtin>0024147210504</g:gtin> <g:price>379.00 EUR</g:price> <g:availability>in_stock</g:availability> <g:condition>new</g:condition> <!-- Microsoft Shopping taxonomy --> <g:microsoft_product_category>Home & Garden > Kitchen & Dining > Cookware > Dutch Ovens</g:microsoft_product_category> <g:product_type>Home > Kitchen > Cookware > Dutch Ovens</g:product_type> <g:shipping> <g:country>DE</g:country> <g:service>Standard</g:service> <g:price>9.90 EUR</g:price> </g:shipping> <g:product_highlight>Enameled cast iron, oven-safe to 260 °C</g:product_highlight> <g:product_highlight>5.3 L capacity, induction-compatible</g:product_highlight> <g:product_highlight>Lifetime manufacturer warranty</g:product_highlight> <g:product_highlight>Available in 21 colors</g:product_highlight> <!-- Structured details for Bing Copilot grounding --> <g:product_detail> <g:section_name>Material</g:section_name> <g:attribute_name>Construction</g:attribute_name> <g:attribute_value>Enameled cast iron</g:attribute_value> </g:product_detail> <g:product_detail> <g:section_name>Dimensions</g:section_name> <g:attribute_name>Capacity</g:attribute_name> <g:attribute_value>5.3 L</g:attribute_value> </g:product_detail> <g:product_detail> <g:section_name>Performance</g:section_name> <g:attribute_name>Max oven temperature</g:attribute_name> <g:attribute_value>260 °C</g:attribute_value> </g:product_detail> <g:product_detail> <g:section_name>Compatibility</g:section_name> <g:attribute_name>Heat sources</g:attribute_name> <g:attribute_value>Induction, gas, electric, ceramic, halogen</g:attribute_value> </g:product_detail> <!-- "Pro-grade performance" held — no source --> <g:review_state>ready</g:review_state> </item> </feed>
Microsoft Shopping ads, Bing Free Listings, the Microsoft Audience Network, and Bing Copilot — all consume the same verified facts, shaped to each destination's character limits and field rules.
The same Bing Merchant feed powers Microsoft Shopping ads on Bing Search, Microsoft Edge, and Microsoft Start. Add bidding, audiences, and assets in Microsoft Advertising — copy stays grounded in the record.
See Shopping setupSame feed, no spend — surface across Bing Search, Bing Shopping, and Microsoft Start. Required attributes overlap with paid Shopping; Central fills both at once.
See Free ListingsMSAN extends the same product feed to Microsoft Edge, Outlook, MSN, and the LinkedIn Audience Network. One verified record, one set of assets, four surfaces.
See Audience NetworkBing Copilot grounds shopping answers on structured product facts. The verified record, the product highlights, and the structured details all feed Copilot's recommendations — same source, AI-readable.
See AI shoppingCentral prepares and publishes Microsoft / Bing Merchant Center output from verified product records. Platform review, account settings, and destination policies still apply — Microsoft Advertising approves the feed.
Bing Merchant Center caps product titles at 70 characters, versus Google's 150. Central drafts Bing-shaped titles inside that cap from verified facts — and surfaces character counts in the readiness scorecard before the feed exports. A single record can keep a longer Google title and a shorter Bing title side by side.
Yes. Bing Copilot grounds shopping answers on structured product facts. The same verified record that powers the Bing Merchant feed — product highlights, structured product details, materials, dimensions, performance, compatibility — gives Copilot the AI-readable evidence it needs. Unsupported claims stay held so Copilot never repeats them.
Microsoft Advertising requires at least one identifier: GTIN, MPN, or brand + product name. For most branded SKUs both GTIN and MPN should be present; for private-label products MPN is often the only identifier. Central validates the GS1 GTIN checksum, normalizes MPN formatting, and flags the record if neither is available so the feed never ships without an identifier.
Central maps each product to the Microsoft Shopping taxonomy (e.g. Home & Garden > Kitchen & Dining > Cookware > Dutch Ovens). Where possible, the same canonical product type is mapped to both Microsoft and Google taxonomies, so one record covers both feeds. Mapping confidence is scored; low-confidence categories surface for review before export.
Yes. The verified product record is canonical; each channel adapts from it. Google MC gets the 150-character title and Google taxonomy; Bing MC gets the 70-character title and Microsoft taxonomy; identifiers, prices, stock, URLs, and structured details stay shared. You build the record once and ship to both feeds without rewriting facts.