By API: you index your catalog (one call), you wire up search (one call), it's live. No plugin to install, no rebuild, no dependency on your CMS. The quickstart guide fits in 3 calls. Integration guides with real code are available for Shopify, PrestaShop, WooCommerce, and Magento.
A 14-day free trial (up to 2,000 requests and 2,000 products) to test with no credit card, then plans starting at €19/month. Counting rules are public and your usage is viewable in real time — no surprise at the end of the month. Full plan details are here.
Generalist engines compare characters; Heurix reads the structure of your references through its annotation cascade. If your catalog is technical (dimensions, standards, sizes, vintages, editions), that's precisely the case Heurix is built for — with rule packs provided per industry, sorting that respects stock, and explainable results. For a blog or a simple editorial site, a generalist engine is more than enough.
No. Heurix plugs into your existing site by API, whatever your CMS — Shopify, PrestaShop, WooCommerce, Magento, or a custom build. Your catalog stays with you; the engine only replaces search.
The matched field on every result explains why it came up, and the ROI simulator gives you an order of magnitude for the economic lever based on your traffic and average order value. The most reliable method remains a before/after test on your zero-result queries — measurable in your analytics tool within the first week.
Eleven rule packs are provided (hardware, automotive, electrical, plumbing, industry, electronics, fashion, wine, books, finance, sport) and the mechanism applies to any catalog where people search by reference, dimension, or variant — books, wine, spare parts, electronics... If your industry has very specific references, tell us about your catalog: designing a fully custom pack is possible on Scale plans.
The first result shows up in an afternoon. Export your catalog to CSV from your ERP, drop it into the console: separator, encoding, and column matching are detected, and the rule pack for your industry is recommended based on your content. You then test search on your own products.
Going live depends on your platform: 2 to 3 days on PrestaShop, 3 to 4 days on WooCommerce — plugin published on wordpress.org, your theme unchanged. A fully custom on-site replacement takes 2 to 3 weeks.
Your visitors keep a working search. The PrestaShop and WooCommerce modules include an automatic fallback: if Heurix doesn't respond within three seconds, your platform's native search takes back over, then Heurix is retried a minute later — no action needed on your part.
A search-engine outage should never become a storefront outage. That's a design principle, not an option.
In France, with OVH (Gravelines or Strasbourg). Your catalogs never leave the European Union, and the engine itself is designed and built in France. For GDPR requirements, it's the simplest scenario to document with your DPO.
Never an abrupt cutoff: past the quota, requests are still served and counted, and overage is billed only if your plan shows an overage rate on the pricing page. Counting rules are public (1 search = 1 request, indexing never counted) and your usage is viewable in real time via the API.
Yes — every keystroke queries the real Heurix engine through the public demo endpoint (/v1/public-demo/search), on two real catalogs (hardware, fashion): same normalization, same typo tolerance, same annotation cascade, same scoring, same result highlighting as any production integration. The description field is omitted from each response to keep the widget fast on mobile — everything else is the genuine article, not a mock.