1. Lighthouse

Level 3 · AOV and units per order

The request

From Catherine Hale, Chief Executive Officer

“Revenue grew every year, but someone told me our customers spend less per order than they used to. Is that true? Show me orders, sales, average order value and units per order for each year.”

Your goal

From lines (built in the starter: valid lines of booked orders, with year and net), set result to a DataFrame with one row per year, sorted by year, and columns year, orders (distinct order_id), net_sales (sum of net), aov (net_sales / orders) and units_per_order (sum of quantity / orders). Round net_sales and aov to 2 decimals and units_per_order to 2.

  • Use the order_items DataFramenot done yet
  • Show exactly year orders net_sales aov units_per_ordernot done yet
  • 3 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

    Revenue is orders times AOV

    Average order value (AOV) is net sales divided by the number of orders. Units per order (UPO) is units sold divided by orders. With orders they form a small identity that every e-commerce report rests on:

    net sales = orders × AOV
    AOV       = units per order × average price per unit

    When revenue moves, this tells you where to look: more orders, bigger baskets, or pricier items.

    Counting orders, not lines

    The data has one row per order line, about 2.5 lines per order. Any count over lines counts lines, so orders have to be distinct order ids:

    lines.groupby("year")["order_id"].nunique()   # 2,972 · 3,772 · 4,409
    lines.groupby("year").size()                  # line counts, two and a half times bigger

    Units are a plain sum of quantity. Both AOV and UPO use the same order count as their denominator, so both are computed after the groupby, from the totals.

    What the numbers say

    Harbor & Pine’s yearly picture:

    year  orders  net_sales     aov     units_per_order
    2023  2,972   1,649,804.36  555.12  5.20
    2024  3,772   2,046,520.24  542.56  5.03
    2025  4,409   2,362,232.24  535.78  4.98

    Net sales grew 43% over two years while AOV fell 3.5%. Every bit of growth came from order volume; the baskets got a little smaller. That is not automatically bad, since more customers buying is good news. But a forecast that assumes AOV stays at 2023’s $555 overshoots.

    AOV is a mean

    AOV inherits every weakness of the mean (see the Statistics track): a handful of business orders worth thousands pull it up, and the median order is about half of it. Keep AOV for planning (it multiplies back into revenue) and use the median for “what does a typical customer spend”.

    Common mistakes

    • size() instead of nunique(). AOV comes out per line, not per order.
    • Averaging line values. lines["net"].mean() is the average line, not the average order.
    • Different order sets. Net sales on booked orders divided by all placed orders mixes two definitions and understates AOV.

    Interview note

    “Revenue is up 15% but AOV is down. What happened?” Answer with the identity: orders must have grown faster than 15%. Then ask which customers drove the extra orders.

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