1. Lighthouse

Level 8 · How the channel mix shifted

The request

From Robert Kim, Chief Operating Officer

“Ops plans packing capacity by channel. Show me each channel's share of orders for 2023, 2024 and 2025 in one chart. How fast is the app taking over?”

Your goal

Count orders (all statuses) per year and channel, and turn the counts into each channel's share of that year's orders (rows add up to 1), rounded to 3. Set result to a DataFrame with columns year (2023, 2024, 2025), app, marketplace, web, sorted by year. Draw it as a stacked bar chart.

  • Use the orders DataFramenot done yet
  • Show exactly year app marketplace webnot done yet
  • 3 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

    What a total is made of

    “How much of the total comes from each part?” is a composition question, and the chart for it is a stacked bar: one bar per period, split into segments. When the totals differ a lot between periods but you care about the mix, stack shares, so every bar is 100% tall and only the segments move.

    Counts, then shares

    pd.crosstab counts rows for each pair of values:

    year = orders["order_date"].dt.year.rename("year")
    counts = pd.crosstab(year, orders["channel"])
    #        app  marketplace   web
    # 2023   819          464  1888
    # 2024  1366          601  2079
    # 2025  2135          702  1946

    To get shares within a year, divide each row by that row’s total. sum(axis=1) adds across the columns, giving one total per year, and div(..., axis=0) divides row by row:

    shares = counts.div(counts.sum(axis=1), axis=0).round(3)
    #         app  marketplace    web
    # 2023  0.258        0.146  0.595
    # 2025  0.446        0.147  0.407

    Stacked and grouped bars in pandas

    ax = shares.plot(kind="bar", stacked=True, rot=0)   # stacked: composition
    ax = counts.plot(kind="bar", rot=0)                  # grouped: compare channels side by side

    Grouped bars answer “which is bigger?” within each year. Stacked bars answer “how big is the whole, and what is it made of?”. rot=0 keeps the year labels upright.

    In plain matplotlib a stack is built by hand: each segment starts where the previous one ended, which is what bottom= does:

    fig, ax = plt.subplots()
    bottom = np.zeros(len(shares))
    for channel in shares.columns:
        ax.bar(shares.index.astype(str), shares[channel], bottom=bottom, label=channel)
        bottom += shares[channel].values
    ax.legend()

    Reading the shift

    In 2023 the website took 59.5% of orders and the app 25.8%. By 2025 the app had 44.6% and the website 40.7%: the app passed the website in order count. The marketplace barely moved, 14.6% to 14.7%. Only the bottom segment of a stack can be compared exactly, because the others float, so put the segment your story is about at the bottom. With only three parts of one total, a pie per year would also work, but three pies side by side are harder to compare than three bars.

    Common mistakes

    • Dividing by column totals (counts / counts.sum()) instead of row totals.
    • Stacking raw counts when the question is about the mix: the growing totals hide the shift.
    • Too many segments. Past five or six, group the small ones into “other”.
    • Forgetting the legend, or leaving it on top of the bars. bbox_to_anchor=(1, 1) moves it to the right of the chart, where it covers nothing.

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