Retail & e-commerce · Power BI template
Retail Merchandising: Sell-Through Power BI template
Power BI merchandising dashboard template: sell-through since launch, weeks of cover, markdown and margin by style, and a ranked list of markdown candidates.
By Nawaf Sharaf · Founder & Reliability Engineer · Updated
Free for commercial useDark version: same layout, colours re-solved and checked for WCAG AA contrast.
BetaOpens in Power BI Desktop with 4 tables of sample data and every visual bound. See what’s inside
Free, no sign-up. The PBIP with sample data includes the background, theme and a README. 1920×1080 fits a new page in a Fluent 2 report; 1280×720 and 2× fit Classic pages. Downloads carry a small “Made with VizForge” mark (sign in to the studio to remove it).
- Layout
- Band header with logo, 5 KPIs, cumulative sell-through lines + style scatter, weekly sales columns + markdown table
- Page size
- 1280×720 px (16:9, Power BI default)
- Theme
- Sunset Retail
Open the sample-data PBIP in Power BI Desktop
Checked against Microsoft Learn's Power BI Desktop projects documentation (as of Nov 2026).
- 1
Unzip to a short path and open the .pbip
Extract the zip to a short local folder such as C:\PBI (Windows limits project paths to 260 characters, and Desktop can't save a project straight to OneDrive or SharePoint), then double-click the .pbip file or use File → Open in Power BI Desktop. Microsoft still lists projects and TMDL as preview features (as of Nov 2026): if Desktop won't open the project, go to File → Options and settings → Options → Preview features, tick “Power BI Project (.pbip) save option” and “Store semantic model using TMDL format”, then restart Desktop.
- 2
Select Refresh once
The project ships without the local data cache (.pbi/cache.abf), so Desktop opens the full model definition without data. Select Home → Refresh: every table is built from values written into its Power Query step, so there is no data source to sign in to.
- 3
Save as .pbix or connect your data
Use File → Save as to keep a single .pbix file, or open Transform data and replace each table's Source step with your own query, keeping the column names so the measures and visuals keep working.
What’s inside the Sell-Through sample model
Rendered from the same definition the download writes as TMDL, so this list always matches the file.
The first 12 weeks of a fictional fashion retailer's autumn/winter season (Aug to Oct 2026): 30 styles across five departments with their opening intake, weekly units sold, full-price units, sales value and markdown value. Slow-selling styles were marked down from week 8. Units: Units; sales and markdown in pounds sterling.
Tables and columns
Calendar
Date table · 2026, one row per dayDate table generated in Power Query (List.Dates), marked as the model's date table.
- Date (date)
- Year (whole number)
- Quarter (text)
- Month (text)
- Month Name (text)
- Week Start (date)
- Weekday (text)
- Fiscal Year (text)
Style
Dimension · 30 rowsStyles in the season with department, price and unit cost.
- Style Code (text)
- Style (text)
- Department (text)
- Season (text)
- Full Price (decimal)
- Unit Cost (decimal)
Receipts
Fact · 30 rowsOpening intake per style.
- Style Code (text)
- Date (date)
- Units Received (whole number)
Style Week
Fact · 360 rowsWeekly sales per style.
- Week (date)
- Style Code (text)
- Units Sold (whole number)
- Full-Price Units (whole number)
- Sales Value (decimal)
- Markdown Value (decimal)
Relationships
Many-to-one, single direction. Inactive relationships are switched on inside a measure with USERELATIONSHIP.
- Receipts[Date] → 'Calendar'[Date]
- Receipts[Style Code] → Style[Style Code]
- 'Style Week'[Week] → 'Calendar'[Date]
- 'Style Week'[Style Code] → Style[Style Code]
DAX measures
All measures live in a dedicated Key Measures table. Copy any of them into your own model; rename the table and column references to match.
Units SoldUnits sold.
Units Sold =
SUM ( 'Style Week'[Units Sold] )Format string: #,0
Units ReceivedSeason intake (not limited by the date filter).
Units Received =
CALCULATE ( SUM ( Receipts[Units Received] ), REMOVEFILTERS ( 'Calendar' ) )Format string: #,0
Sell-Through %Units sold over units received.
Sell-Through % =
DIVIDE ( [Units Sold], [Units Received] )Format string: 0%
Cumulative Sell-Through %Sell-through from launch to each week.
Cumulative Sell-Through % =
DIVIDE (
CALCULATE ( [Units Sold], FILTER ( ALL ( 'Calendar'[Date] ), 'Calendar'[Date] <= MAX ( 'Calendar'[Date] ) ) ),
[Units Received]
)Format string: 0%
Weeks of CoverStock left over the average weekly sales of the last four weeks.
Weeks of Cover =
VAR LastWeek = CALCULATE ( MAX ( 'Style Week'[Week] ), REMOVEFILTERS ( 'Calendar' ) )
VAR Stock = [Units Received] - CALCULATE ( [Units Sold], REMOVEFILTERS ( 'Calendar' ) )
VAR RecentRate = CALCULATE ( [Units Sold], REMOVEFILTERS ( 'Calendar' ), 'Style Week'[Week] > LastWeek - 28 ) / 4
RETURN
DIVIDE ( Stock, RecentRate )Format string: 0.0
Sales ValueSales after markdown.
Sales Value =
SUM ( 'Style Week'[Sales Value] )Format string: £#,0
Markdown ValuePrice reductions given.
Markdown Value =
SUM ( 'Style Week'[Markdown Value] )Format string: £#,0
Markdown %Markdown as a share of sales at full price.
Markdown % =
DIVIDE ( [Markdown Value], [Sales Value] + [Markdown Value] )Format string: 0.0%
Gross Margin %Margin after markdowns and unit cost.
Gross Margin % =
DIVIDE ( [Sales Value] - SUMX ( 'Style Week', 'Style Week'[Units Sold] * RELATED ( Style[Unit Cost] ) ), [Sales Value] )Format string: 0.0%
Full-Price Mix %Units sold at full price.
Full-Price Mix % =
DIVIDE ( SUM ( 'Style Week'[Full-Price Units] ), [Units Sold] )Format string: 0%
What each visual is bound to
The PBIP opens with these fields already on each visual.
| Visual | Type | Fields |
|---|---|---|
| DepartmentSlicer | Slicer | Style[Department] |
| SeasonSlicer | Slicer | Style[Season] |
| Sell-throughCard | Card | [Sell-Through %] |
| Weeks of coverCard | Card | [Weeks of Cover] |
| Markdown %Card | Card | [Markdown %] |
| Gross margin %Card | Card | [Gross Margin %] |
| Full-price mixCard | Card | [Full-Price Mix %] |
| Sell-through since launchLine chart | Line chart | Calendar[Week Start], [Cumulative Sell-Through %], Style[Department] |
| Sell-through vs margin by styleScatter chart | Scatter chart | Style[Style], [Sell-Through %], [Gross Margin %], [Sales Value] |
| Sales and markdown by weekColumn chart | Column chart | Calendar[Week Start], [Sales Value], [Markdown Value] |
| Markdown candidatesTable | Table | Style[Style], Style[Department], [Sell-Through %], [Weeks of Cover], [Gross Margin %] |
Questions this dashboard answers
Each one is answered by a visual on the page, from the sample model's own tables and measures.
- Which styles are selling through fastest since launch, and which are stuck?
- How many weeks of stock are left at the current rate of sale?
- How much margin is being given away in markdowns?
- Which styles should be marked down or reordered next?
About this dashboard layout
Merchandisers make the season's biggest calls in its first weeks: what to reorder, what to leave and what to mark down. The cards give the season so far: sell-through (units sold over units received), weeks of cover at the current rate of sale, markdown as a share of full-price value, gross margin after markdowns, and the share of units sold at full price.
Sell-through since launch accumulates week by week for each department, so a line flattening early shows a range that has stopped selling while there is still time to act. The scatter places each style by sell-through and margin, sized by sales: high sell-through with high margin is a reorder; low on both is a markdown.
Weeks of cover divides remaining stock by the average weekly sales of the last four weeks, the measure that turns sell-through into a date. The markdown-candidates table ranks styles by sell-through, lowest first, with weeks of cover and margin beside each one.
Sales and markdown by week shows when markdowns started and how much sales they bought. The sample is the first 12 weeks of a fictional fashion retailer's autumn/winter season with 30 styles in five departments.
Visuals on the page
Positions are Power BI page pixels. Enter them in Format → General → Properties → Size and position, or use the PBIP download where they are already set.
| Visual | Type | X | Y | Width | Height |
|---|---|---|---|---|---|
| Department | Slicer | 888 | 24 | 176 | 40 |
| Season | Slicer | 1080 | 24 | 176 | 40 |
| Sell-through | Card | 40 | 112 | 168 | 64 |
| Weeks of cover | Card | 296 | 112 | 160 | 64 |
| Markdown % | Card | 544 | 112 | 160 | 64 |
| Gross margin % | Card | 792 | 112 | 160 | 64 |
| Full-price mix | Card | 1040 | 112 | 160 | 64 |
| Sell-through since launch | Line chart | 40 | 224 | 704 | 200 |
| Sell-through vs margin by style | Scatter chart | 792 | 224 | 448 | 200 |
| Sales and markdown by week | Column chart | 40 | 472 | 456 | 208 |
| Markdown candidates | Table | 544 | 472 | 696 | 208 |
Custom visuals for this layout
Built-in Power BI visuals cover most slots above. These slots also suit a custom visual; each page covers the data shape, DAX and a prompt to generate it as a .pbiviz.
Already have a report?
Brand Makeover tries Retail Merchandising: Sell-Through first on every page of your Power BI project (.pbip zip) where it fits: the page's visuals have to go into its 9 data slots without overlaps. Pages it can't seat get another catalog layout or a brand grid. Queries, filters and bookmarks are left as they are. Free, in your browser.
Opens with the Analyst / Dense preset, because the Executive preset doesn't use this layout (9 data slots; this preset uses templates with at most 7).
Restyle my report into thisSwap a slot for a custom visual
Pick any slot and VizForge AI writes a custom visual (.pbiviz, with TypeScript source) sized to it, in this template's colours and shaped for the fields it is bound to.
Generate one that fits this layout.
Card · 168×64 px · bound to [Sell-Through %]
1, 2 or 5 credits depending on the brief · 5 free on signup. Sign in or create a free account on the next screen; the brief is saved for 30 minutes.
A Power BI card visual titled "Sell-through". It sits in a 168×64 px slot on a designed report page. Match the report's brand: data colours #E2541B, #C47E09, #DB2777, #7C3AED, #0891B2, #619C0C; background #FFFFFF; text #2A1A12; font Segoe UI. Transparent visual background so the page design shows through; no visual border. In the sample model it is bound to [Sell-Through %]; keep the same data roles so the fields drop straight in.
Not sure what to build? Browse the visual catalog or open the template in the design studio and hand off any slot from there. Or start in the AI generator with a blank brief.
Colours and theme
Warm cream Power BI theme with coral and amber data colours for retail, e-commerce and marketing dashboards; white cards, espresso text, AA contrast.
Use the background in an existing report
Prefer to keep your own report? Apply the design to it instead of opening the PBIP.
- 1
Download the background
Take the 1920×1080 PNG for a new page in a Fluent 2 report (the default size for new pages), or the 2× PNG (2560×1440) for sharp text on a 1280×720 Classic page. Power BI scales the image to the canvas.
- 2
Set the canvas background
Format page → Canvas background → Browse. Set Image fit to Fill and transparency to 0%.
- 3
Import the theme
Design ribbon → Import theme (in the Power BI service: View → Theme pane), then pick the downloaded JSON. Data colours and fonts now match the design. Older Desktop builds: View → Themes → Browse for themes.
- 4
Place your visuals
Size each visual to the positions above with background and border off, or open the PBIP project where they are already placed.
Questions about this template
Does the Retail Merchandising: Sell-Through template come with sample data?
Yes. The “PBIP with sample data” download contains a semantic model with 4 tables and 10 DAX measures, and every visual on the page is already bound to it. The sample: The first 12 weeks of a fictional fashion retailer's autumn/winter season (Aug to Oct 2026): 30 styles across five departments with their opening intake, weekly units sold, full-price units, sales value and markdown value. Slow-selling styles were marked down from week 8. The data is written into each table's Power Query step, so there is no data source or sign-in.
Is it a .pbix file?
It is a Power BI project (PBIP): a folder of text files that Power BI Desktop opens like a .pbix. Open the .pbip file, select Refresh once to load the sample rows, then use File → Save as if you want a single .pbix.
What visuals are in the Retail Merchandising: Sell-Through template?
The page has 11 visual areas: 2 slicers, 5 cards, 1 line chart, 1 scatter chart, 1 column chart, 1 table. Their exact positions are listed on this page so you can match them in Power BI's Format → General → Properties panel, or skip that step by downloading the PBIP project.
Which theme does the Retail Merchandising: Sell-Through template use?
It ships with the Sunset Retail theme (light tone). Download the theme JSON here, or open the template in the design studio and switch to any other theme or your own brand colours.
Is there a dark version of the Retail Merchandising: Sell-Through template?
Yes. Switch the preview to Dark and every download (background, theme JSON and PBIP) comes in that version. The layout is identical; the page, card and text colours are re-solved for a dark page, and the accent, status and data colours keep their hues but are adjusted until text meets WCAG AA (4.5:1) and chart colours reach 3:1 against the cards.
How do I use the background image in Power BI Desktop?
Select the page, open Format page → Canvas background, choose Browse and pick the PNG, then set Image fit to Fill and transparency to 0%. Give your visuals a transparent background and no border so the designed panels show through.
Can I open the PBIP project in Power BI Desktop?
Yes. PBIR is the default report format in Power BI Desktop since September 2026, and the download is a PBIP project: unzip it and open the .pbip file, select Refresh once and the sample data loads into visuals that are already bound (the empty PBIP leaves the containers unbound for your own data). Microsoft still lists projects and TMDL as preview features (as of Nov 2026), so if Desktop won't open it, enable them under File → Options and settings → Options → Preview features.
Build guides for this dashboard
Guides to the same dashboard job: which custom visuals it needs, the DAX behind them and prompts to generate them.
Dashboard job
Best Power BI Visuals for Retail AnalyticsThe best Power BI visuals for retail analytics — store heatmaps, category Pareto, basket Sankeys, promotional…
Team
Power BI for retailStore league tables, category Paretos and the weekly trading calendar: retail views that make a Monday trading meeting short.
KPI cards for this layout
Headline numbers drawn by one DAX SVG measure each, for the Card visual or a table row.
Want the headline numbers to look like cards rather than plain values? Browse the KPI card gallery or build your own in the SVG measure builder.
Related templates
E-commerce Performance
Retail & e-commerce
Retail Store Performance
Retail & e-commerce
Restaurant Performance
Hospitality
Keep exploring
61 hand-designed Power BI page layouts by department.
80 contrast-checked theme JSON files, light and dark.
Page backgrounds at 1280×720 and 1920×1080 with visual positions.
3,034 icons in 40 categories as SVG, PNG, DAX or theme icon JSON.
Make the Retail Merchandising: Sell-Through template yours
Swap in your brand colours and logo, move panels, add icons and generate missing visuals with AI, then export the background, theme JSON and PBIP project.
The design studio for Power BI. Free, in your browser, no sign-up.