Doofinder for PrestaShop

Transform your PrestaShop search into a conversion machine. Join thousands of merchants using AI-powered search to increase sales and improve customer experience.

🚀 Get Started for Free | 🖥️ Live Demo | 📖 Full Documentation

---

Why Doofinder?

Doofinder turns your basic search bar into an advanced discovery engine. Using AI-powered searchandising and recommendations, we drive measurable gains in conversion and product discovery.

Key Features

• AI Assistant — A smart shopping guide that helps customers find products through natural conversation.
• AI Smart Search — Understands intent and handles typos or synonyms effortlessly.
• Searchandising — Boost, hide, or pin products to run targeted campaigns.
• Personalized Recommendations — Intelligent cross-selling based on real customer behavior.
• Visual Search — Let your shoppers find products using images.
• Auto-Indexing — Your catalog stays in sync automatically as you scale.

---

🛠 Installation & Quick Start

From GitHub (latest release)

1. Download the latest release zip.
2. In your Back Office go to Modules → Module Manager → Upload a module and select the zip.

From PrestaShop Addons
Install Doofinder from PrestaShop Addons via the marketplace in your Back Office or the steps Addons gives you after download.

Then
Complete setup using our step-by-step installation guide.

Requirements

| | Supported versions | | -- | -- | | PHP | 7.1 – 8.4 | | PrestaShop | 1.6.1.0 – 9.x (1.6.1, 1.7, 8.x, 9.x) |

[!IMPORTANT] The module requires PHP 7.1 or higher. The code uses class constant visibility (public const), a syntax introduced in PHP 7.1, so it cannot run on PHP 5.x or 7.0 (a fatal parse error occurs). As a consequence, PrestaShop 1.5.x and 1.6.0.x are no longer supported: those versions are capped at PHP 5.x and cannot run PHP 7.1+. The minimum supported PrestaShop version is 1.6.1.0.

For system requirements by version, see PrestaShop 1.7, PrestaShop 8, and PrestaShop 9.

---

👨‍💻 Development & Maintainer Guide

This repository is optimized for local development using a Makefile and Docker.

.env sits at the repo root and powers both your Docker stack and the generated module files (what doofinder-configure pulls from templates/). It ships with sensible defaults—skim it, adjust shop URL, PrestaShop tag, and plugin version, then make init. Optional overrides go in .env.local, which loads on top of .env.

[!NOTE] make doofinder-configure generates the plugin files from the templates/ directory (using .env) and runs make dump-autoload to regenerate the Composer autoloader. Many other targets depend on it, so running those targets keeps generated files in sync.

Environment and shop access

The root .env lists all variables with comments. For the dev stack, these are the ones you usually touch first:

| Variable | Role | | -------- | ---- | | BASE_URL | Shop hostname as seen by Docker (no https://). | | PRESTASHOP_DOCKER_TAG | PrestaShop image/version used by the stack. | | MYSQL_* | Database for the local shop. | | PS_* | Installer options (language, country, domain, SSL, etc.). | | PS_ADMIN_EMAIL / PS_ADMIN_PASSWORD | Back-office login after install. | | PS_FOLDER_ADMIN | URL segment for the admin (see Default access below). |

Default access (Docker dev stack): After make init, open the shop using the host ports from docker-compose.yml (stock mapping: 9011 → HTTP, 4011 → HTTPS on the container). With the default BASE_URL=localhost and PS_FOLDER_ADMIN=4dm1n from .env, typical URLs are:

| | URL | | -- | -- | | Storefront (HTTP) | http://localhost:9011/ | | Storefront (HTTPS) | https://localhost:4011/ | | Back office (HTTP) | http://localhost:9011/4dm1n | | Back office (HTTPS) | https://localhost:4011/4dm1n |

Back-office login is PS_ADMIN_EMAIL / PS_ADMIN_PASSWORD in .env (stock file uses test@example.com / admin123—change these for anything beyond local-only use). make init prints usable links; if you change ports or BASE_URL, adjust accordingly.

Use cases:

• First-time setup: Run make init once to build images, install PrestaShop, and start containers.
• Install the Doofinder module: after make init, follow the installation guide. Alternatively, use make doofinder-upgrade from the CLI.
• Start / stop the stack: make start, make stop.
• Uninstall the module: make doofinder-uninstall.
• Reinstall the module: make doofinder-reinstall.
• DB snapshot: make db-backup (optionally make db-backup prefix=_name). Restore with make db-restore file=backup.sql.gz.
• Clear cache: make cache-flush.
• Shell in the web container: make dev-console.
• Start from scratch: Run make clean to drop Docker volumes and ./html; type DELETE when prompted, then run make init for a fresh PrestaShop.
• Debug with Xdebug: The stack already enables Xdebug in Docker. Set XDEBUG_HOST and XDEBUG_KEY in .env or .env.local (e.g. host.docker.internal on Docker Desktop, your host IP on Linux), use the same key in your IDE, listen for connections, and browse the shop.

---

Compatibility Matrix

We test against a wide range of PrestaShop and PHP combinations to ensure stability. Example combinations from PrestaShop Docker Hub:

| PrestaShop | PHP | | ---------- | ----------------------- | | 8.2.1 | 8.1, 8.0, 7.4, 7.3, 7.2 | | 8.1.7 | 8.1, 8.0, 7.4, 7.3, 7.2 | | 8.0.5 | 8.1, 8.0, 7.4, 7.3, 7.2 | | 1.7.8.9 | 7.4, 7.3, 7.2, 7.1 | | 1.6.1.x | 7.2, 7.1 |

[!NOTE] PHP 7.0 and 5.x are no longer supported (the module uses public const, which requires PHP 7.1+). PrestaShop 1.5.x and 1.6.0.x are dropped because they cap at PHP 5.x; the minimum is PrestaShop 1.6.1.0 running on PHP 7.1 or higher.

Set PRESTASHOP_DOCKER_TAG in the .env file and (if needed) PHP version in your Docker build args when using these combinations.

---

Support & Contributing

• Need Help? Visit our Support Portal.
• Found a Bug? Please contact Doofinder Support from the Doofinder website.
• Want to contribute? PRs are welcome!

If you find this plugin useful, please give us a ⭐ to support the project!

Try Doofinder / Learn more

Ready to improve your store search? Get started with Doofinder for PrestaShop.