B-Side Voucher Seller Integration (Seller Promotion)
Designed and shipped a B-side mirror integration that syncs seller vouchers and promotions bidirectionally between a legacy marketplace and an e-commerce platform, keeping B-side and C-side data consistent.
- Role
- Backend Engineer
- Timeline
- 2024
- Team
- 3
- Domain
- E-Commerce / Cross-Platform Integration
- Stack
- 7 tech
- Status
- Live
Overview
The B-Side Voucher Seller Integration (Seller Promotion) delivered the mirror integration for seller vouchers and promotions between a legacy marketplace and an e-commerce platform. Working as the designer and implementer of the mirror integration, I made sure seller-side (B-side) promotion data stayed consistent with the customer-side (C-side) view across both platforms.
Gallery
A backend has no screens, so its "UI" is the operational surface: the mirror integration API, the pilot rollout flow, and sync-health dashboards.
Problem & Solution
After seller integration was completed, seller vouchers still needed a reliable mirror section from the e-commerce platform to the legacy marketplace. Promotion data could drift between the two platforms, and any mismatch between B-side and C-side state risked incorrect seller promotions. The flow needed clear technical requirements, broad use-case coverage, and a safe path to production.
I assessed the mirror integration (from the e-commerce platform to the legacy marketplace) for seller vouchers, then designed the technical requirements for the mirror section (e-commerce platform → legacy marketplace) and implemented it in production. I thoroughly understood all use cases, actively participated in every integration-related discussion for voucher sellers, and collaborated closely with teammates. The B-side data flows through voucher-seller-service and is mirrored by promotion-mirror-service, which keeps the two platforms aligned.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
voucher-seller-service (Go / RPC / HTTP) receives seller voucher and promotion events, validates the seller and the use case, then hands off to promotion-mirror-service, which mirrors promotion copies bidirectionally between the legacy marketplace and the e-commerce platform and persists state in a managed RDS (relational database). The design keeps B-side and C-side state consistent and exposes sync health through Prometheus / Grafana.
Features
- Mirror integration assessment (e-commerce platform → legacy marketplace)
- Full use-case coverage for seller vouchers
- Technical requirements for the mirror section
- Bidirectional B-side / C-side consistency model
- Production implementation of the mirror section
- Pilot launch for whitelist sellers
Tech Stack
Engineering Challenges
Seller vouchers and promotions had to be mirrored reliably between a legacy marketplace and an e-commerce platform after seller integration was completed. Fix: a dedicated mirror section with clear technical requirements and generic service boundaries so promotion data replicated correctly in both directions.
Merchant/seller-side (B-side) changes had to stay aligned with the customer-side (C-side) view on both platforms. Fix: a consistency model that validates seller voucher data before mirroring and reconciles state so B-side and C-side never diverged.
The integration touched many voucher and promotion use cases that were easy to miss. Fix: thoroughly mapping all use cases and actively joining every integration-related discussion, collaborating with teammates to close gaps before launch.
Outcomes
Lessons Learned
A clean mirror integration is less about new endpoints and more about mapping every use case, defining clear technical requirements, and keeping B-side and C-side consistent. Launching first with a small whitelist cohort let me validate the integration safely before broader rollout, and close collaboration in every integration discussion kept the cross-platform flow stable.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.