What deliverables should I expect from a UX audit?
Updated March 8, 2026 4 min read
UX audit deliverables vary significantly across providers. Knowing what to expect — and what to demand — separates an audit that gathers dust from one that drives action.
The core deliverable: prioritized findings
The primary output of any UX audit is a list of findings ranked by impact and effort. This is where most of the value lives.
A well-structured findings list includes:
- The issue — A clear description of what the problem is
- Where it occurs — The specific page, section, or interaction
- Why it matters — The user behavior implication (what does this cause customers to do or not do?)
- The recommendation — A specific, actionable fix
- Effort estimate — Is this a theme setting, a small dev task, or a larger project?
- Priority — Where it sits relative to other findings
An audit that returns 50 equal-weighted issues is not useful. A developer or designer looking at that list has no idea where to start. Prioritization is what makes findings actionable — and it’s a service the auditor provides based on their experience with what moves conversion most.
Annotated screenshots
Each finding should include a screenshot of the exact location on your site with callouts or annotations marking the specific issue. This does two things: makes the problem immediately visible without having to re-navigate the site, and makes the report shareable with your development team without ambiguity about what “the trust signals are weak” means.
Annotations should be specific enough that a developer can find the exact element in the theme code without further guidance.
Video walkthrough
Most high-quality audits include a recorded walkthrough (Loom, Vimeo, or similar) where the auditor talks through findings while navigating the live site. Video is valuable because:
- It’s faster to watch than read for stakeholders who need a summary
- Tone and emphasis convey which issues the auditor considers most critical
- It’s easier to share with team members who weren’t in any kick-off meetings
- Questions can be raised against specific timestamps
For team briefings and developer handoffs, video walkthroughs accelerate understanding significantly compared to written reports alone.
Implementation guidance
For each finding, the deliverable should specify what type of fix is involved:
- Theme settings — Configurable in Shopify Admin without development
- Theme code edit — Small Liquid/CSS change, typically 30-60 minutes of developer time
- App addition — A Shopify app handles this (with a specific recommendation)
- Checkout customization — Requires Shopify Plus and Checkout Extensibility
- Development sprint — Larger feature change requiring planning and dedicated dev time
This categorization lets you route items correctly: some go to your designer, some to your developer, some you can handle yourself, some go to the backlog for the next development sprint.
Quick wins summary
A separate, highlighted list of the 5-7 highest-impact, lowest-effort findings. This is for stakeholders who need a starting point — the items that should be addressed in the next 2 weeks, before the full prioritized list is worked through systematically.
Common quick wins in ecommerce audits:
- Adding a shipping cost display in the cart
- Making guest checkout more prominent
- Adding trust signals near the payment form
- Fixing mobile keyboard types for payment fields
- Adding estimated delivery dates to product pages
What better audits add
Revenue impact estimates — For each finding, an estimate of what conversion rate improvement fixing it might deliver, based on the auditor’s experience with similar stores and available research data. “Addressing the surprise shipping cost at checkout is likely responsible for 15-25% of your current checkout abandonment” is more actionable than “shipping cost transparency is an issue.”
Data backing — If the auditor has reviewed your GA4 funnel data and session recordings, findings are contextualized by actual behavior, not just heuristic patterns. “We see in session recordings that 8 out of 20 observed checkout sessions exit immediately after seeing the total cost at the payment step” is a different category of finding than theoretical pattern-matching.
A/B testing roadmap — For stores with sufficient traffic (5,000+ monthly sessions), recommendations on which findings to test vs. just implement, and how to structure those tests.
Figma mockups — For premium-tier audits, visual solutions showing exactly what the recommended change looks like. Eliminates interpretation by developers and designers, accelerating implementation.
What to ask before commissioning an audit
- What specific deliverables are included?
- Will findings be prioritized — and how?
- Will you review analytics or session data, or only evaluate the site visually?
- What format is the final report (document, Notion, Loom video)?
- Is a follow-up call included to walk through findings?
- What’s your experience with this platform and category?
The research page shows exactly what’s included in an audit from BTNG — the deliverable format, what’s covered, and how the prioritization works. Book a call to discuss the right scope for your store.
For a complete breakdown, read E-commerce UX Audit Cost Guide (2026): What You Actually Get for Your Money.