
Business models and licenses for Shopware extensions were the subject of Sandro Groganz's Shopware Community Open Stage session. Drawing on his work in marketing and sales for commercial open source businesses at OSS Flywheel, Sandro explored the choices behind selling an extension. The presentation and discussion covered ways to earn revenue, the role of open source and what happens when Shopware's own offering overlaps with extensions from other businesses.
For agencies and developers in the Shopware community who sell extensions or are considering it, his framework connects these decisions to the customer. Who will pay for the extension? What will they pay for? And what will make them want to keep working with you?
Sandro puts the business model first:
"So picking a license is just the beginning and you should actually not pick it if you don't know your business model yet."
A license determines what others may do with the code. A business still needs to establish what customers will pay for.
Start with the customer
The extension vendors in Sandro's framework include agencies building extensions for client projects, companies selling their own extensions and technology partners connecting products such as a CRM or ERP to Shopware. Hosting providers can also offer extensions that make administration easier. Shopware itself has a different role as the platform vendor, with its own commercial offering.
Sandro asks who the customer is and what remains scarce. Here, scarcity is about the time, expertise and responsibility involved in maintaining and running software, even when the code is available for free.
"How can you make sure that they want to buy your product because you provide the solution to that scarcity and they want to stick with you? For example, automatic updates to your extension, very simple. Or operations, maintenance. Maybe warranty and so on."
That ongoing work includes security fixes, bug fixes, releases and migration options. Larger organizations may also need warranties and other contractual assurances. Sandro's framework connects these considerations with where the software runs, who owns the code and who the competitors are, both inside and outside the Shopware ecosystem.
The discussion returns to this distinction when Niklas from Shopware Developer Relations asks about maintenance.
"Because you know, it's not just building an extension, you have to maintain it."
Sandro agrees: when software solves a complex or recurring problem, customers have a reason to pay for something that works reliably and for people who can maintain it.
Decide what customers will pay for
Sandro describes several revenue models, including paid licenses, subscriptions, open core, dual licensing, hosted applications and services. He presents them as options to consider in relation to the product and its customers.
With open core, an open source extension can be accompanied by proprietary add-ons. Sandro notes that the extension needs to address a sufficiently complex problem for that approach to make sense. He uses Shopware's community offering and additional commercial functionality as an example of the model.
A hosted application offers a different basis for payment: running the software for the customer. Services can include customization, training and consulting. In the discussion, Sandro describes making information about a product widely available so people can use it themselves. Some will still prefer to ask a consultant to build an integration for them.
His commitment to open source leaves room for proprietary licensing when the company's position supports it:
"But I totally get it. If you say, hey, we have a great product, we are the first ones on the market, let's make as much money as possible and let's use a proprietary license. That's totally fine. It makes a lot of sense from a monetization point of view."
Understand the role of free availability
Sandro discusses free open source extensions in the Shopware Store, paid extensions and distribution outside the Store. Free availability and open source licensing are different aspects of an offering. In his explanation, being able to see the source code does not necessarily give someone the permissions associated with an open source license.
He also sees a marketing benefit in open source when the software meets a real need. People can discover an extension, try it and recommend it to colleagues. His example is a recommendation in a company's private Slack channel. The vendor never sees that conversation, but the company may later get in touch because it already uses the extension and wants its commercial version.
Sandro calls this the “dark funnel,” referring to the discovery and evaluation that happen outside the vendor's view. In that example, users have already tried the software before a sales conversation begins.
The work continues after discovery.
"Then of course, further down, you just have to do the usual marketing."
Open source can reduce the effort needed to create awareness, but vendors still need to help people start using the product and become paying customers. Sales conversations may remain part of that process. The free offering is one possible route to adoption, with further work needed around the commercial offer.
Match the license to the model
Licensing becomes easier to discuss once the revenue model is clear. Sandro uses the example of selling software under a permissive license: after paying, a customer may be able to pass it on to someone else. That matters when deciding what the vendor is charging for.
Ownership is another part of the decision. In his explanation of dual licensing, the ability to offer the same code under different terms depends on owning the code. Niklas adds a practical example from Shopware: when the company changed its license, it had to seek permission from contributors.
Sandro also asks vendors to consider how their extension fits into the technical setup. A plugin running inside Shopware, an app and a separate service connected to other systems raise different questions. His framework brings these choices together with the revenue model rather than treating the license as an isolated decision.
Consider your position within Shopware
Distribution affects how customers find an extension. Sandro notes that selling outside the Shopware Store means losing the visibility it provides. Vendors taking that route have to account for the marketing implications.
Sandro also raises a tension within the ecosystem: by adding functionality of its own, Shopware can become a competitor to the extension vendors building on its platform. He points to advanced search and B2B components as examples of the generic commerce capabilities where their offerings can overlap.
"Design your business model for your extension, whether you are ahead of Shopware, whether you're behind, how likely is it that they will bring something similar to the market or not? Take that into account when you think about your extension and your business model."
AI leaves vendors with another question: what happens when customers can build an alternative more cheaply? Sandro sees possible pressure on prices, while maintenance and specialized knowledge still matter, particularly for complex or recurring problems. His answer leaves room for uncertainty:
"But maybe right you can't ask for the same price anymore. You need to go down. Maybe you need to offer more services or more functionality. That's all in flux right now and it's not decided. No one has the right answers to these things yet."



