Create a scoped purchase session
Define customer, product, offer, timing, and connector context for a specific transaction moment.
Purchase Session Infrastructure
Ocliby launches secure, temporary buying sessions from email, SMS, posts, ads, QR codes, chat, support, and future AI surfaces, so commerce can start where intent appears.
WooCommerce is live today. Shopify, Shoptet, and API/webhook connectors are next.
Email / SMS / ad / QR / chat
intent captured
Server-side validation
opaque exchange
Timed purchase window
active
Commerce connector
native execution
01
WooCommerce connector live
06
High-intent surface types
API
Connector expansion path
Email, ads, SMS, posts, creator links, QR codes, and support threads still mostly push customers back through extra pages. Every extra step gives intent more chances to leak.
Purchase Session Infrastructure
Ocliby creates portable purchase sessions: secure, temporary buying windows that can be launched from any high-intent surface and executed through commerce connectors.
How it works
The surface starts intent. Ocliby governs the session. The commerce connector executes native order and payment behavior where supported.
Define customer, product, offer, timing, and connector context for a specific transaction moment.
Use the secure link in email, SMS, ads, QR codes, chat, support, or future AI surfaces.
When clicked, the session opens a focused buying window and finalizes through the native platform path where supported.
Supported surfaces
Ocliby is not an email-only product. Email is one surface among many.
Use cases
The first commercial wedge is repeat purchase, post-purchase, replenishment, win-back, and VIP campaign intent.
Turn a completed order into a scoped buying window for the next relevant product.
pilot-ready
Bring repeat customers back with a faster path to products they already know.
pilot-ready
Launch time-limited purchase windows for lapsed customers and high-value segments.
near-term
Turn launches, drops, and VIP offers into direct transaction entry points.
near-term
Trust model
Sensitive purchase state does not need to live in the browser. Session timing, claims, offer logic, and journey state are governed server-side.
Links do not need to expose full purchase state directly in the browser.
Purchase sessions are validated through backend-controlled claim and exchange logic.
Sessions can expire automatically based on strict server-enforced timing.
Your commerce platform still handles native order and payment behavior where supported.
Connector proof
We are starting where the proof is strongest: real WooCommerce stores, real retention flows, real post-purchase and repeat-purchase use cases.
Pilot Program Active
The current connector supports the product thesis through a real ecommerce platform: post-purchase offers, secure links, timed sessions, and platform-native execution.
Live today as the first working connector for post-purchase, repeat purchase, and campaign sessions.
Planned next connector for merchants already using accelerated checkout and lifecycle campaigns.
Regional connector candidate for Central European ecommerce operators and agencies.
Connector model for custom stores, headless stacks, and future intent surfaces.
Comparison
Ocliby is a session layer for distributed ecommerce intent.
FAQ
A purchase session is a secure, temporary buying window launched from a high-intent surface such as email, SMS, an ad, a QR code, chat, support, or a future AI agent.
No. Payment links usually open a hosted payment page. Ocliby is designed to orchestrate scoped, stateful purchase sessions with rules, timing, personalization, and connector-based execution.
No. Email is an important surface, but Ocliby is built for any place a secure purchase link can live.
No. Ocliby creates a transaction entry point outside the storefront. Your commerce connector still handles native order and payment behavior where supported.
Purchase Session Infrastructure
Request pilot access to see how purchase sessions can work on your store, channels, and connector roadmap.