Updated September 2026
How Platform Extensibility Can Help Your Existing Platform
- What Is Extensibility?
- The Extensible Platform House Analogy
- Be Creative with Your Extensible Platform
- Extensible Software Improves Security Functionality
- Platform Extensibility Creates Efficiency
- The Challenges of an Extensible Platform
- Improve Your Business Processes with Extensibility
- FAQ
- Extensibility on an eCommerce platform refers to the ability of the platform to be easily extended or customized to meet the specific needs of a business.
- This means that businesses can add new features, functionalities, or customizations to their online store without having to rebuild the entire system from scratch.
- An extensible platform also enables businesses to integrate with third-party solutions and services, such as payment hubs, marketing automation, security software to protect customer data, and inventory management systems, to simplify operations and improve the efficiency of business processes.
- Extensibility empowers businesses to adapt and evolve their online store over time as their needs change or grow, ensuring new capabilities help them keep up with the constantly evolving eCommerce landscape.
Using an extensible commerce platform is an excellent way to constantly adapt to the changing of the web. An extensible platform allows businesses to customize their online store to meet their specific needs and requirements, integrate with third-party tools and services, and adapt to changes and growth over time.
This improves the customer experience, and it also simplifies operations, improves efficiency, and empowers small businesses and enterprises to create a tailored online shopping experience that aligns with their unique business model and drives success.
How can the extensibility of a platform benefit a business? Let's take a look at the benefits of an extensibility platform and why it is critical for businesses looking to succeed in today's online marketplace.
What Is Extensibility?
Extensibility is the ability to add capability to a system without modifying what is already there. An extensible platform is built with defined places where new behaviour can be attached, so your additions survive the vendor's next update instead of being overwritten by it.
What is extensibility? Extensibility refers to the ability to make changes to a website without affecting its foundation, its core functionality.
Simplify Processes
One extensibility platform benefit is that it improves processes and gives you full control over each aspect of your eCommerce platform. This means that the platform has a flexible architecture and allows for the integration of third-party tools, plugins, or modules to add new features, functionalities, or customizations to improve business processes.
Adapt Easier
An extensible eCommerce platform allows businesses to adapt and evolve their online stores over time as their needs change or grow. For example, a business might want to add a new payment gateway, integrate with a marketing automation tool, or create a custom checkout process that aligns with its unique business model.
How can the extensibility help? Extensible platforms make it possible to do all of these things and more, without having to completely rebuild the entire system from scratch.
Extensibility is a property of how a platform is built, not a feature it advertises. The documentation tells you more than the brochure.
What the definition actually requires
The phrase that does the work in any definition of extensibility is "without modifying what is already there", and it is worth being precise about why. Adding capability is easy in any system if you are willing to change its existing code. What makes a system extensible is that you do not have to. The design principle behind this is old and is usually stated as software being open for extension, closed for modification: the existing code should not need to change when new behaviour is added, because every such change risks breaking something that already worked and, in a platform you did not write, forfeits your ability to accept the vendor's next version. So extensibility is not a measure of how much a platform can do. It is a measure of how much can be added to it safely, by someone who does not own it.
That distinction explains a common frustration. A platform can be enormously capable and barely extensible, if everything it does is fixed and nothing new can be attached. Another can be sparse out of the box and highly extensible, because it was built expecting to be added to. The first feels better in a demonstration. The second is the one you can still be using in five years, which is why buyers who evaluate on feature lists alone tend to be disappointed on a timescale longer than a procurement cycle.
An extension point you cannot find in the documentation may as well not exist. Judge a platform on what it publishes, not on what it claims.
Extensibility, scalability and flexibility are not the same thing
These three words get used interchangeably in software marketing and they describe genuinely different properties. Separating them makes it much easier to tell whether a platform has the one you actually need.
- Extensibility is about adding capability. Can new behaviour be attached without altering what is already there? A platform that lets you add a shipping method nobody anticipated is extensible.
- Scalability is about handling more. Can the system take ten times the traffic or a hundred times the catalogue without redesign? This is a performance and infrastructure property and it is unrelated to extensibility - a rigid platform can scale beautifully, and a highly extensible one can fall over at modest load.
- Flexibility is about configuration. Can existing behaviour be adjusted through settings rather than code? Flexibility is what you use first, and running out of it is what sends you looking for extensibility.
- Interoperability is about talking to other systems. Can it exchange data with your ERP, your PIM, your tax engine? Extensibility is usually how interoperability gets built, but a platform can ship strong integrations and still give you nowhere to add your own.
The distinction matters commercially. Teams usually discover they need extensibility at the moment they run out of flexibility: the setting they want does not exist, and the question becomes whether the platform offers a supported place to add it or whether someone is about to edit a core file.
Configuration first, extension second, modification never. That ordering is the whole discipline.
Work out which of these four you actually need before evaluating anything. Vendors answer whichever question they can answer best.
| Property | The question it answers | Example | Often confused with |
|---|---|---|---|
Extensibility | Can new behaviour be added without changing what exists? | Adding a shipping method the platform never anticipated | Flexibility |
Scalability | Can it handle far more traffic or catalogue? | Ten times the orders with no redesign | Extensibility |
Flexibility | Can existing behaviour be adjusted by configuration? | Changing tax rules in a settings screen | Extensibility |
Interoperability | Can it exchange data with other systems? | Reading prices from an ERP | Extensibility |
Name which of these four you actually need before any evaluation. Vendors will answer whichever of the four they answer best.
The Extensible Platform House Analogy
An extensible platform is like a house. A house can be redecorated, renovated, added onto, and repaired without the foundation of the house being changed.
For instance, if you’re putting up a shelf in the bedroom, you don’t need to change the kitchen too, and if you want to knock out a wall to make a room bigger, you don’t need to demolish and rebuild the entire house to make that one change.
An extensible software platform works the same way. It gives you a stable coding arena so you can make changes without fearing a collapse. You can make changes to one part of the website while leaving other parts alone, and you can choose which parts of the website you want to affect.
This is extremely useful because web content, consumer trends, and technology are constantly evolving, and you need to keep up with these trends and adjust your website accordingly to continue operating a successful business.
The mechanisms that make a platform extensible
Extensibility is not a single feature, and platforms provide it through several mechanisms with different strengths. Most serious platforms offer more than one, and knowing which is which tells you what you will actually be able to do.
APIs
An API is the platform letting other software ask it to do things. Most commerce platforms expose REST endpoints, and an increasing number offer GraphQL, which lets a caller request exactly the fields it wants in one round trip rather than stitching several responses together. APIs are what let an external system read your catalogue or place an order, and they are the foundation of headless architecture, where the storefront is built separately and talks to the platform purely through them. The question worth asking a vendor is not whether an API exists but what share of the admin functionality it covers, because the gap between the two is where projects get stuck.
Webhooks and events
APIs let you ask. Webhooks let the platform tell you. When an order is placed or a product changes, the platform calls a URL you nominate, so your code reacts to what happened rather than polling to find out. This is what makes near-real-time integration practical without hammering an API on a timer. Check what events are published, whether delivery is retried when your endpoint is down, and whether ordering is guaranteed, because those three answers decide how much work you have to do to make the integration reliable.
Plugins, modules and extension points
This is extensibility in its most direct form: the platform defines places where your code runs, and calls it at the right moment. The vocabulary varies - plugins, modules, extensions, apps, hooks - and the principle does not. Your code lives separately from the platform's, so an upgrade replaces their files and leaves yours alone. The limitation is that you can only extend where an extension point exists, which is why the density and placement of those points is a real difference between platforms that otherwise look similar.
SDKs, and the difference documentation makes
An SDK is a library that makes the above pleasant to use in a given language, handling authentication, retries and the tedious parts. It is not strictly necessary and its presence tells you something anyway: a platform that maintains SDKs, publishes reference documentation and runs a sandbox environment is a platform expecting people to build on it. One with an API and no documentation has a checkbox rather than an ecosystem, and you will discover the difference during implementation rather than during evaluation.
What this lets you extend in commerce specifically
In practice the extension points that matter in eCommerce are predictable. Pricing, where contract or customer-specific logic has to come from an ERP rather than a price field. Checkout, where a business needs an approval step, a purchase order number or a payment method the platform never anticipated. Catalogue, where products carry attributes, units of measure or compatibility data the standard model does not hold, usually via a PIM. Fulfilment, where orders route to different warehouses, suppliers or drop-shippers by rule. Tax and shipping, where a dedicated engine replaces built-in calculation. And identity, where customers already exist in a CRM or a corporate directory. If a platform is extensible everywhere except one of these, and that one is your business, it is not extensible enough for you.
Monoliths, microservices and composable architecture
Where extensibility lives depends on how the system is put together, and the industry has moved through three broad shapes. A monolith is one application containing everything, and extends through plugins and hooks inside itself. This is much less primitive than it is made to sound, and a well-structured monolith with dense extension points is easier to work with than a badly split alternative. Microservices break the system into separate services communicating over the network, so extending can mean replacing or adding a service rather than modifying anything, at the cost of operating many moving parts. Composable architecture, often labelled MACH, takes that further and assembles a platform from best-of-breed services chosen independently: one vendor for search, another for payments, another for content.
Each shape trades the same two things against each other. Extensibility rises and operational simplicity falls. Composable gives you the most freedom to change any single component and hands you an integration project that never quite ends, which is worth it for organisations with genuinely unusual requirements and rarely worth it otherwise. The honest question is not which architecture is most modern but how much of the freedom you would actually use.
Most platforms offer several of these at once. What differs is how much of the system each one can actually reach.
The cheapest extension is the one you do not build. Tell us what your platform will not do and we will tell you whether it needs code, an extension, or a setting nobody found.
Most platforms offer several of these at once. What differs is how much of the system each mechanism can genuinely reach.
Be Creative with Your Extensible Platform
The eCommerce industry is one where innovations are consistently taking place. Whether you run a B2B, B2C, D2C, or another type of business, customers expect their shopping experiences to align with current trends. Extensible software can lead to improved customer service and better business processes.
Platform extensibility allows you to keep up with the times and maybe even set a few trends yourself. Extensible software ensures that you can continuously implement new ideas and technologies at the drop of a hat without having to do an entire overhaul.
With platform extensibility, new pages can be built using existing templates, and existing templates can be updated on the fly and applied to all relevant pages, so you don't have to update them one at a time for site-wide changes. Individual pages can also be changed without affecting others, all via an easy-to-use user interface.
In the end, a platform's extensibility lets you be creative with your commerce platform, adding new features for processes, and business expansion.
Buying an extension instead of building one
A mature platform usually has a marketplace of third-party extensions, and checking it before commissioning anything is the cheapest step in the whole process. Something that costs a few hundred a year and is maintained by someone whose entire business is keeping it working through platform upgrades will beat a bespoke equivalent on almost every measure, including the ones that only show up in year three. The judgement is the same one as with any dependency: check when it was last updated, how it behaves across major versions, whether it touches core files, and what happens if the publisher stops. Build where the capability is genuinely specific to how you trade. Buy where it is a solved problem you happen to need.
Extensible Software Improves Security Functionality
As your business grows, new challenges will arise. These challenges will be easier to overcome if you have an extensible platform in place. So how can the extensibility of a platform benefit a business?
You need to stay up to date with your security software, monitor for errors that might appear on your website, and be aware of new innovations in the security world (both by hackers and website protectors).
Platform extensibility makes it much easier to implement these security updates and you don't have to put your website (and your customers' data) at immediate risk. The parts of your website that are secure and working properly can stay as such while any holes in security are mended and updates are made.
Security is a continuous process, and best practices for security must be followed to keep your customer data safe. Software extensibility saves you from a major headache each time changes need to be implemented.
Extensions are attack surface as well as capability. Review them the way you would review your own code, because in effect it is.
Extensions are attack surface too
Extensibility improves security in one direction and weakens it in another, and honest treatment needs both. It helps because you can patch, replace or add a control without waiting for a vendor release, and because security tooling can be integrated rather than hoped for. It hurts because every extension is code running inside your commerce system, frequently with broad access to customer and payment data, and often written by someone you have never met. A third-party extension from a marketplace is a supply chain dependency in exactly the sense that has caused so much trouble elsewhere. Treat them accordingly: review what an extension can reach before installing it, prefer ones that are actively maintained, keep an inventory of what is installed and why, and remove what is no longer used rather than leaving it dormant and unpatched.
Platform Extensibility Creates Efficiency
As they say, time is money. With an extensible platform, you can make changes to your eCommerce website without having to shut it down and lose business. Since the base code is already set, subsequent changes don’t require as much coding, so changes can be made quickly and efficiently.
Without platform extensibility, it’s easy for your time and finances to be sucked into large overhauls of your website that ultimately ruin your profit margins. But with extensible software for your eCommerce platform, changing your website can be easily integrated into your everyday business costs and routine.
Where the efficiency actually comes from
The efficiency argument is usually made in the abstract, and it is more convincing when made specifically. Most of it is removed manual work: an order that no longer gets rekeyed into an ERP, a price that no longer gets checked against a spreadsheet, a stock figure that no longer gets corrected by hand every morning. Each of those is a person's recurring time, and recovering it is what integration built on extension points buys you. The second source is speed of change, which matters more than it sounds: when a new requirement can be met by adding something rather than by negotiating a platform upgrade, the business stops treating small improvements as projects. And the third is avoided cost, the custom build you did not commission because the platform could be extended to reach the requirement instead.
Measure the first of those. Hours removed from a named process is the only one of the three that a finance director will accept without argument.
The test of extensibility is whether you can still upgrade
An extensible platform that has been extended carelessly is indistinguishable from a rigid one within about two years. The distinguishing question is not what was built, but whether the vendor's next release can still be applied afterwards.
Core modification is the mistake that costs the most
Every platform has a boundary between its own code and yours, and the shortcut is always to reach across it. Editing a core file to change behaviour works immediately, passes testing, and quietly ends your upgrade path: the next release overwrites your change or conflicts with it, so upgrading now means redoing work nobody documented. Teams skip one upgrade, then two, and eventually sit several major versions behind on a platform that is no longer receiving security patches. The eventual cost is a re-platform, and it arrives years after the decision that caused it, which is why the connection is so rarely drawn.
Versioning, breaking changes and deprecation
Extensibility is a promise the platform makes about stability, and the credible version of that promise is versioned APIs with a published deprecation policy. What you want to see is that old versions keep working for a stated period, that breaking changes arrive on a schedule rather than in a patch release, and that deprecations are announced far enough ahead to plan for. Ask how long a major API version is supported and how much notice a breaking change gets. A vendor without a clear answer is telling you that your integrations are their discretion, and the cost of that lands unpredictably.
Keep your extensions boring
The practical discipline is short. Use the documented extension point even when a direct change is quicker. Keep your code in its own repository with its own tests, so it can be reviewed and reasoned about separately. Write down what each extension does and why, because the person maintaining it will not be the person who wrote it. And take the upgrades, regularly and unexcitingly, because the difficulty of an upgrade rises much faster than linearly with how many you have skipped.
Having the source is not the same as being allowed to change it
Open-source platforms are often described as infinitely extensible because you can see and alter every line, and that framing causes real damage. Access to source removes the technical barrier to modification while leaving the upgrade consequence exactly where it was: change a core file in an open-source platform and the next release conflicts with you just as surely as it would in a proprietary one. The discipline matters more when the source is available, not less, because nothing stops you.
Proprietary SaaS platforms enforce that discipline for you by making core modification impossible, which is genuinely protective and is also the constraint people resent. What you give up is recourse when a capability you need does not exist and no extension point reaches it. Neither model is safer in itself. The comparison that matters is between the extension points each one offers, because on a platform you cannot modify those are the whole of what you can do, and on one you can modify they are the whole of what you should.
Take the upgrades. Difficulty rises much faster than linearly with the number you have skipped.
Take the upgrades on a schedule. Difficulty rises far faster than linearly with the number of releases you have skipped.
The Challenges of an Extensible Platform
Extensibility is a valuable aspect of eCommerce platforms as it allows businesses to customize their online store to meet their specific needs and requirements. However, there are several challenges associated with extensibility that businesses must consider. Hiring the right developer can solve these problems.
Compatibility Issues
One of the main challenges of extensibility is the potential for conflicts and compatibility issues between different extensions or customizations. When multiple extensions are added to an eCommerce platform, they can interact in unpredictable ways and result in broken functionality, slow website performance, and ultimately a negative impact on the customer experience.
Not all software is meant to integrate, but in nearly every case it can be integrated. Software engineering can help.
Maintenance Costs
Another challenge is the increased complexity and maintenance costs associated with an extensible eCommerce platform. With more extensions and customizations, it can be difficult to ensure everything is working properly and keeping up with updates and security patches. This can lead to an increased workload for developers and potential security vulnerabilities.
Can You Find the Right Extensions?
Businesses may also face difficulty finding quality third-party extensions that meet their specific needs. This can result in a mismatch between the business requirements and the available extensions, leading to a suboptimal solution.
Watch the Bloat
An over-reliance on extensibility can lead to a bloated system that is difficult to navigate and maintain. Passing it off from one IT team to another may require additional training.
Improve Your Business Processes with Extensibility
At Clarity, we specialize in developing extensible platforms for eCommerce businesses like yours. We customize the platform to fit your needs, and the extensible software engineering can adapt to your business as it scales.
How can the extensibility of a platform benefit businesses? We'd love to show you how it works and how it can improve your eCommerce website with the external systems you require. Get in touch for a complimentary discovery process, a meeting where we'll help you create a plan for your future. Looking forward to hearing from you.
At Clarity, we specialize in developing extensible platforms for eCommerce businesses like yours. We customize the platform to fit your needs, and the extensible software engineering can adapt to your business as it scales.
How can the extensibility of a platform benefit businesses? We'd love to show you how it works and how it can improve your eCommerce website with the external systems you require. Get in touch for a complimentary discovery process, a meeting where we'll help you create a plan for your future. Looking forward to hearing from you.
None of these challenges argue against extensibility. They argue for using it deliberately rather than because it is available.
None of these challenges argue against extensibility. They argue for spending it deliberately rather than because it happens to be available.
The shortcut that cost three years of upgrades
The damage from extending a platform the wrong way is never visible at the time. It is visible about two years later, in a decision nobody connects back to it.
A workwear supplier adds logo personalisation to its store
Corporate workwear sold to businesses, with customer logos embroidered onto garments. Each account has its own approved logo library and placement rules.
The requirement was legitimate
The platform had no concept of a per-customer artwork library, or of a garment whose price depends on stitch count and placement. This genuinely needed building and there was no configuration that would reach it.
The shortcut
Rather than build against the platform's extension points, the agency modified the core pricing and cart classes directly. It was faster, it worked, and it was delivered three weeks early. Everyone was pleased.
Version 1 missed
Eight months later a minor release conflicts with the modified files. Reapplying the changes is quoted at two weeks that nobody has, and the upgrade is deferred to the next quarter. It is not revisited.
Versions 2 and 3 missed
The gap compounds. Each skipped release makes the next harder, because the modified files have drifted further from what the vendor now ships. The conversation shifts from when to upgrade to whether it is worth it.
What it started to cost
New payment methods required a platform version they were not on. A security advisory needed a patch that would not apply cleanly. The developer who wrote the modifications had left, and no one remaining could say with confidence what the changes did.
Year three, the bill
They re-platformed. The personalisation logic was rebuilt properly against extension points in about five weeks, which is roughly what it would have taken at the start. Everything else in the migration - data, integrations, redirects, retraining - was the actual cost, and none of it would have been necessary.
The three weeks saved at the beginning bought a re-platform at the end. That is the usual exchange rate.
Frequently asked questions
How can the extensibility of a platform benefit a business?
The extensibility of an eCommerce platform can benefit businesses in several ways.
First, it allows businesses to customize their online store to meet their specific needs and requirements, which can enhance the customer experience and increase sales.
Second, it enables businesses to integrate with third-party tools and services, such as payment gateways, marketing automation, and inventory management systems, which can simplify operations and improve efficiency.
Third, extensible platforms provide businesses with the flexibility to adapt and evolve their online store over time, as their needs change or grow.
Overall, an extensible eCommerce platform empowers businesses to create a tailored online shopping experience that aligns with their unique business model and drives success.
What does extensibility mean in business?
In business, extensibility refers to the ability of a software or platform to be easily extended or customized to meet the specific needs and requirements of a business. Extensible platforms provides businesses with the flexibility to add new features and functionalities, integrate with third-party tools and services, and adapt to changes and growth over time.
The extensibility of a platform enables small businesses and enterprises to expand their web software platform and add new features with new digital transformation initiatives to improve the customer experience, which leads to improved customer satisfaction.
This can help businesses to create a tailored solution that aligns with their unique business model and drives success. Ultimately, extensibility of a platform enables businesses to use technology in a way that supports their specific needs and gives them a competitive edge, rather than having to conform to a one-size-fits-all solution.
What does extensible mean in programming?
In programming, extensible refers to the ability of software or a programming language to be easily extended or customized by developers. An extensible system provides developers with the flexibility to add new features, functionalities, or modules without having to modify the underlying system.
This is often achieved through the use of a well-defined user interface, plugins, or APIs that allow developers to build on top of existing functionality. This can result in more efficient telemedicine app development, increased code reuse, and the ability to adapt to changing requirements or business needs. In summary, extensibility of a platform is a key characteristic of programming languages and software systems that enable developers to create scalable, adaptable solutions.
What is extensible architecture, and who uses it?
Extensible architecture is software engineering that is designed to be easily extended or modified. This is typically achieved through the use of a well-defined interface or APIs that allow developers to add new functionality or modules to the system without having to modify the core functionality of the existing codebase.
Software extensibility is characterized by a high degree of flexibility, which enables the system to adapt to changing requirements or business needs. An extensible system can result in more efficient development, increased code reuse, and the ability to support a wide range of use cases. In summary, an extensible architecture is a key characteristic of software systems that enable developers to create scalable, adaptable solutions.
What is extensibility in web technology?
In web technology, extensibility of a platform refers to the ability of a web platform, framework, or language to be easily extended or customized to meet the specific needs of a project or application. This means that developers can add new features, functionalities, or modules to the system without having to modify the underlying codebase.
What does extensibility give developers specifically?
Extensible web technology provides developers with the flexibility to create custom solutions that align with the unique requirements of a project or application. This can result in a more efficient telemedicine app development solution, increased code reuse, and the ability to adapt to changing requirements or business needs. In summary, extensibility of a platform is a critical factor to consider when choosing web technology for a project or application.
What is the difference between extensibility and scalability?
They describe unrelated properties. Extensibility is whether you can add capability without altering what is already there. Scalability is whether the system copes with far more traffic, orders or products without being redesigned. A rigid platform can scale superbly, and a highly extensible one can fall over at modest load. If a vendor answers a question about one by describing the other, ask again.
What is an extension point?
A place the platform deliberately provides for your code to run: a hook, an event, a plugin interface, an override the vendor supports. Building at an extension point means your code sits outside the platform's own files, so an upgrade replaces theirs and leaves yours alone. The number and placement of these points is one of the real differences between platforms that otherwise look alike on a feature list.
What is the difference between an API and a webhook?
Direction. With an API your system asks the platform for something or tells it to do something. With a webhook the platform tells your system that something happened, by calling a URL you nominate when an order is placed or a product changes. You need both: APIs to act, webhooks to react without polling on a timer. When evaluating webhooks, ask which events are published, whether failed deliveries are retried, and whether ordering is guaranteed.
Does headless commerce mean the same thing as extensible?
No, though they are related. Headless means the storefront is separated from the commerce engine and talks to it through APIs, which gives you complete control of the customer experience. That control depends on the platform's APIs being extensive, so headless requires extensibility, but it is a specific architectural choice rather than a synonym. A platform can be highly extensible and still be used with its own storefront, which is often the cheaper and entirely sensible decision.
What is the risk of an extensible platform?
That the freedom gets used badly. Extensibility makes it possible to build almost anything, including a great deal that should have stayed configuration, and every extension is code somebody has to maintain, test and understand later.
The specific failure is reaching past the extension points and modifying core files, because it works immediately and silently ends your upgrade path. Within two or three years that leaves you several versions behind, unable to take security patches, on a platform that is extensible in theory and frozen in practice.
How do I tell whether a platform is genuinely extensible before buying?
Ask for the developer documentation rather than the sales material, and see whether it exists, is current, and is public. Ask what share of admin functionality the API covers, since the gap between what the interface can do and what the API can do is where projects get stuck. Ask how long a major API version is supported and how much notice a breaking change gets.
Then test it. Build one genuinely awkward thing your business actually needs, using your own people rather than the vendor's, and see how far the extension points get you before someone suggests editing something they should not.
Related reading
About the author
Autumn Spriggle is a Content Writer at Clarity Ventures with experience in research and content design. She stays up to date with the latest trends in the eCommerce and software development industries so she can write content to help people like you realize the full potential for their business.
Clarity builds extensions that survive the next upgrade and says so when configuration would do.
Custom pricing, checkout logic, catalogue models and integrations built at the platform's extension points rather than through its core, so you can still take updates afterwards. We have been building and extending commerce platforms since 2007. Tell us what your platform will not do, and we will tell you whether it needs code or a setting.