1. Lighthouse

Level 6 · Why each category gets returned

The request

From Angela Rivera, Head of Customer Support

“My team wants to know why each category comes back. Not raw counts, since categories sell very different amounts: for each category, what share of its returns is damaged, late, wrong item or changed mind?”

Your goal

Join each return to its order line and product. Set result to a DataFrame with columns category, changed_mind, damaged, late, wrong_item: for each category, the share of that category's returns with each reason (each row adds up to 1), rounded to 3. One row per category, sorted A to Z.

  • Use the products DataFramenot done yet
  • Use the order_items DataFramenot done yet
  • Show exactly category changed_mind damaged late wrong_itemnot done yet

Your code

Python

Loading the editor…

    ResultPreview of products · press Run to see yours
    Preview of products
    product_idnamecategorysubcategoryunit_price
    101Vale Velvet LoveseatFurnitureSofas1659.00
    102Alder Oak Coffee TableFurnitureTables919.00
    103Orchard Rattan Dining ChairFurnitureChairs789.00
    104Upland Oak BookcaseFurnitureStorage429.00

    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.

    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
    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
    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
    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

    crosstab: a count grid from two columns

    pd.crosstab is a shortcut for the most common pivot: counting how often each pair of values occurs. You pass the two columns directly:

    pd.crosstab(web_sessions["device"], web_sessions["converted"])
    # converted  False  True
    # device
    # desktop    13978   563
    # mobile     21029   520
    # tablet      3800   110

    The first argument becomes the rows, the second the columns. Empty pairs are 0, not NaN, because a count of nothing is zero. It’s a function of the pandas module (pd.crosstab), not a DataFrame method, so the columns can even come from different tables as long as their rows line up.

    normalize: shares instead of counts

    Raw counts mislead when groups differ in size. Mobile had 520 conversions, close to desktop’s 563, but from far more sessions. The normalize argument divides by a total:

    • normalize="index": each cell ÷ its row total. Every row adds up to 1. “Of mobile sessions, what share converted?”
    • normalize="columns": each cell ÷ its column total. Every column adds up to 1. “Of converted sessions, what share were on mobile?”
    • normalize=True (or "all"): each cell ÷ the grand total.
    pd.crosstab(web_sessions["device"], web_sessions["converted"], normalize="index").round(3)
    # converted  False   True
    # desktop    0.961  0.039
    # mobile     0.976  0.024
    # tablet     0.972  0.028

    Desktop converts at 3.9% against mobile’s 2.4%: the share tells the story the counts hid.

    Choosing the direction

    Say the question out loud and listen for “of”. “Of each category’s returns, what share is damaged?” divides by the category (row) total. “Of all damaged returns, what share is Furniture?” divides by the reason (column) total. The two give different numbers from the same counts, and both are correct answers to different questions.

    margins=True adds an All row and column with the totals, which is a quick way to check the counts before you normalize: on the returns data the grand total is 1,673, every return in the table.

    Getting the category

    Returns don’t carry a category. Each return points to an order line (order_item_id), the line points to a product, and the product has the category. Two merges bring it in, and since every return matches exactly one line and every line one product, the row count stays at 1,673.

    Common mistakes

    • Normalizing in the wrong direction. Rows add up to 1 with "index", columns with "columns".
    • Comparing raw counts across groups of very different sizes.
    • Passing column names as strings, pd.crosstab("category", "reason"). crosstab takes the columns themselves, not their names.
    • Reporting shares without the counts behind them. Furniture’s 45.6% damaged rests on only 103 returns; say so.

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