Back to Work

N 01 · Custom Platform

StyleClimate 2025.

Two previous storefronts and not one online order between them. We rebuilt StyleClimate's shop from the database up: the first order arrived within a month of launch, and more than fifty orders later the average is over €1,500.

0 → 50+
online orders since launch
€1.5k+
average order value
< 1 month
from launch to first sale
650+
products live
Sector
E-commerce · HVAC retail & installation
Location
Sofia, Bulgaria
Duration
1 month to launch · ongoing
Engagement
Custom Platform
The StyleClimate storefront shown on a laptop and a phone side by side — a category page of air conditioners on one, the checkout on the other.
The shop as it runs today: more than 650 products live, faceted search, and a checkout built for a purchase that needs a licensed installer.styleclimate.bg

Listen to this case study

0:00 / 10:36

Narrated by A I from the text of this page

Spread 01

Two shops, zero orders.

StyleClimate sells and installs air conditioning in Sofia — Daikin, Mitsubishi, Gree, Fujitsu and a dozen other brands, plus the inspection, installation, maintenance and repair work that goes with them. Founded in 2020, the business ran on phone calls and word of mouth.

Online, it had been through two storefronts — the last of them an OpenCart build with a catalogue of 332 products, maintained between 2022 and 2024. By the owner's count, neither produced a single order. The catalogue was there; the customers weren't.

The brief was not “a nicer website”. It was: make the shop sell. That reframed every decision — what a product page has to answer before someone spends €1,200 on a machine that needs a licensed installer, what a checkout must do for a customer who would rather call, and what the owner needs to see to run it every day.

Spread 02

What we shipped.

One platform, one codebase: the storefront customers see, the checkout, the service pages, the blog, and the admin panel the owner runs the business from. We migrated the OpenCart catalogue, cleaned it and grew it to more than 650 products today, with energy classes, BTU ratings, room sizes and Wi-Fi exposed as filters.

Storefront: category and brand pages with faceted filters, a weighted search that understands Cyrillic and model codes, side-by-side comparison, wishlist and browsing history, product labels, scheduled discounts with countdowns, and a multisplit configurator — pick an outdoor unit, add compatible indoor units from the same manufacturer, get a system price. Sixty-one outdoor units are configured so far.

Checkout: guest by default, address autocomplete on a map, delivery priced from the real driving distance, installation add-ons with a travel estimate, cash on delivery or a DSK Bank consumer loan — and, for the customer who would rather talk, a one-field “order by phone” that creates the order and a callback task in seconds. Order tracking by number, confirmation e-mails and a full status history close the loop.

Around it: four service pages with transparent pricing, a blog with its own editor, a Bulgarian-speaking AI assistant that browses the catalogue, contact and quote forms, and legal pages written for the euro transition.

The multisplit configurator: an outdoor unit selected on the left, compatible indoor units being added on the right, and a running system price beneath.
Fig. 01
Pick an outdoor unit, add compatible indoor units from the same manufacturer, get a system price. Sixty-one outdoor units are configured so far.Storefront

Spread 03

The stack, and why.

Next.js 15 and React 19, TypeScript end to end. One language for the page, the API and the database layer means one small team owns all of it. Server components render product pages on the server and ship almost no JavaScript where none is needed — while the cart, the configurator and the chat stay fully interactive where it counts.

tRPC 11 instead of REST or GraphQL: sixteen routers — products, cart, orders, multisplit, financing, SEO — typed from the database to the component, with no schema to maintain and no client to generate. The same procedures run at build time to pre-render pages and at runtime to hydrate the browser, so the storefront never fetches the same data twice.

PostgreSQL on Neon, Drizzle ORM. Thirty-six tables, typed SQL, versioned migrations. Postgres is boring in exactly the way a shop's database should be: any developer can inherit it. It also carries the assistant's memory and vector index through pgvector, so there is one database to back up, not three.

Better Auth for accounts (e-mail and Google), Tailwind CSS 4 with shadcn/Radix primitives for an accessible design system in weeks rather than months, Resend + React Email for seven transactional templates, and Zod on every input and every environment variable — the build fails if a secret is missing, which is cheaper than finding out in production.

Bun, Vercel and GitLab CI. Bun for fast installs and builds; Vercel for the edge CDN, incremental static regeneration, cron jobs and analytics; GitLab CI for the gates — lint, typecheck and tests run in parallel on every push, main deploys to a test environment hidden behind admin login and marked no-index, and production is a deliberate, manual step. Boring where boring is right, sharp where it pays.

Spread 04

Fast by construction.

