commercetools Reviews

While I was working at my previous company, I used commercetools for about one year and built several projects with it.

My main use case for commercetools is making an e-commerce website where the entire dataset and structure have been handled by commercetools. We built a full-stack e-commerce website using Next.js for the front end and Node.js for the back end, with commercetools as the database. All products, SKUs, product types, and everything have been stored inside commercetools and categorized in a way that allows for efficient fetching. We did not have to design our entire database from scratch.

commercetools fits into my workflow by providing the best feature, which is the structure of the data. When calling commercetools API, the structure is straightforward. We do not have to iterate through nested loops inside the data. The data is simple and we can control what sort of data we want from commercetools. That is one of the features I appreciate the most. Additionally, commercetools provides hundreds of APIs that are very useful in cases where you need to print certain customer data or avoid manual joins. The particular information requested is provided by a separate API. Furthermore, the customizations available in commercetools through the Merchant Center allow you to use your own fields inside the Merchant Center and customize the entire platform. That is one of the great advantages and the key differentiator for using commercetools rather than other e-commerce platforms such as Magento or Shopify.

commercetools is deployed in my organization on a public cloud. We purchased the Merchant Center hosted by commercetools itself. We do not need to host anything ourselves. We bought the cloud version, the public cloud version.

commercetools fits into my workflow by providing the best feature, which is the structure of the data. When calling commercetools API, the structure is straightforward. We do not have to iterate through nested loops inside the data. The data is simple and we can control what sort of data we want from commercetools. That is one of the features I appreciate the most. Additionally, commercetools provides hundreds of APIs that are very useful in cases where you need to print certain customer data or avoid manual joins. The particular information requested is provided by a separate API. Furthermore, the customizations available in commercetools through the Merchant Center allow you to use your own fields inside the Merchant Center and customize the entire platform. That is one of the great advantages and the key differentiator for using commercetools rather than other e-commerce platforms such as Magento or Shopify.

commercetools has positively impacted my organization by saving time. First, you do not have to design your own database from scratch according to your e-commerce website needs. Whatever functionality is needed can be managed through commercetools, whether the store is multinational or single nation with multiple positions. Additionally, commercetools provides numerous APIs that are quite useful when making e-commerce websites. While starting a project, you may not know what APIs you will need, but as you build in real conditions and use commercetools, it is quite valuable that you get each functionality by default. The main issue I encountered is the lack of resources for commercetools. I did not find comprehensive resources to learn commercetools. I learned through documentation, but I did not find materials that explain the whole commercetools system in video or lecture format.

Regarding how commercetools can be improved, I did not find anything that could be better in terms of features for my use case. However, the resources and documentation of commercetools could be clearer so developers can understand the APIs and build websites accordingly. Whatever is needed for my use case, commercetools provides. If the project scales and certain companies require additional changes, you might need customization in Merchant Centers. Otherwise, all the features that are there provide what I needed.

Additionally, commercetools could improve how they handle the customer database and orders by consolidating their two separate collections for carts and orders. Once a cart is ordered, it is converted into an order state, and this process could be improved. Furthermore, they could improve the customer collections. When I was using commercetools, there was no AI analytics, but they could add AI features such as product recommendations for specific customers based on their viewership, cart suggestions, and bundle products. These are improvements they could make.

commercetools performs quite well when handling large volumes of data or high traffic situations. When handling a large volume of data and applying filters, the API fetches data very quickly. It stores data in MongoDB, a document-based database. The fields that can be filtered are already indexed in the database. When applying any sort of filter inside a product, for example, if we have 100 million products inside our database, applying a certain category or specific filter returns the first 10 products very quickly, under one second. That performance is quite impressive.

Regarding reliability, I would say commercetools is highly available. It runs on AWS servers, which are quite popular in the IT industry, and the platform is reliable and highly available. I did not encounter any scenarios where commercetools server went down or went offline or the store went offline.

commercetools supports multi-language and multi-currency requirements for global e-commerce with built-in functionality. You can integrate multi-language and multi-currency capabilities. As mentioned earlier, you can integrate different stores in different regions or different stores within one region, and both can be supported by commercetools.

commercetools integrates with other systems and third-party applications through the back end. The flow we created to use commercetools involves a Node.js middleware that handles calls between the front-end Next.js and the commercetools back end. We implemented commercetools SDK in Node.js, and we can fetch whatever is needed from commercetools. From Node.js itself, we integrate different third-party applications such as Google sign-in or Razorpay for payment gateway. We perform that integration from the Node.js application, but I know that you can do some things from commercetools itself, such as payment gateway integration.

commercetools is quite valuable in terms of requiring less work while working with it. That is one of the reasons I chose commercetools. Additionally, our company wanted to explore commercetools. We were working on projects based on Magento, but we wanted to explore other options such as commercetools and Shopify. We built several projects with commercetools and they are still running fine. I would say it is a good option to choose.

