Published game unavailable in Microsoft Store and missing from search

A Partner Center status of Published is not sufficient by itself: confirm that Zen Fourier’s availability configuration was published to RETAIL, with public discoverability, active acquisition, and the relevant markets enabled.

1. Verify the live RETAIL configuration

In Partner Center → Apps and games → Zen Fourier → Pricing and availability, check:

1. Markets
   • Select All worldwide markets, or confirm that every country/region where acquisition is being tested is selected.
2. Visibility
   • Select Make this product available and discoverable in the Microsoft Store.
   • Confirm the audience is public rather than a private audience.
3. Schedule
   • Release: the configured date and time must have passed.
   • Discoverable in the Microsoft Store: select at release, or verify that its separate date and time have passed.
   • Stop acquisition: select Never.
   • No longer discoverable in the Microsoft Store: select Never.
4. Pricing
   • Confirm that a valid price—including Free, if applicable—is configured.
5. Select Save draft, then Review and publish. These are the documented settings for making a game visible and purchasable.^1^

On Review and publish:

1. Set Publish to to RETAIL, not a development or testing sandbox.
2. Confirm every displayed section has status Complete.
3. Select Publish and wait for the resulting submission to finish processing.

Publishing to a testing sandbox does not make the game publicly available; RETAIL is the target used for Microsoft Store customers.^2^

Also check Store listings for the language associated with the tested market. The listing values control the public Store page. If available, complete Gaming metadata, which can help users find the title in Microsoft Store and the Xbox app.^2^

2. Test availability separately from search indexing

After the RETAIL submission completes, perform these independent tests:

• Open the product’s direct Store listing using its Store ID/link in a private browser window.
• Test while signed out, then in the Microsoft Store app with a normal customer account.
• Test from a Windows region that is explicitly enabled under Markets.
• Record whether:
  • the page opens;
  • the Get or purchase button is enabled;
  • the unavailable message remains;
  • exact-name search returns the title.

Interpret the results as follows:

• Direct page permits acquisition, but search fails: acquisition is live; discoverability or search indexing needs investigation.
• Direct page opens but acquisition is disabled: check market, audience, release schedule, stop-acquisition setting, pricing, and RETAIL publication.
• Direct page is unavailable in every enabled market despite correct RETAIL settings: this requires Microsoft Store catalog support; local Store cache resets or app repairs would not address publisher-side catalog state.

The configured discoverability option controls whether customers can find and acquire the product, while market settings control where it is offered.^3^

3. Escalate if the RETAIL configuration is correct

Microsoft Q&A cannot inspect the private catalog record or Partner Center backend for Zen Fourier. Create a publisher support case through Partner Center → Help (?) → Contact Support, selecting the Store/Partner Center category for app or game management. Microsoft’s Windows developer guidance identifies Dev Center support as the route for Partner Center submissions and app-management issues.^4^

Include:

• Product name and publisher name
• Store ID
• RETAIL submission ID and completion timestamp
• Direct Store listing URL
• Enabled test markets and the Windows/Store region used
• Screenshots of:
  • the completed RETAIL submission;
  • Pricing and availability settings;
  • the disabled Get button and exact error;
  • the empty exact-name search result
• Whether the result reproduces signed out and with multiple customer accounts
• The first date/time the issue was observed

Request verification of:

• acquisition eligibility in RETAIL;
• public audience and market propagation;
• release and stop-acquisition state;
• product-page publication;
• search/catalog indexing.

The public support documentation does not specify a mandatory diagnostic field list for this exact catalog symptom, so the support case should provide the identifiers and reproduction evidence above to let Store operations locate the product without additional exchanges.

References

1. Configure a product to be visible and purchasable in the Microsoft Store
2. Step 5 - Publishing your game in Partner Center
3. Set app pricing and availability
4. Help and guidance for Windows developers