Exploring Shopify: A developer's perspective

Exploring Shopify: A developer's perspective

Exploring Shopify: A developer's perspective

Exploring Shopify: A developer's perspective

Get in-depth tips and insights for Shopify web development from industry experts who use the platform to build websites and online stores.

Get in-depth tips and insights for Shopify web development from industry experts who use the platform to build websites and online stores.

Ecommerce-tips

Ecommerce-tips

Ecommerce-tips

Sep 27, 2024

Hi. I’m Ksenia Zvereva, Developer Community Lead at Mollie, and someone who spends most of my time with developers and the technical community. During my working life, I have mostly worked with ecommerce platforms that require advanced technical knowledge. But recently, I’ve become more and more fascinated by the rise of Shopify in Europe and its efforts to win the hearts and minds of developers.

Curious about its usability myself, I explored the product firsthand. My initial impression? It’s straightforward. Do you really need to be a developer to build with this technology? Maybe not: the level of accessibility and UX is outstanding. Shopify minimises the need for backend maintenance and DevOps, which helps in reducing costs compared to on-prem systems. Its user-friendly interface is accessible even without technical knowledge, allowing users to get started quickly.

I wanted to learn more. So, I sat down with experts that regularly use Shopify to build websites to understand its nuances: Simon Freimoser, Director Client Services – Shopify at Strix DE, Yann Karl, CTO at Strix DE, and Tico van Beurden, Head of Product at Ask Phill, to explore the platform.


Hi. I’m Ksenia Zvereva, Developer Community Lead at Mollie, and someone who spends most of my time with developers and the technical community. During my working life, I have mostly worked with ecommerce platforms that require advanced technical knowledge. But recently, I’ve become more and more fascinated by the rise of Shopify in Europe and its efforts to win the hearts and minds of developers.

Curious about its usability myself, I explored the product firsthand. My initial impression? It’s straightforward. Do you really need to be a developer to build with this technology? Maybe not: the level of accessibility and UX is outstanding. Shopify minimises the need for backend maintenance and DevOps, which helps in reducing costs compared to on-prem systems. Its user-friendly interface is accessible even without technical knowledge, allowing users to get started quickly.

I wanted to learn more. So, I sat down with experts that regularly use Shopify to build websites to understand its nuances: Simon Freimoser, Director Client Services – Shopify at Strix DE, Yann Karl, CTO at Strix DE, and Tico van Beurden, Head of Product at Ask Phill, to explore the platform.


Hi. I’m Ksenia Zvereva, Developer Community Lead at Mollie, and someone who spends most of my time with developers and the technical community. During my working life, I have mostly worked with ecommerce platforms that require advanced technical knowledge. But recently, I’ve become more and more fascinated by the rise of Shopify in Europe and its efforts to win the hearts and minds of developers.

Curious about its usability myself, I explored the product firsthand. My initial impression? It’s straightforward. Do you really need to be a developer to build with this technology? Maybe not: the level of accessibility and UX is outstanding. Shopify minimises the need for backend maintenance and DevOps, which helps in reducing costs compared to on-prem systems. Its user-friendly interface is accessible even without technical knowledge, allowing users to get started quickly.

I wanted to learn more. So, I sat down with experts that regularly use Shopify to build websites to understand its nuances: Simon Freimoser, Director Client Services – Shopify at Strix DE, Yann Karl, CTO at Strix DE, and Tico van Beurden, Head of Product at Ask Phill, to explore the platform.


Hi. I’m Ksenia Zvereva, Developer Community Lead at Mollie, and someone who spends most of my time with developers and the technical community. During my working life, I have mostly worked with ecommerce platforms that require advanced technical knowledge. But recently, I’ve become more and more fascinated by the rise of Shopify in Europe and its efforts to win the hearts and minds of developers.

Curious about its usability myself, I explored the product firsthand. My initial impression? It’s straightforward. Do you really need to be a developer to build with this technology? Maybe not: the level of accessibility and UX is outstanding. Shopify minimises the need for backend maintenance and DevOps, which helps in reducing costs compared to on-prem systems. Its user-friendly interface is accessible even without technical knowledge, allowing users to get started quickly.

I wanted to learn more. So, I sat down with experts that regularly use Shopify to build websites to understand its nuances: Simon Freimoser, Director Client Services – Shopify at Strix DE, Yann Karl, CTO at Strix DE, and Tico van Beurden, Head of Product at Ask Phill, to explore the platform.


Why choose Shopify?

Ksenia Zvereva: To start, why Shopify? What are the typical use cases? 

Tico van Beurden: Shopify offers a solution for all types of ecommerce brands, from small single-person companies to massive brands like Gymshark, Allbirds, and Kylie Cosmetics. The beauty of Shopify is that it helps brands scale without the need to transfer platforms. Whether you're using a theme from the Theme Store, customising a theme, building a custom theme, or going headless – Shopify offers solutions for all types of brands. We used to see a focus on D2C brands, but Shopify is evolving into a solution for all types of online shops. Whether you’re selling online, B2B, offline, or reselling, Shopify can help you.