The reason I give commercetools an eight is that there are platforms available in the market that are more perfect than commercetools, such as Magento, but those platforms are expensive. If your project or site is not limited by budget constraints, you could still choose Magento. Magento is the best available option in the market. However, if your budget is slightly lower and you still want to use more functionalities, commercetools is a viable option. I gave an eight because it is a more mature platform than others, but it is not the perfect platform.

My experience with the documentation and learning resources for commercetools is that it was not very clear. When I wanted to do something, I needed to go through the entire documentation of that particular feature, whether adding a product or adding a custom field. The documentation was not clear. They should separate documentation for the API, showing what response you can get and the structure of the response, from what that particular feature does. They could separate these things, but they are currently integrated into one. Documentation was reasonably decent, but I have read more structured documentation than this. There are quite a number of fewer resources and fewer YouTube resources available. They should organize more coaching sessions for developers so they can learn commercetools. That is the only problem I encountered.

commercetools helps with personalization and customer segmentation for the e-commerce site quite well. Personalization and customer segmentation capabilities are quite good. However, as mentioned, they should include AI features where they can recommend products to customers. They are lacking in that area. Otherwise, it is fine.

commercetools is quite flexible when it comes to customizing the e-commerce experience. Everything you need to change is available through API or Merchant Centers. You can easily change anything.

My advice is to try not to learn everything inside commercetools because it is not required. Learn only those things that are necessary to save time and apply more knowledge to those areas which are required for your product. My rating for this product is eight out of ten.

Public Cloud

Amazon Web Services (AWS)

My main use case for commercetools is majorly B2C, and I have completed multiple B2C projects with commercetools.

A specific example of a B2C project I completed with commercetools is for an Australian customer for whom we executed a large project. It is a composable commerce implementation where commercetools serves the commerce information, but the front end is built using Node.js and React, specifically using Next.js for that project. It is a large, multi-year project that we delivered.

Regarding my main use case and that particular project, we were enabling the project with backend for frontend. We introduced backend for frontend for that company, connecting multiple systems including commercetools, their PIM platform, ERP, and CRM platforms. This backend for frontend served as middleware between the frontend and backend, creating quite an architecture that performed well.

The best features commercetools offers include recent AI-specific implementations on the MCP part. They have introduced two major areas: one is on Agentic Commerce and the other is on the AI agent. They refer to Agentic Commerce as Agentic Lift and for the AI agent as Autonomous, with the frontend for Autonomous being Mosaic. These two features are what we are currently exploring, and they seem quite interesting, focusing on aspects many other e-commerce platforms are also considering.

These two new features are gaining traction, but aside from those, commercetools has pioneered the composable commerce part of the architecture. It has all the necessary APIs to develop a B2C or B2B platform, utilizing GraphQL and offering good speed. I do not see many competitors having the same pioneering approach.

Commercetools has positively impacted our organization as a service company by allowing us to execute multiple projects and bring in a good amount of business for us.

The kind of business impact I have seen includes delivering commercetools projects for various customers, and as a partner, our company has built multiple accelerators. These accelerators help us sell commercetools internally, enabling us to speed up processes for customers. For example, a new customer we are currently in the discovery phase with found our customer service accelerator very useful, and we are helping them understand and initiate things. This illustrates the opportunities commercetools provides us, which we leverage when paired with the platform.

Improvements for commercetools could focus on their major initiatives around Agentic Commerce and the AI agent. They may need to enhance their marketing strategy as they currently do not host large-scale marketing events. While technology-wise they are solid, a better marketing strategy could benefit them.

On the technical side, commercetools operates robustly as a composable commerce platform. They have an excellent roadmap and strong technology, so I do not see major trouble there. Support is also good overall, although they may be a bit slow with our queries at times.

Improvements for commercetools that have not been discussed yet could include a broader feature set. They offer a good range of features for building B2C or B2B platforms, but enhancing their capabilities could yield a more competitive platform, especially when they face questions regarding why to choose commercetools over others. Their strengths lie in composable commerce and the recent Agentic Commerce, but expanding their feature list would create a more rounded offering.

I have been using commercetools for around two years.

Commercetools is very stable.

In terms of scalability, commercetools provides a set of APIs for functionality, and with their MCPs, we can access all areas of commercetools effectively. The cloud infrastructure allows for flexible scaling up or down as needed.

Customer support from commercetools receives positive feedback, as customers generally consider it to be quite good.

I previously used CCV2, an SAP-based e-commerce platform, which necessitated developing all required APIs manually, unlike the flexibility offered by commercetools, where all APIs are typically built in. Transitioning to commercetools allowed for a much smoother approach aligned with a headless composable MACH architecture.

I have seen a return on investment because development time has significantly reduced with AI involvement. Customers utilizing AI agents for development experience quicker time to market, especially with our accelerators such as the migration accelerator. These implementations help save time effectively.

My experience with pricing, setup cost, and licensing for commercetools reveals that they have competitive pricing. Customers purchase the service directly from commercetools, and if negotiations are necessary, they can work directly with the company.

