ornibird.com

The signal

When we listed NP Search on the PrestaShop Addons marketplace in May 2026, we ran zero outbound marketing. The listing was the experiment: does a self-hosted search module — paid once, no recurring fee, no SaaS in the loop — get bought on a marketplace where every competitor is a SaaS recurring-revenue model?

We got the answer ~7 days later. Cédric, who runs the bird-supplies retailer ornibird.com on PrestaShop 8.2 from Belgium, found the listing, bought NP Search, and replaced Doofinder on his store the same afternoon.

The before-state

ornibird had been running on Doofinder for the previous ~18 months. Doofinder did the job — typo-tolerance, searchandising rules, the overlay shoppers expect on a specialty retail storefront. The complaint wasn't features. It was the recurring fee, which had gradually crept into "line-item visible at quarterly review" territory, and the fact that Cédric was reading PrestaShop Addons one evening and spotted NP Search.

This is the buyer profile we've come to expect for migrations into NP Search: the shop is small enough that recurring SaaS is visible in the P&L, established enough to have configured the SaaS thoroughly, and run by someone who reads the marketplace because they care about their stack.

The migration shape

From conversation with Cédric and from the way we've designed NP Search to coexist during transitions, the rough shape was:

1. Install side-by-side: NP Search and Doofinder both active. The overlays bind to different selectors so there was no visual conflict.
2. Copy the configuration: synonyms, searchandising rules (pin / boost / hide), zero-result fallback — all the merchandising logic Cédric had accumulated on Doofinder, ported over to NP Search's admin in about an hour.
3. Run shadow for the storefront: NP Search's overlay took over the search bar; Doofinder remained installed but inactive. That gave Cédric a quick rollback path if anything went sideways.
4. Cancel the SaaS subscription: a week later, with analytics looking good (top queries matching, no-result rate down, click-through preserved), Cédric cancelled Doofinder and uninstalled the module.

What this taught us

Before Cédric, we'd been operating on a thesis: that the "best-in- category self-hosted plugin" niche existed for PrestaShop, and that merchants who were paying SaaS for things that should be one-time would migrate if a credible alternative was on the marketplace where they shop. We weren't sure.

Cédric's purchase confirmed three things in one transaction:

• The marketplace listing alone is enough. We didn't need outbound sales, didn't need content marketing yet, didn't need paid acquisition. The PrestaShop Addons listing did the work.
• The migration friction is low enough to win. One afternoon of work to switch saves €348+/year forever. That math is obvious once the customer sees it. The hard part is making the alternative discoverable.
• One paying customer is the only proof point that matters. A second won't unlock 10x; the first one already proved the loop can close.

The compounding effect on our roadmap

This single data point is why neuroplugin shifted from "we sell some plugins, maybe consulting, see what sticks" to "best-in-category in three focused PrestaShop categories — search, age-restriction compliance, conversion mechanics." Cédric didn't ask for that focus; it's just what the signal said to do.

It also justified the engineering investment in the compatibility watcher — once we have customers, we need to honour the "no surprise breakage on next PrestaShop release" contract. The watcher's existence is the long-tail commitment that makes the one-time purchase model sustainable.

What we don't know

For honesty: this case study is light on the metrics you'd usually see in a vendor case study. We don't have Cédric's pre- vs post- migration conversion numbers, his query volume, or his AOV. He's a customer, not a co-marketer. What we have is the purchase, the candid feedback, and the public testimonial — and that's enough to share without inventing data we don't have.

If you're in Cédric's shoes

Specifically: PrestaShop store between 1k and 50k SKUs, currently paying for Doofinder / Searchspring / Algolia, and you'd rather not renew that bill — read the search plugin comparison post. The 3-year TCO math is the part that matters.

Then see NP Search for the product page.