1. Lighthouse

Level 5 · Lighting in a price band

The request

From Jordan Reyes, Head of Marketing

“Our 'Light for less' campaign covers lighting from $50 to $200, both ends included. Can you list those products from cheapest to most expensive? Alphabetical where prices match, please.”

Your goal

Set result to a DataFrame of products with category 'Lighting' and unit_price between 50 and 200 inclusive, columns name and unit_price, sorted by unit_price ascending then name ascending, with the index reset.

  • Use the products DataFramenot done yet
  • Show exactly name unit_pricenot done yet
  • 10 rows, sorted as askednot 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
    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
    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

    Ranges with between

    “From $50 to $200” is a range. You could write two comparisons:

    (products["unit_price"] >= 50) & (products["unit_price"] <= 200)

    between says the same thing more clearly:

    products["unit_price"].between(50, 200)

    By default both ends are included, matching how people usually speak about ranges. Change it with inclusive="left", "right" or "neither" when the brief says “under $200” or “over $50”. Always check which one the brief means. The Harbor & Pine catalog has products at exactly $189 and $159, and you’ll find edge cases like a $200 product in real catalogs all the time.

    between works on dates too, which you’ll use constantly:

    orders[orders["order_date"].between("2025-11-01", "2025-11-30 23:59:59")]

    Filtering on text

    Text columns have a .str accessor with vectorised string methods that return masks:

    products["name"].str.contains("Lamp")              # name includes 'Lamp'
    products["name"].str.contains("lamp", case=False)  # ignore case
    products["name"].str.startswith("Oak")
    products["subcategory"].isin(["Pendants", "Chandeliers"])

    So “every product with Brass in the name” is products[products["name"].str.contains("Brass")].

    Two cautions with str.contains:

    • It treats the pattern as a regular expression by default, so characters like (, . and + have special meanings. Pass regex=False to match text literally.
    • On a column with missing values, it returns NaN for those rows, and using that as a mask fails. Pass na=False to treat missing text as “doesn’t contain”.

    Building the answer

    mask = (products["category"] == "Lighting") & products["unit_price"].between(50, 200)
    (
        products.loc[mask, ["name", "unit_price"]]
        .sort_values(["unit_price", "name"])
        .reset_index(drop=True)
    )

    sort_values with a list sorts ascending on every column by default, which is what this brief wants.

    The price is a snapshot

    products.unit_price is the current list price. Some products had a price rise in March 2025, so older order lines in order_items show a lower price paid. For a campaign list, the current price is right. For revenue, always use the price on the order line. Picking the right column for the question is part of the job.

    Check the edges

    After filtering a range, look at the smallest and largest values that made it through: result["unit_price"].agg(["min", "max"]). If the brief says $50 to $200 and the minimum is $54.99, check whether a product at exactly $50 exists and was wrongly excluded. Edge checks like this take seconds and catch the inclusive/exclusive mistakes that reviewers love to find.

    Common mistakes

    • Using between when the brief says “under” and including the upper bound.
    • Forgetting na=False on str.contains for a column with gaps.
    • Searching with the wrong case: str.contains("lamp") misses “Floor Lamp”.