Before choosing commercetools, I evaluated options such as Optimizely Commerce and BigCommerce. After thorough research, I determined that commercetools was a superior platform for my needs.

Regarding how I am exploring those AI features and any early benefits or challenges, it is very early, and Agentic Commerce is not yet full-fledged. The plan is to discuss with customers to see how we can implement it and what benefits our existing customers would gain from that. Agentic Commerce is picking up speed, and the AI agent has the potential to autonomously adjust product pricing based on competitor pricing, which is a thought I have for implementation. The AI agent also allows us to create promotions on the fly, which is another nice feature.

For data migration and synchronization when implementing commercetools for new clients, we have created a migration tool that understands the structure of existing platforms. Utilizing AI, it helps map the schema for commercetools and manage data transfer seamlessly, ensuring sensitive information is protected while developing API-based architecture quickly for our customers.

The biggest challenges I typically face during a commercetools implementation involved past difficulties with data imports and synchronization, but with recent improvements and AI assistance, processes are moving smoothly now, and I do not see significant issues currently.

To ensure my team stays updated with new features and updates from commercetools, I have implemented an AI agent that scrapes information weekly from various sources. This agent pulls data from newsletters, social media, and the commercetools website, providing me with the latest developments, roadmaps, and press releases to take into consideration.

For training and onboarding new team members working with commercetools, we focus on educating them about e-commerce principles first. Once they grasp the foundational concepts, we introduce them to key commercetools APIs, ensuring they are not overwhelmed while building their understanding gradually.

To measure the success of commercetools implementations for clients, we look at how the platform meets their enhanced functionality needs and how we can accommodate those within commercetools, or via an intermediary database when required. The platform's flexibility for front-end integrations also plays a vital role in our success metrics.

When handling integrations between commercetools and other systems such as ERP or CRM platforms, commercetools allows us to build web hooks for automatic order passing to those systems. This flexibility allows us to create events and process any triggers efficiently, utilizing backend for frontend architecture to connect multiple platforms.

In terms of accuracy and reliability of output from commercetools' AI capabilities, it is quite accurate for tasks such as searching for or checking out products. It effectively understands user prompts and provides good responses. Mosaic also performs well because it is directly connecting to their APIs to find the right tools that need to be called.

My advice for those looking into using commercetools is to view it as a solid mid-range e-commerce platform. It is best suited for those willing to build their front-end. While they offer some integrations such as Frontastic, building a flexible, robust front-end while leveraging commercetools as a backend e-commerce platform is the ideal approach. I would rate this platform a seven out of ten.

Public Cloud

Google

I use commercetools for architecture purposes, and I have worked on specific use cases such as the OMS tool OneStock and the search engine Algolia. In those perspectives, I have used commercetools in an automation, automotive B2C application, specifically for automotive car parts. It includes functionalities such as a product catalog, a cart, and a checkout, as well as pricing and promotions, which are integral to what we are using. I have also utilized it for a MACH architecture, payments, and payment gateways such as Mollie for the Europe region. commercetools serves as a central commerce layer with API-first integration, tying everything together.

commercetools' product information management system has significantly aided my data management processes, particularly with over 10 million different products in our B2B application. We have implemented it seamlessly without performance issues, allowing us to effectively manage our extensive product catalog.

commercetools' multi-tenancy features have been beneficial for my business model by enabling multi-region deployments. We can maintain different setups for various regions, such as the Benelux and US, which makes maintaining distinct aspects much more accessible.

The best features in commercetools include its API-first flexibility, allowing direct plug-ins to Algolia and Mollie without being locked into native modules. Each module functions seamlessly, which I experienced while using OMS with OneStock. The connectivity and implementation are significantly easier with it.

The API-first architecture of commercetools has helped my integration needs by allowing business logic to stay in the background and be exposed only to the front-end for business intelligence and web pages. commercetools ensures compatibility with our constraints, such as GDPR compliance and CCPA, which are already implemented, making it easier to manage compliance moving forward.

commercetools' microservices support my scalable architecture by allowing each action to have a dedicated API. For instance, the cart service is accessible through one API, and order management functions similarly through a different microservice. This structure facilitates seamless operations across various functions.

commercetools is very cost-effective in comparison to custom builds, offering better overall value with built-in GDPR compliance, security, and performance features, thus eliminating the need for additional resource reliance.

The advanced analytics dashboards in commercetools assist in tracking customer behavior and sales trends by providing insights in both B2B and B2C scenarios. The B2C analytics track user interactions during sales events, such as Black Friday, showcasing system resilience and user engagement effectively.

One improvement I would like to see in commercetools relates to DSAR functionality; specifically, customer information should be easily anonymized. Currently, when customers unsubscribe, their personal identifiable information (PII) requires extensive manual tracking across multiple databases, which complicates the anonymization process.

I have been using commercetools for more than one and a half years.

I experienced a challenging moment when commercetools had scheduled downtime, impacting user login and operations simultaneously, which caused significant difficulties for our B2B aspects.

