Shopify email apps
Best Shopify Email Apps for Agency-Managed Stores in 2026
An agency’s email platform must be repeatable without becoming generic. Permissions, naming conventions, QA, reporting, and client ownership matter as much as the number of automations a tool can create.
We prioritize reusable operating patterns, account separation, review workflows, and defensible reporting. Confirm current pricing, seats, and client-account terms from official sources before standardizing a stack.
Shortlist for agencies
| App | Best fit | First workflow | Tradeoff |
|---|---|---|---|
| Sequenzy | Small agencies standardizing email sequences | Client onboarding sequence | May lack enterprise agency controls |
| Klaviyo | Agencies managing complex lifecycle programs | Reusable lifecycle framework | Governance and account costs need careful control |
| Omnisend | Retail agencies launching email and SMS quickly | Retail campaign template | Client-specific edge cases need documentation |
| Brevo | Agencies supporting marketing and transactional email | Standard transactional handoff | More manual ecommerce modeling |
| Drip | DTC agencies reporting on repeat purchase | Retention reporting playbook | Less suitable for non-commerce clients |
| Shopify Email | Agencies handling simple native campaigns | Retention reporting playbook | Limited account and branch governance |
| Mailchimp | Agencies delivering newsletter programs across clients | Retention reporting playbook | Client-level automation depth varies |
| ActiveCampaign | Agencies joining marketing to CRM and sales workflows | Retention reporting playbook | More training and maintenance |
| Sendlane | DTC agencies scaling commerce lifecycle delivery | Retention reporting playbook | Review agency access and support terms |
| Customer.io | Agencies supporting event-rich product clients | Retention reporting playbook | Requires strong reusable event contracts |
| Privy | Agencies testing capture and campaign acquisition | Retention reporting playbook | Not a complete lifecycle delivery platform |
| Postmark | Agencies separating transactional infrastructure | Retention reporting playbook | Not a promotional campaign suite |
| Resend | Technical agencies building custom client systems | Retention reporting playbook | Engineering owns permissions and operations |
Sequenzy for agency-managed stores
Best for: Small agencies standardizing email sequences. Sequenzy is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Focused workflows and low operational overhead. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Focused workflows and low operational overhead; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | May lack enterprise agency controls; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Klaviyo for agency-managed stores
Best for: Agencies managing complex lifecycle programs. Klaviyo is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Deep events, segments, and reusable flow logic. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Deep events, segments, and reusable flow logic; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Governance and account costs need careful control; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Omnisend for agency-managed stores
Best for: Retail agencies launching email and SMS quickly. Omnisend is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Accessible multichannel automation. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Accessible multichannel automation; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Client-specific edge cases need documentation; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Brevo for agency-managed stores
Best for: Agencies supporting marketing and transactional email. Brevo is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Broad channel coverage and contact options. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Broad channel coverage and contact options; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | More manual ecommerce modeling; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Drip for agency-managed stores
Best for: DTC agencies reporting on repeat purchase. Drip is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Commerce automation and revenue context. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Commerce automation and revenue context; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Less suitable for non-commerce clients; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Shopify Email for agency-managed stores
Best for: Agencies handling simple native campaigns. Shopify Email is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Fast catalog and customer setup. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Fast catalog and customer setup; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Limited account and branch governance; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Mailchimp for agency-managed stores
Best for: Agencies delivering newsletter programs across clients. Mailchimp is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Familiar templates, audiences, and campaign workflow. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Familiar templates, audiences, and campaign workflow; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Client-level automation depth varies; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
ActiveCampaign for agency-managed stores
Best for: Agencies joining marketing to CRM and sales workflows. ActiveCampaign is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Flexible automation and account context. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Flexible automation and account context; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | More training and maintenance; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Sendlane for agency-managed stores
Best for: DTC agencies scaling commerce lifecycle delivery. Sendlane is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Behavioral automation and reporting. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Behavioral automation and reporting; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Review agency access and support terms; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Customer.io for agency-managed stores
Best for: Agencies supporting event-rich product clients. Customer.io is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Flexible event-triggered orchestration. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Flexible event-triggered orchestration; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Requires strong reusable event contracts; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Privy for agency-managed stores
Best for: Agencies testing capture and campaign acquisition. Privy is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Forms, popups, and lightweight workflows. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Forms, popups, and lightweight workflows; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Not a complete lifecycle delivery platform; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Postmark for agency-managed stores
Best for: Agencies separating transactional infrastructure. Postmark is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: Reliable streams and delivery visibility. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | Reliable streams and delivery visibility; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Not a promotional campaign suite; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Resend for agency-managed stores
Best for: Technical agencies building custom client systems. Resend is valuable when the agency can keep client data, approvals, access, and reporting distinct. A reusable framework should define what changes by client—catalog, audience, consent, offer, and brand voice—rather than copying every trigger unchanged.
Why it stands out: API-first delivery and component control. Start with a documented onboarding, QA checklist, and one reporting template. Evaluate time-to-launch, error rate, client approval cycles, and cohort outcomes instead of presenting an unsupported average revenue claim.
| Pros | API-first delivery and component control; supports repeatable client delivery; can use Shopify signals. |
|---|---|
| Cons | Engineering owns permissions and operations; seats, accounts, and contact volume affect total cost. |
| Pricing context | Verify official pricing for contacts, sends, seats, permissions, and SMS. |
| Source | Official product information |
Decision guide
| Agency priority | Start with | Reason |
|---|---|---|
| Complex lifecycle delivery | Klaviyo | Deep event and segment controls. |
| Lean standardized sequences | Sequenzy | Focused operations can simplify delivery. |
| Commerce retention reporting | Drip | Good fit for DTC client cohorts. |
See the Shopify email overview , alternatives library , and implementation guide .
Consent and purchaser suppression for Agency managed stores
Hold the agency managed stores launch until consent is documented per app and purchase events suppress agency managed stores promos immediately after checkout — both verifiable in an audit. Protect the agency managed stores channel first: post-purchase, refund-window, and support-case promos do more damage than dull agency managed stores copy.
| Audience state | Required handling | Why it matters |
|---|---|---|
| No documented consent | No agency managed stores promos without proof; transactional messages only | Agency Managed Stores consent is the legal basis of every send |
| Consented, never purchased | Agency Managed Stores education and proof before any offer | First-touch agency managed stores codes create discount dependence |
| Active cart, no checkout | Remind agency managed stores carts with context first, no instant code | Protects agency managed stores profit when purchase intent is hottest |
| Purchased recently | Agency Managed Stores buyers get education, not another pitch | Agency Managed Stores suppression protects the new-customer glow |
| Refund or return open | No agency managed stores promos mid-case; resume after resolution | Service-active agency managed stores shoppers reject promos |
| Repeated non-engagement | Agency Managed Stores sunset policy precedes complaint spikes | Shields agency managed stores sender reputation and inboxing |
| SMS consent present | Cap agency managed stores SMS cadence within legal quiet windows | One agency managed stores SMS complaint outweighs many email ones |
| Wholesale or B2B account | Isolate agency managed stores wholesale comms from retail blasts | Agency Managed Stores retail promos can violate B2B terms |
| Free or disposable email domain | Verify agency managed stores throwaway addresses pre-journey | Agency Managed Stores bounces from junk signups hurt inboxing |
| Staff and test accounts | Agency Managed Stores internal accounts never enter production | QA agency managed stores sends distort real performance |
| Competitor or researcher signals | No bespoke agency managed stores track for competitor signals | Agency Managed Stores consistency beats clever carve-outs |
| Legacy list without timestamps | Reconfirm agency managed stores consent where timestamps are missing | Old agency managed stores permission without records is a risk |
Margin, app costs, and pricing for Agency managed stores
Judge agency managed stores on margin, not attribution. A durable agency managed stores program absorbs subscription, overages, SMS, capture, creative, agency, and discount costs and still pays. For agency managed stores, a stack at fifteen percent of attributed margin needs simplification first, optimization second.
Pricing changes frequently and varies by region, contact volume, and contract term, so check the official pricing pages of every shortlisted app and model an eighteen-month total that includes a peak season. Before banking on free for agency managed stores, check which free-tier limit — contacts, sends, branching, support — hits your agency managed stores plan earliest.
| Cost component | What to model | Common failure |
|---|---|---|
| Platform subscription | Tier your agency managed stores plan to contacts you truly hold | Agency Managed Stores tier bought for phantom growth |
| Contact or send overages | Map agency managed stores list growth to tier thresholds | Peak agency managed stores volume blowing past tier limits |
| SMS credits | Agency Managed Stores text volume from real opt-in math | agency managed stores text costs wished into email costs |
| Discount budget | Agency Managed Stores code depth times likely redemption | Agency Managed Stores automation minting discount hunters |
| Creative and ops time | Operator hours the agency managed stores program consumes weekly | agency managed stores maintenance hours wished away |
| Migration and setup | agency managed stores switch priced in imports and rebuild labor | agency managed stores migration shedding consent proof |
| Support and success tiers | Agency Managed Stores severity coverage: paid or included | Agency Managed Stores help-desk limits exposed by drops |
| Third-party integrations | Agency Managed Stores review, loyalty, capture add-ons | agency managed stores side-tools eclipsing core cost |
| Deliverability remediation | agency managed stores inbox-health monitoring and cleanup | Agency Managed Stores inbox harm priced above the plan |
Decision table for Agency managed stores
| Situation | Start with | Reason |
|---|---|---|
| Occasional sends, small catalog | Shopify Email | Zero-learning-curve start for light agency managed stores needs |
| Branching and suppression matter | Klaviyo | Agency Managed Stores branching and suppression depth |
| Small team, email plus light SMS | Omnisend | Small-team agency managed stores workflows across email and SMS |
| Broad newsletter operations | Mailchimp | Agency Managed Stores breadth for newsletter-led operations |
| Lean lifecycle operations | Sequenzy | Pay-per-email agency managed stores operation for selective volume |
| Developer-led custom builds | Customer.io | Developer-grade agency managed stores event triggers |
| CRM-led sales follow-up | ActiveCampaign | Account-linked agency managed stores sequences for B2B motion |
| Simple list growth and popups | Privy | Early agency managed stores momentum through capture widgets |
| Commerce cohort analysis | Drip | Cohort-aware agency managed stores views on second orders |
Common failure modes in agency managed stores email
| Failure | Prevention | Cost of getting it wrong |
|---|---|---|
| Discount in the first touch | Agency Managed Stores incentives only after intent signals | agency managed stores discount-first trains bargain hunting |
| No purchase suppression | Agency Managed Stores exits wired to order and checkout events | agency managed stores promos chasing paid customers grate |
| Consent imported without proof | Map agency managed stores consent timestamps and sources | Agency Managed Stores liability when sources are vague |
| Flows only one operator understands | Agency Managed Stores flows legible to any operator | Agency Managed Stores key-person risk on undocumented flows |
| Measuring clicks only | Score agency managed stores on profit, returns, grievances | Click-only agency managed stores metrics bless aggression |
| Ignoring deliverability signals | Watch agency managed stores bounces and spam signals | Agency Managed Stores neglect compounds into rescue spend |
| Peak-season flow changes | agency managed stores calm-before-peak change moratorium | Peak-week agency managed stores experiments fail loudest |
| SMS without a channel strategy | Give agency managed stores SMS its own job spec apart from email | Agency Managed Stores channel overlap triggers opt-outs |
Implementation order for a agency managed stores program
- Agency Managed Stores first step: consent sources documented and mapped.
- For agency managed stores, test-fire order, cart, refund, and support events first.
- Write agency managed stores suppression and exits before any agency managed stores flow exists.
- Pilot agency managed stores with one bounded journey plus holdout measurement.
- Thirty days into agency managed stores, score margin and audience health.
- For agency managed stores, growth waits for transferable editing.
- Document agency managed stores freeze terms before the season.
- Agency Managed Stores finance: stack cost over margin, quarterly.
- For agency managed stores, dusty journeys get archived quarterly.
Metrics review cadence for agency managed stores
| Metric | Definition | Review cadence |
|---|---|---|
| Margin per send | Net agency managed stores margin post-discounts and delivery cost | Monthly |
| Repeat purchase rate | agency managed stores-driven second purchases per quarter | Monthly |
| Complaint and unsubscribe rate | Agency Managed Stores tracked per campaign and flow | Weekly |
| Suppression accuracy | agency managed stores-buyer samples screened for breaches | Weekly |
| Time to edit safely | Agency Managed Stores edit time for a fresh operator | Quarterly |
| Holdout lift | agency managed stores incrementality from holdout contrast | Quarterly |
Agency managed stores matchup FAQ
Klaviyo or Shopify Email for agency managed stores?
For agency managed stores, Shopify Email covers occasional small-catalog campaigns; Klaviyo earns its keep when agency managed stores demands event branching, catalog-aware blocks, and segment reporting — model profile billing on projected agency managed stores growth first.
Omnisend vs Klaviyo for agency managed stores?
Omnisend gets agency managed stores teams sending sooner with light SMS attached; Klaviyo stretches agency managed stores segmentation further. Test-drive one real agency managed stores flow each way before judging.
Mailchimp or Klaviyo for agency managed stores?
For agency managed stores, Mailchimp trades on familiarity, Klaviyo on Shopify event fidelity; settle agency managed stores pricing by checking both official pages at your contacts.
Do I need a separate SMS tool for agency managed stores?
For early agency managed stores, bundled SMS is enough; specialists earn their agency managed stores fee only via measured lift. Validate agency managed stores opt-ins, quiet hours, and per-message rates beforehand.
How should I suppress audiences in agency managed stores flows?
Guard agency managed stores with exits for buyers, open cases, refunds, and no-consent profiles, auditable per agency managed stores flow. In agency managed stores, a suppression miss hurts worse than a missed blast.
What does agency managed stores email cost?
Costs combine the platform subscription, contact or send overages, SMS credits, template and creative work, and the discount budget your agency managed stores campaigns consume. For agency managed stores budgeting, treat any static quote as stale — check official pricing pages and model an eighteen-month total before committing.
Which app should a lean team pilot first for agency managed stores?
Open agency managed stores with the tool at full command in fourteen days — simple agency managed stores sends natively, branched agency managed stores on a lean platform. Shipping agency managed stores beats architecting it.
How do I measure agency managed stores email results?
Measure agency managed stores on contribution, not vanity sends: margin per send, repeat purchase, unsubscribes, complaints, and support load alongside attributed revenue, with a holdout cohort proving the agency managed stores journeys caused the lift.
Can I run agency managed stores email without an agency?
Yes, if the scope stays small. Pick one agency managed stores journey, document consent and suppression rules, and reuse a simple template system. For agency managed stores, hire help only if journey complexity, inbox-placement remediation, or peak agency managed stores volume genuinely exceeds what the team can run.
When should I graduate from my first app for agency managed stores?
For agency managed stores, the graduation signal is operational: unsafe flow edits, unreliable purchase-state segmentation for agency managed stores, or cost forecasts that break as contacts grow. For agency managed stores, that moment usually arrives when more than two people maintain flows or when peak campaigns require documented suppression.
How much discounting is acceptable for agency managed stores?
Treat discounts as one lever, not the default. For agency managed stores, test content-led recovery and loyalty first, cap discount depth against margin, and document who can approve exceptions. If most agency managed stores revenue needs a code, the agency managed stores program has a value problem rather than a pricing problem.
Which Shopify data matters most for agency managed stores?
Order and refund state, cart and browse events, consent source, and product availability cover most agency managed stores decisions. Before layering agency managed stores branching on events, fire each one in a test purchase and record what every agency managed stores-relevant field means for both teams.
How do I avoid duplicate sends across apps for agency managed stores?
Give one platform ownership of each agency managed stores journey, document which app sends what, and share suppression lists where the tools support it. Keep a weekly agency managed stores peak-season audit: pull sample customers, list each agency managed stores message they got, flag overlaps.
What should a agency managed stores pilot include?
For agency managed stores, a tight pilot wins: single audience, at most two journeys, explicit suppression, a holdout, and a day-thirty agency managed stores review of margin and complaints with pre-agreed pass/fail lines.
Governance and documentation for agency managed stores
| Practice | Standard | Risk it prevents |
|---|---|---|
| Flow ownership | One accountable agency managed stores operator per flow | agency managed stores ghosts sending expired incentives |
| Naming convention | Agency Managed Stores prefixes by job and audience | Unnamed agency managed stores sprawl unauditable in season |
| Change log | agency managed stores edits stamped, dated, explained | agency managed stores performance drift with no log |
| Access control | Agency Managed Stores seats on least privilege | agency managed stores rogue sends from open permissions |
| Quarterly flow review | Prune idle agency managed stores branches quarterly | Tangled agency managed stores logic slowing changes |
| Incident runbook | agency managed stores break-glass steps pre-written | Lagging agency managed stores response to bad sends |
Peak season readiness for agency managed stores
- Lock agency managed stores flow edits a full fortnight before peak.
- For agency managed stores, trial every journey against real order events.
- Check agency managed stores exits filter buyers and open cases.
- Agency Managed Stores measurement needs bigger peak holdouts.
- Agency Managed Stores texting policy written before peak.
- Agency Managed Stores billing checked on peak math.
- Staff daily agency managed stores deliverability watch on complaints and bounces.
- Bank agency managed stores rollback plans ahead of sends.
For agency managed stores, schedule quarter-one review before the first send. Writing agency managed stores suppression rules, discount caps, and escalation paths down in week one saves weeks of peak-season triage and hands newcomers a working agency managed stores playbook.
Close each agency managed stores quarter with a written ledger — agency managed stores sends shipped, suppressions honored, margin retained, failed bets — so agency managed stores vendor decisions rest on one shared evidence file, not scattered memory.