1. Lighthouse

Level 3 · A 7-day average for the dashboard

The request

From Jordan Reyes, Head of Marketing

“The daily order chart for last holiday season jumps around too much to read. Can you add a 7-day average next to the daily count for November and December 2025?”

Your goal

Count orders per day (all statuses, every calendar day). Set result to a DataFrame with columns order_date (the day), n_orders (orders that day) and avg_7d (mean of n_orders over that day and the 6 days before it, rounded to 2), for the days 2025-11-01 to 2025-12-31 only (61 rows), sorted by order_date ascending, index reset. The first rows of November must use the October days before them, not NaN.

  • Use the orders DataFramenot done yet
  • Show exactly order_date n_orders avg_7dnot done yet
  • 61 rows, sorted as askednot done yet

Your code

Python

Loading the editor…

    ResultPreview of orders · press Run to see yours
    Preview of orders
    order_idcustomer_idorder_datestatuschannel
    10011252023-01-01 20:51:19completedweb
    10021562023-01-02 07:58:46completedweb
    1003222023-01-02 10:25:27completedmarketplace
    1004482023-01-02 11:21:51completedmarketplace

    Mote checks your result

    Press Run. Each row that matches the goal becomes a firefly in your lantern.

    DataFrames

    Loaded for you as pandas DataFrames, plus pd and np.

    orders12,000 rows · 7 columns
    • order_idinteger
    • customer_idinteger
    • order_datetimestamp
    • statusvarchar
    • channelvarchar
    • shipping_feedecimal
    • coupon_codevarchar
    First 5 rows of orders
    order_idcustomer_idorder_datestatuschannelshipping_feecoupon_code
    10011252023-01-01 20:51:19completedweb0.00NaN
    10021562023-01-02 07:58:46completedweb0.00NaN
    1003222023-01-02 10:25:27completedmarketplace4.99WELCOME10
    1004482023-01-02 11:21:51completedmarketplace4.99WELCOME10
    1005822023-01-02 11:43:36completedweb0.00WELCOME10
    customers2,018 rows · 9 columns
    • customer_idinteger
    • first_namevarchar
    • last_namevarchar
    • emailvarchar
    • cityvarchar
    • statevarchar
    • signup_datedate
    • segmentvarchar
    • referral_sourcevarchar
    First 5 rows of customers
    customer_idfirst_namelast_nameemailcitystatesignup_datesegmentreferral_source
    1OwenHudsonowen.hudson@icloud.comSan FranciscoCA2022-06-02consumersearch
    2DouglasMendozadmendoza69@gmail.comAtlantaGA2022-06-02consumerNaN
    3HenryBrookshbrooks@lakesidecafe.comLos AngelesCA2022-06-04businessNaN
    4BrianGrahambgraham@bluecedarhomes.comSeattleWA2022-06-06businesspinterest
    5KyleJimenezkjimenez27@yahoo.comIndianapolisIN2022-06-07consumerNaN
    products120 rows · 8 columns
    • product_idinteger
    • namevarchar
    • categoryvarchar
    • subcategoryvarchar
    • unit_pricedecimal
    • unit_costdecimal
    • launched_ondate
    • is_activeboolean
    First 5 rows of products
    product_idnamecategorysubcategoryunit_priceunit_costlaunched_onis_active
    101Vale Velvet LoveseatFurnitureSofas1659.00NaN2023-09-11true
    102Alder Oak Coffee TableFurnitureTables919.00503.502024-05-16true
    103Orchard Rattan Dining ChairFurnitureChairs789.00429.872023-05-27true
    104Upland Oak BookcaseFurnitureStorage429.00214.702022-12-20true
    105Avery Leather Bed FrameFurnitureBeds449.00232.702021-08-31true
    order_items30,338 rows · 6 columns
    • order_item_idinteger
    • order_idinteger
    • product_idinteger
    • quantityinteger
    • unit_pricedecimal
    • discount_pctdecimal
    First 5 rows of order_items
    order_item_idorder_idproduct_idquantityunit_pricediscount_pct
    11001121931.990.00
    21001154311.990.00
    31002154411.990.00
    410021941149.000.00
    51002193219.990.00
    returns1,673 rows · 5 columns
    • return_idinteger
    • order_item_idinteger
    • returned_ondate
    • reasonvarchar
    • refund_amountdecimal
    First 5 rows of returns
    return_idorder_item_idreturned_onreasonrefund_amount
    1142023-01-10damaged83.69
    2422023-01-10wrong_item19.99
    31052023-01-14wrong_item10.99
    4242023-01-16changed_mind26.99
    51262023-01-16late20.99
    employees60 rows · 8 columns
    • employee_idinteger
    • first_namevarchar
    • last_namevarchar
    • departmentvarchar
    • titlevarchar
    • manager_idinteger
    • hire_datedate
    • salaryinteger
    First 5 rows of employees
    employee_idfirst_namelast_namedepartmenttitlemanager_idhire_datesalary
    1CatherineHaleExecutiveChief Executive OfficerNaN2016-03-01285000
    2RobertKimExecutiveChief Operating Officer12017-01-09235000
    3MeganCollinsSalesHead of Sales12018-04-16172000
    4ChloeGutierrezSalesAccount Executive32020-01-2172000
    5FrankBellSalesAccount Executive32023-05-2173000
    web_sessions40,000 rows · 7 columns
    • session_idinteger
    • customer_idinteger
    • started_attimestamp
    • devicevarchar
    • sourcevarchar
    • pages_viewedinteger
    • convertedboolean
    First 5 rows of web_sessions
    session_idcustomer_idstarted_atdevicesourcepages_viewedconverted
    1NaN2023-01-01 23:02:24mobilepaid1false
    2182023-01-01 15:07:49desktoppaid1false
    3NaN2023-01-01 16:55:46desktopdirect7false
    4NaN2023-01-01 12:43:28mobileorganic3false
    5NaN2023-01-01 13:06:21mobilesocial2false
    marketing_spend3,276 rows · 3 columns
    • spend_datedate
    • channelvarchar
    • amountdecimal
    First 5 rows of marketing_spend
    spend_datechannelamount
    2023-01-01paid492.99
    2023-01-01email37.38
    2023-01-01social200.53
    2023-01-02paid709.13
    2023-01-02email64.13

    The lesson

    Why smooth a daily series

    Daily numbers are noisy. Harbor & Pine’s orders swing with the day of the week, with paydays and with promotions, so a daily chart looks like a seismograph. A moving average (also called a rolling average) replaces each day with the mean of a window of days ending on it. A 7-day window covers every weekday exactly once, so the weekly rhythm cancels out and the trend shows.

    rolling(n)

    rolling(7) slides a window of 7 rows along the series; the aggregation after it runs on every window:

    daily = orders.set_index("order_date").resample("D").size()
    daily.head(8).tolist()
    # [1, 8, 6, 4, 10, 9, 5, 8]
    daily.rolling(7).mean().round(2).head(8).tolist()
    # [nan, nan, nan, nan, nan, nan, 6.14, 7.14]

    The 7th value, 6.14, is the mean of the first seven days (43 orders / 7). The first six values are NaN because a full window of 7 rows doesn’t exist yet. If you’d rather get a value from the first day on, pass min_periods: rolling(7, min_periods=1) averages whatever rows are available, so the first three values become 1.0, 4.5 and 5.0. That’s convenient but misleading at the start of a chart, which is why the default is strict.

    .sum(), .max(), .median() and .std() work after rolling too. A rolling 7-day sum is “orders in the last week”, another common dashboard number.

    The window counts rows, not days. That’s why the daily series comes from resample("D"): it has exactly one row per calendar day, zeros included, so 7 rows really are 7 days. On a series with missing days you’d use a time-based window like rolling("7D") instead.

    Window first, filter second

    Jordan only wants November and December. If you filter first, the window has nothing to look back on:

    daily.loc["2025-11-01":].rolling(7).mean().head(7)   # six NaN, then 17.71

    Compute the rolling mean on the full history and cut the date range at the very end. Then 1 November 2025 averages 26 October to 1 November: 14.29.

    What the holiday season looks like

    On Black Friday, 28 November 2025, orders jump from 24 to 56. The daily count spikes for four days (56, 51, 58, 67) and drops back to 24 on 2 December, but the 7-day average keeps climbing for a few days, because the spike is still inside the window. It peaks at 44.14 on 4 December, the last day whose week still contains the whole Black Friday weekend and Cyber Monday. A moving average always lags: it tells you the level of the last week, not of today.

    Common mistakes

    • Filtering the date range before rolling, which leaves NaN at the start of the period.
    • Rolling over raw orders instead of a daily series: the window is 7 orders, not 7 days.
    • Using min_periods=1 without saying so, which makes the first days look calmer than they were.
    • Reading the peak of a moving average as the peak day. It lags the real spike.

    Pick what may run on this site. You can change this any time from "Cookie settings" at the bottom of every page.