I find commercetools highly scalable with no limitations on scalability, supported by a solid AWS infrastructure, effectively handling high visibility periods such as Black Friday with over 50,000 concurrent users without issues.

I find the setup process of commercetools straightforward, with minimal challenges due to the support offered by the commercetools team. They provide ongoing assistance whenever needed, which simplifies deployment, such as with integration tools such as Datadog.

The setup process of commercetools is straightforward, with minimal challenges due to the support offered by the commercetools team. They provide ongoing assistance whenever needed, which simplifies deployment.

The key differences in comparison to other competitors include commercetools' use of a MACH architecture, which allows easy integration with business intelligence and web applications. However, a con is the need for improvements in DSAR processes for user anonymization.

What went well with commercetools is the API-first flexibility and its ease of integration with Algolia and Mollie without being locked into native modules. The pricing promotions engine manages complex rules effectively, and the headless architecture provides freedom on the front-end.

Everything apart from the previous mention is good; I am impressed with the flexibility and performance of commercetools. I consider it to be an advanced system.

My advice for organizations considering commercetools is to leverage its MACH architecture and headless principles, as it is well-suited for e-commerce applications. After researching various options a year and a half ago, I confidently recommend choosing commercetools for future projects. I would rate this review an 8 out of 10.

Public Cloud

Amazon Web Services (AWS)

My main use case for commercetools is that we built an e-commerce website and we also created a custom application for customer service inside the Merchant Center. We have built multiple websites for different leading industries, so most of the use case comes with e-commerce.

The custom application for customer service inside the Merchant Center helps our team and users accomplish better customer support. We found that as a merchant center, commercetools serves as a tool for complete back-end services, and customer support comes into play. Most companies used to handle customer support via email, but we thought about building a custom application inside Merchant Center to give it to end users so they can handle customer inquiries and related queries within the Merchant Center. They don't need a different tool or different system to manage their customer services.

I have built multiple websites using front end, which I was part of. We use Sigma designs to build and most of the use cases involved building APIs. We used to integrate with third-party applications where their order management system is in a different system such as Azure or a different OMS. We integrate that with commercetools and help them place orders or build back-end APIs. I also worked closely with the architect and sometimes help build the architecture for the back-end project.

The best features commercetools offers in my experience are that it is completely headless. You can make it a standalone back-end application or a standalone front-end application or you can do both, or the possibilities are limitless with commercetools. It doesn't function in a certain way and you don't have any limitations with commercetools. There are a few limitations, but you can be versatile with commercetools. You can use commercetools as a database or as an order management system and you can use it in any possible way. It is a complete system for digital commerce.

The flexibility of commercetools has benefited my team in various ways. Since this is completely headless, if a customer comes in with their order management system in a different system and they wanted to integrate it with commercetools, it is completely possible with an API key. You can integrate it in a matter of minutes and use that order management system. If they have a payment provider in a different system such as PayPal or a different payment system, you can just use API keys and integrate it to commercetools and that's complete. If they want content management or some other things and want to integrate the website to commercetools, that's completely possible. Everything is possible and using the possibilities, we are able to integrate the APIs and databases. It was possible to complete the project.

Commercetools has impacted my organization positively by allowing us to give a better solution compared to other options. If it's completely React based, you have to build everything from scratch. However, commercetools as a SaaS platform gives you everything. You have the APIs, most of the APIs required are available and you have a built-in database with commercetools. You have everything required to speed up your project. If you compare it to plain ReactJS and JavaScript or Java, you have to build everything from scratch or set up the database, which is a time-consuming process. Whereas commercetools has everything in place, you just have to use things and speed up the process. In that way, it is really beneficial.

commercetools can be improved in many ways and there are challenges and frustrations I have run into. commercetools can be improved in many ways because they are only limited to certain things such as product, order and e-commerce stuff, where they could be more versatile. They have payments, but you have to integrate third-party systems or there are certain limitations to it. Since I'm not actively part of it, I don't remember details. There are places that require a lot of improvements, especially the front end, which I was exposed to for a brief amount of time. The front end is not as structured as before, though I heard that it's been improved compared to before. There are a lot of improvements that can be made, and even in GraphQL queries, there can be improvements. I've noticed a lot of flaws here and there, but minimal.

I would add more about the needed improvements from a documentation perspective. There is not much support compared to other things. There are documents, but they are brief and explain what is what and what API can do. If you compare it to AWS or Google, other platforms have tutorials which help you integrate or there are small tutorials with short 30 seconds to one-minute videos that help you do certain things in certain ways. However, commercetools doesn't provide those tutorials to end users or step-by-step guidance. The documentation is there and much clearer, but it would be nice if it's in a video format.

I have been using commercetools for about two years.

Regarding commercetools' AI capabilities, when I was working with commercetools, it was at its lowest settings, so I didn't find that much interesting back then.

Regarding commercetools' AI capabilities, I think its accuracy and reliability of output were around 40 to 50%. When I worked with commercetools AI about a year ago, the accuracy was around 40 to 50%. The answer would change when asked the same question repeatedly. The first time if it says A as an answer, the second time it would say B as an answer. The answer keeps changing even though the question is the same. I hope the accuracy is improved now, but when I was exposed to it, the accuracy was a bit low.

