How do I create a weekly markdown dashboard for my boutique?
Build a Google Sheet with columns for style name, current tier, units sold this week, quantity on hand, weeks of supply, weeks remaining, and an action flag. Review it every Monday.
“This is the answer to 'should I panic.' You open the sheet Monday morning. Red items move to the next tier. Green items stay.”
A Monday markdown dashboard is a simple Google Sheet that takes about 20 minutes to review each week. Set up columns for SKU or style name, category, current discount tier, units sold this week, current on-hand quantity, updated weeks of supply, weeks remaining in the season, and an action flag.
The action flag is a basic formula: if weeks of supply is greater than weeks remaining, it reads 'move down.' Otherwise it reads 'hold.' Add conditional formatting so red highlights items that need to drop a tier and green highlights items that are fine. This turns your dashboard into an instant visual decision tool.
The key benefit is replacing reactive, emotion-driven discounting with a consistent data ritual. Instead of panicking on a slow Saturday and slashing prices, you open the sheet Monday morning, move red items to the next tier, leave green items alone, and go about your week. Toolio's research specifically recommends weekly sell-through reporting over monthly post-mortems for this reason.
Listen to the full episode: Episode 25: How to Price Your Summer Sale to Protect Margins While Clearing Inventory (The Math Every Boutique Needs)
More answers from this episode
- How do I build a tiered markdown ladder for my boutique's summer sale?
- How do I calculate my true cost per piece for boutique inventory?
- How do I set up Shopify compare-at price for a sale correctly?
- Should I discount basics and trendy pieces the same way during a summer sale?
- Should I put my best-selling styles on sale during a summer clearance?
- Should I try anything before putting summer inventory on sale?
Source: BoutiquePulse podcast. Last updated: 2026-06-03 · Sourcing & methodology · Corrections log