Chip-In Discount & Chip-In Ongoing
Designed a co-funded discount voucher system where the platform and sellers "chip in" to a shared discount — with a clean database relationship design, a reusable logic architecture, and a follow-up that halved development time.
- Role
- Senior Backend Engineer
- Timeline
- 2024
- Team
- 4
- Domain
- E-Commerce / Promotion & Discounts
- Stack
- 7 tech
- Status
- Live
Overview
The Chip-In Discount project introduced a co-funded discount voucher mechanism where the platform and sellers each "chip in" to a shared discount, and Chip-In Ongoing extended it into a recurring follow-up. As technical lead and owner, I drove the work from the initial technical design through delivery, defining requirements, the supporting database relationship design, and the logic architecture. The launch increased voucher volume to ~110k — roughly a 2.24% increase month-over-month.
Gallery
A backend has no screens, so its "UI" is the operational surface: the voucher API contract, the discount configuration flow, and volume/quality dashboards.
Problem & Solution
The platform needed discounts that could be co-funded by both the platform and sellers, with contribution splits, caps, and the voucher lifecycle handled reliably. Without a clean data model and shared logic, co-funding would fragment into ad-hoc fields, making the follow-up Ongoing work slow and error-prone.
I led the project from the initial technical design phase, ensuring all requirements were defined. I assessed the project needs and created a supporting database relationship design, then designed the logic architecture around voucher-service and discount-service and enforced high-quality coding practices. I kept the project on track so all milestones were met on time, mentored a junior engineer, and collaborated with fellow engineers who contributed to the project's success. On the Chip-In Ongoing follow-up, the reusable architecture cut development from a full sprint to half a sprint.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
voucher-service owns voucher creation, validation, and lifecycle, persisting vouchers and their co-funding relationships in a Managed RDS. discount-service computes the platform-vs-seller contribution split (ratio and cap). The database relationship design keeps co-funding a first-class relation rather than scattered columns, which made the Ongoing extension straightforward. Prometheus/Grafana track voucher volume and release quality.
Features
- Co-funded voucher creation & validation
- Platform/seller contribution split
- Discount rule configuration
- Voucher rollout & monitoring
- Chip-In Ongoing (recurring) support
- Database relationship design for co-funding
- Logic architecture for the voucher lifecycle
- New API contracts & enum fields
Tech Stack
Engineering Challenges
The discount had to be co-funded, so the split between platform and seller needed a clean, queryable model. Fix: a dedicated database relationship design that made contribution ratios and caps first-class rather than ad-hoc fields.
The Ongoing variant reused most of the base flow but risked a full rebuild. Fix: a logic architecture designed for extension so the follow-up shipped in half a sprint instead of a full one.
A fast timeline usually trades away quality. Fix: enforced high-quality coding practices and broad self-testing, resulting in only 7 bugs found before release and none after.
Outcomes
Lessons Learned
Investing early in a clean database relationship design and an extensible logic architecture paid off directly: the Chip-In Ongoing follow-up shipped in half the time with minimal bugs (7 before release, none after). Owning a project end-to-end — design, quality, mentoring, and delivery — matters as much as the code itself.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.