Simon Freimoser: Couldn’t agree more! Shopify has done great in leaving that image of the ‘shopsystem for small entrepreneurs’ behind. The last couple of Shopify Editions, their bi-annual releases of new features, have especially appealed to larger companies. Shopify now serves SMEs, niche-players, and dropshippers just as well as it serves larger enterprises with or without physical outlets. Also the foothold they’ve gained with pure B2B players in the last year or so is truly remarkable and shows that they take their vision of ‘making commerce better for everyone’ seriously.

Ksenia Zvereva: Shopify is renowned for its intuitive interface, templates, and themes. But why do developers love building with Shopify? It isn’t a developer-first platform. What is the developer’s role in a Shopify project?

Tico van Beurden: Shopify might not be a developer-first platform, but it’s definitely developer-friendly with a customer-first approach. At the end of the day, we don’t make websites for ourselves but for our clients. Shopify understands this and puts it into practice. This makes sense because the platform and developers both serve the same goal: making the website better and the life of the business easier. Shopify offers good development tools such as their own CLI and SDKs, which we then use to build our sites. This, in combination with a stable backend with extensive features that keep evolving, creates a very developer-friendly environment.

Yann Karl: Shopify’s emphasis is definitely on the user side, but also the developer appeal has grown significantly in the last couple of years. The abundant API offering allows developers to extend the platform's functionality and integrate with external systems easily, even without the need of a middleware. 

Liquid, Shopify’s template engine, is easy to learn and a powerful tool to create custom themes and storefronts. It’s also already well integrated into existing development platforms which support e.g. auto-complete or code suggestions to ease up daily developer life.

To get started, Shopify offers detailed documentation for all its extension points and functions, supporting developers not only on customising themes, but also on building custom apps for additional functionalities or third party integrations, which can then be sold on the Shopify App Store.

In general, from a user and developer perspective, Shopify's ready-to-use infrastructure offers fast time to market which allows all parties to focus on building a great experience without worrying about hosting, security, or performance issues.

Ksenia Zvereva: To start, why Shopify? What are the typical use cases? 

Tico van Beurden: Shopify offers a solution for all types of ecommerce brands, from small single-person companies to massive brands like Gymshark, Allbirds, and Kylie Cosmetics. The beauty of Shopify is that it helps brands scale without the need to transfer platforms. Whether you're using a theme from the Theme Store, customising a theme, building a custom theme, or going headless – Shopify offers solutions for all types of brands. We used to see a focus on D2C brands, but Shopify is evolving into a solution for all types of online shops. Whether you’re selling online, B2B, offline, or reselling, Shopify can help you.

Simon Freimoser: Couldn’t agree more! Shopify has done great in leaving that image of the ‘shopsystem for small entrepreneurs’ behind. The last couple of Shopify Editions, their bi-annual releases of new features, have especially appealed to larger companies. Shopify now serves SMEs, niche-players, and dropshippers just as well as it serves larger enterprises with or without physical outlets. Also the foothold they’ve gained with pure B2B players in the last year or so is truly remarkable and shows that they take their vision of ‘making commerce better for everyone’ seriously.

Ksenia Zvereva: Shopify is renowned for its intuitive interface, templates, and themes. But why do developers love building with Shopify? It isn’t a developer-first platform. What is the developer’s role in a Shopify project?

Tico van Beurden: Shopify might not be a developer-first platform, but it’s definitely developer-friendly with a customer-first approach. At the end of the day, we don’t make websites for ourselves but for our clients. Shopify understands this and puts it into practice. This makes sense because the platform and developers both serve the same goal: making the website better and the life of the business easier. Shopify offers good development tools such as their own CLI and SDKs, which we then use to build our sites. This, in combination with a stable backend with extensive features that keep evolving, creates a very developer-friendly environment.

Yann Karl: Shopify’s emphasis is definitely on the user side, but also the developer appeal has grown significantly in the last couple of years. The abundant API offering allows developers to extend the platform's functionality and integrate with external systems easily, even without the need of a middleware. 

Liquid, Shopify’s template engine, is easy to learn and a powerful tool to create custom themes and storefronts. It’s also already well integrated into existing development platforms which support e.g. auto-complete or code suggestions to ease up daily developer life.

To get started, Shopify offers detailed documentation for all its extension points and functions, supporting developers not only on customising themes, but also on building custom apps for additional functionalities or third party integrations, which can then be sold on the Shopify App Store.

In general, from a user and developer perspective, Shopify's ready-to-use infrastructure offers fast time to market which allows all parties to focus on building a great experience without worrying about hosting, security, or performance issues.

Ksenia Zvereva: To start, why Shopify? What are the typical use cases? 

