One script on the site you already have
The Dual-Action UI ships as a plug-in. It works with your catalog, your search stack and your styling — and it does not ask you to change any of them.
What it takes to run it
Most retail technology asks you to migrate something. This does not. LiveSearch attaches to controls that already exist on your pages and reads the catalog you already publish.
Add the script
One tag on your product and results pages, plus a single line of configuration.
Connect the catalog
So the options mean something — a feed, an API, or whatever you already expose to your search provider.
Style it as your own
The menu inherits your storefront's look. To a shopper it reads as part of your site, because it is.
- Never an empty result set. An option is only offered if it leads somewhere.
- Built from the item in view. Options are generated for the exact product being rejected.
- Nothing is taken away. The ordinary behavior of every control is preserved.
What sits behind the script tag
Six pieces. Only the first one runs on your site; the rest are ours to operate.
LiveSearch plug-in
The browser-side script. Attaches to the controls you already have, renders the options, and hands each choice back. This is the only piece that touches your site.
Menu, Signals and Config APIs
A multi-tenant web service. The plug-in asks it what options to show, reports what was chosen, and picks up per-retailer configuration.
AI engine
Generates candidate options from the item being viewed, then ranks and personalizes them. It gets sharper as signal accumulates.
Signal store
Every choice, stored as a labeled first-party record against the item, the reason and the outcome — yours, exportable, and not shared with anyone.
Catalog sync
Reads your product data so the options mean something. Runs once to get started, then keeps pace as the catalog changes.
Admin portal and dashboard
Where your team tunes what the menus offer and reads what shoppers have been saying.
The report nobody else can produce
Analytics tells you where shoppers dropped off. Session replay shows you what they did. Neither tells you what they wanted. Because LiveSearch collects the reason directly, the retailer-side view is a straight readout rather than an inference.
The same feed exports into whatever you already run — personalization, merchandising, remarketing, or your own models.
Why shoppers leave
Reasons ranked by frequency, so you can see what is actually costing you conversions.
Which products get rejected
The items shoppers open and abandon most, and the reason attached to each.
How price-sensitive they are
Where in your catalog "too expensive" appears, and at what price points.
Three ways to put it to work
One technology, matched to how each kind of customer buys.
SaaS subscription
A sales-optimization plug-in distributed through no-code platforms and their app marketplaces. Tiered subscription, priced by catalog size and traffic.
Enterprise license
The same plug-in deployed directly — or the underlying IP licensed to teams who prefer to build their own implementation. Annual fee scaled to GMV and traffic.
IP licensing and royalties
License the patent portfolio and embed Dual-Action UIs directly into the products you already sell to retailers.
Tell us where it would fit
Retailer, platform, or software company — the shape of the conversation changes, but the starting point is the same.