1. Lighthouse

Level 3 · Combine conditions with & and |

The request

From Daniel Brooks, Head of Operations

“I'm auditing what customers pay us for shipping on our own channels. I need completed web and app orders where the customer actually paid a shipping fee.”

Your goal

Set result to a DataFrame of orders with status 'completed', channel 'web' or 'app', and shipping_fee greater than 0, with only the columns order_id, customer_id, channel, shipping_fee. Keep the original row order and index.

  • Use the orders DataFramenot done yet
  • Show exactly order_id customer_id channel shipping_feenot done yet
  • 1,996 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

    Combining masks

    Real filters have several conditions. pandas combines boolean masks with three operators:

    operator meaning Python keyword it replaces
    & both are true and
    | at least one is true or
    ~ not not
    completed = orders["status"] == "completed"
    paid_ship = orders["shipping_fee"] > 0
    
    orders[completed & paid_ship]
    orders[completed | paid_ship]
    orders[~completed]               # everything that isn't completed

    Why not and and or? Those Python keywords need a single True or False, and a Series of 12,000 values isn’t one. Using them raises ValueError: The truth value of a Series is ambiguous. When you see that error, you’ve used and/or where you needed &/|.

    Parentheses are required

    & and | bind more tightly than == and >. Without brackets, orders["status"] == "completed" & orders["shipping_fee"] > 0 is read as orders["status"] == ("completed" & orders["shipping_fee"]) > 0 and fails. Wrap every comparison:

    (orders["status"] == "completed") & (orders["shipping_fee"] > 0)

    Naming each mask, as above, avoids the problem entirely and makes long filters readable.

    isin: one of several values

    To match any value from a list, isin beats a chain of |:

    orders["channel"].isin(["web", "app"])
    # same as
    (orders["channel"] == "web") | (orders["channel"] == "app")

    isin returns a mask like any comparison, so it combines with & the same way. Its opposite is ~orders["channel"].isin([...]), the pandas version of “not in”.

    Putting it together with loc

    mask = (
        (orders["status"] == "completed")
        & orders["channel"].isin(["web", "app"])
        & (orders["shipping_fee"] > 0)
    )
    orders.loc[mask, ["order_id", "customer_id", "channel", "shipping_fee"]]

    Wrapping the expression in brackets lets you break it across lines, one condition per line, which is how most teams format filters.

    Check your filter

    Before you hand over a filtered table, check the counts make sense:

    mask.sum()                                  # rows kept
    orders.loc[mask, "channel"].value_counts()  # only web and app?
    orders.loc[mask, "shipping_fee"].min()      # above 0?

    These three lines take seconds and catch inverted conditions, wrong values and missing brackets.

    query as an alternative

    pandas also has orders.query("status == 'completed' and shipping_fee > 0"), where and/or are allowed because the string is parsed by pandas. It’s tidy for quick exploration. Boolean masks are more common in production code because they work with any Python variable or function without string building.

    Common mistakes

    • Using and/or instead of &/|.
    • Missing parentheses around comparisons.
    • Using | when the brief needs &: “completed orders from web or app” is completed & (web | app), not completed | web | app.

    If you know SQL

    isin is IN (...), & is AND, | is OR and ~ is NOT.