Tico van Beurden: Shopify offers a solution for all types of ecommerce brands, from small single-person companies to massive brands like Gymshark, Allbirds, and Kylie Cosmetics. The beauty of Shopify is that it helps brands scale without the need to transfer platforms. Whether you're using a theme from the Theme Store, customising a theme, building a custom theme, or going headless – Shopify offers solutions for all types of brands. We used to see a focus on D2C brands, but Shopify is evolving into a solution for all types of online shops. Whether you’re selling online, B2B, offline, or reselling, Shopify can help you.

Simon Freimoser: Couldn’t agree more! Shopify has done great in leaving that image of the ‘shopsystem for small entrepreneurs’ behind. The last couple of Shopify Editions, their bi-annual releases of new features, have especially appealed to larger companies. Shopify now serves SMEs, niche-players, and dropshippers just as well as it serves larger enterprises with or without physical outlets. Also the foothold they’ve gained with pure B2B players in the last year or so is truly remarkable and shows that they take their vision of ‘making commerce better for everyone’ seriously.

Ksenia Zvereva: Shopify is renowned for its intuitive interface, templates, and themes. But why do developers love building with Shopify? It isn’t a developer-first platform. What is the developer’s role in a Shopify project?

Tico van Beurden: Shopify might not be a developer-first platform, but it’s definitely developer-friendly with a customer-first approach. At the end of the day, we don’t make websites for ourselves but for our clients. Shopify understands this and puts it into practice. This makes sense because the platform and developers both serve the same goal: making the website better and the life of the business easier. Shopify offers good development tools such as their own CLI and SDKs, which we then use to build our sites. This, in combination with a stable backend with extensive features that keep evolving, creates a very developer-friendly environment.

Yann Karl: Shopify’s emphasis is definitely on the user side, but also the developer appeal has grown significantly in the last couple of years. The abundant API offering allows developers to extend the platform's functionality and integrate with external systems easily, even without the need of a middleware. 

Liquid, Shopify’s template engine, is easy to learn and a powerful tool to create custom themes and storefronts. It’s also already well integrated into existing development platforms which support e.g. auto-complete or code suggestions to ease up daily developer life.

To get started, Shopify offers detailed documentation for all its extension points and functions, supporting developers not only on customising themes, but also on building custom apps for additional functionalities or third party integrations, which can then be sold on the Shopify App Store.

In general, from a user and developer perspective, Shopify's ready-to-use infrastructure offers fast time to market which allows all parties to focus on building a great experience without worrying about hosting, security, or performance issues.

Ksenia Zvereva: To start, why Shopify? What are the typical use cases? 

Tico van Beurden: Shopify offers a solution for all types of ecommerce brands, from small single-person companies to massive brands like Gymshark, Allbirds, and Kylie Cosmetics. The beauty of Shopify is that it helps brands scale without the need to transfer platforms. Whether you're using a theme from the Theme Store, customising a theme, building a custom theme, or going headless – Shopify offers solutions for all types of brands. We used to see a focus on D2C brands, but Shopify is evolving into a solution for all types of online shops. Whether you’re selling online, B2B, offline, or reselling, Shopify can help you.

Simon Freimoser: Couldn’t agree more! Shopify has done great in leaving that image of the ‘shopsystem for small entrepreneurs’ behind. The last couple of Shopify Editions, their bi-annual releases of new features, have especially appealed to larger companies. Shopify now serves SMEs, niche-players, and dropshippers just as well as it serves larger enterprises with or without physical outlets. Also the foothold they’ve gained with pure B2B players in the last year or so is truly remarkable and shows that they take their vision of ‘making commerce better for everyone’ seriously.

Ksenia Zvereva: Shopify is renowned for its intuitive interface, templates, and themes. But why do developers love building with Shopify? It isn’t a developer-first platform. What is the developer’s role in a Shopify project?

Tico van Beurden: Shopify might not be a developer-first platform, but it’s definitely developer-friendly with a customer-first approach. At the end of the day, we don’t make websites for ourselves but for our clients. Shopify understands this and puts it into practice. This makes sense because the platform and developers both serve the same goal: making the website better and the life of the business easier. Shopify offers good development tools such as their own CLI and SDKs, which we then use to build our sites. This, in combination with a stable backend with extensive features that keep evolving, creates a very developer-friendly environment.

Yann Karl: Shopify’s emphasis is definitely on the user side, but also the developer appeal has grown significantly in the last couple of years. The abundant API offering allows developers to extend the platform's functionality and integrate with external systems easily, even without the need of a middleware. 

Liquid, Shopify’s template engine, is easy to learn and a powerful tool to create custom themes and storefronts. It’s also already well integrated into existing development platforms which support e.g. auto-complete or code suggestions to ease up daily developer life.

To get started, Shopify offers detailed documentation for all its extension points and functions, supporting developers not only on customising themes, but also on building custom apps for additional functionalities or third party integrations, which can then be sold on the Shopify App Store.

