The Problem
A tiffin vendor needed customers to choose meals for each delivery day and skip days when they did not need food. The charge depended on those choices: item prices and combination discounts varied, and changes partway through a billing cycle required recalculation.
What We Built
A subscription food platform with:
- Weekly menu customisation — the vendor publishes a fixed menu for the week. Customers select which items they want for each day. The system stores their selections and updates the delivery schedule.
- Dynamic pricing engine — the system calculates the subscription price based on the customer's selections. Pricing rules cover item costs and combination discounts, variations by day, and proportional adjustments for changes during a billing cycle.
- Subscription lifecycle management — pause, resume, skip days, change items, cancel. Each modification recalculates the billing.
- Delivery scheduling — the vendor sees a daily dashboard showing how many tiffins to prepare and where to deliver them.
What We Learned
The pricing model had to account for changes during an active subscription, including skipped days and different meal selections. Keeping that calculation separate from Stripe's payment collection let the vendor's menu rules determine the bill.