Customer service rating: 4

My advice to others looking into using commercetools is that it is a good tool to purchase or build your web application on it, or to use it as an order management system. commercetools is good. I would definitely recommend someone if they are on a tight budget and they want a great, reliable solution to manage their order system or to host a website. commercetools is really good. I would completely recommend commercetools. I gave this review a rating of 7 out of 10.

Public Cloud

Amazon Web Services (AWS)

My main use case for commercetools is that it functions as a commerce engine in a MACH environment where all of the rest is implemented by different services or different third-party vendors. But the commerce itself, such as card calculations, checkout, and the commerce engine itself, is commercetools.

A specific example of how I used commercetools in a project is that it served as the center core of the e-commerce system. All items which were added into the cart were calculated properly, promotions were applied, discounts were applied, and whatever else was needed. There were no specific tiers for customers' pricing because it was B2C. The rest of the checkout logic was implemented using commercetools.

I think that the primary use of commercetools is to act as the center of the e-commerce system.

The best features commercetools offers include being API-first, which nobody was thinking in this way before. If you ever worked with SAP Hybris or ATG, ATG Commerce, how they call it, Oracle ATG, it was a monolithic system which implements everything in one. Then commercetools stepped in and provided a lot of APIs which are comfortable for developers to work with, which are charged per API use, which are flexible to use in different scenarios. I think for B2C, it is a great solution because at EPAM we were able to implement it quickly. A typical Hybris project is two years, while a commercetools project is more like half a year before go live.

What made those APIs comfortable for developers is that the documentation is very structured. They were able to quickly identify all of the integration scenarios and estimate them. Unlike Hybris or similar monolithic engines, it was much faster because multiple teams were working in parallel. As far as I remember, we had six or seven teams. That is unbelievable speed and that is an unbelievable amount of people working in parallel compared to traditional monolithic systems.

Commercetools has positively impacted my organization by providing a great opportunity to increase time to market. When it comes to pricing, I think it was more or less the same. Every big project is expensive. There was no significant difference in commercetools versus other systems.

The faster time to market benefited my team by allowing us to launch the first MVP version to production in half a year. That is absolutely impossible in traditional monolithic systems.

Commercetools can be improved by remembering that B2B capabilities are limited, unlike Hybris which has a lot out of the box. I think there is a big problem with budgeting nowadays. Most of the customers are looking for cheaper solutions as BigCommerce or Shopify or whatever else. I have seen that at EPAM and I see it now. People are not ready for large-scale commerce re-implementations unlike it was in 2020. For the rest, I think it is a good product. I am not in a position to compare it feature to feature to any modern solution, but most of the customers have selected it before we started the project. So we were not in a position to recommend it or compare it to other systems.

I do not have any ideas about capabilities, but another thought is that Salesforce Commerce has a much larger developer base. I do not know why, but it is much easier to find a Salesforce Commerce Cloud developer, and the rates will be lower, unlike commercetools developer. Probably that is important for some of your clients.

I have been working in my current field for more than twenty years.

Commercetools is stable; I have never seen any faults on a production environment caused by commercetools itself.

For Primark, commercetools' scalability is impressive as they have one million users per day. That is pretty scalable. I think that is an amazing system for that.

I previously used SAP Hybris, and their licensing model was too expensive for the amount of orders they had. Moreover, Hybris got outdated and everyone at Primark wanted to change that.

We did not purchase commercetools through the AWS Marketplace; that was a direct relationship between the customer and a commercetools representative.

Before choosing commercetools, the customer evaluated other options, but I was not part of this process. So the decision was taken by the customer before we stepped in.

I do not have any ideas about capabilities, but another thought is that Salesforce Commerce has a much larger developer base. I do not know why, but it is much easier to find a Salesforce Commerce Cloud developer, and the rates will be lower, unlike a commercetools developer. Probably that is important for some of your clients.

On a scale of one to ten, I would rate commercetools an eight because it is a solid commerce system. I do not see any significant flaws. It is not a ten because to me, it requires a lot of technical knowledge, solution architecture, and proper software development principles or frameworks to implement such a project in a short timeline. A random developer would not be able to use it efficiently.

I chose eight specifically instead of a higher or lower number because it requires a lot of engineering culture and the random developer would not be able to use it effectively, unlike a simpler system as Shopify.

I literally have no idea about commercetools' AI capabilities. I have not seen any AI in commercetools.

I am not the person to talk about the accuracy and reliability of output regarding commercetools' AI capabilities.

My advice to others looking into using commercetools is that in 2026, I would go with a simpler solution. It is really hard to use all of its capabilities, and probably you do not need most of them. If you are not a Primark, if you are not a large international, multi-country, multi-currency, multi-language, multi-catalog company, then probably you do not need that kind of capabilities.

Public Cloud

Amazon Web Services (AWS)

