Intools Budget Sellers — Bulk Seller Coupon Creation
A simplified bulk seller-coupon creation flow between an internal operations tool and the merchant voucher platform, delivered in a single sprint.
- Role
- Backend Engineer (Tech Lead)
- Timeline
- 2023
- Team
- 1
- Domain
- E-Commerce / Merchant Vouchers
- Stack
- 8 tech
- Status
- Live
Overview
Intools Budget Sellers was a backend project that let operators create seller budget coupons in bulk directly from the internal operations tool, targeting the merchant voucher platform. I created the tech plan and led the implementation, deliberately favouring a simplified design so a working feature could be shipped in a single sprint while laying a modest foundation for future bulk coupon creation.
Gallery
A backend has no screens, so its "UI" is the operational surface: the bulk-creation API, the operator flow, and delivery dashboards.
Problem & Solution
Creating budget coupons for many sellers one at a time through the existing surfaces was slow and error-prone for the operations team. The team needed a bulk path from the internal operations tool into the merchant voucher platform, but had only a single sprint to deliver something working and safe.
I designed a small, focused backend feature: the internal operations tool submits a bulk seller-coupon request to a thin backend service, which validates the input and fans out per-seller creation calls to the merchant voucher platform, then returns a per-seller result summary. The tech plan explicitly chose a simplified data path — reuse of existing voucher platform APIs, minimal new storage, and no new async infrastructure — so the scope stayed inside the sprint. The interface was kept narrow but explicit, so future bulk-coupon iterations can extend it without a rewrite.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
The bulk coupon service sits between the internal operations tool and the merchant voucher platform. Requests are validated up front, coupons are created per seller against the voucher platform, and results are aggregated back to the operator. A managed RDS backs request bookkeeping, Redis is used for lightweight caching, and Prometheus/Grafana provide success-rate and latency visibility.
Features
- Bulk seller list input from the internal operations tool
- Coupon parameter configuration for a batch
- Validation and fan-out to the merchant voucher platform
- Per-seller creation result reporting
Tech Stack
Engineering Challenges
The team had one sprint to deliver a working bulk seller-coupon path. Fix: I wrote the tech plan around a deliberately simplified design that reused the existing merchant voucher platform APIs and kept the internal operations tool integration thin, so the whole flow could be built and validated end-to-end within the sprint.
The simplified design still had to be a useful foundation for future bulk coupon features. Fix: I defined a small, explicit request contract and kept per-seller result handling separate from the input path, so richer bulk flows can be added later without reshaping the current interface.
Outcomes
Lessons Learned
A deliberately simplified design can be a real feature: writing a tight tech plan up front let the team ship a useful bulk path in one sprint, while leaving a clear seam to grow into a richer bulk coupon capability later.
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.