Santekno
Projects/Rilisan Spesial × MVC — Shop-Page Voucher Visibility
Tokopedia logoPart of Tokopedia · Senior Software Engineer, Promotion Team
Backend / APILive

Rilisan Spesial × MVC — Shop-Page Voucher Visibility

Integrated a special-release campaign feature with the merchant voucher platform so vouchers surface on a shop's page when the shop participates in the campaign — delivered smoothly with the campaign team.

2023-mvc-rilisan-special · main
# E-Commerce / Promotions
$ go -X POST /2023-mvc-rilisan-special/v1/sync
→ 201 Created
{ "status": "ok" }
publish 2023-mvc-rilisan-special.synced
Role
Backend Engineer (Lead)
Timeline
2023
Team
3
Domain
E-Commerce / Promotions
Stack
8 tech
Status
Live
01

Overview

Rilisan Spesial × MVC — internally the "Rilisan Spesial × MVC" project — connected a special-release campaign feature to the merchant voucher platform so that vouchers become visible on a shop's page whenever the shop is enrolled in the campaign. As lead engineer on the integration, I designed and delivered the backend changes and coordinated the release with the campaign team.

A backend has no screens, so its "UI" is the operational surface: the voucher visibility API, the campaign enrollment flow, and release dashboards.

API contract — shop-page voucher listing with enrollment check
Ops view — special-release enrollment & voucher surfacing
Grafana — release health and cross-team delivery signals
03

Problem & Solution

Problem

Vouchers created on the merchant voucher platform were not automatically surfaced on the shop page for shops taking part in the special-release campaign feature. Without a first-class integration, shoppers arriving at a participating shop would not see the vouchers tied to that campaign, and the two systems had no shared notion of "this shop is currently enrolled".

Solution

I added enrollment-aware visibility on the voucher read path: when the shop page requests vouchers for a shop, the merchant voucher service checks the shop's enrollment in the special-release campaign feature and returns the eligible vouchers accordingly. The change reused existing voucher storage and contracts, kept the shop-page consumer thin, and was aligned end-to-end with the campaign team so the enrollment source of truth stayed in one place.

04

Workflow

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

flowchart diagram

enroll

enrollment signal

check enrollment & vouchers

surface vouchers

Shop

Special-Release Campaign

Merchant Voucher Service

Managed RDS

Shop Page

Use case interaction
sequence diagram
Managed RDSCampaign ServiceMerchant Voucher ServiceShop PageManaged RDSCampaign ServiceMerchant Voucher ServiceShop Pagelist vouchers for shopis shop enrolled in special-release?enrollment statusfetch eligible vouchersvoucher listvouchers to display
Voucher visibility on shop page
05

Architecture

flowchart diagram

metrics

Shop Page

Merchant Voucher Service

Campaign Service

Managed RDS

Redis Cache

Prometheus / Grafana

System architecture
Architecture notes

The merchant voucher service exposes RPC and HTTP endpoints for voucher listing, backed by a managed RDS and a Redis cache for hot lookups. On the read path it calls the campaign service to check special-release enrollment, then returns the eligible vouchers to the shop page. Prometheus and Grafana provide release-health signals for the rollout.

state diagram

shop joins special-release

vouchers surface on shop page

campaign ends or shop opts out

not_enrolled

enrolled

visible

hidden

Shop enrollment & voucher visibility lifecycle
06

Features

Shopper
  • Vouchers surface on the shop page for participating shops
  • Consistent voucher listing tied to campaign enrollment
System
  • Enrollment-aware voucher visibility rules
  • Cross-service integration with the campaign feature
  • Backwards-compatible API contracts for the shop page
07

Tech Stack

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

Engineering Challenges

01
Making voucher visibility conditional on campaign enrollment

Vouchers from the merchant voucher platform needed to appear on the shop page only when the shop was enrolled in the special-release campaign feature. Fix: I added enrollment-aware visibility rules on the voucher read path, delegating enrollment lookup to the campaign service so the shop-page surface stayed a thin consumer with clear semantics.

02
Coordinating a smooth cross-team release

The change touched the merchant voucher platform, the campaign feature, and the shop-page surface — each owned by a different team. Fix: I aligned interface contracts and rollout steps with the campaign team up front and staged the release behind clear checkpoints, which is why the launch went out cleanly with no post-release issues.

09

Outcomes

0
post-release issues
shop page
voucher visibility surface
smooth
cross-team delivery
10

Lessons Learned

Small, well-scoped integrations still succeed or fail on cross-team coordination. Getting the enrollment contract and the rollout checkpoints agreed with the campaign team early was the reason the release went out smoothly with zero post-release issues, even though the change spanned three surfaces.

Interested in working together?

Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.