1. Lighthouse

Level 5 · Do pricier products sell fewer units?

The request

From Thomas Whitaker, Head of Merchandising

“Before we raise prices on the bestsellers I want to see price against units sold for the whole range. Roughly how many units do we lose for every extra dollar of price?”

Your goal

For each product, take units = the sum of quantity over order lines with quantity > 0 that belong to orders with status 'completed' (all years). Draw a scatter of products' unit_price (from products) against units, fit a straight line with np.polyfit, and set result to the slope of that line (units per extra dollar), a float rounded to 2.

  • Use the products DataFramenot done yet
  • Use the orders DataFramenot done yet
  • Store a number in resultnot 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
    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
    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

    One point per thing

    A scatter plot answers “do two numbers move together?”. Each point is one observation, here one product: its list price across, its units sold up. Build that table first, one row per product:

    units = lines.groupby("product_id", as_index=False).agg(units=("quantity", "sum"))
    per_product = products[["product_id", "unit_price"]].merge(units, on="product_id")
    len(per_product)   # 120 products, all sold at least once

    Then draw:

    fig, ax = plt.subplots()
    ax.scatter(per_product["unit_price"], per_product["units"], alpha=0.6)
    ax.set_xlabel("List price (USD)")
    ax.set_ylabel("Units sold")

    alpha makes the dots partly transparent, so where points pile up you see a darker patch instead of one blob. The pandas version is per_product.plot(kind="scatter", x="unit_price", y="units").

    A trend line with np.polyfit

    The cloud slopes down, but by how much? np.polyfit(x, y, 1) fits the straight line (degree 1) closest to all the points and returns its slope and intercept:

    slope, intercept = np.polyfit(per_product["unit_price"], per_product["units"], 1)
    # slope ≈ -0.56, intercept ≈ 608
    x = np.array([0, per_product["unit_price"].max()])
    ax.plot(x, slope * x + intercept, color="red")

    Two x values are enough to draw a straight line. The slope reads in the units of the axes: y units per x unit, so here units sold per dollar of price. -0.56 means that, across the range, each extra $100 of list price goes with about 56 fewer units sold.

    Reading it honestly

    The best seller, the Delancey Brass Vase at $19.99, sold 2,320 units; the Laurel Teak Solar Lantern at $1,289 sold 6. But the points are widely scattered around the line, so the slope is a summary of the whole range, not a forecast for one product. It also compares different products: it doesn’t say what would happen if Thomas raised the price of one of them. That needs a price test. A scatter shows that two things go together; it doesn’t prove that one causes the other.

    Common mistakes

    • Plotting every order line instead of one point per product: thousands of overlapping dots.
    • Passing y before x to polyfit, which flips the meaning of the slope.
    • Reading the slope as cause and effect. It describes how the points lie, nothing more.
    • Using ax.plot with markers for a scatter and forgetting linestyle="", which joins the points with lines in table order.

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