Standalone module

Other updates

Navigating centralized access, performance guardrails, and platform modernization.

Ask about this Page
Copy for LLM
View as Markdown

After completing this page, you should be able to:

  • Implement multi-dimensional segmentation by leveraging the new capability to assign a single customer to multiple Customer Groups via the customerGroupAssignments field.

  • Explain the impact of commercetools Identity on cross-region authentication and how it unifies access across Studio and the Merchant Center.

  • Design resilient integrations that handle the new rate limits for the Change History API using exponential back-off and targeted querying.

  • Identify the performance benefits of React 19 for Merchant Center Customizations and understand the migration path for dependencies.

  • Locate and utilize integrated developer tools, such as the GraphQL IDE and API Playground, within the redesigned Merchant Center settings.

Multiple Customer Groups

Historically, a commercetools Customer object could only be associated with a single Customer Group. This restriction often necessitated complex workarounds for integrators managing customers who qualified for different tiers or segmentation rules simultaneously.

This limitation is now eliminated. Customers can now belong to multiple Customer Groups (up to 500).
This powerful change introduces the customerGroupAssignments field on the Customer object, enabling sophisticated segmentation. A single customer can now benefit from multiple group affiliations at the same time.
The previous customerGroup field will be retained to ensure complete backwards compatibility.

commercetools Identity

Security and user management reached a major milestone in October 2025 with the global transition of the Merchant Center to commercetools Identity. This unified authentication service provides a single, secure account for all commercetools business tools—including Studio and the Merchant Center—across AWS and GCP regions in North America, Europe, and Australia. By centralizing login credentials, this move simplifies Single Sign-On (SSO) integration and enhances security through more robust multi-factor authentication. It preserves your existing project-level permissions and roles while ensuring your global team has consistent access to the entire commercetools ecosystem without the friction of managing fragmented credentials.

Rate limits for Change history API

In 2025 we have introduced rate limits for the Change History API to ensure platform stability and prevent high-volume audit queries from impacting system performance.
If an integration exceeds the allowed request threshold, the API will return a 429 Too Many Requests status code. Developers should implement exponential back-off logic and focus on efficient, targeted queries rather than broad polling to stay within these limits and maintain reliable access to audit logs.

React 19 migration guide for Merchant Center Customizations

In June 2025, commercetools introduced a migration guide to transition Merchant Center Customizations to React 19. This enables developers to leverage the latest performance optimizations and modern features like the use API and Actions. This update ensures that Custom Applications and Custom Views remain fully compatible with the platform’s latest frontend architecture while benefiting from improved rendering and state management. By following this guide to update core @commercetools-frontend dependencies, teams can ensure their UI extensions remain robust, secure, and future-proof.

Deprecations

As you may have noticed, numerous Import/Export capabilities have been added to the Merchant Center. With these enhancements, we’ve decided to deprecate ImpEx.

What about the API Playground and GraphQL IDE, you ask? No need to worry—they’re now integrated into the Merchant Center and better than ever! You can find them in your Project by navigating to Settings ➜ Developer settings.

Additionally, the Menu Visibility feature has been removed from the Merchant Center. Previously, this feature enabled administrators to manually conceal menu links for specific sections. Now, access control is exclusively managed through standard Merchant Center permissions. This decision allows us to concentrate development resources on improving core features that deliver more substantial value.

Test your knowledge