In general, from a user and developer perspective, Shopify's ready-to-use infrastructure offers fast time to market which allows all parties to focus on building a great experience without worrying about hosting, security, or performance issues.

Shopify challenges

Ksenia Zvereva: With Shopify's simplicity, are there any challenges, like customisation or infrastructure, that customers and developers should keep in mind when building with it?

Simon Freimoser: While there definitely are challenges, it’s always a matter of how you tackle them, right? I would say there are both customization and infrastructure challenges. But ultimately, a Shopify project is almost 50% mindset work. Yes, the customisation capabilities seem to be limited at a first glance and in-depth customisation might only be possible with extensive knowledge of Liquid, their APIs, or even Hydrogen, which is part of their own headless framework. At the end of the day though, asking the question whether a customisation is necessary and evaluating its impact versus the necessary effort, often does the trick. 

Another hotly discussed topic is Shopify’s heavy dependency on its app ecosystem and the sheer amount of apps to choose from. But Shopify has worked to improve this. Shopify has now integrated its core functionality into its app stack. While other functionalities still require third parties, there’s a clear direction on which apps and providers are best in their field. Yes, they can get quite pricey, but it’s also comparably easy to quickly drive up the return on investment. 

When looking at the total cost of ownership of a Shopify store, we often see the overall costs of a store increasing. But, simultaneously, we see profits rising in multiples of the amount invested. This shows that solely looking at the cost might pose a challenge in the short term but quickly gets put into perspective when businesses can benefit from the total gains from those initial investment costs.

This is similar to Shopify's infrastructure challenges. As an API-first platform, it sometimes requires microservices or middleware to settle specific requirements or migrate certain data points. While this seems cumbersome, we've seen various cases where this approach resulted in a slimmer and more transparent middleware stack, which solved many historical issues on the side. 

So the challenge here is to get merchants to employ a middleware – most of them have a dark past with this tooling – and to prove that it has changed throughout the years and is now very different from its previous reputation as black-boxed sorcery.

Tico van Beurden: Shopify’s infrastructure is excellent, and they take care of many things so you and your client can focus on what you should be doing. Hosting is on Shopify, so you don’t need to figure that out, and with a 99.99% uptime, there’s nothing to worry about there. Shopify also has a built-in CDN, which automatically compresses images and offers them in different sizes for the user. Shopify’s templating language is ecommerce focused, so it gives you the majority of the properties that you need out of the box. This allows you to build a modern website with just a default Shopify Plan.

However, since Shopify takes care of infrastructure, some things are impossible on its native platform. For example, you can’t change the URL structure. This is a hot topic for businesses switching platforms as it dramatically impacts SEO. As a developer, the challenge is to find a creative solution for your clients while staying as close to the native behaviour of the platform as possible. Customising and hacking your way around the platform will create technical debt in the future.

Ksenia Zvereva: While Shopify handles the hosting, security, and maintenance, allowing developers to focus on building, it seems there are still some aspects to be mindful of.

Ksenia Zvereva: With Shopify's simplicity, are there any challenges, like customisation or infrastructure, that customers and developers should keep in mind when building with it?

Simon Freimoser: While there definitely are challenges, it’s always a matter of how you tackle them, right? I would say there are both customization and infrastructure challenges. But ultimately, a Shopify project is almost 50% mindset work. Yes, the customisation capabilities seem to be limited at a first glance and in-depth customisation might only be possible with extensive knowledge of Liquid, their APIs, or even Hydrogen, which is part of their own headless framework. At the end of the day though, asking the question whether a customisation is necessary and evaluating its impact versus the necessary effort, often does the trick. 

Another hotly discussed topic is Shopify’s heavy dependency on its app ecosystem and the sheer amount of apps to choose from. But Shopify has worked to improve this. Shopify has now integrated its core functionality into its app stack. While other functionalities still require third parties, there’s a clear direction on which apps and providers are best in their field. Yes, they can get quite pricey, but it’s also comparably easy to quickly drive up the return on investment. 

When looking at the total cost of ownership of a Shopify store, we often see the overall costs of a store increasing. But, simultaneously, we see profits rising in multiples of the amount invested. This shows that solely looking at the cost might pose a challenge in the short term but quickly gets put into perspective when businesses can benefit from the total gains from those initial investment costs.

This is similar to Shopify's infrastructure challenges. As an API-first platform, it sometimes requires microservices or middleware to settle specific requirements or migrate certain data points. While this seems cumbersome, we've seen various cases where this approach resulted in a slimmer and more transparent middleware stack, which solved many historical issues on the side. 

So the challenge here is to get merchants to employ a middleware – most of them have a dark past with this tooling – and to prove that it has changed throughout the years and is now very different from its previous reputation as black-boxed sorcery.

Tico van Beurden: Shopify’s infrastructure is excellent, and they take care of many things so you and your client can focus on what you should be doing. Hosting is on Shopify, so you don’t need to figure that out, and with a 99.99% uptime, there’s nothing to worry about there. Shopify also has a built-in CDN, which automatically compresses images and offers them in different sizes for the user. Shopify’s templating language is ecommerce focused, so it gives you the majority of the properties that you need out of the box. This allows you to build a modern website with just a default Shopify Plan.

