How do we bill Magento modules purchased on kowal.store?

Simple licensing terms, no subscriptions, and installation support

When you buy a Magento module on kowal.store, you pay for it once. We do not add a recurring subscription just for using the module, we do not make the extension dependent on a monthly fee, and we do not lock installation to a specific domain. Our model is simple: the customer buys the module, receives access to the package, a license key, and documentation, and can then implement the solution in their Magento stores according to the needs of their organization.

Below, we explain the key rules for billing, licensing, updates, and technical support for modules available on kowal.store.

1. No subscriptions

Modules sold on kowal.store do not operate on a subscription model. This means that after purchasing a module, you do not have to pay every month or every year just to keep using it.

In practice:

• you buy the module once,
• you do not pay a recurring license fee just for using the module,
• the module does not stop working after a subscription period ends, because there is no such subscription,
• the purchase cost is predictable from the start.

This is a good solution for Magento stores that want to control maintenance costs and avoid multiplying fixed fees for every extension.

2. Lifetime updates

For purchased modules, we provide lifetime access to updates published by kowal.store. If we develop a module further, fix bugs, adapt it to newer Magento versions, or improve how it works, the customer can use the available updates without buying the module again.

Updates may include, among other things:

• bug fixes,
• module performance improvements,
• Magento 2 compatibility updates,
• security fixes,
• minor feature enhancements,
• Composer installation improvements.

It is worth remembering that updating a module does not always mean individually implementing changes in a specific store. Access to updates itself is part of the purchase, while custom development work, analysis of conflicts with other modules, or larger store modifications may require a separate service.

3. One license key per customer

We assign the license key to the customer, not to a single domain. It does not matter whether you install the purchased module in a production, test, development, staging environment, or in several stores belonging to the same company.

This means that:

• you do not need to buy a separate license just because you have a test environment,
• you can safely test the module before production deployment,
• you can use the modules within your own store infrastructure,
• moving the store to another domain or server does not require purchasing a new license.

This model is convenient for store owners, agencies, and technical teams that work across multiple environments and need flexibility when deploying Magento.

4. Free installation support for modules from kowal.store

For modules purchased on kowal.store, we offer free support with basic installation. If there is an issue during installation with access to the package, Composer configuration, enabling the module, or standard Magento commands, we help you get through the process.

Installation support typically includes:

• help downloading the module,
• providing Composer commands,
• verification of basic installation steps,
• help enabling the module in Magento,
• showing where to configure it in the admin panel,
• answers to questions about standard installation.

If the issue results from a custom store configuration, a conflict with another extension, Magento core modifications, server errors, or the need for an individual implementation, we can offer an additional technical service. This keeps basic support free, while more complex work is priced fairly according to the actual scope.

5. Comprehensive module documentation

We aim to describe each module so that its installation, configuration, and day-to-day use are as clear as possible. Documentation is especially important in Magento, because installing an extension is often only the first step. Correct module setup, understanding the available options, and checking how it works in a specific store process are also essential.

Module documentation may include:

• technical requirements,
• Composer installation instructions,
• Magento commands required after installation,
• configuration description in the admin panel,
• sample initial settings,
• description of how the most important features work,
• tips for post-deployment testing,
• information about common issues and how to resolve them.

As a result, both technical users and store owners can use the modules and better understand what has been implemented and how to manage the feature in the Magento panel.

6. Composer installation and organized access to packages

We provide modules in a way that is convenient for Magento 2 projects, most often through Composer. This is the standard and secure way to install extensions in Magento, especially in production environments managed by developers or agencies.

Composer makes it easier to:

• install a specific module,
• update to a newer version,
• control dependencies,
• deploy to test and production environments,
• maintain a repeatable deployment process.

This means the module is not a random file manually uploaded to the server, but part of an organized store maintenance process.

7. Clear rules for stores, agencies, and IT teams

The kowal.store licensing model was designed with real Magento work in mind. Stores often have a production environment, staging, local development environments, multiple store views, multiple domains, or a separate technical team. A license assigned to the customer makes this kind of work easier and reduces formalities.

We do not want customers to have to wonder whether testing an installation on staging will generate an additional cost. We also do not want a domain change, server migration, or infrastructure reorganization to force the repurchase of the same module.

8. What is included in the module price?

The module price primarily includes:

• one-time purchase of the module,
• the customer's right to use the module,
• a license key assigned to the customer,
• access to updates published by kowal.store,
• installation, configuration, and usage documentation,
• basic installation support for a module purchased on kowal.store.

Work that goes beyond the standard module purchase may be billed separately, for example custom modifications, non-standard integrations, analysis of conflicts with other extensions, work in the customer's environment, or full feature implementation by our team.

9. Why did we choose this model?

Magento is a system for stores that often grow over many years. Modules should support that growth, not create more unclear costs. That is why we focus on a simple model: one-time purchase, no subscriptions, updates, documentation, and installation help.

For the customer, this means:

• greater cost predictability,
• fewer formalities during deployments,
• freedom to work in test environments,
• easier cooperation with an agency or your own IT team,
• access to updates without buying the module again,
• a clear separation between purchasing the module and individual implementation work.

Summary

Magento modules available on kowal.store are billed in a simple and transparent way. We do not require subscriptions, we provide lifetime access to updates, we assign the license key to the customer, we help with basic installation, and we provide the documentation needed for configuration and use.

This is a model for companies that want to develop Magento without unnecessary licensing restrictions and without unpredictable recurring fees.