NP Search-first pilot for 10 PrestaShop stores
We are selecting ten stores for a measured, manually supported rollout. NP Search is the recommended first step: establish search quality and real order-line participation, then add Sentinel only when the payment stack is a safe fit for observation.
A good pilot fit
- PrestaShop 8.0.5–9.1.4, with the exact PHP version, theme, and payment modules disclosed during intake.
- A staging clone or an agreed low-risk installation window, plus a current database and file backup.
- Enough real search and order activity to establish a useful 14-day baseline; low-volume stores can use a longer observation window.
What the pilot includes
- A reversible NP Search staging install, package checksum, compatibility review, and defined rollback path.
- A measured search report covering submitted queries, zero-result rate, result CTR, add-to-cart participation, and real search-attributed order lines.
- An optional Sentinel fit review only after search is stable, limited to a disclosed staging payment path. Applying does not create a purchase or subscription.
Safety and evidence boundary
Search-attributed revenue proves search participation, not causal uplift. Sentinel observes and diagnoses; it does not block checkout, change payment requests, alter order state, disable a gateway, or repair a payment flow. Each named gateway still needs store-specific verification.
Read the public compatibility report →Apply for the NP Search-first pilot
Include the store URL, exact PrestaShop and PHP versions, theme, current search service, catalogue languages, approximate monthly orders, and staging availability. Payment-module details are optional until Sentinel is being reviewed.