Kılıf Sepeti
The storefront and the catalogue behind it, rebuilt on a modern application framework so that product data, pricing and merchandising come from one source instead of three.
Context
Retail catalogues are rarely authored; they are accumulated. Products arrive from suppliers in whatever shape the supplier keeps them, and the shop is expected to sell them the same day.
Friction
The same product had a different name, a different image and a different price depending on which screen you asked. Fixing one did not fix the others.
Every merchandising decision started with an argument about which number was current.
A catalogue isan operation,not a page.
System
Incoming supplier data is normalised into one product record before it is allowed anywhere near the storefront. The storefront renders that record; it does not hold opinions about it.
Building on the application framework rather than a shop template meant the catalogue could stay a data problem instead of becoming a theme problem.
Interface
Server-rendered category and product pages, with the catalogue's own structure — not a carousel — doing the navigation work.
Data
One product record, one price, one place a correction is made. Everything downstream — the storefront, the exports, the reports — reads it.
Evolution
The catalogue layer is being pulled toward the same operational database the store systems use, so that stock a customer sees is stock the shop actually has.