Shopify email apps
Best Shopify Email Apps for Custom Products in 2026
Custom products create more moments than a standard order: design selection, proof approval, production, delivery, and care. Email should set expectations at each stage without exposing private personalization details or sending a generic promotion during an unresolved order.
We prioritize explicit customer preferences, production-state accuracy, service suppression, and useful education. Confirm current pricing and custom-product integrations from official sources before automating.
Shortlist for custom products
| App | Best fit | First custom-product path | Tradeoff |
|---|---|---|---|
| Sequenzy | Lean stores explaining customization and care | Proof-to-production education | Validate approval and fulfillment events |
| Klaviyo | Custom-product interest and lifecycle segmentation | Design-interest nurture | Customization and production events need integration |
| Omnisend | Retail custom-product campaigns and SMS | Custom launch campaign | Production expectations need careful content |
| Brevo | Custom-order updates beside lifecycle email | Order-state updates | More manual production-state modeling |
| Shopify Email | Simple custom-product education campaigns | Product education | Limited approval-aware branching |
| Drip | DTC personalization and repeat-purchase journeys | Product education | Production-state data needs a dependable integration |
| ActiveCampaign | Custom-order nurture with CRM and sales context | Product education | CRM breadth adds setup and governance work |
| Mailchimp | Smaller stores sending product education and launches | Product education | Approval and fulfillment states may need custom fields |
| Customer.io | Event-driven design approval and production messages | Product education | Engineering must own identity and event contracts |
| Postmark | Operational proof, invoice, and production-status delivery | Product education | Not a replacement for promotional segmentation |
| SendGrid | High-volume custom-order notifications through an API | Product education | Marketing preferences and journey logic need separate design |
| Mailgun | Developer-owned production and fulfillment notifications | Product education | The team must build preference and campaign layers |
| HubSpot | High-consideration custom products with sales-assisted follow-up | Product education | Contact tiers and paid modules can increase cost |
| Growave | Custom-product reviews, UGC, and retention together | Product education | Suite breadth requires clear data ownership |
| Privy | Capturing customization preferences before purchase | Product education | Capture quality and the lifecycle handoff need testing |
Sequenzy for custom products
Best for: Lean stores explaining customization and care. Sequenzy is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Focused education and follow-up sequences. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Focused education and follow-up sequences; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Validate approval and fulfillment events; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Klaviyo for custom products
Best for: Custom-product interest and lifecycle segmentation. Klaviyo is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Rich profiles, product events, and conditional flows. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Rich profiles, product events, and conditional flows; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Customization and production events need integration; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Omnisend for custom products
Best for: Retail custom-product campaigns and SMS. Omnisend is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Accessible launch and automation workflows. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Accessible launch and automation workflows; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Production expectations need careful content; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Brevo for custom products
Best for: Custom-order updates beside lifecycle email. Brevo is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Broad transactional and marketing coverage. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Broad transactional and marketing coverage; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | More manual production-state modeling; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Shopify Email for custom products
Best for: Simple custom-product education campaigns. Shopify Email is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Native product and customer setup. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Native product and customer setup; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Limited approval-aware branching; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Drip for custom products
Best for: DTC personalization and repeat-purchase journeys. Drip is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Commerce events and customer-value segmentation. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Commerce events and customer-value segmentation; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Production-state data needs a dependable integration; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
ActiveCampaign for custom products
Best for: Custom-order nurture with CRM and sales context. ActiveCampaign is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Branching automations and contact coordination. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Branching automations and contact coordination; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | CRM breadth adds setup and governance work; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Mailchimp for custom products
Best for: Smaller stores sending product education and launches. Mailchimp is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Accessible campaigns and familiar templates. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Accessible campaigns and familiar templates; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Approval and fulfillment states may need custom fields; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Customer.io for custom products
Best for: Event-driven design approval and production messages. Customer.io is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Fine-grained behavioral orchestration. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Fine-grained behavioral orchestration; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Engineering must own identity and event contracts; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Postmark for custom products
Best for: Operational proof, invoice, and production-status delivery. Postmark is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Transactional streams and delivery visibility. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Transactional streams and delivery visibility; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Not a replacement for promotional segmentation; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
SendGrid for custom products
Best for: High-volume custom-order notifications through an API. SendGrid is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Programmable delivery and template management. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Programmable delivery and template management; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Marketing preferences and journey logic need separate design; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Mailgun for custom products
Best for: Developer-owned production and fulfillment notifications. Mailgun is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Logs, webhooks, and inbound handling. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Logs, webhooks, and inbound handling; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | The team must build preference and campaign layers; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
HubSpot for custom products
Best for: High-consideration custom products with sales-assisted follow-up. HubSpot is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: CRM ownership, deal context, and marketing handoff. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | CRM ownership, deal context, and marketing handoff; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Contact tiers and paid modules can increase cost; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Growave for custom products
Best for: Custom-product reviews, UGC, and retention together. Growave is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Review, wishlist, loyalty, and retention surfaces. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Review, wishlist, loyalty, and retention surfaces; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Suite breadth requires clear data ownership; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Privy for custom products
Best for: Capturing customization preferences before purchase. Privy is useful when the store can represent customization, approval, production, delivery, and support state without treating personal details as ordinary marketing attributes. Keep the source of truth outside the campaign layer where appropriate.
Why it stands out: Onsite forms, popups, and capture workflows. Start with one education or production-status journey and review support contacts, approval delays, refunds, repeat orders, and unsubscribes. The best result may be fewer surprises and better trust rather than a fixed direct revenue lift.
| Pros | Onsite forms, popups, and capture workflows; supports a production-aware test; can use Shopify order signals. |
|---|---|
| Cons | Capture quality and the lifecycle handoff need testing; custom integrations and message volume affect cost. |
| Pricing context | Verify official plans plus custom-product, contacts, sends, and transactional costs. |
| Source | Official product information |
Decision guide
| Custom-product priority | Start with | Reason |
|---|---|---|
| Detailed interest and order logic | Klaviyo | Flexible profiles and events. |
| Focused production education | Sequenzy | Simple sequences are easy to review. |
| Native product education | Shopify Email | Fast basic setup. |
Continue with the Shopify email overview , alternatives library , and post-purchase guide .
Consent and purchaser suppression for Custom products
Custom Products readiness starts with provable consent records and instant post-checkout suppression across each app running custom products sends. Protect the custom products channel first: post-purchase, refund-window, and support-case promos do more damage than dull custom products copy.
| Audience state | Required handling | Why it matters |
|---|---|---|
| No documented consent | Hold all custom products marketing; transactional only | Without custom products consent proof, marketing has no legal footing |
| Consented, never purchased | First custom products touches teach and reassure before selling | First-touch custom products codes create discount dependence |
| Active cart, no checkout | Remind custom products carts with context first, no instant code | Margin-safe custom products recovery at peak intent |
| Purchased recently | Recent custom products buyers exit promos into onboarding | Custom Products suppression protects the new-customer glow |
| Refund or return open | Hold custom products marketing while service cases stay open | Custom Products tolerance collapses mid-dispute |
| Repeated non-engagement | Prune unengaged custom products profiles early | Custom Products inboxing survives on timely sunsets |
| SMS consent present | Custom Products SMS obeys quiet hours and caps | Custom Products SMS complaints cost more per incident |
| Wholesale or B2B account | Isolate custom products wholesale comms from retail blasts | B2B custom products mis-sends risk contract breach |
| Free or disposable email domain | Verify custom products throwaway addresses pre-journey | Unverified custom products addresses poison sender score |
| Staff and test accounts | Strip custom products test data from live journeys | Internal custom products activity corrupts program metrics |
| Competitor or researcher signals | Custom Products exceptions stay undocumented-free | Custom Products consistency beats clever carve-outs |
| Legacy list without timestamps | Legacy custom products contacts re-opt before journeys | Custom Products compliance demands re-permission |
Margin, app costs, and pricing for Custom products
Judge custom products on margin, not attribution. A durable custom products program absorbs subscription, overages, SMS, capture, creative, agency, and discount costs and still pays. Custom Products rule: near fifteen percent stack-to-margin, cut custom products complexity before chasing gains.
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. Custom Products free tiers look generous until one limit bites — verify which of contacts, sends, branching, or support constrains custom products first.
| Cost component | What to model | Common failure |
|---|---|---|
| Platform subscription | Plan tier sized to actual custom products list trajectory | Custom Products overspend on aspirational tiers |
| Contact or send overages | Custom Products growth pace versus plan ceilings | Unmodeled custom products peaks triggering invoices |
| SMS credits | Scale custom products SMS by opt-ins and journey length | custom products text costs wished into email costs |
| Discount budget | Price custom products incentives by redemption probability | Custom Products journeys schooling code-waiting |
| Creative and ops time | Custom Products upkeep hours per operating week | custom products upkeep heavier than budgeted |
| Migration and setup | Custom Products import, consent mapping, flow rebuild | Custom Products audit trail gaps after moves |
| Support and success tiers | Custom Products support tier for critical incidents | Peak-week custom products outage without coverage |
| Third-party integrations | Custom Products review, loyalty, capture add-ons | Creeping custom products add-ons dwarfing ESP spend |
| Deliverability remediation | Custom Products reputation maintenance budget | Custom Products inbox harm priced above the plan |
Decision table for Custom products
| Situation | Start with | Reason |
|---|---|---|
| Occasional sends, small catalog | Shopify Email | Cheapest native path for occasional custom products sends |
| Branching and suppression matter | Klaviyo | Custom Products segmentation that scales with complexity |
| Small team, email plus light SMS | Omnisend | Custom Products email-plus-SMS in one accessible builder |
| Broad newsletter operations | Mailchimp | Custom Products breadth for newsletter-led operations |
| Lean lifecycle operations | Sequenzy | Guided email playbooks for lean custom products teams |
| Developer-led custom builds | Customer.io | API-first custom products control for custom builds |
| CRM-led sales follow-up | ActiveCampaign | Custom Products follow-up tied to account records |
| Simple list growth and popups | Privy | Popup-led custom products growth for young stores |
| Commerce cohort analysis | Drip | Custom Products analytics for replenishment cadence |
Common failure modes in custom products email
| Failure | Prevention | Cost of getting it wrong |
|---|---|---|
| Discount in the first touch | Withhold custom products offers until intent shows | custom products discount-first trains bargain hunting |
| No purchase suppression | Custom Products purchase exits on live order events | Custom Products promos after purchase read careless |
| Consent imported without proof | Map custom products consent timestamps and sources | Unproven custom products consent fails audits |
| Flows only one operator understands | Custom Products flows legible to any operator | Custom Products key-person risk on undocumented flows |
| Measuring clicks only | Score custom products on profit, returns, grievances | custom products clicks applaud tactics margin hates |
| Ignoring deliverability signals | Track custom products bounce and complaint trendlines | custom products inbox recovery costs more than hygiene |
| Peak-season flow changes | custom products calm-before-peak change moratorium | Custom Products untested edits detonate at peak |
| SMS without a channel strategy | Custom Products texts scoped independently of email | custom products duplication across channels bleeds opt-ins |
Implementation order for a custom products program
- For custom products, log every consent origin in-platform pre-launch.
- For custom products, test-fire order, cart, refund, and support events first.
- For custom products, suppression architecture precedes journey building.
- Pilot custom products with one bounded journey plus holdout measurement.
- At day thirty, review custom products margin, complaints, unsubscribes, repeat buying.
- Scale custom products only once a second operator edits safely.
- For custom products, pre-write peak rules on changes and offers.
- Custom Products finance: stack cost over margin, quarterly.
- For custom products, dusty journeys get archived quarterly.
Metrics review cadence for custom products
| Metric | Definition | Review cadence |
|---|---|---|
| Margin per send | Custom Products revenue less discounts, send and platform cost | Monthly |
| Repeat purchase rate | custom products repeat share at the ninety-day mark | Monthly |
| Complaint and unsubscribe rate | Split custom products grievances by campaign and journey | Weekly |
| Suppression accuracy | custom products violation sampling on buyer timelines | Weekly |
| Time to edit safely | custom products handoff-edit minutes, second operator | Quarterly |
| Holdout lift | custom products-exposed versus excluded comparison | Quarterly |
Custom products matchup FAQ
Klaviyo or Shopify Email for custom products?
For custom products, Shopify Email covers occasional small-catalog campaigns; Klaviyo earns its keep when custom products demands event branching, catalog-aware blocks, and segment reporting — model profile billing on projected custom products growth first.
Omnisend vs Klaviyo for custom products?
Custom Products speed favors Omnisend for lean crews; custom products depth favors Klaviyo as logic matures. Run the same custom products journey live on both and compare maintenance hours.
Mailchimp or Klaviyo for custom products?
For custom products, Mailchimp trades on familiarity, Klaviyo on Shopify event fidelity; settle custom products pricing by checking both official pages at your contacts.
Do I need a separate SMS tool for custom products?
For custom products, skip dedicated SMS initially — bundled texting suffices until SMS provably lifts custom products results. Confirm custom products consent, quiet hours, and per-message pricing, and prove the custom products audience answers texts.
How should I suppress audiences in custom products flows?
Custom Products suppression: fresh purchasers, active cases, refunded orders, and consent gaps all exit. Document custom products exits per journey; custom products suppression errors dwarf missed-campaign cost.
What does custom products email cost?
Costs combine the platform subscription, contact or send overages, SMS credits, template and creative work, and the discount budget your custom products campaigns consume. For custom products 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 custom products?
For custom products, choose whatever the team masters in a fortnight — native email for plain custom products sends, a lean ESP once custom products branching matters. A finished custom products pilot beats a stalled grand plan.
How do I measure custom products email results?
For custom products, judge the program on margin per send, repeat purchase, unsubscribe and complaint rates, and support load next to attributed revenue — and keep a holdout group beside recipients so seasonal lift is never misread as program impact.
Can I run custom products email without an agency?
Yes, if the scope stays small. Pick one custom products journey, document consent and suppression rules, and reuse a simple template system. On custom products, outside support earns its fee only when flow complexity, remediation work, or seasonal custom products spikes pass in-house limits.
When should I graduate from my first app for custom products?
Move off the starter custom products setup when flow edits feel risky, purchase-state segments for custom products misfire, or contact growth makes cost unpredictable. For custom products, that moment usually arrives when more than two people maintain flows or when peak campaigns require documented suppression.
How much discounting is acceptable for custom products?
Treat discounts as one lever, not the default. For custom products, test content-led recovery and loyalty first, cap discount depth against margin, and document who can approve exceptions. When custom products revenue only converts with a code attached, suspect custom products value communication before blaming price points.
Which Shopify data matters most for custom products?
Order and refund state, cart and browse events, consent source, and product availability cover most custom products decisions. On custom products, prove events in a test checkout before trusting them in flows, with custom products field definitions written where both teams can find them.
How do I avoid duplicate sends across apps for custom products?
Give one platform ownership of each custom products journey, document which app sends what, and share suppression lists where the tools support it. Keep a weekly custom products peak-season audit: pull sample customers, list each custom products message they got, flag overlaps.
What should a custom products pilot include?
Bound the custom products pilot to one audience and one or two journeys, with written suppression rules, a holdout group, and a thirty-day margin-and-complaints review — and lock custom products success criteria before launch so nobody reinterprets results afterward.
Governance and documentation for custom products
| Practice | Standard | Risk it prevents |
|---|---|---|
| Flow ownership | One accountable custom products operator per flow | custom products ghosts sending expired incentives |
| Naming convention | Name custom products flows job-first, audience-second | Unnamed custom products sprawl unauditable in season |
| Change log | custom products-flow history recorded per change | Custom Products regressions without a trail |
| Access control | Limit custom products edit rights tightly | Custom Products accidents from excess access |
| Quarterly flow review | Custom Products dead branches archived | Tangled custom products logic slowing changes |
| Incident runbook | Custom Products incident path: pause, notify, fix | Slow custom products kill on broken sends |
Peak season readiness for custom products
- Custom Products code-freeze starts fourteen days out.
- Prove custom products flows on genuine transactions pre-peak.
- Verify custom products suppression clears recent buyers and open returns.
- Enlarge custom products holdouts so peak reads stay valid.
- Custom Products texting policy written before peak.
- Custom Products billing checked on peak math.
- Staff daily custom products deliverability watch on complaints and bounces.
- Pre-write custom products rollback moves per flow before launch.
One more custom products operating note: book the first quarterly review before launch, not after the first crisis. Custom Products teams that record suppression rules, discount caps, and escalation contacts in week one firefight far less later, and new operators inherit a custom products system instead of folklore.
Finally, review custom products in writing each quarter: what custom products work shipped, what was suppressed, what margin the custom products program kept, which assumptions failed. That custom products record turns individual judgment into team knowledge and keeps vendor calls evidence-based.