Microsoft Product Explorer: how to audit catalogs and ad disclaimers

Microsoft confirmed two operationally useful updates in its June 22, 2026 product roundup. First, Product explorer provides an account-wide way to search and filter a Microsoft Merchant Center catalog, review which products are active or serving, inspect performance information, find eligibility or metadata gaps, and export filtered product lists. Microsoft said the feature was available under Products for advertisers with fewer than 100,000 SKUs. It also said Products would not be visible to advertisers with more than 100,000 SKUs.

Second, Microsoft documented campaign-level disclaimers for Responsive Search Ads, Performance Max, and Audience ads across eligible search and native contexts. The two formats are a popup, available for Native ads with a 500-character allowance, and an additional inline line with an 80-character allowance. Advertisers can configure a disclaimer in advanced settings during campaign creation or change it later in campaign settings. Microsoft states that an approved disclaimer serves with every eligible ad in the campaign. Those are official facts. The implementation guidance below is CreatikLab’s operational interpretation, not an additional Microsoft commitment.

The value is not another dashboard by itself. Product advertising often fails between systems: the source catalog says an item exists, the feed processor transforms it, Merchant Center decides whether it is eligible, and the campaign decides whether it can serve. A searchable catalog view can shorten the path from a weak product cohort to the metadata or eligibility issue that needs an owner. The export function also makes the diagnosis easier to move into a ticket, spreadsheet, merchandising workflow, or controlled remediation queue.

The disclaimer update addresses a separate but related governance problem. Required conditions are frequently handled through improvised copy, landing-page footnotes, or duplicated campaign text. A campaign-level field can create consistency, but it also increases the impact of a mistake because the setting applies broadly. CreatikLab’s interpretation is therefore simple: treat Product explorer as a triage layer and disclaimers as governed campaign assets, not as automatic optimization features.

Begin by verifying whether Products appears in the relevant Microsoft Merchant Center account. Do not assume that every account, store structure, market, or catalog can use the same workflow. Microsoft expressly identifies advertisers with fewer than 100,000 SKUs and says the Products area is not visible above 100,000. The announcement does not explain how SKUs are counted across stores, countries, languages, variants, or duplicated offers. It also does not resolve the exact boundary case of an advertiser with precisely 100,000 SKUs.

• Record the SKU total shown by the systems your team currently trusts.
• Confirm whether Products is visible to the user role performing the audit.
• Document the account, store, market, and feed included in the observation.
• Escalate an exact-threshold or counting ambiguity rather than guessing.
• Keep the existing feed-monitoring process active until the new view has been validated.

This access check prevents teams from building a process around a screen that part of the organization cannot see. It also exposes permissions and catalog architecture issues before they are confused with product eligibility problems.

Microsoft confirms that Product explorer can search and filter catalog information, show active and serving products, display performance, reveal eligibility or metadata gaps, and export filtered lists. It does not publish a complete field dictionary in the cited announcement. Before standardizing an audit, inventory the filters, dimensions, status definitions, and performance columns actually available in your account. Record those definitions in the operating procedure so that active, serving, eligible, and performing are not treated as interchangeable states.

A useful triage starts with business cohorts rather than one product at a time. Separate priority categories, high-margin ranges, seasonal inventory, recently changed items, and products expected to support current campaigns. Within each cohort, compare status and the performance information the interface provides. Export the subset that needs investigation and assign a reason code such as metadata review, eligibility review, commercial review, or no action. These reason codes are a CreatikLab recommendation; Microsoft does not state that Product explorer supplies them.

1. Save a dated baseline of the catalog totals and the filtered cohort being investigated.
2. Confirm that the filters represent the intended store, market, category, or business segment.
3. Compare active and serving states without assuming either one means the product is profitable.
4. Review the eligibility or metadata gaps identified in the interface.
5. Export the affected list and preserve the filter logic used to create it.
6. Trace each issue back to its source of truth rather than patching the same symptom repeatedly.
7. Assign an owner, priority, decision, and evidence field to every remediation batch.
8. Recheck the cohort after Microsoft reflects the changes and record unresolved items.

Do not edit a large catalog merely because a filter produces a long list. Validate a small, commercially relevant sample first. A metadata change can affect titles, categorization, policy review, landing-page consistency, and reporting outside the immediate campaign. The official source does not specify processing latency, refresh frequency, rollback tools, or the format of exported files, so the procedure should capture these details from the live account before promising turnaround times.

Microsoft describes two layouts. The popup format is available for Native ads and allows up to 500 characters, with a clickable label opening the fuller disclosure. The inline format displays an additional line below the ad and allows up to 80 characters. These limits should not be generalized to every placement. The official roundup does not provide a complete compatibility table for every campaign subtype, market, language, device, or inventory source.

The format decision should follow the communication need. A short condition that must be immediately visible may fit the inline line. A longer explanation may fit the Native popup where that layout is eligible. That is an operational choice, not legal advice. Have the appropriate legal or compliance owner approve the wording, label, language, landing-page consistency, and scope. Keep a register showing which campaigns use which version, who approved it, when it was reviewed, and what business condition would require an update.

