Tips, Tricks and Resources

Hey commercetools Community! 👋 Let's talk about something super cool today – Custom Views in Merchant Center! 🚀 So, what are Custom Views, you ask? In a nutshell, they allow you to tailor the Merchant Center to your unique business needs. Think of them as a way to go beyond the traditional usage and make the platform truly yours. Isn’t that awesome? 😎 Imagine having a Product Detail Page (PDP) preview page or creating views that are CSR-specific. Yep, Custom Views can make that happen! 🎉 Here are a few ways you can use Custom Views: PDP Preview: Create a special preview page for your products to see exactly how they will appear to customers before they go live. 🛍️ CSR Specific Viewing: Design views tailored for Customer Service Representatives to access the information they need quickly and efficiently. 💼 Business-Specific Dashboards: Customize dashboards to display the key metrics and insights that matter the most to your business. 📊 With Custom Views, the possibilities are end

Hi, I’m trying do import products trough the Merchant Center CSV import and we had a file that was working a few weeks/months and now when I tried again the same file it is not working anymore. The reported error is useless as you can see from the screenshot. Product import error, Merchant Center Guess there where some “under the hood changes” that destroy our old import file, and the logging is very bad for the Merchant Center import, for every case that fails it’s very hard to guess what’s wrong. Regards, Drazen

Hey community,as you might now, in presales we are often explaining what our software does. I recorded a short video about commercetools Checkout.The differences when it comes to full page checkout vs. payment only, PSP and giftcard integration and predicates to control which payment method is being displayed.It is not an official commercetools video just something a Solutions Engineer created.

commercetools released custom views a while ago and we are often asked in presales, what do they do? For this purpose we have built a small collection of different views and just in case you need them, here is the repository :-) https://github.com/commercetools-demo/integration-views Most of the data is actually fake but looks really good. Listing the carts of a user Cart detail Customer Dashboard Shopping List of a Customer Edit the Shopping List Adding Items to a Shopping List Order Dashboard

commercetools gives amazing flexibility in extending the system and adding functionality. Two major approaches include creating an API Extension or putting a new microservice in front of the commercetools API. It’s often confusing on when to use each approach. I’ve pulled together my thoughts here - https://www.ariessolutions.io/api-extensions-and-microservice-layers/ - but would love to hear your take. How do you decide when to build an API Extension or when to build a service?

Hello commercetoolers! Exciting news for anyone working on loyalty! Voucherify has just rolled out an open-source Next.js loyalty app accelerator, powered by top MACH technologies like Voucherify, Segment, and Braze. You can grab the code from GitHub to speed up your app development or use it as a proof of concept to showcase how the MACH stack can be used for building loyalty programs. More information can be found here: https://www.voucherify.io/blog/open-source-loyalty-accelerator-for-omnichannel-retail Comment or DM me for access! ✨

We’ve just launched a new youtube channel. Are first series covers commercetools Promotions. - What topics should we add next?

Hey community members,a while ago I wrote a blogpost about how we bootstrap our projects in presales. You can read the blogpost here: https://commercetools.com/blog/how-to-kickstart-your-commercetools-projects Just wanted to let you know that we have just released a new version of the code: https://github.com/commercetools/project-bootstrap The repository contains a collection of all kind of commercetools APIs . So if you ever need to do anything with our APIs, it might be a good starting point. Currently the project contains actions to import, export and translate data. While the repository is part of the commercetools organization, you will not get official support for the code. It is really just some code to help you move quicker.

I have been working with the Commercetools AI-powered Developer Assistants. I shared my first impressions here:https://www.linkedin.com/pulse/i-tried-commercetools-ai-powered-developer-assistants-murillo-infdc/?trackingId=2eayqVx8S%2FGADxvy4eU9KQ%3D%3D . If you are not using it yet, I suggest you start using it.

Hi all, We’ve recently launched a handful of helpful assets if you’re thinking about running more loyalty-focused incentives and strategies in your commercetools store! Here you can find the webinar that Voucherify co-hosted with commercetools on how composability impacts loyalty: https://commercetools.com/resources/video-on-demand/next-level-loyalty Also, here you can find a handy cheat sheet of all the steps you need to consider when planning a loyalty program – from design to operations: https://www.voucherify.io/ebooks/the-loyalty-framework As a partner of commercetools for all things loyalty & promotions, I’d love to hear about the good and the bad when it comes to the loyalty strategies you’ve implemented for your store. Let’s brainstorm together on how to improve your already thriving or soon-to-be reward programs 🙌

Recently, I needed to generate a token to log a customer into a web app based on Commercetools. Using the Java SDK to communicate with Commercetools, I found that their Authorization API offers several authorization flows: Client Credentials: Creates a token for an API Client. Password Flow: Creates a token using the customer's login credentials. Anonymous Session Flow: Creates a token for an anonymous session (for a customer who might log in or sign up later). Refresh Token Flow: Refreshes an access token. In this article, I'll focus on generating an authentication token using the Password Flow. Commercetools provides an out-of-the-box method called GlobalCustomerPasswordTokenSupplier for this purpose. Below is the code snippet I used in a service class to generate the token. public static AuthenticationToken getTokenForGlobalCustomer(final String prefix, final String email, final String password) throws IOException { final Properties prop = new Properties(); prop.load(ClientService.c

🎉 Hey everyone! 🎉 Are you ready to take your development game to the next level? 🚀 Have you tried out the TypeScript SDK Sandbox Template! 🔧 Whether you're delving into TypeScript development or aiming to streamline your workflow with the commerectools SDK, this sandbox template is your ultimate companion. Boasting pre-configured settings and a user-friendly interface, it's never been simpler to delve into the potentials of our robust SDK. This sandbox template offers the ideal environment to experiment, test, and tinker with the commerectools SDK. From product management to order handling, everything you need is right at your fingertips. 💡 Some wonders you can achieve with the TypeScript SDK Sandbox Template? Take a dive into: Product Management: Effortlessly explore creating, updating, and deleting products. Order Handling: Test the waters with order creation, processing, and management functionalities. 🔗 Eager to kick-start your exploration? Swing by Sandbox to access the sand

Hello! We would like to invite your thoughts on what makes you choose GraphQL over Rest API? Is it the idea of ability to pick required fields to query and receive a pre-defined result or is it about ability to query complex and interrelated data sources via one endpoint? Tip: commercetools allows you to query entities either via Rest or GraphQL API depending upon your specific use cases. Our GraphQL schema lets you determine query complexity when you design your application which helps you prevent any performance issues these GraphQL queries may add. Please read more here

The commercetools SDKs make it easy to gain more visibility into your commerce operations. We provide popular APM integration support in each of our SDKs to enable users to track sessions/requests effectively and monitor the reported data dashboard and performance statistics. Here is the documentation. We’re curious: How do you keep an overview of the status and performance of all the other components of your commerce implementation?