Working with PrestaShop?

PrestaShop store stuck or breaking? We fix it.

Most PrestaShop stores that reach us were built in Europe, upgraded halfway, and now sit on a version that nobody wants to touch. We finish the upgrade, sort out the modules, and leave the store running on a version that still gets security fixes.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

prestashop.log

still failing

What it is

PrestaShop at a glance

PrestaShop is an open-source ecommerce platform started in Paris in 2007 by two students, Igor Schlumberger and Bruno Leveque, as a school project that grew into a full product. It runs on PHP with MySQL or MariaDB, used Smarty templates for years, and moved to Symfony and Twig underneath from the 1.7 release onward.

It is mostly found in Europe, with France, Spain, Italy and Poland making up much of the install base, and is less common in the United States than Shopify or WooCommerce. Multi-shop, multi-language and multi-currency are part of the core, and the current major version is the 8.x series.

Type
Open-source ecommerce platform
First released
2007
License
OSL 3.0 for the core, AFL 3.0 for modules and themes
Maintained by
PrestaShop SA and the contributor community
Typically used for
SMB stores, European retailers, multi-shop brands, stores that need multi-language and multi-currency

The honest version

PrestaShop pros and cons

No technology is all upside. This is where PrestaShop earns its place and where it tends to cause trouble.

Where PrestaShop is strong

  • Free and genuinely openThe core is OSL 3.0 and modules and themes are AFL 3.0, so you can host it anywhere and modify what you need without asking anyone.
  • A full ecommerce feature setMulti-shop, multi-language, multi-currency, catalog with attributes and combinations are all built in, not bolted on through paid extensions.
  • A real European presenceTax rules, carrier integrations and payment gateways for France, Spain, Italy and Poland are first-class citizens inside the platform.
  • A large module marketplaceThousands of modules exist for almost every requirement, though quality is uneven and you should check a module before trusting it.
  • Symfony underneathFrom PS 1.7 onward the framework is Symfony with Twig, which pulls the codebase closer to modern PHP and widens the pool of developers who can read it.

Where PrestaShop bites

  • Version jumps are painfulEach hop from 1.6 to 1.7 and then to 8.x broke overrides, template conventions and module compatibility, so an upgrade is a project rather than a click.
  • Module quality varies wildlyThe marketplace mixes excellent work with abandoned modules, and many stores run modules whose authors stopped answering tickets years ago.
  • The override folder is a footgunOverrides stack silently and conflict with each other and with module overrides, which is how an innocent update turns into a blank page.
  • Default performance is poorOn ordinary shared hosting with no cache tuning and no CDN, PrestaShop categories crawl, and the standard advice of 'buy a bigger server' only hides the cause.
  • English documentation is spottyThe core docs are usable but thinner in English than in French, and community answers are often split across two languages.
  • Thinner talent pool in the USCompared with Magento or WooCommerce, finding a US developer who has shipped real PrestaShop work is harder, and agencies outside the EU are rarer.

Sound familiar?

Common PrestaShop problems we fix

The PrestaShop problems that bring people to us, and what you have once each one is fixed.

PrestaShop 1.6 reached end of life June 2022

The store is still on PrestaShop 1.6

An unsupported version with no security fixes, modules that no longer install, and a payment gateway that will drop it at the next PCI audit.

Upgraded to a supported release

Module: 'blockcart' not compatible with PrestaShop 8

Modules broke after the last upgrade

Modules written for 1.6 or early 1.7 that use removed hooks or old template paths, so half the front office stopped rendering.

Modules replaced or rewritten

override folder: conflict with core override

A small change took the whole site down

Overrides left behind by a previous developer collide with a module override, and the cache rebuild fails silently.

Overrides audited and cleared

TTFB 6.1s on category pages

Catalog pages are painfully slow

Smarty cache off, no full-page cache, product attribute queries unindexed, and a theme that loads every image at full size.

Category pages under a second

Multi-shop: product duplicated across shops

Multi-shop is out of sync

Products, stock and prices drift between shops because an import script writes to one shop context and ignores the others.

Shops back in step

payment module: callback IP not whitelisted

Orders are being dropped at payment

The gateway's IPN callback cannot reach the store, so paid orders stay in a pending state and stock never decrements.

Payments and orders reconciled

handoff: agency unresponsive

Taking over from a European agency

No handover, credentials in someone else's name, and a staging site you cannot log into.

Access and source back in your hands

What we do

PrestaShop help, from rescue to upkeep

Call us for one broken module, or hand us the whole store.

Rescue
Down after an upgrade or a module install. We get the store taking orders again, then work out what actually changed.
Upgrades
PS 1.6 to 1.7 to 8.x, rehearsed on a copy first so the production cutover is boring.
Module work
Replacing abandoned modules, patching the ones worth keeping, and writing new ones in-house when nothing on the market fits.
Performance
Smarty and full-page cache, database indexing, image handling and hosting that fits the real traffic, measured both ways.
Handovers
Taking a store back from a European agency, consolidating access, and producing a handover that would actually help the next person.
Managed Tech
Core and module patch windows tested on a copy first, verified backups, store health reports each week, and someone to ring when checkout misbehaves.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running PrestaShop alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

PrestaShop questions

Something else? Call+1 737 727 7327

Can you upgrade our PrestaShop 1.6 or 1.7 store to PrestaShop 8?

Yes. PrestaShop 1.6 reached end of life in June 2022 and no longer gets security fixes, so the upgrade matters. We copy the store to a staging server, upgrade there, rewrite or replace any modules that do not run on 8.x, test the full checkout, and only then schedule a short cutover on the live site.

Our PrestaShop store is slow, what can we do?

The common causes are Smarty cache turned off, no full-page cache in front, oversized theme images, missing indexes on product attribute tables, and hosting that is too small for the catalog. We measure before and after and fix the ones that are actually costing seconds, not the ones that sound impressive.

Can you take over a PrestaShop store from a European agency?

Yes, and this is a common reason stores reach us. We consolidate access, pull the source and database into version control, document what every custom module does, and leave you with a store you can move again later if you want to.

Should we move from PrestaShop to Shopify or WooCommerce?

Only if the platform is genuinely holding the business back. For an EU-centric store with multi-shop and multi-currency, PrestaShop is often still the right fit. For a small US-only catalog without those needs, Shopify or WooCommerce may be cheaper to run. We will say plainly which way we would go in your case.

Why do our PrestaShop modules keep breaking after each update?

Because module compatibility across major versions has never been smooth, and the marketplace is full of modules whose authors have moved on. We audit the module list, drop the ones you do not use, patch the ones worth keeping, and replace the abandoned ones with maintained alternatives.

How much does PrestaShop help cost?

Estimates are free. Tell us the version, the modules, and what is going wrong, and you get a price before any work starts.

Free estimate

PrestaShop giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.