Promo Page for Seller Apps — Multi-Device Ads & Promotions
Supported the Promo Page (Ads & Promotions) feature on the seller mobile app — extended an existing endpoint to render promos across multiple devices (including the single-device case), designed data-storage customization so new promos ship faster via an internal operations tool, and prepared a clean handover with HLD, LLD, and endpoint docs while migrating the code into a new service repository owned by a downstream platform team.
- Role
- Backend Engineer
- Timeline
- 2022
- Team
- 3
- Domain
- E-Commerce / Ads & Promotions
- Stack
- 7 tech
- Status
- Live
Overview
The Promo Page (Ads & Promotions) feature on the seller mobile app surfaces promos to sellers directly inside their operations flow. As the backend engineer supporting this feature — alongside a mobile-apps team — I extended the existing Promo Page endpoint to support multiple devices, shaped the data storage so ops could iterate on promos quickly through an internal operations tool, and prepared a clean handover to a downstream platform team that would own the feature going forward.
Gallery
A backend has no screens, so its "UI" is the operational surface: the extended Promo Page API contract, the internal-ops configuration flow, and the handover documentation package.
Problem & Solution
The original Promo Page endpoint was tuned for a single delivery surface, and every new promo type or targeting change tended to require code work. On top of that, some promos were valid on only one device, so the endpoint needed a way to express and enforce that constraint. At the same time, long-term ownership of this surface was moving out of our service, so anything I built had to be documented and migratable — not just working.
I extended the existing Promo Page endpoint to become device-aware: a single contract now serves multiple devices, with a per-promo rule that keeps single-device-only promos correctly scoped. I customized the underlying data storage so schema changes for future promo types would not require a full endpoint rewrite, and I aligned the endpoint shape with an internal operations tool so ops could configure Ads & Promotions entries directly, minimizing per-promo integration effort. For the handover, I prepared HLD, LLD, endpoint reference and related tech documentation, and migrated the code into a new service repository owned by a downstream platform team.
Workflow
Three actors interact with the service; the diagrams are written in English to stay consistent across both languages.
Architecture
The Promo Page service (Go) owns the Ads & Promotions read path for the seller mobile app and the admin write path used by an internal operations tool. Promo entries live in a Managed RDS with a schema shaped for future customization; a device-aware filter runs inside the extended endpoint so the same contract serves every supported device while still honoring single-device-only promos. The service exposes RPC and HTTP surfaces, and Prometheus and Grafana track request health. For the handover, the code was migrated into a new service repository owned by a downstream platform team, with HLD, LLD, and endpoint documentation kept alongside it.
Features
- Promo Page endpoint for the seller mobile app
- Multi-device rendering rules for a single promo
- Single-device-only promo constraint handling
- Data-storage customization for future promo changes
- Endpoints designed for rapid change via an internal operations tool
- Existing endpoint reused and extended to minimize integration effort
- HLD, LLD, and endpoint documentation
- Related tech documentation for downstream owners
- Code migration into a new service repository owned by a downstream platform team
Tech Stack
Engineering Challenges
The Promo Page endpoint originally assumed a single delivery surface, but promos now had to fan out across multiple devices — and some promos were still restricted to a single device. Fix: extended the existing endpoint with a device-aware filter so one contract could serve every device the seller mobile app supported, while the single-device constraint stayed enforceable per promo.
New promos were expected to keep landing quickly, so the schema and endpoints could not be locked to today's exact fields. Fix: customized the data-storage layout and shaped the endpoints so ops teams could push new Ads & Promotions entries through an internal operations tool without a code change per promo, keeping integration effort low.
Long-term ownership was moving to a downstream platform team, and the receiving team needed enough context to run the feature without back-and-forth. Fix: prepared HLD, LLD, endpoint reference, and related tech documentation, then migrated the code into a new service repository so the downstream team took over a self-contained, documented feature.
Outcomes
Lessons Learned
Extending an existing endpoint instead of building a new one paid off twice: it kept the mobile-apps integration cheap and it left a single contract to hand over. Shaping storage and endpoints around the internal operations tool meant new promos could go live without a code change per promo — the kind of design-for-change decision that quietly compounds. And a good handover is a design deliverable, not an afterthought: HLD, LLD, endpoint docs, and a clean migration into a new service repository let the downstream platform team pick the feature up on day one.
Related Santekno Tutorials
Interested in working together?
Order, payment, or high-traffic event pipelines — let's talk architecture and trade-offs.