Kılıf Sepeti
A physical retail business — stores, a service counter, staff, stock, cash and a ledger — rebuilt as one operating model. The storefront is a surface on top of it, not the thing itself.
Context
Kılıf Sepeti is a physical business before it is a digital one. Devices come in over a counter, stock sits on a shelf someone has to count, staff open and close a till, and a technical service desk takes in repairs that carry a promise.
Software arrived into that, years after the business already worked. Nothing here started on a blank page.
Friction
Each domain kept its own record. Stock in one place, the till in another, the repair in a notebook, the ledger somewhere else entirely — and the same event written down more than once, differently each time.
The visible symptom was the catalogue: the same product had a different name, a different image and a different price depending on which screen you asked. The invisible one was worse. Every decision started with an argument about which number was current.
A store isa systemwith a door.
System
The answer was not one application. It was one operating model: each domain gets the system that suits it, and every one of them writes to the same operational truth.
The shop floor runs on Mağaza OPS, the service counter on Service OS, the ledger on SayHesap, the task layer on Yönetim, and SAYAPP holds the operational record they share. The storefront is one more surface on that record — the one customers happen to see.
Interface
Server-rendered category and product pages, with the catalogue's own structure — not a carousel — doing the navigation work.
Building on the application framework rather than a shop template meant the catalogue could stay a data problem instead of becoming a theme problem.
Data
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.
One product record, one price, one place a correction is made. Everything downstream — the storefront, the exports, the reports — reads it.
The domains the business is actually made of, each named by the system that runs 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.
The direction of travel is the same for every domain: fewer separate records, one place a correction lands.