LAUNCH QA · TRANSACTIONAL EMAIL
The email should match what really happened—and only send when it should.
This center validates ClaraWide’s existing email catalog and browser-local queue behavior without pretending a preview queue proves real inbox delivery. It separates what we can test today from provider, DNS, webhook, retry and mailbox evidence that only exists in production.
AUTOMATED CATALOG AUDIT
Every defined template should render usable content
Checks labels, groups, summaries, subjects and bodies across the current catalog with representative QA data.
PROTOTYPE BEHAVIOR SUITE
Preference + duplicate logic without polluting your queue
The suite temporarily exercises browser-local email behavior, then restores the exact queue and preferences that were there before it ran.
TEST NOW
Open Email Operations →Email behavior you can actually inspect in clarawidetest
Only mark Pass after you performed the stated check. Clear / Not Checked is available if you click the wrong result.
PRODUCTION LATER
Delivery controls the static test site cannot prove
Leave these blank until ClaraWide is connected to a real transactional-email provider and the named behavior has genuinely been tested.
Prototype-suite history
Record a delivery/content defect
OPEN FINDINGS
Email launch blockers & defects
Critical and High open findings also surface in Admin Operations.
EVIDENCE BACKUP
Export or reset this QA layer
The export includes the catalog audit, manual checks, production-later checks, automated suite runs, issues and a summary of the current browser-local email queue.
NEXT LAUNCH LAYER
Open Recovery Center →Backup, restore & rollback evidence
Email evidence now has a dedicated gate. The next critical launch layer is proving that ClaraWide data and deployments can be recovered safely when something breaks.