Weekly Sales and Inventory Review
Weekly review run by the store manager to compare sell-through against on-hand, identify reorder and markdown candidates, and flag aged or obsolete SKUs before the next buy. Designed for specialty retail and small chains running on Lightspeed, Shopify POS, or NetSuite.
Sales Performance Review
-
Pull weekly sales by department and SKU
-
Compare comp sales to prior year
-
Review UPT, ATV, and conversion rate
Pull units per transaction, average transaction value, and conversion against door count from the POS dashboard. Flag any associate whose UPT is 30%+ below team average for coaching at the next shift huddle.
-
Identify top and bottom 10 SKUs
Rank by sell-through and gross margin, not just units sold. A high-volume low-margin SKU that's eating end-cap real estate is a different problem than a slow seller in a back-corner four-way.
Collects file -
Evaluate active promotions and GWP
Check redemption rate on this week's BOGO, GWP, or loyalty offers. Note any promo where the discount cut margin below the cost-protection floor — those need district manager review before they renew.
Inventory Position
-
Run on-hand vs. on-order report
Pull available-to-sell, on-PO, and in-transit by SKU from the inventory system (NetSuite, Cin7, Lightspeed). Reconcile against any open receiving discrepancies from the past week before treating the numbers as truth.
-
Calculate weeks of supply by category
WOS = on-hand ÷ average weekly sell-through. Categories under 2 WOS are reorder candidates; over 12 WOS are markdown candidates. Adjust thresholds for seasonal departments (swimwear in May vs. October).
-
Flag aged and obsolete inventory
Run the aging report for stock over 90 days on hand. Common gotcha: returned merchandise that re-enters inventory at original receipt date masks true age — filter on last-sold date, not received date.
Collects list -
Verify cycle count variances from this week
Pull this week's cycle count results from the stockroom team. Variance over $250 or 5% on a single SKU should not be auto-adjusted — investigate for receiving error, mis-scan, mis-labeled stock, or shrink before posting the adjustment.
Collects list
Markdown and Clearance Decisions
-
Build the markdown candidate list
Pull SKUs over 12 weeks of supply or under 20% sell-through after 60 days. Note current markdown stage (first, second, third, terminal) so the next reduction follows the markdown matrix rather than guesswork.
-
Review margin floor before approving cuts
Any markdown that drops the SKU below cost requires district manager sign-off — store managers can't unilaterally approve below-cost. Document the GMROI impact in the markdown log.
Collects list Collects paragraph -
Escalate below-cost markdowns to district manager
Send the markdown list with cost, current price, proposed price, and weeks-on-hand. DM has 48 hours to approve, counter, or reject before the markdown event is staged for the floor.
-
Update price tags and POS at register
Print new tags from the POS markdown batch. Common mistake: floor tags reprinted but POS price not pushed — register rings the old price, customer disputes, manager override eats time. Verify both before opening.
Replenishment and Reorders
-
Build the reorder list from low-WOS SKUs
Pull SKUs under 2 weeks of supply that aren't being walked down intentionally. Cross-reference vendor lead time — a 3-week lead time on a 2-WOS item means you're already stocking out before the PO arrives.
Collects number -
Submit POs to vendors or DC
For vendor-direct, submit through the vendor portal with the PO number from the inventory system. For DC replenishment, file the allocation request with the planner. Confirm receipt acknowledgment within 24 hours.
-
Process return-to-vendor on defective stock
Pull RTV-eligible items per vendor agreement (defective, recalled, or seasonal carry-back). Most vendor agreements require RTV claims within 30 days of receipt — file late and the credit is forfeit.
Weekly Close and Reporting
-
Document customer feedback themes
Pull NPS, loyalty CRM notes, and any logged complaints from the past week. Look for repeat themes — three customers asking for a sold-out size in a week is a real signal, not noise.
-
Submit weekly summary to district manager
Include comp sales, traffic, conversion, top/bottom SKUs, markdown actions taken, and reorder PO total. The DM uses this for the Monday district call — late submissions delay the whole region's review.
Collects file Collects signature
Use this template
Copy it to your account, customize the steps, and run it with your team in minutes.
Browse hundreds of free templates across every team and industry.
Back to template libraryRelated templates
More workflows your team can run.
Run Weekly Sales and Inventory Review with your team
Customize the steps, assign roles, set a schedule, and keep a complete record for every run.