Santekno
Projects/Intools Budget Sellers — Bulk Seller Coupon Creation
Tokopedia logoPart of Tokopedia · Senior Software Engineer, Promotion Team
Backend / APILive

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.

2023-intools-budget-seller · main
# E-Commerce / Merchant Vouchers
$ go -X POST /2023-intools-budget-seller/v1/sync
→ 201 Created
{ "status": "ok" }
publish 2023-intools-budget-seller.synced
Role
Backend Engineer (Tech Lead)
Timeline
2023
Team
1
Domain
E-Commerce / Merchant Vouchers
Stack
8 tech
Status
Live
01

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.

A backend has no screens, so its "UI" is the operational surface: the bulk-creation API, the operator flow, and delivery dashboards.

API contract — bulk seller-coupon request
Ops view — operator bulk-creation form
Grafana — bulk-creation success rate
03

Problem & Solution

Problem

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.

Solution

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.

04

Workflow

Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.

flowchart diagram

submit seller list

bulk create request

create per seller

metrics

Operator

Internal Operations Tool

Bulk Coupon Service

Merchant Voucher Platform

Prometheus / Grafana

Use case interaction
sequence diagram
Merchant Voucher PlatformBulk Coupon ServiceInternal Operations ToolOperatorMerchant Voucher PlatformBulk Coupon ServiceInternal Operations ToolOperatorsubmit seller list + coupon specbulk create requestvalidate + fan outcreate seller couponsper-seller resultbatch summary
Sequence flow
05

Architecture

flowchart diagram

cache

metrics

Internal Operations Tool

Bulk Coupon Service

Merchant Voucher Platform

Managed RDS

Redis

Prometheus / Grafana

System architecture
Architecture notes

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.

state diagram

input ok

dispatch to voucher platform

all sellers created

some failures

submitted

validated

creating

completed

partial

Bulk coupon creation lifecycle
06

Features

Operator Flow
  • Bulk seller list input from the internal operations tool
  • Coupon parameter configuration for a batch
Bulk Coupon Backend
  • Validation and fan-out to the merchant voucher platform
  • Per-seller creation result reporting
07

Tech Stack

language
Go
framework
RPC framework
protocol
RPCHTTP
database
Managed RDS (relational database)
cache
Redis
observability
PrometheusGrafana
08

Engineering Challenges

01
Landing scope in a single sprint

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.

02
Leaving room for future bulk coupon capability

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.

09

Outcomes

1
sprint to delivery
bulk
seller coupon creation
min-effort
via simplified design
10

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.