However, since Shopify takes care of infrastructure, some things are impossible on its native platform. For example, you can’t change the URL structure. This is a hot topic for businesses switching platforms as it dramatically impacts SEO. As a developer, the challenge is to find a creative solution for your clients while staying as close to the native behaviour of the platform as possible. Customising and hacking your way around the platform will create technical debt in the future.

Ksenia Zvereva: While Shopify handles the hosting, security, and maintenance, allowing developers to focus on building, it seems there are still some aspects to be mindful of.

Ksenia Zvereva: With Shopify's simplicity, are there any challenges, like customisation or infrastructure, that customers and developers should keep in mind when building with it?

Simon Freimoser: While there definitely are challenges, it’s always a matter of how you tackle them, right? I would say there are both customization and infrastructure challenges. But ultimately, a Shopify project is almost 50% mindset work. Yes, the customisation capabilities seem to be limited at a first glance and in-depth customisation might only be possible with extensive knowledge of Liquid, their APIs, or even Hydrogen, which is part of their own headless framework. At the end of the day though, asking the question whether a customisation is necessary and evaluating its impact versus the necessary effort, often does the trick. 

Another hotly discussed topic is Shopify’s heavy dependency on its app ecosystem and the sheer amount of apps to choose from. But Shopify has worked to improve this. Shopify has now integrated its core functionality into its app stack. While other functionalities still require third parties, there’s a clear direction on which apps and providers are best in their field. Yes, they can get quite pricey, but it’s also comparably easy to quickly drive up the return on investment. 

When looking at the total cost of ownership of a Shopify store, we often see the overall costs of a store increasing. But, simultaneously, we see profits rising in multiples of the amount invested. This shows that solely looking at the cost might pose a challenge in the short term but quickly gets put into perspective when businesses can benefit from the total gains from those initial investment costs.

This is similar to Shopify's infrastructure challenges. As an API-first platform, it sometimes requires microservices or middleware to settle specific requirements or migrate certain data points. While this seems cumbersome, we've seen various cases where this approach resulted in a slimmer and more transparent middleware stack, which solved many historical issues on the side. 

So the challenge here is to get merchants to employ a middleware – most of them have a dark past with this tooling – and to prove that it has changed throughout the years and is now very different from its previous reputation as black-boxed sorcery.

Tico van Beurden: Shopify’s infrastructure is excellent, and they take care of many things so you and your client can focus on what you should be doing. Hosting is on Shopify, so you don’t need to figure that out, and with a 99.99% uptime, there’s nothing to worry about there. Shopify also has a built-in CDN, which automatically compresses images and offers them in different sizes for the user. Shopify’s templating language is ecommerce focused, so it gives you the majority of the properties that you need out of the box. This allows you to build a modern website with just a default Shopify Plan.

However, since Shopify takes care of infrastructure, some things are impossible on its native platform. For example, you can’t change the URL structure. This is a hot topic for businesses switching platforms as it dramatically impacts SEO. As a developer, the challenge is to find a creative solution for your clients while staying as close to the native behaviour of the platform as possible. Customising and hacking your way around the platform will create technical debt in the future.

Ksenia Zvereva: While Shopify handles the hosting, security, and maintenance, allowing developers to focus on building, it seems there are still some aspects to be mindful of.

Ksenia Zvereva: With Shopify's simplicity, are there any challenges, like customisation or infrastructure, that customers and developers should keep in mind when building with it?

Simon Freimoser: While there definitely are challenges, it’s always a matter of how you tackle them, right? I would say there are both customization and infrastructure challenges. But ultimately, a Shopify project is almost 50% mindset work. Yes, the customisation capabilities seem to be limited at a first glance and in-depth customisation might only be possible with extensive knowledge of Liquid, their APIs, or even Hydrogen, which is part of their own headless framework. At the end of the day though, asking the question whether a customisation is necessary and evaluating its impact versus the necessary effort, often does the trick. 

Another hotly discussed topic is Shopify’s heavy dependency on its app ecosystem and the sheer amount of apps to choose from. But Shopify has worked to improve this. Shopify has now integrated its core functionality into its app stack. While other functionalities still require third parties, there’s a clear direction on which apps and providers are best in their field. Yes, they can get quite pricey, but it’s also comparably easy to quickly drive up the return on investment. 

When looking at the total cost of ownership of a Shopify store, we often see the overall costs of a store increasing. But, simultaneously, we see profits rising in multiples of the amount invested. This shows that solely looking at the cost might pose a challenge in the short term but quickly gets put into perspective when businesses can benefit from the total gains from those initial investment costs.

