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.
- Role
- Backend Engineer
- Timeline
- 2025
- Team
- 2
- Domain
- E-Commerce / Data Reconciliation
- Stack
- 6 tech
- Status
- Archived
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.
Gallery
A backend has no screens, so its "UI" is the operational surface: the divergence report, the repeatable comparison runs, and the handover artifacts.
Problem & Solution
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.
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.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
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.
Features
- Cross-domain comparison logic
- New comparison data source
- Reconciliation scripts (SQL-like) detection
- On-schedule technical design
- Documentation & script handover
Tech Stack
Engineering Challenges
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.
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.
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.
Outcomes
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.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.