Contact
One address reaches all of us, and there is deliberately no form on this page: a form would send mail to that same address, with a screen in between telling you it worked. Write to us directly instead — here is what to say, and what to put in the subject line.
Support
Write to [email protected]. A build that failed, a module misbehaving on your shop, a question the documentation does not answer, or feedback on the beta — that address reaches us for all of it, and beta is exactly when a report still changes something.
There is no ticket system behind it and no automatic reply to expect: a person reads what you send. We are not going to put a number on how quickly we answer while we are in beta, because it is not a promise we could keep yet.
What to put in the message
- The email address your account uses, if you are writing from a different one.
- The name of the module, and roughly when you built it if you have built more than one.
- What you expected to happen and what happened instead, in the words you would use out loud.
- Your PrestaShop and PHP versions, and your theme, if the module is installed and behaving oddly on your shop.
Billing and credits
One credit is spent the moment you approve a spec, and it goes straight back if the handover to the pipeline fails. If you have run out of builds and want more, write with “More builds” in the subject — the button in your account opens that same message.
The rest of your account goes to the same address: a credit you think was spent when it should not have been, the address the account is under, or closing it altogether.
Partnerships and press
Agencies, hosts and PrestaShop people who want to work with us, and journalists writing about what we are doing, are welcome at the same address. Put “Partnership” or “Press” in the subject so it does not sit in the support queue.
Sponsoring the project and investing in it each have their own page, with the detail worth reading before you write. They appear here as they are published.
Security
If you have found something that looks like a vulnerability, send it to [email protected] with “Security” in the subject and the steps to reproduce it, and please give us the chance to fix it before it goes public. We do not run a bounty programme, so there is nothing to claim beyond our thanks — and credit in the fix, if you would like it.
Questions about how a build actually works are answered in the documentation, in more detail than an email would give you.
Read the documentation