Commerce
Ready meals, custom meals, plans, bundles, nutrition, allergens, promotions, gift cards, credit and reorder flows.
Case study ยท Fit & Healthy Chef
A custom commerce and operations platform for a growing meal-service business
FitHealthyChef needed more than an online catalogue. The platform coordinates products, subscriptions, payments, customer accounts, delivery eligibility and staff operations through one evolving system.
- Custom commerce
- Subscriptions and delivery
- Security and admin operations
Make complex operational rules feel simple to the customer
Meal selection, nutrition, recurring plans, payment state, delivery zones and fulfilment rules all affect whether an order can be accepted. Those rules must remain consistent across the storefront, API and staff tools.
- Server-authoritative pricing and promotions
- Delivery zones, postcodes, cut-offs and time windows
- Recurring subscriptions and customer self-service
- Operational hand-off to dispatch providers
- Secure staff and customer account lifecycle
One platform across the customer and operational journey
Billing
Stripe checkout, subscriptions, billing portal and webhook-driven payment state.
Delivery operations
Eligibility rules, cut-offs, dates, time windows, dispatch hand-offs, retries and exception handling.
Administration
Catalogue, order, subscription, customer and reporting workflows for staff.
Sensitive workflows designed as first-class product features
The Java 21 and Spring Boot API uses deny-by-default security, rotating sessions, role-based access, mandatory staff MFA, audit records and server-side validation. Automated build and deployment checks protect releases across the Angular storefront and backend.
- JWT access with rotating refresh sessions
- Customer MFA option and mandatory staff MFA
- Trusted devices, session controls and account lifecycle
- Auditable administrative actions
- Versioned release and rollback workflows
A production-shaped platform now moving through client validation
Core commerce and operations workflows are implemented and the system is in client validation and pre-production hardening. Transactional email and final anti-abuse configuration remain launch dependencies, so this case study deliberately avoids claiming public production revenue or conversion results.