This is similar to Shopify's infrastructure challenges. As an API-first platform, it sometimes requires microservices or middleware to settle specific requirements or migrate certain data points. While this seems cumbersome, we've seen various cases where this approach resulted in a slimmer and more transparent middleware stack, which solved many historical issues on the side. 

So the challenge here is to get merchants to employ a middleware – most of them have a dark past with this tooling – and to prove that it has changed throughout the years and is now very different from its previous reputation as black-boxed sorcery.

Tico van Beurden: Shopify’s infrastructure is excellent, and they take care of many things so you and your client can focus on what you should be doing. Hosting is on Shopify, so you don’t need to figure that out, and with a 99.99% uptime, there’s nothing to worry about there. Shopify also has a built-in CDN, which automatically compresses images and offers them in different sizes for the user. Shopify’s templating language is ecommerce focused, so it gives you the majority of the properties that you need out of the box. This allows you to build a modern website with just a default Shopify Plan.

However, since Shopify takes care of infrastructure, some things are impossible on its native platform. For example, you can’t change the URL structure. This is a hot topic for businesses switching platforms as it dramatically impacts SEO. As a developer, the challenge is to find a creative solution for your clients while staying as close to the native behaviour of the platform as possible. Customising and hacking your way around the platform will create technical debt in the future.

Ksenia Zvereva: While Shopify handles the hosting, security, and maintenance, allowing developers to focus on building, it seems there are still some aspects to be mindful of.

Shopify development best practices

Ksenia Zvereva: What are your top Shopify best practices, both project and development-wise?

Simon Freimoser: First and foremost, it starts with a proper definition of the foundations we're working with. This includes clear documentation of the specific project objectives, just as much as going in there 'data-first' by checking all underlying data structures a business already offers. If you know the information architecture of every data entity, it's way easier to align the project work from the get-go. It sounds easy and obvious, but this step is often missed.

Following the foundational work, the next crucial step is comprehensive project planning. Here, it's important to reiterate the unique aspects of Shopify projects: quick time-to-market, scalability, and extensibility. Planning in iterations and milestones allows you to use these features to deliver a successful project effectively.

Once the development phase begins, it's essential to have robust and swift testing procedures in place. This ensures that speed and seamless functionality, critical features of Shopify development, are maintained even after the coding is complete.

Last but not least, throughout the development process, ask yourself: "Is the thing I'm currently doing contributing to merchant enablement?" If a business can't manage the store self-sufficiently and it inhibits their maintenance efforts, you are doing something wrong.

Ksenia Zvereva: And on the development side?

Yann Karl: It's crucial that all developers strictly adhere to Shopify's development guidelines and best practices for themes and apps. Remember, with great power comes great responsibility. You shouldn't just customise for the sake of it. 

The first step in preparing our developers to work with Shopify is to instil the right mindset. Always consider the platform's capabilities first, then challenge the customer, rethink, and only then, think of ways to customise without reinventing the wheel. As Simon mentioned, our approach to working with our development staff is akin to our approach to client work.

In general, best practices apply the same way as with other projects: use version control for your development work to manage changes and collaborate effectively, and keep themes, apps and integrations up to date as well as possible to prevent incompatibilities, bugs or security issues.

Shopify offers an excellent CLI component that supports developers in handling the whole process of deploying changes to your different themes for testing, staging and production. It is a must-use for everyone working on any code change.

Last but not least, maintain clear and thorough documentation for all custom code, functionalities, and configurations. This is crucial to achieve a high level of maintainability for the entire project – for you and your colleagues.

Tico van Beurden: We try to stay as close to Shopify’s native features and behaviour as possible. Implementing a third-party tool can create more technical debt as well as additional monthly costs. We believe in Shopify and try to use its native features as much as possible to ride the wave successfully. We built our front end with the same goal: to utilise as many native browser features as possible.

Maintaining a lean development setup that isn’t overly reliant on too many packages is also crucial. The more packages you add, the more reliant you become and the more maintenance you need to do. Also, when in doubt about a particular implementation, looking at how it’s done in Dawn, Shopify’s own theme is beneficial. You can install this theme for free on any store to observe its behaviour or check the public repository for technical implementation details.

Utilising Shopify’s GitHub integration for deployment and instant backups is another best practice that ensures smooth operations and instant backups. Additionally, with server-less functions, you can extend the functionality of your native theme by utilising Shopify’s Admin APIs. This way, you can extend your theme with features that aren’t possible out of the box.


Are you planning to build with Shopify? Make sure to check out our Mollie x Shopify plugin, as well as our integration guides.

Want to continue this discussion? Join the Mollie Developer Community to talk to our engineers, product teams, and fellow community members. 

Ksenia Zvereva: What are your top Shopify best practices, both project and development-wise?

Simon Freimoser: First and foremost, it starts with a proper definition of the foundations we're working with. This includes clear documentation of the specific project objectives, just as much as going in there 'data-first' by checking all underlying data structures a business already offers. If you know the information architecture of every data entity, it's way easier to align the project work from the get-go. It sounds easy and obvious, but this step is often missed.

