WooCommerce shows what customers did. ASI decides what the business is allowed to do next.
Advanced Subscriber Intelligence connects WooCommerce purchase evidence to ASI Core so operators can build smarter audiences from real customer behaviour without turning the shop into a hidden send engine.
Orders, products, categories, refunds, coupons, repeat buying, customer value, and purchase timing can become useful evidence. Identity, marketing consent, suppression, validation, jurisdiction, bounce state, campaign eligibility, Preflight, Queue Safety, and sending remain owned by ASI Core.
Buying something is not the same as asking to be marketed to. WooCommerce contributes evidence. ASI applies the protection rails. The operator approves the action.
Buyer Evidence, Not Permission
ASI Core Owns Truth
Operator-Reviewed Sending
The store supplies evidence. The store does not own subscriber truth.
WooCommerce may contain useful customer records and buying behaviour, but ASI Core remains authoritative for identity, consent, suppression, validation, eligibility, audiences, campaigns, sending, reporting, and evidence.
Why WooCommerce needs a protected evidence lane
Commerce systems are rich in useful behaviour and equally rich in awkward data.
Useful buying evidence
Products, categories, spend, refunds, coupons, purchase dates, and repeat orders can support far better audience planning than generic list membership.
Messy identity
Guest orders, duplicate customers, shared email addresses, plus-addressing, old accounts, and conflicting customer fields are normal WooCommerce conditions.
Conflicting permission
One record may show marketing consent while another record using the same address does not. An unsubscribe may sit elsewhere. Core must resolve the conflict.
Dangerous automation temptation
A purchase event can make it tempting to send immediately. ASI prevents commerce activity from becoming an unreviewed marketing trigger.
WooCommerce is the deliberate direct-module exception.
WooCommerce keeps its existing protected direct connection to ASI Core. Other external systems use the canonical ASI API.
→
Protected Woo Pipe
→
ASI Core
→
Operator Review
→
Protected Send Workflow
Module control remains available
The WooCommerce module retains its individual enabled-or-disabled control. Disabling the module stops the evidence route without changing Core truth.
No independent Woo database truth
The module does not maintain an authoritative subscriber, consent, suppression, audience, campaign, or sending state outside ASI Core.
No direct list mutation
WooCommerce cannot silently add, remove, reactivate, suppress, or reclassify subscribers in protected ASI audiences.
No direct send trigger
Store activity cannot bypass Draft Content Review, Preflight, Queue Safety, provider pacing, operator permissions, or ASI queue creation.
Commerce evidence with its source still attached.
ASI can use the evidence WooCommerce genuinely holds while keeping the origin and limits of that evidence visible.
Orders and order dates
Completed, processing, cancelled, refunded, failed, or other order states can contribute to customer and purchase-history evidence.
Products and categories
Specific products, product families, categories, variations, quantities, and purchase combinations can support reviewed audience definitions.
Spend and customer value
Order value, lifetime spend, average order value, repeat purchasing, and higher-value categories can add useful commercial context.
Refunds and cancellations
Refunds, charge concerns, cancellations, and returned products may indicate that a cheerful promotional follow-up would be badly timed.
Coupons and promotions
Coupon use, offer response, discount dependency, and promotional purchase patterns can contribute to audience planning without becoming permission.
Customer and guest records
Registered customers and guest orders can contribute identity evidence, but neither record type is automatically treated as marketing consent.
Address and country evidence
Billing, shipping, declared country, missing country, and inconsistent address data can inform jurisdiction review without bypassing Stage 8 confirmation.
Marketing-consent evidence
Explicit consent, explicit no-consent, missing consent, timestamps, source fields, and conflicting legacy hints can be passed to Core for protected resolution.
The difficult part is not reading the order. It is understanding the customer safely.
WooCommerce databases often contain several records that appear to describe the same person, with different permission, address, order, and account evidence.
Duplicate email identities
Two customer records may use the same email while holding different names, addresses, orders, or consent claims.
Conflicting consent
One record may show consent and another may not. A later unsubscribe or complaint must outrank the convenient record.
Odd addresses and countries
Missing countries, invalid-looking postal data, temporary addresses, and conflicting billing and shipping evidence require review rather than guesswork.
Role and shared accounts
Accounts such as sales, orders, info, office, or shared family addresses may behave differently from an individually controlled mailbox.
Guest and historic orders
Old guest purchases and stale customer records may still be commercially interesting while lacking current permission, validation, or eligibility.
Refunded or dissatisfied customers
A customer with purchase history may also have a refund, complaint, support issue, or suppression record that changes the appropriate next action.
A customer record is not automatic marketing permission.
ASI distinguishes commerce evidence from marketing eligibility. A valid order, account, payment, or email address cannot silently create consent that the customer never gave.
Explicit consent
Clear marketing consent with usable source and timestamp evidence can support eligibility, subject to all other ASI checks.
Explicit no-consent
A clear no-consent record is not overridden because the customer bought recently, spent more money, or appears commercially attractive.
Unknown or missing consent
Blank, missing, ambiguous, or inherited hints remain uncertainty. ASI does not promote unknown consent into a confident Yes.
Suppression always outranks
Unsubscribe, complaint, abuse, block, bounce, or protected hold evidence remains above current purchase activity.
Audience ideas can begin in WooCommerce. Sendable audiences are created by ASI Core.
An operator can define the commercial question using Woo evidence. Core then resolves the identities and applies the protected eligibility rails before the audience becomes usable.
Define the buyer pattern
Choose products, categories, dates, spend, order states, repeat behaviour, exclusions, or another bounded commercial question.
Build the evidence set
WooCommerce returns the matching customer and order evidence with source context. It does not mark the recipients sendable.
Apply ASI Core truth
Identity, consent, suppression, validation, jurisdiction, bounce state, eligibility, duplicates, and current list health are resolved.
Create the protected audience
Eligible recipients enter the appropriate protected audience while held, quarantined, rejected, or suppressed records remain excluded with reasons.
Commercially useful questions, filtered through protected eligibility.
These examples describe the buyer evidence used to propose an audience. They do not bypass consent, suppression, validation, jurisdiction, or Preflight.
Specific product buyers
Customers who bought pink hair bands in the last six months, a named product, or a defined product family.
Product A but not Product B
Buyers of one product who have not purchased a companion, refill, accessory, upgrade, or follow-on product.
Lapsed repeat buyers
Customers with previous repeat buying who have not ordered inside the chosen reactivation period.
High-value category buyers
Customers whose verified orders and spend indicate meaningful value in a selected category or product line.
Coupon-led buyers
Customers whose order history shows a particular promotion, coupon, or offer pattern that may affect future campaign planning.
Protected exclusions
Customers matching the commercial pattern but excluded because marketing consent, suppression, validation, jurisdiction, bounce, or current eligibility does not support sending.
The shop dashboard can choose the campaign. ASI Core owns the campaign.
The Woo surface can display the ASI Core template library so an operator can choose an approved campaign without moving template truth into WooCommerce.
Choose an ASI template
Display approved ASI templates, campaign names, permitted fields, current version, and available sender options.
Preview and adjust permitted fields
Allow the operator to preview the campaign and change only the fields Core permits without creating a separate Woo-owned HTML version.
Run Review and Preflight
Draft Content Review, sender identity, audience eligibility, Preflight, Queue Safety, and operator permissions remain ASI-owned checks.
Preserve the exact version sent
ASI records the final template, subject, preview text, HTML, audience, sender, review result, approver, request source, and sent version.
Woo evidence can refine the audience. It cannot lower the send standard.
Every Woo-originated campaign still moves through the same protected ASI rails as a campaign created directly through the ASI interface.
Draft Content Review
Subject, content, accessibility, duplication, preview text, and other advisory evidence remains visible before sending.
Preflight
The chosen audience is checked against current suppression, validation, consent, bounce, hold, provider, and campaign evidence.
Queue Safety
Live bounce, complaint, provider, queue, and campaign evidence can hold or stop movement after the send begins.
Provider-aware sending
Google MX and other provider lanes retain their pacing, warm-up, hold, rejection, and recovery rules.
Commerce context can meet campaign evidence without becoming a separate report truth.
WooCommerce can display bounded ASI campaign results and evidence returned by Core. Reports Builder remains authoritative.
Campaign status
Created, reviewed, held, queued, sending, completed, stopped, or rejected state can be returned with the permitted operational context.
Audience outcomes
Eligible, excluded, suppressed, held, invalid, unknown-consent, jurisdiction, and other bounded audience outcomes can be displayed.
Campaign evidence
Attempts, accepted transport evidence, delivered estimates, bounces, unsubscribes, complaints, clicks, and provider behaviour can be returned from Reports Builder.
Human-confidence evidence
Woo surfaces may display ASI’s 0% to 92% confidence results and reason context without recalculating click meaning independently.
Connected commerce does not outrank the Core.
These boundaries keep the module useful without turning it into a quieter, less protected version of ASI.
No consent creation from purchase
An order, account, payment, coupon, or repeat purchase cannot silently become marketing permission.
No suppression override
A commercially valuable customer remains excluded when unsubscribe, complaint, abuse, bounce, block, or other protected suppression applies.
No direct campaign truth
Templates, campaign versions, audiences, approvals, sent content, queue state, and reporting evidence remain owned by ASI Core.
No automatic send on store event
An abandoned basket, completed order, refund, new account, product purchase, or customer change cannot wake ASI sending by itself.
Smarter commerce audiences.
Woo evidence helps operators answer better commercial questions while ASI resolves the identities, exclusions, consent, eligibility, campaigns, sending, and reporting underneath.
A permission shortcut.
The module does not convert customers into automatic subscribers, restore suppressed recipients, create lawful purpose, guarantee deliverability, or replace operator judgement.
Explore the surrounding ASI rails
Continue into ASI Integrations, Subscriber Validation Pipeline, Email Compliance, Sending Engine & Queue Control, Campaign Reports & Insights, and Bot Clicks vs Human Click Detection.
Use WooCommerce evidence without handing WooCommerce the keys.
Talk to ASI about connecting customer and order evidence, resolving consent and identity conflicts, building protected commerce audiences, selecting ASI-owned campaigns from the store workflow, and returning reporting evidence without creating a second truth engine.