My main use case for commercetools is for a raffle platform where people can buy tickets, add them to their cart, pay for them, and then a winner is chosen from those raffle tickets.

The best features commercetools offers include developer friendliness with many tools available to assist in both development and ideation. The AI Assistant is quite strong and can help with technical questions or architectural questions. There is also the API Playground that you can use to experiment with the data and see what kind of data you are getting back, and the extensibility. The architecture is set up in a way that you can connect to cloud platforms, and its system with extensions and subscriptions is a very elegant way of dealing with extensibility.

Out of those features, the AI assistant is what I find myself using most frequently. It has a very good understanding of what commercetools can do and how best practices are implemented. When we started, this AI Assistant was not available yet, and we had to rely on a technical analyst, but we have noticed that when the AI assistant was introduced, you could basically ask all questions there and it has about the same result. When it comes to the most valuable feature, I would say that the extensibility framework that they have set up is the number one feature of using commercetools.

commercetools has positively impacted my organization, especially for developer experience, as it is a very good tool to work with because it almost feels tailored towards developers. They have great APIs and great documentation. For the organization, I would say that the speed of the go-to-market was quite incredible. I remember when we first kicked off the project, we went live in about a month and a half with a full checkout experience with a payment integration, which is quite amazing. Apart from that, the MACH architecture that commercetools has prompts the rest of the organization to see what is possible and see what the future of these kinds of platforms is and hold themselves to a higher standard.

commercetools can be improved in terms of the interface, especially if you have been away from it for quite a while, as it tends to evolve a lot. Documentation that we have written for our developers or for our analysts becomes outdated very quickly. That is a good thing because there are many features being pushed and many changes, but it is not very consistent. Also, while it is part of the API-first strategy, certain features could really do with a UI. Sometimes you have to use an API to get to a feature, whereas a UI could make it more user-friendly. An API always means that a developer has to execute it or somebody who has technical knowledge. With their Merchant Center, they cover a lot of the functionality, but I remember that promotion-wise or voucher-wise, we could only configure certain features via API at that time. I did see that they added an interface for this, but in general, it is in its nature API-first, and that means that sometimes the interface in the Merchant Center lags behind, which is unfortunate if you are used to having full package solutions that have all of the functionality in the interface.

I have been working in my current field since 2012, so that is coming up on 14 years now. I first used commercetools in February 2023.

I cannot share any metrics or numbers around time saved, cost reduction, or any other measurable outcomes my organization saw after adopting commercetools since we started from scratch, so I do not have anything to compare it to. However, the measurable outcome is the fact that we had a very tight deadline and we were able to meet it because of commercetools and the way that the platform is set up. Cost reduction is hard to define, but in terms of time saved in development, I think if we had to do it on a different platform, we would have spent around three to five times the effort.

Regarding governance and security, if you are looking at the AI chat assistant, I did notice that sometimes it feels like it has access to certain internal information, and it was found out that it was hallucinating and offering internal APIs. I would rate commercetools overall at a nine out of ten. I chose a nine out of ten because the approach that they are taking with the API-first strategy is something that needs to be applauded, but it does mean that for business users, it can feel a bit immature or unsure if the feature is really going to be there in the long run. There are often some beta features that are only available via API, and it can give a sketchy feeling when you are implementing a feature that you cannot use via Merchant Center or maybe will be deprecated in the long run.

My main use case for commercetools is maintaining a website that uses commercetools as a database. A quick, specific example of how I interact with commercetools in my daily work is that every day I have to check commercetools for a specific client. I check orders, investigate any new bugs, and use commercetools front end for these tasks.

Other than that, I use commercetools API daily. If something is not available through commercetools front end, then I have to use the API directly to maintain something, check orders, check users, or perform other necessary tasks.

The best feature that commercetools offers in my experience is customizability. For every specific entity in commercetools, you can create a custom entity, and under custom entity, you have your own custom fields. Everything is customizable and you can incorporate whatever specific requirements you have. Pretty much everything is doable in commercetools.

Regarding the customization options I mentioned, we have a few enterprise clients that have a lot of custom, unusual features and options that they require, and everything that we have had to implement, we could do it inside of commercetools one way or another. The commercetools documentation is pretty huge and very helpful. For example, we had to implement multi-warehouse for a specific client inside of commercetools and you can create your own custom parcels, custom packages, and custom shipping options. Since everything is customizable, we can implement everything.

One of the great features of commercetools is that you can subscribe to changes for any entity. Inside of commercetools, you can create subscriptions for any entity and any change on that entity. If you have a microservice on a microservice architecture, you can create a new microservice and new event, new service bus, and based on that specific subscription that you create, you can create an event bus, and based on those messages, you can do everything. You can subscribe to only products change, for example, and based on the products change messages, you can implement whatever you need.

commercetools has impacted my organization positively, especially for a specific client if they request scalability. If you want to create something that is infinitely scalable, commercetools is a great way to do that. Since everything is messages and service bus or event-driven architecture, there is no limit on how many orders you can process daily and how far you can go.