Following the foundational work, the next crucial step is comprehensive project planning. Here, it's important to reiterate the unique aspects of Shopify projects: quick time-to-market, scalability, and extensibility. Planning in iterations and milestones allows you to use these features to deliver a successful project effectively.

Once the development phase begins, it's essential to have robust and swift testing procedures in place. This ensures that speed and seamless functionality, critical features of Shopify development, are maintained even after the coding is complete.

Last but not least, throughout the development process, ask yourself: "Is the thing I'm currently doing contributing to merchant enablement?" If a business can't manage the store self-sufficiently and it inhibits their maintenance efforts, you are doing something wrong.

Ksenia Zvereva: And on the development side?

Yann Karl: It's crucial that all developers strictly adhere to Shopify's development guidelines and best practices for themes and apps. Remember, with great power comes great responsibility. You shouldn't just customise for the sake of it. 

The first step in preparing our developers to work with Shopify is to instil the right mindset. Always consider the platform's capabilities first, then challenge the customer, rethink, and only then, think of ways to customise without reinventing the wheel. As Simon mentioned, our approach to working with our development staff is akin to our approach to client work.

In general, best practices apply the same way as with other projects: use version control for your development work to manage changes and collaborate effectively, and keep themes, apps and integrations up to date as well as possible to prevent incompatibilities, bugs or security issues.

Shopify offers an excellent CLI component that supports developers in handling the whole process of deploying changes to your different themes for testing, staging and production. It is a must-use for everyone working on any code change.

Last but not least, maintain clear and thorough documentation for all custom code, functionalities, and configurations. This is crucial to achieve a high level of maintainability for the entire project – for you and your colleagues.

Tico van Beurden: We try to stay as close to Shopify’s native features and behaviour as possible. Implementing a third-party tool can create more technical debt as well as additional monthly costs. We believe in Shopify and try to use its native features as much as possible to ride the wave successfully. We built our front end with the same goal: to utilise as many native browser features as possible.

Maintaining a lean development setup that isn’t overly reliant on too many packages is also crucial. The more packages you add, the more reliant you become and the more maintenance you need to do. Also, when in doubt about a particular implementation, looking at how it’s done in Dawn, Shopify’s own theme is beneficial. You can install this theme for free on any store to observe its behaviour or check the public repository for technical implementation details.

Utilising Shopify’s GitHub integration for deployment and instant backups is another best practice that ensures smooth operations and instant backups. Additionally, with server-less functions, you can extend the functionality of your native theme by utilising Shopify’s Admin APIs. This way, you can extend your theme with features that aren’t possible out of the box.


Are you planning to build with Shopify? Make sure to check out our Mollie x Shopify plugin, as well as our integration guides.

Want to continue this discussion? Join the Mollie Developer Community to talk to our engineers, product teams, and fellow community members. 

Ksenia Zvereva: What are your top Shopify best practices, both project and development-wise?

Simon Freimoser: First and foremost, it starts with a proper definition of the foundations we're working with. This includes clear documentation of the specific project objectives, just as much as going in there 'data-first' by checking all underlying data structures a business already offers. If you know the information architecture of every data entity, it's way easier to align the project work from the get-go. It sounds easy and obvious, but this step is often missed.

Following the foundational work, the next crucial step is comprehensive project planning. Here, it's important to reiterate the unique aspects of Shopify projects: quick time-to-market, scalability, and extensibility. Planning in iterations and milestones allows you to use these features to deliver a successful project effectively.

Once the development phase begins, it's essential to have robust and swift testing procedures in place. This ensures that speed and seamless functionality, critical features of Shopify development, are maintained even after the coding is complete.

Last but not least, throughout the development process, ask yourself: "Is the thing I'm currently doing contributing to merchant enablement?" If a business can't manage the store self-sufficiently and it inhibits their maintenance efforts, you are doing something wrong.

Ksenia Zvereva: And on the development side?

Yann Karl: It's crucial that all developers strictly adhere to Shopify's development guidelines and best practices for themes and apps. Remember, with great power comes great responsibility. You shouldn't just customise for the sake of it. 

The first step in preparing our developers to work with Shopify is to instil the right mindset. Always consider the platform's capabilities first, then challenge the customer, rethink, and only then, think of ways to customise without reinventing the wheel. As Simon mentioned, our approach to working with our development staff is akin to our approach to client work.

In general, best practices apply the same way as with other projects: use version control for your development work to manage changes and collaborate effectively, and keep themes, apps and integrations up to date as well as possible to prevent incompatibilities, bugs or security issues.

Shopify offers an excellent CLI component that supports developers in handling the whole process of deploying changes to your different themes for testing, staging and production. It is a must-use for everyone working on any code change.

Last but not least, maintain clear and thorough documentation for all custom code, functionalities, and configurations. This is crucial to achieve a high level of maintainability for the entire project – for you and your colleagues.

