Microsoft Ads Shopping: Merchant Center and Feed Operations

#01What must exist before a Shopping campaign?

Identify the advertiser, verified domain relationship, Microsoft Merchant Center store and feed owner. The person editing ads may not own the store or the commerce integration. Record who can resolve a domain issue, change feed mappings and confirm product facts.

A merchant may reuse compatible source data or supported import routes, but Google Merchant Center is not the Microsoft destination. Microsoft supports its own attributes, policies, markets and diagnostics. Treat cross-platform reuse as a mapping exercise rather than evidence of automatic parity.

Confirm the intended sales market, currency, fulfilment and product eligibility. A product that is legal and available in the store's home country may not be eligible for every advertised market. The course does not provide an exhaustive country or restricted-product list; the current official requirements and actual account must be checked.

The Google Performance Max controls lesson provides related feed-led advertising context. Microsoft's store binding, product selection, attributes and campaign behaviour need independent verification before launch.

#02How should product identity be designed?

Use stable product IDs that map consistently to the merchant's actual offers. An ID should not change simply because a title or price changes. If IDs are repeatedly regenerated, reporting continuity, diagnostics and product-event relationships become harder to interpret.

Distinguish an individual variant from its group. A black cable tray and a white cable tray may belong to the same product family while remaining separate purchasable variants. The item-group relationship does not replace the unique identity of each offer.

Use genuine manufacturer identifiers such as GTIN, MPN and brand where applicable. Do not invent a GTIN to clear a warning or reuse an unrelated identifier from another product. Where the documented identifier-exists mechanism is appropriate, use it honestly and according to current rules.

Keep the mapping between commerce SKU, Microsoft product ID and any dynamic-remarketing event identifier explicit. A technically valid event that references the wrong feed item can undermine product relevance. Marketing should own the acceptance contract even when a specialist implements the mapping.

#03Which offer attributes deserve daily attention?

Price, currency, availability, variant and destination should describe the same purchasable offer. A feed showing the cheapest variant while the landing page preselects a more expensive one can create a misleading experience even if both prices exist somewhere on the page.

Microsoft's attribute documentation notes defaults that deserve care. Availability can default to in stock when omitted. Therefore, omission is not a safe way to express uncertainty about stock. Send an explicit, accurate state through the approved integration and test how unavailable items are handled.

Tax and shipping requirements vary by market. Do not apply a universal tax-exclusive rule or copy one country's shipping requirement into every feed. Assign a local commercial or legal reviewer where necessary and record the basis used for both advertised and reported values.

#04How do titles, descriptions and images support relevance?

Write product titles that identify the item and its decisive attributes. A stock code alone rarely helps a buyer understand a tray's installation method or size. Descriptions should explain useful facts, not repeat a list of promotional adjectives.

Use accurate category and variant information. Do not add popular but unrelated terms to attract traffic. The feed is a product representation, not a place to disguise unsupported claims or imply compatibility that the product team has not verified.

Images should show the actual offer clearly and follow Microsoft's current requirements. A lifestyle image that appears to include several products can mislead if only one item is sold. Review crop, variant colour and any included accessories against the product page.

Do not import image-size rules from Google's future policy announcements into Microsoft guidance. Specifications can differ by platform, product category and date. The marketer's acceptance sheet should point to the current Microsoft requirement rather than hard-coding an unverified cross-platform number.

#05How should feed refresh and diagnostics operate?

Choose an approved update route and cadence that reflects how quickly stock and price change. Microsoft's scheduled feed-file fetching is not a promise of real-time processing. A successful source export also does not prove that the destination has fetched, parsed and approved the latest version.

Track source generation time, destination fetch status, processing results, rejected items and last confirmed offer state. Microsoft's attributes include product-expiration behaviour, so a feed that once worked cannot be left unattended indefinitely. Verify the current expiry and refresh requirements for the route in use.

Classify diagnostics by cause: source data, mapping, policy, domain, market eligibility or temporary processing. Fix the authoritative source where possible. Repeatedly patching destination values while the next sync restores the error creates a recurring incident rather than a solution.

Maintain a product sample for manual checks. Include a best seller, a variant family, an unavailable item, a sale item and a market-restricted item. These cases reveal more than checking only a healthy default product. Use fictional or authorised data and avoid exposing customer information in shared diagnostics.

#06How should you control campaign product selection?

Microsoft documents that Shopping campaigns can include all products by default. Review the campaign's filters and product groups before serving. A merchant intending to advertise only high-contribution organisers should not assume the campaign name limits it to that collection.

Use product attributes and custom labels to express business groupings where supported. A label might represent an internally defined margin band, seasonal range or fulfilment constraint. Keep the underlying definition documented and current; a label called profitable does not calculate profitability by itself.

Store selection is consequential. Microsoft states that the associated store cannot simply be changed after the campaign is saved. Verify the correct store and market before creation, and do not promise a trivial later switch if ownership or catalogue selection is wrong.

