A small team building inspectable commerce modules.

Every plugin is built and supported by the maker. We follow a tight loop: ship a focused build, validate it on the supported platform matrix, publish the exact evidence, submit it through the appropriate sales channel, and iterate from consented merchant feedback.

Our /ops backend watches PrestaShop, WordPress, and WooCommerce upstream releases every 6 hours and records what changed. Detection is automatic; certification is not. A compatibility row is marked verified only after the relevant install, back-office, storefront and scenario checks pass with retained evidence.

We price by product shape instead of forcing every extension into the same model. A self-hosted module does not need a recurring access fee just to keep running. Hosted infrastructure and continuous compatibility work are different, and we price them explicitly.

Our current one-time modules range from €49–€199. Each product page states exactly which updates are included and whether an optional renewal is available. WooCommerce products with ongoing compatibility coverage use annual licensing from €49–€99; the product page is always the source of truth.

If you stop renewing a one-time license, the delivered version keeps working. A subscription remains active through its paid term. There is no hidden plan upgrade between the price card and checkout.

Operationally, the most fragile thing about owning a PrestaShop or WooCommerce module is keeping it compatible with each upstream core release. PS ships minor / patch versions every 2–3 months; WP + WC ship multiple core releases per year. Each one can break a hook, a controller signature, a template syntax.

Our compatibility matrix watcher polls upstream GitHub releases and the wp.org core version-check API every 6 hours. A detected release enters the validation queue; it stays unverified until the relevant test matrix has passed. We publish the tested build, platform, PHP, theme and scenario scope.

There is no automatic 24-hour certification promise. A release can remain unverified when the evidence is incomplete, and the public matrix must say so.

Three connected areas, with live products and pilots labelled separately:

• Product discovery and catalogue health — on-site search, technical SEO operations and product-feed diagnostics. The product pages separate local evidence from outcomes controlled by search engines, ad platforms or third parties.
• Conversion and checkout operations — promotions, bundles, shipping thresholds, cart recovery and observe-only checkout monitoring. Every workflow exposes its write boundary, guardrails and failure states before purchase or pilot intake.
• Retention and access safeguards — loyalty operations and bounded age self-declaration. The buyer labs surface economic assumptions, stored evidence and limits so a merchant can reject a poor fit before installation.

We don't have a strategy for "everything else." If you need fraud detection, payment processing, or transactional email, buy the SaaS — that's the right shape of tool for those categories.

neuroplugin is operated by YCY Consulting and Investment SL (NIF B22450688), a Spanish limited company based in Madrid. Sales are invoiced with the applicable EU VAT handling. A DPA is available on request for B2B buyers in regulated verticals.

We publish a merchant quote or case study only after we retain written permission and the source records behind every factual claim. Until then, public proof is limited to the compatibility evidence and clearly labelled pilot results. The first ten-store checkout pilot is accepting applications; no merchant outcome or revenue claim is published before it is measured and approved.