Tico van Beurden: We try to stay as close to Shopify’s native features and behaviour as possible. Implementing a third-party tool can create more technical debt as well as additional monthly costs. We believe in Shopify and try to use its native features as much as possible to ride the wave successfully. We built our front end with the same goal: to utilise as many native browser features as possible.

Maintaining a lean development setup that isn’t overly reliant on too many packages is also crucial. The more packages you add, the more reliant you become and the more maintenance you need to do. Also, when in doubt about a particular implementation, looking at how it’s done in Dawn, Shopify’s own theme is beneficial. You can install this theme for free on any store to observe its behaviour or check the public repository for technical implementation details.

Utilising Shopify’s GitHub integration for deployment and instant backups is another best practice that ensures smooth operations and instant backups. Additionally, with server-less functions, you can extend the functionality of your native theme by utilising Shopify’s Admin APIs. This way, you can extend your theme with features that aren’t possible out of the box.


Are you planning to build with Shopify? Make sure to check out our Mollie x Shopify plugin, as well as our integration guides.

Want to continue this discussion? Join the Mollie Developer Community to talk to our engineers, product teams, and fellow community members. 

Ksenia Zvereva: What are your top Shopify best practices, both project and development-wise?

Simon Freimoser: First and foremost, it starts with a proper definition of the foundations we're working with. This includes clear documentation of the specific project objectives, just as much as going in there 'data-first' by checking all underlying data structures a business already offers. If you know the information architecture of every data entity, it's way easier to align the project work from the get-go. It sounds easy and obvious, but this step is often missed.

Following the foundational work, the next crucial step is comprehensive project planning. Here, it's important to reiterate the unique aspects of Shopify projects: quick time-to-market, scalability, and extensibility. Planning in iterations and milestones allows you to use these features to deliver a successful project effectively.

Once the development phase begins, it's essential to have robust and swift testing procedures in place. This ensures that speed and seamless functionality, critical features of Shopify development, are maintained even after the coding is complete.

Last but not least, throughout the development process, ask yourself: "Is the thing I'm currently doing contributing to merchant enablement?" If a business can't manage the store self-sufficiently and it inhibits their maintenance efforts, you are doing something wrong.

Ksenia Zvereva: And on the development side?

Yann Karl: It's crucial that all developers strictly adhere to Shopify's development guidelines and best practices for themes and apps. Remember, with great power comes great responsibility. You shouldn't just customise for the sake of it. 

The first step in preparing our developers to work with Shopify is to instil the right mindset. Always consider the platform's capabilities first, then challenge the customer, rethink, and only then, think of ways to customise without reinventing the wheel. As Simon mentioned, our approach to working with our development staff is akin to our approach to client work.

In general, best practices apply the same way as with other projects: use version control for your development work to manage changes and collaborate effectively, and keep themes, apps and integrations up to date as well as possible to prevent incompatibilities, bugs or security issues.

Shopify offers an excellent CLI component that supports developers in handling the whole process of deploying changes to your different themes for testing, staging and production. It is a must-use for everyone working on any code change.

Last but not least, maintain clear and thorough documentation for all custom code, functionalities, and configurations. This is crucial to achieve a high level of maintainability for the entire project – for you and your colleagues.

Tico van Beurden: We try to stay as close to Shopify’s native features and behaviour as possible. Implementing a third-party tool can create more technical debt as well as additional monthly costs. We believe in Shopify and try to use its native features as much as possible to ride the wave successfully. We built our front end with the same goal: to utilise as many native browser features as possible.

Maintaining a lean development setup that isn’t overly reliant on too many packages is also crucial. The more packages you add, the more reliant you become and the more maintenance you need to do. Also, when in doubt about a particular implementation, looking at how it’s done in Dawn, Shopify’s own theme is beneficial. You can install this theme for free on any store to observe its behaviour or check the public repository for technical implementation details.

Utilising Shopify’s GitHub integration for deployment and instant backups is another best practice that ensures smooth operations and instant backups. Additionally, with server-less functions, you can extend the functionality of your native theme by utilising Shopify’s Admin APIs. This way, you can extend your theme with features that aren’t possible out of the box.


Are you planning to build with Shopify? Make sure to check out our Mollie x Shopify plugin, as well as our integration guides.

Want to continue this discussion? Join the Mollie Developer Community to talk to our engineers, product teams, and fellow community members. 

Stay up to date

Never miss an update. Receive product updates, news and customer stories right into your inbox.

Stay up to date

Never miss an update. Receive product updates, news and customer stories right into your inbox.

Connect every payment. Upgrade every part of your business.

Never miss an update. Receive product updates, news and customer stories right into your inbox.

Stay up to date

Never miss an update. Receive product updates, news and customer stories right into your inbox.

Form fields
Form fields
Form fields

Table of contents

Table of contents

MollieGrowthExploring Shopify: A developer's perspective
MollieGrowthExploring Shopify: A developer's perspective