1. Lighthouse

Level 8 · Units sold per product tag

The request

From Thomas Whitaker, Head of Merchandising

“The site team exported the tags we put on eight products. Each product can have several tags, and the export lists them in one cell. How many units have we sold under each tag?”

Your goal

Turn tags_export['tags'] into real lists (a missing cell counts as no tags), give each product and tag its own row, and add the quantity of every line in order_items for that product (all order lines, as they are). Set result to a DataFrame with columns tag and units (total quantity per tag), one row per tag, sorted by units descending then tag ascending, index reset. Products without tags are left out.

  • Use the order_items DataFramenot done yet
  • Show exactly tag unitsnot done yet
  • 4 rows, sorted as askednot done yet

Your code

Python

Loading the editor…

    ResultPreview of order_items · press Run to see yours
    Preview of order_items
    order_item_idorder_idproduct_idquantityunit_price
    11001121931.99
    21001154311.99
    31002154411.99
    410021941149.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.

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

    Lists inside cells

    Sometimes one cell holds several values: a product’s tags, a job’s required skills, the answers to a “pick all that apply” question. Stored in a DataFrame, that’s a column whose cells are lists. You can’t group or count by it directly, because groupby needs one value per row.

    explode fixes that. It gives every list item its own row and repeats the other columns:

    df = pd.DataFrame({"product_id": [101, 113], "tags": [["statement", "bestseller"], ["bestseller"]]})
    df.explode("tags")
    #    product_id        tags
    # 0         101   statement
    # 0         101  bestseller
    # 1         113  bestseller

    The index labels repeat (0, 0, 1), which tells you which rows came from the same original row. Add .reset_index(drop=True) if you want a clean 0, 1, 2. An empty list becomes one row with NaN, and a missing cell stays missing.

    When the lists arrive as text

    Files can’t store Python lists. A CSV or a database export writes them as text, so after loading, the cell is the string "['statement', 'bestseller']", square brackets and quotes included. explode treats a string as a single value and leaves it alone.

    ast.literal_eval (from Python’s built-in ast module) reads such text back into the real object. It only accepts literals: lists, dicts, tuples, numbers, strings, True, False and None. Unlike eval, it never runs code, so it’s safe on data from a file.

    import ast
    ast.literal_eval("['gift-idea', 'small-space']")   # ['gift-idea', 'small-space'], a list

    Apply it to the column, guarding against missing cells, which are not strings:

    col.apply(lambda x: ast.literal_eval(x) if isinstance(x, str) else [])

    A worked example: counting tags

    After converting and exploding the eight-product export, there are 12 rows: one per product and tag, plus a NaN row for the product with an empty list and one for the product with a missing cell. Counting tags is then an ordinary value_counts:

    exploded["tags"].value_counts()
    # gift-idea      4
    # bestseller     3
    # statement      2
    # small-space    1

    Joining the exploded rows to order_items on product_id brings in every order line of each product, once per tag. A product with two tags has its units counted under both, so the tag totals add up to more than the products sold. That’s correct for “units sold under each tag”, but say so when you report it.

    Common mistakes

    • Exploding a text column. The string isn’t a list, so explode changes nothing.
    • Calling ast.literal_eval on a missing cell, which raises an error. Check isinstance(x, str).
    • Using eval instead of ast.literal_eval on file data. eval runs whatever code the text holds.
    • Adding up per-tag totals as if they were a grand total: multi-tag products are counted more than once.

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