An email deliverability audit checks whether the sending setup and audience are ready for the next campaign. Before a major Shopify promotion, verify authentication with a real message, inspect exclusions after recent data changes, and review how comparable sends have performed. Turn any findings into a clear fix, pause, or proceed decision before the team depends on the launch.
Check identity and configuration
Verify the visible sender, monitored reply address, authentication, and domain alignment with a real test message. Review recent DNS or service changes and confirm that the people responsible for the domain know which systems are legitimate senders.
Use Sendvio's deliverability tools and support where appropriate, but keep the actual result as evidence. A configuration that worked months ago should not be assumed unchanged after a migration or new integration.
Ask for evidence that the setup works today
Keep a recent controlled message showing the intended sender, reply route, and authentication results. Record any unresolved failure and the owner responsible for it. A screenshot of DNS records alone does not demonstrate that the actual campaign is using the expected identity and alignment.
Review changes since the last successful campaign: new services, domain edits, migration, form updates, or imports. Check the sending streams affected by shared configuration. Do not replace a record simply because a checklist says authentication needs attention; understand the current setup with the domain owner first.
Confirm that replies and unsubscribe routes work through the supported process. These are operational parts of the sender relationship, not footer decoration. Preserve the relevant exclusion state when records move between systems or are updated in bulk.
Review audience and volume
Inspect subscription records, invalid and bounced statuses, older inactive groups, and recent acquisition sources. Keep unsuitable contacts out of the promotion rather than treating peak season as an exception to normal audience quality.
Compare planned volume with the recent sending pattern. Automated warming or rewarming can support a controlled process, but it does not justify ignoring complaints or sudden delivery changes. Prepare the growth before the event rather than attempting a last-minute jump.
Turn findings into a release decision
Classify each finding by its consequence. An authentication failure affecting the intended stream, an unexplained audience source, or broken exclusion handling should stop the affected send until resolved. A minor copy preference can be handled separately without obscuring those material issues.
Compare planned volume with recent sending and coordinate campaigns with active automations. Use the account's supported warming or rewarming process where needed. Avoid inventing a fixed safe multiplier or assuming that a seasonal deadline makes a sudden expansion acceptable.
Assign a person to monitor the first controlled sends and state what evidence would pause further expansion. Review the actual failure and complaint patterns in context, including the receiving requirements applicable to your audience. A plan that names an owner and a response is more useful than a vague instruction to watch deliverability.
Set monitoring and stop decisions
Assign an owner to watch the first sends and define which unexpected results require investigation before continuing. Review failures, deferrals, complaints, and customer response together.
Keep a short record of the checks and unresolved questions. If a material issue remains, revise the audience or schedule instead of hiding it behind a creative deadline. The audit is useful when it changes a decision early enough to protect the campaign, not when it becomes a completed checklist nobody consults again.
Finish the audit with a short decision record: ready, ready with a narrower audience or revised schedule, or waiting for specific fixes. List the evidence and unresolved questions. This gives the campaign team a practical next step and ensures that the review changes the launch decision when the sending foundation is not yet dependable.