Managing Ad Packages: How We Replaced Hardcoded Integrations with a Dynamic Architecture and a Back Office Authors: Beliz Yavaş, Mehmet Sezer In this article, we will walk through how we built a …

Trendyol Tech Blog offers a glimpse into the technology and engineering practices powering one of Turkey's leading e-commerce platforms. With a focus on scalability, performance, and innovation, Trendyol Tech shares insights into microservices architecture, data engineering, and machine learning. Developers can learn about building high-traffic e-commerce systems, optimizing delivery pipelines, and leveraging  technologies to drive business growth.

Trendyol Tech

Trendyol's engineering team replaced a manual, hardcoded ad package integration process with a dynamic, data-driven architecture. The core change was migrating from a NoSQL document store to a normalized PostgreSQL schema with entities for Assets, Asset Types, Units, Packages, Details, Business Rules, Prices, and Quotas. This allowed new ad solutions to be added by inserting database rows rather than writing code. A Back Office application was built on top so business teams could independently create, configure, publish, and manage ad packages without opening developer tickets. The result was faster campaign launches, reduced engineering overhead, and team autonomy on both sides.

Managing Ad Packages: How We Replaced Hardcoded Integrations with a Dynamic Architecture and a Back Office

Solution (1): From NoSQL Chaos to Relational Clarity

Get Beliz Yavaş’s stories in your inbox

Solution (2): Back Office for Self-Serve Management