We have increased order volume, but that is not only because of commercetools. That is also because of some other things, but after commercetools implementation, we have faster processing times and at the same time we can ship more orders daily.

commercetools can be improved with plugins and third-party packages. For example, the payment depends on what your requests are and which payment you use. You can use some third-party or plugin for payment that is outdated and we had some issues on that part, but it depends on what your exact need is.

I have been using commercetools actively for the past two years.

commercetools is pretty stable.

commercetools is infinitely scalable, so that is one great thing. One thing to mention is that backward compatibility with commercetools is excellent, so you don't have to be constantly updating everything.

Customer support is excellent. If you have any issue that you can't figure out, you can call customer support and resolve pretty much everything you need.

We have used .NET CMS for NopCommerce, which is open source and free to use. It is just outdated, built a long time ago, more than ten plus years ago, so it had to be redone.

We did evaluate other options, but I don't really remember right now. It was a long time ago. The main thing was scalability, so that is why we decided on commercetools.

The project is not that long in production, so we don't have any specific metric right now.

We haven't had any issues with commercetools security.

The main issue is the price. Usually you have a Windows server and that is pretty much the only thing you have to pay. If you want to switch and make everything infinitely scalable, you have to do Azure serverless, commercetools, and the expense ramps up and gets pretty expensive. If you really need it, take commercetools. Other than that, I would just do some open-source CMS and go from there.

At this point, the product works flawlessly.

It depends on how you look at it. If you think about commercetools, the product itself is an excellent solution that you can use. However, it is pretty expensive and sometimes it makes sense to create a monolithic architecture project that can sustain a lot of orders. commercetools is great for very large enterprise solutions, but anything smaller, I think it is just too expensive.

You can use commercetools AI implementation for searching documentation and helping you decide on what to implement and where, and I have used it and it is pretty nice. I haven't had any issues, but I didn't use it that much.

My overall rating for this product is eight out of ten.

My main use case for commercetools is B2B and B2C, majorly B2C.

A quick specific example of how I'm using commercetools for B2C is that we have been using commercetools for catalog, cart, pricing, promotion, and orders.

I do not have anything else to add about my main use cases for commercetools.

The best features commercetools offers are catalog, cart, and order.

What I value about the catalog, cart, and order features is the modeling that I could do with the catalog and cart. Additionally, I appreciate the support that I have for the orders and the modeling of it. I also have integrations where I can do extensions and subscriptions with commercetools, which is a SaaS platform, and I can get back the payload from commercetools. Those are some good features.

commercetools has positively impacted my organization, as we have been using commercetools for more than five years. We have implemented two productions end to end, and we have been getting inquiries for commercetools.

Regarding the positive impact, we have seen the agility and the speed and customer satisfaction as well, so we could deliver things in less time.

I think commercetools can be improved if they can reduce their downtime, as that would be really helpful. The other area is noisy neighbor because it is a SaaS product. If they can somehow manage the noisy neighbor, meaning when there is a load on the data of one customer, the other customer should not get impacted, so that is where they can improve.

I am satisfied regarding additional needed improvements or any other pain points I have experienced.

I have been using commercetools for six plus years.

commercetools is stable in my experience.

commercetools' scalability is good, but before every peak season, we have to ask them to scale out, and if they do that, it is okay.

The customer support is good.

I would rate the customer support a nine on a scale of one to ten.

Before commercetools, we used Elastic Path, and we switched because at that point in time, Elastic Path was not SaaS. commercetools was and it supports MACH: Microservices, API, cloud-native, and headless solution.

I did not purchase commercetools through the AWS Marketplace.

I was not involved in the pricing, setup cost, and licensing, as there is another team, so I do not have that data with me.

I do not have information about a business relationship with this vendor other than being a customer.

I have not seen a return on investment, and I do not have that information with me.

I was not involved in the pricing, setup cost, and licensing, as there is another team, so I do not have that data with me.

Before choosing commercetools, we evaluated just two options: Elastic Path and commercetools.

My advice to others looking into using commercetools is to discuss your functional and non-functional requirements with them before deciding on it and do some kind of a proof of concept with the platform before deciding on it.

I would not prefer to add anything else about the features before we move on.

I did not purchase commercetools through the AWS Marketplace.

We have not used commercetools' AI capabilities yet, so I cannot comment on its accuracy and reliability of output.

I found this interview good and do not think anything should change for the future. I would rate this review an eight on a scale of one to ten. Thank you.

Private Cloud

Amazon Web Services (AWS)

My main use case for commercetools is for a migration for a large company, a multi-brand, multi-country, multi-channel organization that wanted to migrate from SAP Hybris to commercetools.

