Selected Work
Lalezar

We built the catalogue on a data structure that was ready to sell.

We defined the product, variant and stock model, then tied sales, analytics and collection planning into one panel.

Client: LalezarE-Commerce · Product Data · Analytics · Planning
Lalezar storefront
Lalezar

Context

Taking the store experience to digital.

Lalezar is a clothing brand with a long retail history. In retail, product information is naturally produced across several sources: supplier lists, store inventory and the photoshoot archive. That worked for store operations; e-commerce, however, required a single consistent product record.

So we began by defining the product data model and consolidated the existing records against it. The catalogue, sales, analytics and collection planning all sit on that same structure.

6 ay
design & development
1200+
products moved into the catalogue
2026
the store went live

What we delivered

  • User research & UX strategy
  • Information architecture & category tree
  • Interface (UI) design
  • Product data model & data cleansing
  • E-commerce development
  • Payment, shipping & accounting integrations
  • SEO, performance & launch

Problem

What worked for the store did not carry over to digital.

01
Product data from many sources

Product information was produced separately on the supplier, store and studio side.

02
Content assets held apart

Images, measurements and copy sat in separate archives, stretching the time to publish.

03
Limited sales visibility

Product-level sales performance could not be fed straight into collection planning.

How it worked before

Supplier lists
Each supplier provided data in its own format
Store inventory
Sizes and colours were kept as separate records
Photoshoot archive
Images were stored in a separate archive
Manual consolidationSources were matched up by hand before each launch
Catalogue entry
The same information recompiled for every product
Campaign setup
Stock had to be verified from a separate source
Sales tracking
Reporting depended on matching products by hand

Solution

Product data, catalogue and analytics in one model.

01

Product data & cleansing

We put product data on a structure governed by explicit rules.

lalezar / veri
VeriVeri Kalitesi
Veri Kalitesi
Toplam Kayıt
Temizlenen
Bekleyen
Yayına Hazır
Veri Kalitesi KurallarıKuralları Düzenle
Aynı ürün, farklı kayıtAd ve koda göre eşleşen kayıtlar
İnceleToplu Düzelt
Görseli eksik ürünYayına alınamaz durumdaki kayıtlar
İnceleToplu Düzelt
Kategorisiz ürünAğaçta yeri belirlenmemiş kayıtlar
İnceleToplu Düzelt
Eksik varyant bilgisiBeden veya renk tanımı olmayan
İnceleToplu Düzelt
Product record
Ürün Kartı
YayındaElbise
Beden / Renk Matrisi
SMLXLSiyahBejBordo
Toplam Stok
Fiyat
Görsel
KaydetÖnizle
Rule-basedMissing fields, category gaps and duplicate records are flagged against defined rules.
Bulk fixesRecords caught by the same rule are handled in bulk rather than one by one.
02

Catalogue & sales

We made products, variants and stock manageable from a single list.

lalezar / katalog
KatalogÜrünler
Ürünler
Yeni Ürün
Tüm ÜrünlerYayındaTaslakStokta Yok
Ara…
KategoriSezonBeden
Filtrele
ÜrünKategoriVaryantStokSezonDurumFiyat
ElbiseYayında
GömlekTaslak
PantolonStok yok
CeketYayında
ElbiseTaslak
GömlekStok yok
PantolonYayında
CeketTaslak
ElbiseStok yok
123…
Variant matrixSize and colour live on one record, with stock held per variant.
Publish controlA product with missing fields stays in draft instead of going live.
03

Analytics & collection planning

We connected sales data to the plan for the next collection.

lalezar / analiz
AnalizÜrün Performansı
Ürün Performansı
Satılan Ürün
Ciro
Sepet Ortalaması
İade Oranı
Haftalık Satış EğrisiSon 12 hafta
Bu sezonGeçen sezon
En Çok Satan Ürünler
1
2
3
4
5
Collection plan
Sonbahar Koleksiyonu
Yayına Al
Veri Girişi3
Yayına Hazır3
Season comparisonThis season sits against the last on one chart, with the category split beside it.
From plan to publishCollection steps run from photoshoot to data entry to launch in the same panel.

System map

The product record at the center, everything tied to it.

LALEZARStructured around the product record
Product
Name, code and category
Variant
Size, colour and stock
Content
Images and copy
Order
Cart, payment and shipping
Campaign
Discounts and collections
Analytics
Sales and performance

The product record sits at the center; variants, stock, content, orders and analytics all attach to it.

Design and engineering decisions

We started from the data, not the interface.

01We set the product data model before design; the catalogue was built on top of it.

02We defined size and colour as variants of one product, not as separate products.

03We matched the admin panel’s wording to the language the store team already used.

04We kept the brand identity intact while making the simplifications conversion needed.

Outcome

1200+

Products were structured and moved into the catalogue.

6

Months from design to build.

2026

The store went live.

Product, variant, stock and sales data now sit in one structure, with catalogue management and collection planning run from the same panel.

We can build a system like this together.

Instead of handing you a template, we understand how your company actually works and design the right structure.