KnobaseHOW IT WORKS
How products become labeled offers in AI services.
AI services request a contextual offer after they answer. Merchants approve catalog products so those products can become offer candidates. Campaigns stay optional.
An app sends a contextual request. Policy decides offer or no-fill. The offer is rendered in a separate labeled UI. Merchants approve collections instead of creating one campaign per product.
For AI services
App → contextual request → policy → Offer or no-fill → separate UI → verified event. Knobase does not rewrite the organic answer. No-fill, policy block, error, and timeout fail open.
For Shopify merchants
Shopify catalog → collection approval → eligible products → contextual Offer. Default recommendation uses approved products. Campaigns add event, discount, or timing rules.
Why Product and Campaign are distinct
A Product keeps source facts and external IDs. A Campaign is commercial policy. Mixing them makes review harder and creates stale claims.
How trust and disclosure work
The offer object includes disclosure. Publishers control placement and frequency. Product facts and campaign claims should stay reviewable.