A concrete example of how commercetools is helping in this migration process is its MACH architecture, which has helped significantly because the microservices-based foundation provides superior agility. Additionally, the possibility of integrating whatever tools are necessary to manage each part of an e-commerce operation provides substantial flexibility to manage a brand however desired and adapt it to specific needs.For example, when managing translations, this freedom meant that by using an external platform, we were able to be super agile in changing any translation, even on the fly if necessary.The feature that has positively surprised me in my day-to-day work is the ease of use of its control panel and its architecture, which I believe is very well thought out and is its greatest strength.Regarding the control panel, I find everything in general very intuitive and useful for daily management. All the settings panel and control panel elements are very accessible, and if logic is used to find the most obvious place for something, it is indeed there.commercetools has positively impacted my organization by improving efficiency, facilitating the integration of new services, and especially development with its microservices architecture, which greatly encourages having new releases and being able to deploy much more frequently and atomically without as many regression errors, because everything is more isolated, which helps significantly.

There is no other specific aspect of commercetools that has been especially valuable for me or my team during this migration process, but in general, the whole MACH architecture has turned out to be super useful. For cases of especially very large companies that want to heavily adapt the product to very specific needs, it seems to be really powerful, although in some aspects it may fall short compared to other alternatives, such as when configuring out-of-the-box tools.The issues I encountered with configuring the shipping methods in commercetools relate to the out-of-the-box configuration, where there is a limitation on the number of delivery modes. We had to economize when creating them. With so many countries and brands to configure, we often had to adapt the shipping methods, which were ultimately independent for each brand and country, and we had to negotiate with the stakeholders of each country and brand so that they would have to adapt their shipping options to what was already configured or try to create a new more generic version of a shipping method.This limited us a bit when managing this very large company because of all the countries and brands involved, which created challenges.commercetools could improve in some out-of-the-box tools, such as the configuration of delivery modes, which could be a bit more flexible and powerful, but in general, it is a fairly mature and powerful platform that can have a great future.

I have been working as a developer for about eight and a half years, focused on e-commerce and specifically mainly on Salesforce Commerce Cloud for four and a half years, almost five, and with commercetools I have only been working for about four months in the role of IT Business Partner.

commercetools merits a rating of nine overall.I give commercetools a nine and not a ten because of certain limitations in the power of some out-of-the-box tools, but in general, everything else is a ten. I lower it one point because of this limitation that I encountered in my specific case.My advice to other companies considering implementing commercetools is to ensure that the type of architecture fits their needs, as it may not be necessary for some companies to have something so powerful, though its flexibility and agility compared to other alternatives is a big plus. My overall review rating for commercetools is nine out of ten.

On-premises

Other

My main use case for commercetools is that I use it daily to integrate the e-commerce engine for a large website belonging to a major client.

The integration works by using commercetools to manage the checkout, where we handle orders, carts, and promotions, including discounts, cart discounts, and discount codes. We use most, but not all, of the features that commercetools offers to support our e-commerce integration.

In my experience, some of the best features commercetools offers are customer groups, which let you differentiate customers, and promotions, which give you the power to make strategic marketing decisions.

These features have helped me on my projects when implementing marketing strategies  for example, during Black Friday, when we created promotions targeted at customers in a specific customer group to increase the likelihood of them purchasing certain products.

I also integrated custom applications into the Merchant Center, giving our client the ability to see additional information that isn't available in the standard order section, such as a custom list of orders.

I don't have any improvements to suggest. I really enjoy working with commercetools, and I currently don't have any other suggestions regarding things that need improvement — even small ones, such as documentation, UI, or integrations.

I have been using commercetools for a year.

In my experience, commercetools is stable. I haven't encountered any unexpected downtime or instability, even during high-traffic periods such as Black Friday.

The scalability of commercetools is good it can handle growth and spikes in demand without any issues. I haven't experienced any problems related to this.

My experience with commercetools' customer service has generally been positive. The documentation is very solid and often resolves issues without the need to open a ticket. When I have needed to reach out  usually for more nuanced API behavior or webhook edge cases — the team has been responsive and technically competent.

I did not previously use a different solution before commercetools as this is my first time with it.

The initial setup wasn't straightforward for me or my team, since I had no prior knowledge of commercetools when I started working with it. I learned commercetools gradually, through on-the-job experience and self-study.

I monitor and track errors or issues in commercetools using external tools, as there isn't a built-in feature for this.

I have not seen a return on investment as I am just a developer.

My experience with pricing, setup costs, and licensing has been good, as I use the embedded pricing feature that commercetools offers to attach prices to our product catalog.

Before choosing commercetools, we evaluated other platforms and headless e-commerce solutions similar to commercetools.

The AI is helpful for simple questions, but for more complex ones, it sometimes gives me the wrong answer — its accuracy isn't 100%.

commercetools is very flexible because it's headless, so through the API you can easily connect it to other platforms, such as AWS, for example by using extensions and subscriptions.

The documentation and resources available for commercetools are very clear and helpful.

For testing, I only do visual testing through the Merchant Center, since the platform doesn't provide support for this process.

I think commercetools handles high-traffic events, such as Black Friday, well, without performance issues.

I can easily manage user access and permissions within commercetools, as there's a dedicated section for configuring these settings.

I would rate this product an 8 overall.

Amazon Web Services (AWS)