Builds on request
Signing up does not include free builds. Write to us and we add credits to your account by hand. No card is asked for and none is stored — the portal has no payment page at all.
PrestaShop 8 & 9 No code required
Describe it. Monster builds it.
Let's build your PrestaShop module.
Describe what your store should do. We'll brainstorm it together, then I build it, test it on a real PrestaShop installation, document it, and deliver the installable module.
How credits work
A build credit is the unit of work here: one credit is one module, taken all the way — written, tested, translated, documented and packaged. Credits are granted on request; a new account starts with none.
Talking is free
Describing an idea, working it through with the agent, changing your mind or walking away costs nothing, however long the conversation runs.
One credit, spent on approval
The credit is taken at the moment you approve the spec and the module goes to the build pipeline — never while you are still talking. Every approval spends one, including a changed version of a module you already have.
A failed handover gives it back
If the handover to the pipeline fails right then, the credit returns to your balance in the same request and nothing has been built. If a build fails later, write to us and a person looks at it.
Your balance is on your account page. At zero, brainstorming still works but approving is refused, and more builds are arranged by email: Ask for more builds
Create an account, describe the module, and ask us for credits when you are ready to build.
Create an accountQuestions before you start
Which PrestaShop versions are supported?
PrestaShop 8.x and 9.x, on PHP 8.1 or later. You choose either or both when you describe the module, and both are selected by default. 1.7 is shown in the version picker but cannot be chosen: the pipeline does not target it, and nothing older is supported.
Does the module work with multistore?
Yes, as long as you say so before the build. Multistore is a switch on the composer toolbar; it decides whether settings are stored per shop or globally and whether the module's own tables carry a shop column. It is settled in the conversation and exercised while the module is tested — cheap to decide up front, expensive to retrofit afterwards.
Which languages can the module ship with?
English, French, German, Spanish, Italian, Dutch, Polish and Portuguese, in any combination; English, French, Spanish and German are on by default. The translations ship inside the module's own language files. This is a different setting from the language this site is displayed in.
Who owns the delivered code?
You do. The zip is yours to use, change, install on as many shops as you like, resell, and hand to your own developer. Every source file carries a licence header naming the commercial licence it ships under, and the full text is in LICENSE.md inside the package.
What you wrote stays yours as well: your description, your messages and any screenshot you attach are used to build your module and for nothing else.
What happens if the build fails?
A step that keeps coming back wrong is retried up to three times. If it still does not pass, the module is flagged as needing attention on its own page rather than shipping something broken, and we look into those ourselves.
The credit comes back by itself in one case: when the handover to the build pipeline fails at the moment you approve. If a build fails after that, write to [email protected] and a person looks at it.
Can I change the spec mid-conversation?
That is what the conversation is for. Add to it, contradict yourself, drop a feature or start over — while a module is a draft, nothing is queued and nothing is charged.
Approving starts the build. While it runs the conversation follows progress; once the zip is ready you can keep chatting on that module and rebuild with changes for another credit. Read the summary before you press the button.
How do I install the zip?
It is an ordinary PrestaShop module zip. In the back office, go to Modules, then Module Manager, and use “Upload a module” to drop it in — PrestaShop unpacks and installs it in one step. Or unpack the zip yourself and copy the folder into your shop's /modules directory over FTP or SSH, keeping the folder name exactly as it comes out, then press Install in the Module Manager.
Either way, “Configure” opens the module's own settings page in the back office, and uninstalling from the same screen removes the tables, tabs and settings it created. Install it on a staging copy of your shop first and click through it there.
Does anyone need access to my shop?
No, in either direction. Nothing is installed on your shop for you, no shop credentials are asked for, and the module never calls home. That also means there are no automatic updates: what you download stays as it is until you build something new.