This guide provides an introduction to all of the native product types in Magento and when it makes sense to use them.

This checklist is designed to provide support for retailers looking to launch a new Magento 2 store - detailing areas that should be considered prior to going live, through the project and post-launch.

This question has come up a couple of times with Magento clients of ours over the last few months – with clients asking whether customer accounts should be global (giving customers the ability to login on any store) or restricted to an individual website level. By far the most common use case for this would be for international retailers with multiple localised websites – and there’s not really a right or wrong answer.

A couple of weeks ago I was asked for recommendations from a long-standing client for a solution for maintaining their Magento 1 store for ~2 months beyond the June end of life date – and, with this not being the first time I’ve been asked about this, I decided to write up a blog post.

One of the most common frustrations with eCommerce platforms that I hear from clients and retailers in general is content management, with very few mainstream eCommerce platforms having a good offering in this area. I wrote this article specifically for Magento as it’s a really common discussion topic when we go through requirements gathering phases with clients looking to move over to Magento 2.

Headless commerce is everywhere at the moment – with merchants, eCommerce platforms, technology partners and CMS providers focusing heavily on readying for this shift. The concept of ‘headless’ provides benefits around performance, serving different formats, development flexibility and fairly often achieving best-in-breed CMS features (via integrating with a headless CMS or traditional CMS) and more. The headless eCommerce trend will only continue to grow and there are new examples of bigger and better-known sites using Magento for headless builds every week at the moment.