Subscription water commerce
5-gallon delivery was sold as coupons in a notebook. We shipped a UAE catalog with bottle SKUs, booklet sizes, and dispenser bundles on one record.
The situation & problem
AquaVita delivers low-sodium water on a route. Pricing lived in booklet SKUs a brochure could not compute.
The operational constraints
AED catalog, subscription booklet math, and bundles that combine coupons with a dispenser.
Architectural tradeoffs & what was refused
Instagram checkout only. A restaurant menu plugin pretending to be a route business.
What I built & shipped
Product catalog, coupon-book SKUs, dispenser bundles, cart, and order path.
Architecture & stack
Commerce catalog with subscription-style SKUs. Booklet size is a product, not a caption.
Result & measurable impact
Booklet sizes and dispenser bundles are purchasable objects, not a price rumor.
Next iterations & roadmap
Route-aware delivery slots so the storefront respects the van schedule.
System surfaces & interface captures
Hover and click any record to open the full-resolution pixel inspector with zoom lens and 1:1 precision.
Have a similar constraint?
Tell me where your current operational system or product is breaking.