PrestaShop Module Licensing, Activation & Support Explained

Every paid module we sell at mypresta.rocks comes with a license and a period of support, and almost every question our support desk answers about billing comes down to the same thing: people mix up what a license is and what support is. They're two different things, bought once, that behave differently for the rest of the module's life. This page is the plain-English walkthrough we point customers to — the one that replaces a dozen half-answers scattered across our FAQ.

It's written for two kinds of reader. If you bought one module for one shop, the main sections are all you need. If you run modules across several client stores, read the For agencies section at the end — the rest still applies, but that part is where the fleet details live.

For the formal legal terms, see our License Agreement. This guide doesn't restate the legal wording — it tells you how the product actually behaves.

Written and maintained by the mypresta.rocks team — we build and support these PrestaShop modules ourselves. Last updated: 5 July 2026.

The short version

Try any module free for 30 days. Buy whenever you're ready — before or during the trial. When you buy, you activate in place: your installation and settings stay exactly as they are, nothing is reinstalled or reset. Paid modules include three months of support to start. The one distinction to hold onto: a license unlocks the module on a store and never expires; support is a period of time and is counted per store.

License vs. support — the one distinction that explains everything

Keep these two apart and the rest of this page is obvious.

That table is the whole model. Everything below is just detail.

1. Try it free for 30 days

Every paid module has a 30-day demo you download from mypresta.rocks. It's the real module, fully functional — not a locked or watermarked preview of the paid one. Install it, configure it, run it on your shop for a month, and decide with real data instead of a screenshot.

And to be straight with you: we like it this way. We'd genuinely rather you run the demo, confirm the module solves your problem, and buy because it earned its place — than pay on a promise and feel stuck with something that didn't fit. You get a module you already know works; we get customers who are glad they bought, and far fewer tickets that start with "this isn't what I expected." A fully-functional 30-day demo is how everyone ends up on the same side.

The one optional step at download

When you download, you can optionally enter your email and the domain you'll install on. There's exactly one reason to do it: if you later buy using that same email, your store can offer you one-click activation — no key to copy, nothing to look up. Skip it and you lose nothing; you'll simply paste a license key after buying instead. Both paths end in the same place.

2. Buy whenever you're ready

You can buy at any point — before you download, during the trial, or after it ends. There's no penalty for waiting and no rush; the trial and the purchase are independent of each other.

What's included:

• Paid modules include three months of support free, counted from your purchase date.
• You can choose 6, 9, or 12 months of support instead. That number is the total support period, also counted from the purchase date — not an extra block added on top of the three months.
• Free modules include no support time. If you want support on a free module, you add it separately (see Monthly support).

The price of each support tier and of the monthly plan is shown on the module's own page and at checkout — it's set per module, so we don't quote figures here.

3. Activate — in place, nothing reset

This is the step people worry about, so let's be plain: activating keeps your installation and settings. Nothing is reinstalled and nothing is reset. You don't reinstall the module, you don't lose your configuration, you don't start over. Activation simply flips the module from "trial" to "licensed" where it already sits.

There are three ways to do it. They all reach the same result — pick whichever fits your situation.

Option A — one click on the module's License tab

If your purchase matches the email and domain you gave at download, an activation offer appears on the module's License tab inside your shop's admin: a panel headed "Your purchase is ready" with an "Activate purchase now" button. Only that store's admin sees it, and it's still an explicit click — nothing happens on its own. If you see the offer, this is the fastest route there is.

Option B — assign it in your mypresta.rocks account

Log in to your mypresta.rocks account and map the license to your store's domain. The store activates itself on its next check-in — no key to paste, no email to match. For most people this is the cleanest path, and it's the one to use if you didn't fill in the email and domain at download.

Option C — paste your license key

Every license has a key in the form MPR-XXXX-XXXX-XXXX-XXXX. Paste it on the module's License tab and activate. This needs no account and works even on a store that can't reach us at that moment — it's the fallback that always works.

4. How support works — the honest rules

Support is where the "per store" idea matters most, so here it is with no small print.

Support is per store

