Shipping Events as First‑Party Customer Data
Brian Whalley, Co-Founder of Wonderment, on Klaviyo's product-market fit
The key idea was to treat shipping events like first party customer data instead of a carrier utility feed. Wonderment built around the gap between checkout and delivery, where brands usually hand the order to a 3PL and carrier, then lose visibility. By pulling tracking events into the merchant’s own workflows, help desk, alerts, and site, shipping becomes something the brand can act on, segment on, and message around, much like Klaviyo did for marketing data.
-
In practice, owned data means the merchant is not just showing a branded tracking page. The merchant can trigger tickets for return to sender, stalled shipments, and unfulfilled orders, push alerts into Slack or a warehouse, and feed raw events into Sheets or a data warehouse for custom analysis.
-
The contrast with earlier tools was not that tracking pages did not exist. AfterShip also offers branded pages, segmentation, and event tracking. The difference was product philosophy. Wonderment centered the merchant’s control of messaging and downstream use of shipment events across support, CRM, and analytics, not just shopper visibility.
-
That matters because WISMO is usually the biggest support queue in ecommerce. When shipment data lives inside Gorgias or Zendesk instead of on a UPS or USPS page, an agent does not have to hunt across systems, and the brand can contact the customer before the complaint arrives.
This logic pushes post purchase software toward becoming a customer data layer for fulfillment. The winners will not just show package status. They will decide who needs a refund, who should get a replenishment shipment, which carrier is underperforming by region, and which message should go out before trust breaks.