Review overlap with other Shopping and Performance Max activity. Standard Shopping has priority settings for relevant overlaps, but avoid universal claims about which campaign always wins across every product and automated campaign. Use current product-specific documentation and actual account evidence rather than a simplified hierarchy copied from another platform.

#07What should the launch and incident process look like?

Require evidence at four levels: feed accepted, item eligible, campaign configured correctly and customer journey valid. Approval at one level does not guarantee impressions or profitable orders. Lack of delivery can involve bids, budget, targeting, policy, competition or measurement, not only feed health.

Define incident triggers such as widespread price mismatch, unavailable products still advertised or a feed that has stopped refreshing. Identify who may pause affected campaigns and who repairs the source. A sales promotion should not proceed merely because the campaign owner cannot reach the feed owner.

Keep a change log for attribute mappings, store settings, product filters and integrations. A feed app update can alter many items at once. Compare representative products before and after changes rather than discovering the effect through a month-end performance decline.

#08What should an out-of-stock runbook contain?

Trace the stock change from the commerce system to the feed output, destination processing and advertised offer. A source correction is not complete until the relevant destination state and customer journey have been checked. Conversely, a destination warning may require investigation of a failed fetch rather than a change to genuine stock data.

Define who can contain exposure while the feed owner repairs the source. Depending on the affected scope and approved process, an authorised operator may restrict products or pause affected delivery. Keep the original issue, correction time and representative item evidence. Do not repeatedly mark an unavailable item in stock to remove a warning or preserve campaign volume.

After recovery, review why the control failed: stale export, omitted attribute, mismatched variant or an unowned integration. Fixing that cause is more valuable than recording a one-off manual repair that the next scheduled feed will overwrite.

#09Worked example: Ledgerline

Ledgerline prepares an illustrative Shopping launch for desk organisers. Its feed includes planners and cable accessories as well, and unavailable white organisers omit the availability field. The campaign draft would include all products by default.

The team finds that the omission could represent the unavailable variant as in stock. It corrects the source mapping, verifies stable variant IDs and creates an explicit product-selection plan. It also checks that a promotional price ends consistently in the source feed and on the product page using the agreed time zone.

Walkthrough

1. Confirm the Microsoft store, domain relationship, market and feed owner.
2. Map commerce IDs, variant groups and genuine manufacturer identifiers.
3. Compare price, currency, availability and destination for a representative sample.
4. Review shipping, tax and restricted-product requirements for the intended market.
5. Inspect fetch and processing status rather than relying on source-export success.
6. Define campaign filters or product groups before accepting all-product defaults.
7. Document incident owners and the evidence needed for launch approval.

The example does not predict impressions or sales. It establishes a feed and campaign contract that can be tested before spending.

#10Common mistakes

Treating Google approval as Microsoft approval skips the destination's actual rules. Inventing identifiers to remove warnings corrupts product truth. Omitting stock because the integration is uncertain can be especially dangerous when the documented default is in stock.

Another mistake is using a campaign name as a product filter. Finally, do not diagnose every delivery problem by raising bids. First confirm product eligibility, store selection, market settings, current feed processing and the actual customer offer.

#11Try it yourself

Create a feed acceptance sheet for five representative fictional products or authorised offers. Include stable ID, variant group, identifiers, price basis, availability, destination, market and refresh owner. Mark which fields are source-controlled and which are configured in Microsoft.

Draft a product-selection plan and a feed-failure response. Include one unavailable variant and one promotion crossing a date boundary. A complete exercise explains how the team will detect stale or mismatched offers before they become an advertising incident.

#12Quick quiz

1. Does a compatible Google feed eliminate Microsoft review?

Answer: No. Microsoft attributes, policies, markets, diagnostics and destination configuration still require verification.

2. Why is omitting availability risky?

Answer: Microsoft's documented default can be in stock, so omission may misrepresent an unavailable offer.

3. Does the campaign name restrict which products are advertised?

Answer: No. Review actual filters and product groups, especially because all products can be included by default.

#13What should a Shopping launch record prove?

Prove store ownership, market eligibility, current feed health, truthful offers, explicit product selection and a usable destination. Keep delivery and commercial performance as later evidence, not assumptions created by approval.

Previous: Microsoft Ads Budgets and Bidding: Pacing With Reliable Goals · Next: Microsoft Ads Performance Max: Assets, Products and Controls

Or return to the Microsoft Ads for Marketers track.

Related: Microsoft Ads Landing Pages: Relevance, Quality and Policy QA · Microsoft Ads Performance Max: Assets, Products and Controls · Microsoft Ads Reporting: GA4, Attribution and Profit Decisions

#14Common questions

What happens if availability is omitted? Microsoft documents an in-stock default in its attributes guidance. Send explicit accurate availability rather than using omission to represent uncertainty.

Can related variants share one indistinguishable identity? Use stable individual offer identities and the appropriate group relationship. A variant group does not replace the identity of each purchasable offer.

Can a saved Shopping campaign freely switch Merchant Center stores? Microsoft documents a fixed store association after saving. Verify the correct store before creation and assess the supported migration route if it is wrong.