PrestaShop Guides

Own modules · Support in Spanish

PrestaShop guides: modules, migrations, and connections with your management system

We have spent years developing modules for PrestaShop, and these are the guides that come out of that work. Fewer than the WooCommerce ones, but written with the same criteria: what really breaks and how to avoid it, not a copied list of features from the marketplace.

See our modules What’s coming

Dropshipping and suppliers in PrestaShop

Connect a wholesaler with PrestaShop and keep the catalog, stock, and orders updated automatically.

See the Dreamlove connector for PrestaShop →

Synchronize Dreamlove with PrestaShop: complete step-by-step guideSynchronizing Dreamlove with PrestaShop is easy: import catalog, stock, and prices, and automate orders step by step…Automatic Dreamlove PrestaShop dropshippingDreamlove PrestaShop dropshipping Dreamlove PrestaShop dropshipping Doing Dreamlove PrestaShop dropshipping has a…5 foolproof strategies for your dropshipping with Prestashop and DreamloveBoost your dropshipping with Prestashop & Dreamlove Sync Dropshipping has established itself as the business model…

How to choose a PrestaShop module without regretting it

This is the decision that is hardest to undo. A badly chosen module not only fails to do what you expected: it blocks the next store update and, if it touches the core, leaves traces even after you uninstall it. These are the five checks we make before installing anything:

Compatibility with your exact version, not with “PrestaShop 8” in general. Between 8.0 and 8.2 there are differences that break modules.
Date of the last update. More than a year without changes usually means abandoned, and an abandoned module is an impossible migration in two years.
Who provides support: the person who wrote it or an intermediary. In a real issue, the difference is days.
Whether it respects documented hooks or touches the core. The first survives updates; the second does not.
What it loads on the front end. A module that only works in the back office does not affect what the customer sees; one that adds CSS and JavaScript on every page does.

And the check that saves the most money: always install in a test environment first. In PrestaShop, a badly made module can leave the store blank, and discovering that in production on a Friday afternoon is expensive.

Which version of PrestaShop should you have

This is the source of half the problems that reach us, so it’s worth saying clearly.

If you are on 1.6, you are on a version without security patches and on PHP versions that are no longer supported. It’s not about having the latest: your hosting will eventually force a PHP version your store can’t handle, and every new payment gateway will stop offering you a module. Migrating is not optional; it’s a matter of when.

If you are on 1.7, you have some room, but the clock is ticking. Upgrading to 8 is much less traumatic than coming from 1.6, because the architecture is already the same: this is the cheap time to do it.

If you are on 8, stay up to date within the branch. Minor updates bring security patches and rarely break anything.

One warning we always give: do not migrate during peak season. Choose the slowest month of the year, not the one that suits your calendar. And have a rollback plan ready.

Four mistakes we see again and again

Touching the core instead of using overrides. It works today and makes updating impossible tomorrow. If someone did that in your store back then, that part is archaeology when it’s time to migrate.
Accumulating modules that are no longer used. Even if disabled, they are still there, and during migration you have to decide on each one. Uninstall what you don’t use.
Not having a tested backup. A backup you have never restored is not a backup; it’s a folder.
Entering orders into the invoicing program manually. One hundred orders a month is more than three hours, plus errors. It’s the first thing we would automate.

Upcoming PrestaShop guides

These three are written and scheduled. If you’re interested in any of them, come back that week or write to us and we’ll let you know when it’s published.

September 7The best plugins for PrestaShopThe seven types of module that a real store actually needs, which ones are unnecessary, and how not to hurt performance by installing too many.

September 14Migrating from PrestaShop 1.6 to 8What is guaranteed to break — theme, modules, customizations, and URLs — the six steps in order, and what to test before going live.

September 21Connect PrestaShop with your invoicing softwareThe four ways to do it, what to check so it doesn’t duplicate invoices, and why e-invoicing changes the calculation.

PrestaShop or WooCommerce?

We get asked this often, and the honest answer is that it depends on where you’re coming from, not on which is “better.”

PrestaShop comes more ready out of the box for a store: tax management by zone, carriers with rules, customer groups with their own rates, and multistore. In return, every major update is a project and the module ecosystem is smaller.

WooCommerce has many more plugins and more people who know how to work with it, and it relies on WordPress for all content — which is no small detail in a business that lives off SEO. In return, building a serious store requires more pieces.

We develop for both. If you’re already on one, it almost never pays to switch just for the sake of switching: it’s more profitable to fix what’s failing. And if you’re starting out and SEO will be your main channel, WooCommerce makes it easier. You have the WooCommerce guides here.

Need a module that doesn’t exist?

We develop custom modules for PrestaShop: connection with your ERP, supplier synchronization, and compliance. With direct support from the people who write them.

See the modules Tell us about your case