One support covers one store — not your whole account, not every shop you own. If you run the same module on two stores and want both covered, you buy support for each.

The clock starts at purchase

Your support period begins on your purchase date, whether or not you've assigned it to a store yet. Assigning later doesn't reset or pause the clock, so it's worth assigning promptly.

You must assign support to a store to get worked answers

To receive worked ticket responses, support has to be assigned to that specific store. A store without assigned support can still open tickets — they're logged, but auto-closed, and reopened only if we accept the issue for work. Assigning isn't a formality; it's what turns your tickets into answers.

Activate first, then assign

Support can only be assigned to a store once the license is active there — but you don't have to do it in two trips. When you activate a module that has support waiting, the License tab offers a single “Activate license + assign support” button (with “Activate license only” as the fallback). One click activates the license and assigns support together, so you're fully covered from day one. And if the support step ever hits a snag, your license still activates — a support hiccup never leaves you with an inactive module.

Monthly support

You can keep a store covered with a monthly plan. If you already have prepaid support — the free three months, or a 6/9/12-month tier — the monthly plan simply starts when that runs out. You're never double-charged for the same period. The one exception is a free module with monthly-only support: there's no prepaid period to wait out, so it's charged immediately.

Moving support to another store

You can move support from one store to another. It's allowed, but deliberately rate-limited: once support has been assigned to a store, there's a 14-day cooldown before you can reassign it elsewhere. That gap is there for real events — launching from staging to production, or replacing a store you've closed — not for rotating one support plan around several live shops week to week.

One detail worth knowing: whether the support time travels with the move also depends on whether support was already used on the old store, and monthly (auto-renewing) support carries its own "locked until" date. If a move is ever blocked, that's why — open a ticket and we'll sort it out with you.

5. Domains — what one license actually covers

A license is bound to one production domain, and we've made the everyday build-and-launch workflow fit inside that single license on purpose:

• www and non-www are the same domain. example.com and www.example.com are one and the same to the license.
• A subfolder install on that domain is the same domain. example.com and example.com/test/ share the one license.
• Dev, staging and test subdomains don't consume your slot. A subdomain that carries a development label — dev.example.com, staging.example.com, test.example.com and similar (dev, staging, stage, test, preprod, qa, uat, demo, sandbox, local) — is recognised as non-production automatically, as are localhost and raw IP addresses. Build and test freely; activate your live domain when you go live.
• A genuinely separate production store needs its own license. Two different live domains — say store-a.com and store-b.com — are two production stores, even under one owner, so they need two licenses.

Moving to a new domain is fine — re-bind the license from staging to production at launch, or to a new domain if the store moves. Releasing a domain slot carries a short 72-hour cooldown before that slot can be reused, so plan a launch cutover as one step rather than flipping back and forth. (Moving support to a different store is a separate action with its own 14-day cooldown — see above.)

For agencies and freelancers

If you install our modules across multiple client stores, the model is deliberately simple — and it scales by store, not by account.

One license per client store

Each store that runs a module needs its own license. There's no fleet or site-group license that covers many stores from a single purchase — it's one license per client store.

Support is per store too

Support doesn't pool across your clients. Buy support for each store you want covered. One support plan does not cover a fleet: if five client stores should have worked ticket responses, that's five supports.

Run the whole portfolio from your account

Your mypresta.rocks account is the control panel for everything. From there you:

• Assign each license to its store's domain — the stores then activate themselves on their next check-in, so there are no keys to distribute.
• Assign support to each store that needs it.
• Re-bind a license when a client goes from staging to production (mind the 72-hour slot cooldown).

That's the entire agency workflow: one license and, where you want cover, one support per client store — all managed centrally, all self-activating.

Where to go next

• License Agreement — the formal legal terms.
• Your mypresta.rocks account — assign licenses and support to your store domains.
• Still stuck? Open a ticket from your account and a real person will pick it up.

This guide is maintained by the mypresta.rocks team, who build and support these modules directly. It describes how our licensing and support work in practice; if anything here ever disagrees with what you see in your account, tell us and we'll fix the guide.