# Weekly Sales Summary {% hint style="info" %} **Quick Answer:** A weekly sales report shows sell-in units and revenue by SKU and channel for the past 7 days, compared to the prior week and your active forecast. In Moselle, Mo can build one in under 5 minutes from your live data. {% endhint %} ## What is a Weekly Sales Report? **A weekly sales report** is a recurring snapshot of sell-in performance across your SKUs and channels for a rolling 7-day window. It compares this week against last week and — when layered with your active forecast — surfaces where demand is running ahead, behind, or on track. Unlike one-off sales lookups, a weekly cadence gives you a consistent rhythm for spotting early signals: a channel pulling ahead, a SKU starting to soften, or a promotional lift that carried over longer than expected. ### Why Weekly Sales Reports Matter * **Catch trends early:** Week-over-week comparisons reveal momentum shifts before they show up in monthly rollups * **Validate your forecast:** Comparing actuals against forecasted demand each week keeps your plan grounded in what's actually happening * **Channel accountability:** Breaking down sales by channel shows where your volume is coming from and whether channel mix is shifting * **Stakeholder alignment:** A consistent weekly output keeps sales, ops, and finance teams working from the same numbers ## What Makes a Great Weekly Sales Report? The most useful weekly sales reports are: * **Channel-separated:** Blending DTC, wholesale, and Amazon into a single number hides what's actually driving — or dragging — performance * **Comparable:** Side-by-side this week vs. last week makes trends immediately visible * **Forecast-anchored:** Showing actuals against the active forecast turns a descriptive report into a diagnostic one * **SKU-level:** Brand-level revenue summaries look clean but bury the story. SKU-level data is where the decisions live ### Key Metrics to Include | Metric | What It Tells You | | ----------------------- | ---------------------------------------------------------- | | Units sold (this week) | Volume performance for the current period | | Revenue (this week) | Dollar performance for the current period | | Units sold (prior week) | Baseline to measure week-over-week change | | Week-over-week change | Absolute and percentage delta in units or revenue | | Forecast variance | Gap between actuals and the active forecast for the period | ## Before You Start: Make Sure Your Data Is Clean * [ ] **Sales are fully synced.** Confirm your connected channels have no gaps or delays in order data before running the report * [ ] **Returns and cancellations are excluded.** Make sure you're reporting on net sell-in, not gross orders * [ ] **Your time window is clear.** "This week" should be defined consistently — rolling 7 days or a fixed Mon-Sun window — so comparisons stay apples-to-apples * [ ] **Your active forecast is current.** If the forecast hasn't been updated recently, the variance column will be misleading ## How to Build a Weekly Sales Report with Mo **Time Required:** 5 minutes **Difficulty:** Beginner {% stepper %} {% step %} ### Open Mo and Set Your Context Click **Mo** in the left sidebar to open the chat page. Start with a prompt that specifies the time window, output type, and scope: > "Show me weekly sell-in by SKU for all channels, this week vs. last week" > "Give me a weekly sales summary by channel — units and revenue — for the past 7 days" > "Which SKUs had the biggest week-over-week sales change this week?" Be specific from the start. Mo builds a better first output when you define the time period and the grouping upfront. {% endstep %} {% step %} ### Review the Output Mo will return a SKU-level or channel-level breakdown showing units and revenue for this week and last week. Scan for: * **Large positive swings** — Is a channel or SKU unexpectedly ahead? Confirm whether it reflects real demand or a timing difference * **Large negative swings** — Is something softening? Check whether it's a data sync issue or a genuine demand signal * **Flat performers** — Consistent week-over-week output is a healthy signal for planning purposes {% endstep %} {% step %} ### Layer in Forecast Variance Once you have the week-over-week view, add your forecast to understand whether performance is on plan: > "Add a vs. forecast column to this report" > "Which SKUs are more than 15% above or below forecast this week?" Forecast variance is the most actionable layer. SKUs running significantly above forecast may need a replenishment review. SKUs running below may indicate a demand shift worth adjusting. {% endstep %} {% step %} ### Refine and Filter Narrow or expand the report to match your focus for the week: * Add `"for Sephora only"` or `"excluding Amazon"` to filter by channel * Add `"ranked by revenue"` to sort the output by dollar impact * Add `"show only SKUs with more than 10% week-over-week change"` to isolate movers Common follow-up asks: > "Which SKUs had the biggest week-over-week revenue decline?" > "Break this down by channel for just our top 20 SKUs" > "Export this as an Excel file" > {% endstep %} {% step %} ### Save as a Favourite Once the report is right, save it so you can run it again with one click each week. Type **"Save this chat as a prompt"** → copy Mo's output into a new chat to verify it runs correctly → then save it as a favourite called **Weekly Sales Recap**. {% hint style="success" %} A saved Weekly Sales Recap prompt turns a 5-minute build into a 30-second pull every Monday morning. {% endhint %} {% endstep %} {% endstepper %} ## How to Read Your Weekly Sales Report | Signal | What It Means | Recommended Action | | -------------------------------- | --------------------------------------- | ----------------------------------------------------- | | Revenue up >20% week-over-week | Strong demand surge or promotional lift | Check inventory coverage — reorder if WOS is dropping | | Revenue down >20% week-over-week | Demand softening or channel data gap | Verify sync, then check forecast alignment | | Above forecast by >15% | Demand running ahead of plan | Pull forward replenishment review | | Below forecast by >15% | Demand lagging the plan | Revisit forecast, check channel sell-through | | Flat week-over-week | Stable demand | Maintain current plan | ## Best Practices for Weekly Sales Reports **Run it on the same day every week.** A Monday morning pull gives you a clean prior-week view before the new week's orders accumulate. Consistency in timing makes week-over-week comparisons more reliable. **Don't blend sell-in and sell-through in the same report.** Sell-in (what shipped to retailers) and sell-through (what consumers bought) measure different things. Keep them in separate views to avoid misreading performance. **Pair the sales report with your WOS report.** Revenue trends only matter if you have enough inventory to support them. A SKU running 30% above forecast needs an urgent coverage check, not just a pat on the back. **Flag outliers before distributing.** A missing channel sync or a bulk order that closed late can skew weekly numbers significantly. A quick sanity check before sharing keeps the conversation focused on real signals. ## Frequently Asked Questions
What is the difference between sell-in and sell-through? Sell-in measures units shipped from your warehouse to retail partners or fulfillment. Sell-through measures units sold from retail shelves to end consumers. For DTC brands, they are effectively the same. For wholesale brands, the gap between sell-in and sell-through is a key signal of retail health.
Should I use rolling 7 days or a fixed Mon–Sun window? Either works — the important thing is consistency. Rolling 7 days keeps the report always current. A fixed Mon–Sun window makes week-over-week comparisons cleaner because you're always comparing the same calendar slice. Specify your preference in the prompt so Mo applies it consistently.
How do I handle weeks with major promotions or events? Flag promotional weeks explicitly when sharing the report. A 40% revenue spike during a sale does not tell you the same story as a 40% organic spike. Note the promotion in context and compare against the same promotional week in a prior year if available.
Can I include multiple channels in a single report? Yes. Mo can break down performance by channel side by side. Ask for "all channels" in your initial prompt or add "break this down by channel" as a follow-up to split the output.
## Related Guides {% content-ref url="/pages/Dlc8GAJGV7FQH8Q9j9gA" %} [Mo Custom Reports](/analytics/reporting/mo-reports/mo-custom-reports.md) {% endcontent-ref %} {% content-ref url="/pages/ZiMAO4xUpdTQI2yoZWu5" %} [Weeks of Supply (WOS) Report](/analytics/reporting/mo-reports/mo-standard-reports/wos-report.md) {% endcontent-ref %} {% content-ref url="/pages/aYMGZMjVZa0NMZNaCeKo" %} [Forecast vs Actuals](/analytics/reporting/mo-reports/mo-standard-reports/forecast-vs-actuals.md) {% endcontent-ref %} {% content-ref url="/pages/DAsnRIRTbbjM6bgR0RLM" %} [Save Your Favourite Prompts](/mo/tips/save-favourite-prompts.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://learn.moselle.io/analytics/reporting/mo-reports/mo-standard-reports/weekly-sales-summary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.