About module.monster

Why it exists

Sooner or later a shop needs something PrestaShop does not do by itself: a badge under one supplier's products, a rule that changes what checkout offers, an export a wholesaler insists on. Individually these are small jobs — roughly a day for a developer who knows PrestaShop — but getting one built means finding an agency, writing a brief, waiting for a quote and explaining your shop to somebody who has never seen it.

That overhead is why a lot of those ideas stay ideas. module.monster is built for exactly that size of job: you describe it in your own words and get a working, installable module back, with no brief and no scoping call.

How it works

You type what your shop should do, and an agent that knows PrestaShop works the idea through with you: it leads with its best guess, pushes back when an idea is already core PrestaShop behaviour or is really three modules in one, and settles what a builder cannot guess — where the module appears, which hooks it uses, what you can configure, and what it deliberately will not do. Nothing is built and no credit is spent until you approve that spec. Approving hands it to a pipeline that writes the module, installs and exercises it on a live PrestaShop, translates it into the languages you picked, captures the screens, writes an illustrated guide and packages the lot as a zip. It runs unattended, so you can close the tab and come back to a finished module.

What we commit to

• The module is yours. Inside the zip is readable PHP under a commercial licence that lets you use, modify, resell and redistribute it, licence text included — read it, change it, or hand it to your own developer.
• It is an ordinary PrestaShop module zip. You install it yourself from your back office, whenever you choose, by the same route as any other module.
• It targets PrestaShop 8.x and 9.x on PHP 8.1 or later and follows standard module conventions: a configuration page in the back office, database tables namespaced to the module, and an uninstall that removes its tables, tabs and settings again.
• No access in either direction. Nobody here touches your shop, and the module does not call home or depend on module.monster to keep working — it goes on working whatever happens to us.
• The spec is agreed before anything is built. Brainstorming is free however long it takes, one credit is spent at the moment you approve, and it goes straight back if the handover to the pipeline fails.

We are in beta

The badge next to our name is not decoration. The service runs end to end and the modules it delivers are real, but it is young and still finding its own edges.

What that means for you: keep to one module at a time, sized at about what a good developer would build in a day; install what you get on a staging copy of your shop before it goes anywhere near the live one; and expect a build to fail now and then. A step that keeps coming back wrong is retried up to three times, and then the module is flagged as needing attention rather than delivered broken — you see that on its page, and we look into those ourselves.

What the service does today is written down in full, limits included, in the documentation. We would rather tell you where it stops than let you find out halfway through a build.

Who builds it

module.monster is a product of VSTEQ Softwares Private Limited.

Talking to us

Write to [email protected]. A build that went wrong, a module misbehaving on your shop, your credit balance, or a question this page does not answer — that address reaches us for all of it.

Beta feedback goes to the same place, and it is worth sending: beta is precisely when a report still changes something.