Connect
Verify up to two Resend sending domains per store.
WooCommerce command center
Know what your store needs next.
Connect the store, understand the evidence, approve the action, and measure what happened—without losing control of cost or delivery.
WooCommerce only in this release. No campaign is sent automatically.
Commerce evidence
The answer starts with the ledger.
Revenue
Paid-order ledger
Orders
Status-aware totals
Customers
RFM and retention
Freshness
Visible on every answer
Revenue, orders, customers, inventory, and RFM stay deterministic and traceable. AI can explain the evidence; it does not invent it.
How it works
A continuous path from store evidence to measured action.
The system does not jump from a prompt to a live change. It builds durable state at every boundary.
01
Connect
Verify WooCommerce credentials, encrypt them, and keep every query scoped to the active store.
02
Sync
Durable jobs ingest products, orders, and customers while Redis coordinates locks, progress, and recovery.
03
Understand
Deterministic analytics produce KPIs, comparisons, RFM, data quality, and forecast scenarios.
04
Contextualize
Brand profile, published knowledge, confirmed facts, and conversation history explain what the numbers mean for this store.
05
Decide
Ask Store and opportunities show evidence, confidence, freshness, and a concrete next step.
06
Act safely
Approve the exact SEO revision or campaign content, audience, and sender before provider work begins.
07
Measure
Provider and store events update outcomes, suppression, action history, and future recommendations.
Campaign operations
The send is a sequence, not a shortcut.
Domain, sender, audience, approval, provider draft, and launch remain separate durable decisions.
Identify
Create up to five sender aliases on each verified domain.
Target
Choose all eligible subscribers, an RFM segment, or a saved rule group.
Approve
Lock the exact content revision and freeze the eligible recipients.
Draft
Create a provider draft without sending anything.
Launch
Confirm the frozen count, then explicitly begin delivery.
Trust & control
Useful automation needs visible boundaries.
Evidence, permissions, provider work, and cost remain inspectable at every stage.
Cost boundary
Small-model routing, durable spend ledger, per-operation estimates, bounded SEO batches, and no paid calls during ordinary test runs.
Store isolation
Every source, memory, conversation, recommendation, audience, sender, and campaign is scoped to the active organization and store.
Human approval
SEO pushes and campaign sends require explicit review. Content edits invalidate old approvals.
Operational history
Accepted, dismissed, launched, failed, and measured are distinct durable states—not a single vague activity feed.
Contact protection
Customer addresses live in an encrypted operational vault, stay masked by default, and are never supplied to OpenAI.
Provider evidence
Resend webhooks are signature-verified and deduplicated. Unsupported inbox/spam placement is never fabricated.