Microsoft says disclaimers can be added from advanced settings while creating a campaign and edited, removed, or replaced later through campaign settings. That flexibility should be paired with change control. Before launch, verify the campaign type, intended audience, applicable market, selected layout, character count, wording, link behavior, and approval status. After approval, preview or observe eligible ads where possible and preserve evidence that the expected version is attached to the correct campaign.

Microsoft’s statement that an approved disclaimer serves with every eligible ad is important but narrow. It does not mean every campaign, placement, or impression is eligible, and it does not certify that the wording satisfies a law, industry code, promotion rule, or contractual requirement. It also does not guarantee clicks, conversions, or better performance. Build an exception path for disapprovals, missing displays, outdated terms, mismatched languages, and campaigns copied from older templates.

Measure the two updates separately. For catalog work, create a dated baseline for the exported cohort: number of products in each relevant state, the identified gap, recent media activity, and the business outcome used by your organization. After remediation, compare the same cohort using the same filters and reporting window. A serving-to-active ratio can be a useful internal diagnostic, but it is not presented by Microsoft as an official success metric. More serving products are not automatically better if they have weak margins, poor stock availability, or unsuitable landing pages.

For disclaimers, track implementation quality first: campaigns reviewed, wording approved, eligible campaign coverage, rejected or missing instances, and time to correct an exception. Then monitor downstream indicators such as click-through rate, conversion rate, qualified lead or order quality, revenue, and margin where those measures are available in your stack. Product explorer may not contain every business metric, so connect the audit to the advertiser’s established analytics and finance data.

Annotate every material feed or disclaimer change. Compare stable periods and avoid claiming causality from a simple before-and-after chart. Promotions, bids, budgets, inventory, seasonality, competitor behavior, and creative changes can move simultaneously. Where campaign structure and risk permit, use a limited cohort or controlled release. Microsoft does not promise a performance uplift from either feature, and neither should an implementation team.

• Do not assume access for catalogs at or above the documented threshold.
• Do not assume Microsoft counts SKUs in the same way as your feed platform or ERP.
• Do not treat active, serving, eligible, and profitable as equivalent conditions.
• Do not assume correcting a metadata gap guarantees eligibility or impressions.
• Do not apply the 500-character popup limit outside the documented Native context.
• Do not assume the 80-character format is supported on every placement.
• Do not interpret disclaimer approval as legal certification.
• Do not infer pricing, API access, geography, language coverage, refresh latency, or export format from the announcement.
• Do not promise improved conversion rates or lower media costs.

There is also an organizational risk: a new interface can become a second source of truth rather than a diagnostic layer. Decide which system owns product data, which team may change it, and where approvals are recorded. Retailers running both Microsoft and Google should keep platform findings separate while applying a shared governance discipline. Teams that need that broader paid-search structure can review CreatikLab’s Google Ads management approach without assuming the platforms expose identical controls.

1. Confirm Product explorer access, catalog scope, permissions, and the SKU threshold.
2. Document the available fields and status definitions before creating reports.
3. Choose one commercially important product cohort and export its baseline.
4. Fix a validated sample at the source, then verify what changed in the interface.
5. Inventory campaigns that require promotional, safety, regulatory, or contractual wording.
6. Obtain the appropriate approval and test the eligible disclaimer layout on a controlled scope.
7. Connect catalog and disclaimer changes to an annotated measurement report.
8. Expand only after ownership, exceptions, and review frequency are clear.

The objective is not to maximize the number of feed edits or disclaimers. It is to reduce unresolved catalog issues, make required information consistent, and preserve an audit trail from diagnosis to business result. If several accounts, markets, or data systems are involved, MarketingPro can provide the decision framework around the platform work.

Describe the situation to Lia in MarketingPro—include the SKU volume, feed symptoms, campaign types, required wording, current measurement setup, and decision deadline—so the diagnosis continues with context instead of restarting through a generic contact form.

What is Product explorer in Microsoft Merchant Center?

It is a catalog view that Microsoft says can search and filter products, show active and serving status, provide performance information, identify eligibility or metadata gaps, and export filtered product lists. The official roundup does not publish a complete field dictionary or data-refresh schedule.

Who can access Product explorer?

Microsoft states that it is available under Products for advertisers with fewer than 100,000 SKUs. It says Products is not visible for advertisers with more than 100,000 SKUs. The announcement does not explain the counting method or the exact 100,000-SKU boundary.

Does fixing a metadata gap guarantee that a product will serve?

No. The feature can help identify metadata or eligibility gaps, but the source does not promise that a correction will make a product eligible, generate impressions, or improve commercial performance. Other policy, campaign, inventory, landing-page, and auction factors may still matter.

Which Microsoft Advertising disclaimer formats are documented?

Microsoft documents a popup layout for Native ads with a 500-character allowance and an inline additional line with an 80-character allowance. The source does not provide a complete placement, market, language, or device compatibility matrix.

Does an approved disclaimer guarantee legal compliance?

No. Microsoft says an approved disclaimer will serve with every eligible ad in the campaign. That is a delivery statement, not legal certification. Advertisers still need the appropriate legal or compliance review for wording, scope, language, and applicable obligations.

How should advertisers measure the impact of Product explorer?

Create a baseline for a fixed product cohort, preserve the filters and export, record the issue and remediation, and compare the same cohort after changes appear. Connect platform status to revenue, margin, stock, or lead quality rather than treating a larger serving count as success by itself.