Ask ten platform vendors how customizable their software is and you will get ten confident answers. Ask what it takes to change the checkout and the answers get shorter.
The two usual choices
Most eCommerce platforms fall on one side of a line. Some hand you all of the source code, which gives you freedom and also the job of maintaining every part of it. Others keep the code closed and offer settings, themes and plug-ins, which is quick to start and hard to bend once your requirements stop looking like everyone else’s.
Where the line should sit
The useful question is not whether code is open or closed. It is which parts of the store benefit from being either. The engine that searches products, caches pages and moves data is the same for every merchant, and it rewards careful, centralized engineering. The storefront, checkout, reporting and integrations are where merchants differ, and those are the parts you want to change without asking permission.
What a hybrid looks like in practice
- A closed, tuned core that owns performance-critical work such as search, caching and data access.
- An open layer that renders the store and can be modified for branding, custom carts or tracking.
- Events and interfaces between the two, so your changes never need to touch the core.
How to test a platform against this
List the five changes you expect to make in the next two years. For each one, ask where it would be made, who could make it and how long it would take. The answers tell you more than any feature checklist.