Core capabilityStore connectionConnect an ecommerce store through a documented integration or data interface. 4 points maximum | Supported4 / 4 pts Customer behavior and commerce data drive connected channels. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityProduct and order dataUse store products, purchases or orders in marketing. 4 points maximum | Supported4 / 4 pts Customer behavior and commerce data drive connected channels. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkOrder changes after purchaseIngest a later order state such as refund, cancellation, or fulfillment for marketing use. 5.6 points maximumAsk for a demonstrationUpdate an existing test order after purchase and show the resulting event or customer state. A scenario to run with the supplier; not a completed product test. | Not verified0β5.6 / 5.6 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Depth checkProduct-level targetingUse catalog identifiers or product/category purchase history in audience or message logic. 6.4 points maximumAsk for a demonstrationBuild a product- or category-specific customer selection and show the underlying order data. A scenario to run with the supplier; not a completed product test. | Not verified0β6.4 / 6.4 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Core capabilityAbandoned-cart recoveryTrigger follow-up when a shopper abandons a cart or checkout. 4 points maximum | Supported4 / 4 pts Flows API manages event-driven email/SMS and abandonment flows. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityPost-purchase or retention flowsAutomate follow-up after purchase or at a customer lifecycle stage. 4 points maximum | Supported4 / 4 pts Order-triggered flows include thanks, upsell and review requests. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkStop recovery after conversionRecheck an abandoned-cart customerβs purchase status before a later recovery message. 5.6 points maximumAsk for a demonstrationComplete a test purchase during the recovery delay and show the next reminder being avoided. A scenario to run with the supplier; not a completed product test. | Supported5.6 / 5.6 pts Cart flows recheck purchase filters before subsequent messages. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkLifecycle experimentsCompare alternative lifecycle-message paths or content using a controlled recipient split. 6.4 points maximumAsk for a demonstrationCreate two recovery or retention variants and show separate outcome reporting. A scenario to run with the supplier; not a completed product test. | Supported6.4 / 6.4 pts Random flow splits compare message variants and paths. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityCommerce email campaignsSend store-related email campaigns or journeys. 3.2 points maximum | Supported3.2 / 3.2 pts Customer behavior and commerce data drive connected channels. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilitySMS, push or messaging engagementReach customers through an additional direct messaging channel. 3.2 points maximum | Supported3.2 / 3.2 pts Customer behavior and commerce data drive connected channels. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkChannel-specific consent pathsSelect messaging paths according to the customerβs channel-specific subscription or eligibility. 4.8 points maximumAsk for a demonstrationShow an email-only shopper and an SMS-subscribed shopper taking appropriate paths. A scenario to run with the supplier; not a completed product test. | Not verified0β4.8 / 4.8 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Depth checkCross-channel frequency coordinationApply contact-pressure limits across at least two channels in commerce journeys. 4.8 points maximumAsk for a demonstrationDemonstrate how a recent message in one channel changes a later message in another. A scenario to run with the supplier; not a completed product test. | Not verified0β4.8 / 4.8 pts Smart Sending is channel-specific; the reviewed evidence does not establish a shared configured rule across channels. Not verified Β· Oct 15, 2026Source β |
|---|
Core capabilityRevenue or conversion reportsRelate messaging activity to recorded orders, revenue or conversions. 2.4 points maximum | Supported2.4 / 2.4 pts Campaign/flow reporting includes conversions and CSV exports. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityReporting export or data APIRetrieve marketing results for analysis outside the reporting screen. 2.4 points maximum | Supported2.4 / 2.4 pts Campaign/flow reporting includes conversions and CSV exports. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkAttribution-rule controlInspect and adjust the rule or time window assigning store conversions to marketing. 3.2 points maximumAsk for a demonstrationChange a lookback or qualifying interaction and explain the attribution impact. A scenario to run with the supplier; not a completed product test. | Supported3.2 / 3.2 pts Configurable channel windows and qualifying interactions determine conversion attribution. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkPortable campaign revenue dataExport or query campaign- or message-linked revenue for external analysis. 4 points maximumAsk for a demonstrationRetrieve campaign revenue with campaign identifiers in an export or API response. A scenario to run with the supplier; not a completed product test. | Supported4 / 4 pts Campaign/flow reports export engagement and revenue by campaign. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityAI marketing contentGenerate commerce campaign text or creative material with AI. 2.4 points maximum | Supported2.4 / 2.4 pts Composer creates campaigns; task credits apply. Official documentation Β· Oct 15, 2026Source β |
|---|
Core capabilityAI personalization or analyticsUse commerce or engagement data for AI targeting, recommendations or analysis. 2.4 points maximum | Supported2.4 / 2.4 pts Composer audits campaigns and segments; task credits apply. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkAI using real commerce dataUse catalog, purchase, or customer activity data for AI recommendations, analysis, or personalization. 3.2 points maximumAsk for a demonstrationAsk AI about a real product or customer cohort and inspect which store data informs the answer. A scenario to run with the supplier; not a completed product test. | Not verified0β3.2 / 3.2 pts This specific workflow has not been established by the reviewed evidence. Not verified Β· Oct 15, 2026Source β |
|---|
Depth checkReview AI commerce changes before releaseReview or explicitly approve AI-generated campaign or workflow changes before publication. 4 points maximumAsk for a demonstrationAsk AI to create a commerce campaign and show the boundary before it goes live. A scenario to run with the supplier; not a completed product test. | Supported4 / 4 pts Composer audit is advisory: changes must be reviewed and applied by the marketer. Official documentation Β· Oct 15, 2026Source β |
|---|
Depth checkPredict the customer's next order dateDemonstrate "Predict the customer's next order date" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Predict the customer's next order date" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Klaviyo estimates next order date from individual and aggregate customer purchase patterns. Predictive features require qualifying purchase history and data volume; predictive values are estimates. Historic CLV is not predictive. Official documentation Β· Oct 21, 2026Source β |
|---|
Depth checkEstimate customer churn probabilityDemonstrate "Estimate customer churn probability" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Estimate customer churn probability" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Klaviyo estimates churn probability from order count, frequency and elapsed time. Predictive features require qualifying purchase history and data volume; predictive values are estimates. Historic CLV is not predictive. Official documentation Β· Oct 21, 2026Source β |
|---|
Depth checkExclude out-of-stock products from recommendationsDemonstrate "Exclude out-of-stock products from recommendations" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Exclude out-of-stock products from recommendations" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkSet expiry rules for individual promotional codesDemonstrate "Set expiry rules for individual promotional codes" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Set expiry rules for individual promotional codes" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkTrigger flows from subscription renewal or cancellationDemonstrate "Trigger flows from subscription renewal or cancellation" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Trigger flows from subscription renewal or cancellation" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkKeep customer data from different stores separateDemonstrate "Keep customer data from different stores separate" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Keep customer data from different stores separate" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|
Depth checkDeduct refunds in historical customer valueUse a test customer with an order and partial refund. Show how historical value changes and identify excluded fees or taxes. 2.5 points maximumAsk for a demonstrationUse a test customer with an order and partial refund. Show how historical value changes and identify excluded fees or taxes. A scenario to run with the supplier; not a completed product test. | Supported2.5 / 2.5 pts Historic CLV includes previous orders net of refunds and returns. Predictive features require qualifying purchase history and data volume; predictive values are estimates. Historic CLV is not predictive. Official documentation Β· Oct 21, 2026Source β |
|---|
Depth checkTarget events using product variant identifiersDemonstrate "Target events using product variant identifiers" with test data. Show the result, an exception case, and the required plan. 2.5 points maximumAsk for a demonstrationDemonstrate "Target events using product variant identifiers" with test data. Show the result, an exception case, and the required plan. A scenario to run with the supplier; not a completed product test. | Not verified0β2.5 / 2.5 pts This specific check has not been verified. Missing evidence does not mean the capability is absent. Ask for a demonstration in the proposed plan. Not verified Β· Oct 21, 2026Source β |
|---|