1. Lighthouse

Level 8 · Products that sold in only one quarter

The request

From Thomas Whitaker, Head of Merchandising

“Which products sold in Q1 2025 but not in Q2, or the other way round? I want to see what dropped off and what's new before the summer catalog goes out.”

Your goal

Build units per product (sum of quantity) for orders placed in Q1 2025 and for Q2 2025 (the q1 and q2 order tables are given). Outer-merge the two on product_id and set result to a DataFrame of the products that appear in only one quarter: columns product_id, q1_units, q2_units (NaN where the product didn't sell that quarter), sorted by product_id ascending, index reset.

  • Use the orders DataFramenot done yet
  • Use the order_items DataFramenot done yet
  • Show exactly product_id q1_units q2_unitsnot 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
    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
    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
    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

    Four kinds of merge

    how= decides which keys survive a merge:

    • "inner" (the default): only keys found on both sides.
    • "left": every key from the left table, with NaN where the right has no match.
    • "right": the mirror image, every key from the right table. a.merge(b, how="right") keeps the same rows as b.merge(a, how="left"), only the column order differs, so most people just write the left version.
    • "outer": every key from either side, with NaN wherever one side is missing.

    Thomas wants products missing from either quarter, so only an outer merge keeps everything he needs.

    Units per quarter, then outer

    First reduce each quarter to one row per product. q1[["order_id"]] keeps only the order ids, so merging with order_items brings in the lines of Q1 orders and nothing else:

    q1_units = q1[["order_id"]].merge(order_items, on="order_id").groupby(
        "product_id", as_index=False
    ).agg(q1_units=("quantity", "sum"))

    107 products sold in Q1 and 111 in Q2. The outer merge gives 116 rows:

    both = q1_units.merge(q2_units, on="product_id", how="outer", indicator=True)
    both["_merge"].value_counts()   # both 102, right_only 9, left_only 5

    indicator=True adds the _merge column, which says where each row came from. It’s the easiest way to filter the “only on one side” rows, and it doubles as a check: 102 + 9 + 5 = 116.

    Reading the result

    The five Q1-only products include the Sable Oak Daybed, the Elm Cashmere-Blend Area Rug and the Cedar Ceramic Candle, all discontinued. The nine Q2-only products include the Rowan Walnut Dresser (launched 2025-04-21) and the Pacifica Black Metal Arc Lamp (2025-04-05), plus garden beds, grill tools and planters that only sell once outdoor season starts. A product missing from Q2 shows NaN in q2_units, not 0: pandas can’t know whether “no row” means zero sales or missing data, so it leaves that decision to you.

    Common mistakes

    • Using the default inner merge, which throws away exactly the one-sided products.
    • Merging the raw order lines of the two quarters instead of per-product totals, which fans out.
    • Filtering on q2_units == 0 to find missing products. Missing shows up as NaN, not 0.
    • Forgetting to drop the _merge column from the final table.

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