Santekno
Projects/Merchant Marketing Managed Service Data Reconciliation
ByteDance logoPart of ByteDance · Software Engineer, Promotion Platform Team
Backend / APIArchived

Merchant Marketing Managed Service Data Reconciliation

Designed a cross-domain reconciliation system with reconciliation scripts to keep Promotion and Product data for the Merchant Marketing Managed Service consistent, verifiable, and handover-ready.

2025-merchant-voucher-custody-reconciliation · main
# E-Commerce / Data Reconciliation
$ go -X POST /2025-merchant-voucher-custody-reconciliation/v1/sync
→ 201 Created
{ "status": "ok" }
publish 2025-merchant-voucher-custody-reconciliation.synced
Role
Backend Engineer
Timeline
2025
Team
2
Domain
E-Commerce / Data Reconciliation
Stack
6 tech
Status
Archived
01

Overview

The Merchant Marketing Managed Service Data Reconciliation effort ensured data consistency between the Promotion and Product domains, a core dependency for the managed-service program. I owned analysis, technical design, and partial implementation of the reconciliation solution.

A backend has no screens, so its "UI" is the operational surface: the divergence report, the repeatable comparison runs, and the handover artifacts.

Reconciliation report — cross-domain divergences
Test view — repeatable, verifiable comparison runs
Handover — technical design, scripts & docs
03

Problem & Solution

Problem

Data divergence between Promotion and Product could cause incorrect managed-service results and operational issues. The program needed a reliable way to detect inconsistencies that was correct, extensible, and easy to verify.

Solution

I broke the reconciliation problem into clear technical use cases, defining comparison logic, data boundaries, and scope. I designed and implemented a new comparison data source for cross-domain validation and developed reconciliation scripts (SQL-like) to detect inconsistencies in a transparent, repeatable, and testable way, then delivered the design on schedule with a full script and documentation handover.

04

Workflow

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

flowchart diagram

managed-service data

managed-service data

reconciliation-script compare

Promotion Domain

Reconciliation System

Product Domain

Divergence Report

Use case interaction
sequence diagram
Reconciliation ScriptReconciliation SystemProduct DomainPromotion DomainReconciliation ScriptReconciliation SystemProduct DomainPromotion Domainpull managed-service datapull managed-service datarun comparison logicinconsistenciesreport divergences
Sequence flow
05

Architecture

flowchart diagram

handover

Promotion Domain

Comparison Data Source · Go

Product Domain

Reconciliation Script (SQL-like)

Divergence Results

Docs & Scripts

System architecture
Architecture notes

A dedicated comparison data source pulls managed-service data from both the Promotion and Product domains, and reconciliation scripts run SQL-like comparison logic to surface divergences. The design favored a script-driven approach over heavy application code, with documentation and scripts packaged for smooth handover.

state diagram

technical design

comparison source + scripts

docs + script handover

analyzed

designed

implemented

handed_over

Reconciliation delivery lifecycle
06

Features

Reconciliation Design
  • Cross-domain comparison logic
  • New comparison data source
  • Reconciliation scripts (SQL-like) detection
Delivery
  • On-schedule technical design
  • Documentation & script handover
07

Tech Stack

language
Go
platform
reconciliation platform
tooling
reconciliation script
database
Managed RDS (relational database)
observability
PrometheusGrafana
08

Engineering Challenges

01
Detecting cross-domain data divergence

Promotion and Product data could diverge and produce incorrect managed-service results. Fix: a dedicated comparison data source and reconciliation scripts that make inconsistencies transparent, repeatable, and testable.

02
Designing for verifiability and extensibility

The reconciliation system had to be a reliable core capability, not a one-off. Fix: a script-driven, query-like approach that emphasized correctness and easy verification while reducing heavy application logic.

03
Ensuring continuity across a project handover

The project transitioned before full implementation. Fix: on-schedule design plus production-ready scripts and thorough documentation so the next assignee could move directly into testing without re-analysis.

09

Outcomes

2
domains reconciled
1
reconciliation system designed
on-time
technical design delivery
handover-ready
handover readiness
10

Lessons Learned

Clear technical handover and knowledge transfer matter as much as implementation, especially for cross-phase projects. Owning beyond personal task boundaries — delivering executable scripts and docs — preserved project momentum through the transition.

11

Related Santekno Tutorials

Interested in working together?

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