Tuzla Ambalaj & Temizlik ↔ Temiz Tedarik

The same product family has two different buyers: a local customer with today's need who can walk into a store, and a business buyer who makes a weeks-long sourcing decision by sector. One general retail site serving both left each one underserved — too much business language for the local shopper, too little sector and volume context for the business buyer.

Instead of one general e-commerce build, we designed two separate digital experiences: Tuzla Ambalaj for local discovery and routing to the physical store, Temiz Tedarik for sector-based product discovery and need-list building. Both draw on the same stock and the same supplier; what differs is not the interface but the information architecture built around each customer's behaviour.

Tuzla Ambalaj's category tree lists real SKUs across party supplies, packaging, food-service containers, cleaning and disposable tableware; product pages show no price — current price and stock are confirmed over WhatsApp or in store, a deliberate product decision made on 2026-10-06, not a gap. Local SEO foundations (store and location structured data, category-split sitemaps, legacy site URLs preserved with redirects) and WhatsApp/phone/directions flows all serve the same goal: getting the customer to the physical store.

Temiz Tedarik presents 309 products sourced from Tuzla Ambalaj's real stock across eight sector pages (apartment buildings, restaurants & cafés, hotels, offices, clinics, cleaning companies, markets & grocers, nurseries & kindergartens) and six ready-made supply packages. A business searches for products and builds its own need-list on the "Build a Quote List" page; the request is first saved as a reference number in Temiz Tedarik's own database, then sent to the contracted supplier through the buyer's own WhatsApp.

What links the two platforms is not a technical integration but a documented business relationship: Temiz Tedarik has no shared database, API or webhook — the only connection point is a single WhatsApp number hardcoded in its code. Sale, quote, delivery and invoicing always run through Tuzla Ambalaj; Temiz Tedarik does not present itself as a party to that contract. And while Temiz Tedarik's discovery reach is nationwide, the one supplier's actual service area is limited to Tuzla, Kartal, Pendik, Maltepe, Gebze and Dilovası — we say so plainly rather than let "national" imply more than it does.

Both platforms share the same product stance: no visible price, no cart, the decision closes in a WhatsApp conversation. Beyond that, each runs on its own stack suited to its scale — Tuzla Ambalaj on Cloudflare Workers, Temiz Tedarik on Vercel and Neon Postgres. Both run consent-gated measurement; no personal data or message text is ever sent as an event.

Both systems went live on 2026-10-15; Temiz Tedarik's quote-request pipeline had a brief same-day outage from a missing environment variable, fixed and re-verified the same day. For that reason, this case makes no claim of increased customers, sales, traffic or ranking — there is no measurement window yet. Both platforms' own analytics are running; this page will be updated with dated numbers once a real window exists.

Every business has its own customer behaviour, and the digital infrastructure should be built to match it. Tuzla Ambalaj and Temiz Tedarik show how the same supplier's two different buying behaviours can be represented by two separate digital systems: one built to be found and visited, the other to be discovered and listed.