Speed was not tuned at the end; it is how the pages are built. Every public page is static: the home, categories, brands, services, blog and every product page are rendered ahead of time and served from the CDN. Product pages regenerate in the background at most once an hour so price and stock stay fresh; categories and brands once a day; a product added in the admin renders on its first request and is cached from then on.

The pre-render is fed by the same tRPC procedures the app uses, so the first paint arrives with its data already in it and the browser hydrates from that snapshot instead of refetching. Static generation is deliberately serialised — four workers, no threads — so a 500-page build doesn't open 500 database connections and fall over; linting and type-checking moved out of the build into CI for the same reason.

The details add up: images through next/image with WebP spec sheets, fonts self-hosted at build time, the chat route's bundle cut from 10 MB to 1 MB by keeping the AI runtime out of the serverless package, HSTS preload and a full set of security headers, one canonical host, and versioned local caches so a returning visitor never sees a stale price — a rule that paid for itself the day prices switched from leva to euro.

Spread 05

Built to be found.

Search is the front door for a shop nobody has heard of, so every page tells Google exactly what it is. Product pages carry Product, Offer and AggregateRating structured data with price, availability and discount end dates, plus breadcrumbs; categories and brands carry breadcrumbs; posts carry BlogPosting; the site itself carries Organization and WebSite. Titles, descriptions and Open Graph images are generated per product with sensible fallbacks, so nothing ships blank.

The sitemap is generated from the database. robots.txt blocks dozens of filter-parameter permutations so crawl budget goes to real pages. Moved pages redirect permanently so their equity follows. Two product feeds — Google Shopping and Pazaruvaj, the Bulgarian price-comparison site — publish the live catalogue with the right currency, VAT and shipping.

The owner can watch it working: the admin has a DataForSEO-backed rank tracker, keyword research, a site audit and a backlink view, and seventeen blog posts since February keep the long-tail queries covered.

The rank tracker in the StyleClimate admin: tracked keywords with their current position, movement and search volume, over a position-history chart.
Fig. 02
Rank tracking, keyword research and a site audit live in the admin the owner already opens every day — not in a monthly report from somebody else.Admin · SEO

Spread 06

Built to sell.

A €1,200 air conditioner is not an impulse buy, so the platform removes reasons to hesitate. Guest checkout is the default — nine orders in ten never create an account. Financing is not hidden on a bank's website: DSK Bank's loan schemes are quoted on the product page itself, monthly instalment included, through the bank's merchant API.

Delivery is priced from the real driving distance through Google's Routes API and free above the threshold; the installation team's travel is estimated the same way — free within 30 km, per kilometre beyond. Nothing is “to be confirmed later”. For customers who prefer to talk, the one-field phone order creates a callback task instead of a form to fill in; roughly one order in four arrives that way.

Abandoned carts are captured and followed up by a daily cron with one-click unsubscribe — about half of them come back and buy. A Bulgarian-speaking assistant, built on Mastra and OpenAI with retrieval over the catalogue and the blog, answers “which unit for 35 m² under €1,300?” with actual products and links, and is held to an evaluation suite for relevance, hallucination and toxicity before any prompt change ships. Every step of the funnel fires GA4 e-commerce events behind a consent banner, with our own team's sessions excluded from the numbers.

Spread 07

Running the shop.

The admin is where the platform earns its keep daily: products with images, specs, labels and multisplit configuration; five hundred scheduled discount rules; orders with status history, internal notes and PDF, Excel or CSV export; reviews; a blog editor with tags and comments; contact submissions; newsletter; and e-mail templates the owner edits without a deploy.

And the euro. Bulgaria changed currency on 1 January 2026, and dual pricing was mandatory until 8 August. The re-denomination ran as a single database transaction with nine audit tables, twenty-plus in-transaction assertions and an idempotency guard we proved by running it twice; feeds, financing, e-mails, analytics and local caches switched in the same release. 1,290 prices, verified against their originals to the cent.

The orders screen in the StyleClimate admin: a list of orders with status badges, one opened to show its status history, internal notes and export controls.
Fig. 03
The screen the shop is actually run from — orders with status history, internal notes and exports, alongside products, discounts, reviews and the e-mail templates the owner edits without a deploy.Admin · Orders

Spread 08

Where it stands.

The catalogue went live in November 2025 and the first order arrived within a month. Since then the shop has sold every month, at an average order well above a thousand euros — from a business that had never taken an order online. The figures above come from the production database, not a slide.

The engagement continues: promotions, brand pages, content and the SEO programme are iterated monthly, and the codebase is documented to be inherited whenever StyleClimate decides to take it in-house. The shop is live at styleclimate.bg.

Working on something similar?

Submit a brief