ConversionEX
Services
WorkReviewsAboutContact
Milan

Shopify Store Design & Development in Milan

Custom Shopify storefronts for Lombardy brands whose product is configurable, whose buyers are half Italian and half everywhere else, and whose accountant has opinions about the checkout.

Delivered remotely for brands across Milan and Italy.

Build · Milan

Why Milan brands come to us for this

  • Variant and configurator logic for finishes, fabrics, sizes and made-to-order lead times, instead of a PDF price list behind a contact form
  • Italian at home and English, German or French for export, built into the theme so filters, cart and transactional email all translate together
  • Checkout that collects codice fiscale, partita IVA and SDI or PEC destination conditionally, without taxing a private buyer with a business form
  • Delivery and freight-quote logic that distinguishes a courier parcel from a two-person furniture delivery in the Brianza belt
  • Launch scheduled around Salone and the February and September fashion weeks, never into them

The hard part of a Milan build is almost never the homepage. It is the product. A Brianza sofa comes in nine frames, forty fabrics and three depths; a Como scarf exists in a colourway that only ran for one season; a leather bag can be personalised with initials and ordered in a width the site has never had to express. Most Italian stores solve this by putting a PDF price list behind a contact form, which turns a buying decision into an email thread and hands the order back to whoever answers fastest.

The second problem is that one store is being asked to serve two completely different buyers. An Italian customer in Milan wants an Italian interface, a delivery promise measured in days, and the payment methods they already use. A German or French buyer wants a price in their own market that is not a currency conversion accident, duties made obvious before the cart, and copy that was written rather than machine-translated. We build both on one catalogue, at theme level, so navigation, filters, size guidance, cart and transactional email switch together instead of a widget translating the product title and leaving everything else in Italian.

Then there is the paperwork nobody puts in a design brief. An Italian order can need codice fiscale, partita IVA, and an SDI recipient code or PEC address, and a default theme collects none of it. Capturing those fields cleanly — only when they apply, only for the buyers who need them, without turning checkout into a tax form for a private customer buying a candle — is a build decision. Retrofitting it means emailing customers for data you should have asked for once.

One cataloguedomestic Italian and export storefronts share products, stock and admin
Theme-level i18ntranslation keys built in at the start, not an app bolted to the header
Pre-fair cutoverwe launch clear of Salone and fashion week, never during them
Local context

The build has to survive April

Milan's year has a spike in it that most agency timelines ignore. Salone del Mobile at Rho Fiera turns April into the single biggest order-taking window for anything to do with interiors, and the Fuorisalone spills the same attention across Tortona, Brera and Isola for a week. Fashion labels get the same effect twice, in February and September. That has two consequences for a build. First, the storefront has to be live and stable well before the fair, not launched into it, because the week you get the most qualified traffic of the year is the worst possible week to be debugging a new theme. Second, the store has to have somewhere to put that traffic: a press and press-kit path, a showroom or appointment request that is not a generic contact form, and collection pages for the pieces you are actually showing. We scope Milan builds backwards from the fair date and cut over in the quiet stretch — usually late autumn or the first half of the summer, never August, when half your suppliers are closed anyway.

Scope

What Design & Build includes

The same standard of work we run for every client — applied to a Milan brand’s realities.

Full service detail
01

Conversion-Led UX & Wireframes

Wireframes for home, collection, product, cart and checkout drawn from your own session recordings, site-search logs and support tickets. Not a template library.

02

Custom Online Store 2.0 Theme

A bespoke theme in clean, commented Liquid with modular sections your team can rearrange themselves. Zero dependency on page-builder apps.

03

Merchandising & Navigation System

Collection architecture, filtering, badging and cross-sell rules mapped to how your catalogue actually sells. Bestsellers surface; dead stock stops eating grid space.

04

Speed Budget & Core Web Vitals

Image pipeline, third-party script audit and app cleanup enforced against a hard budget: LCP under 2.5s on 4G mobile, CLS under 0.1, INP under 200ms.

05

Catalogue & Content Load

Products, variants, metafields, collection copy and redirects loaded and QA'd in a dev store before cutover. You review a real store, not a Figma file.

06

Launch, Handover & Documentation

Loom walkthroughs, a written theme guide and 30 days of post-launch fixes included. Your team owns the store from day one.

Scoped and quoted for your Milan store

We do not work off a rate card. Every Milan engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.

Get this scoped
How it runs

From kickoff to results

01

Discovery & Data Pull

Two weeks inside your analytics, heatmaps, site search and support inbox. We leave with a ranked list of what is currently costing you revenue.

02

Architecture & Wireframes

Sitemap, template inventory and grey-box wireframes for every page type. Signed off before a single pixel gets designed.

03

Design System

Figma component library, type scale and every awkward state: empty cart, sold out, pre-order, bundle, back-in-stock, subscription upsell.

04

Build & QA

Liquid development in a dev store, tested on real devices and against your live app stack. Accessibility checked to WCAG 2.1 AA.

05

Launch & Measure

Redirect map, tracking validation, DNS cutover on a low-traffic window. Then 30 days of monitoring against the pre-launch baseline.

Proof

Design & Build results

Anonymised under NDA. Figures pulled from the client’s own analytics.

Performance Apparel (DTC)

~$6M/yr DTC, 900+ SKUs across size and colour variants, US · Shopify Plus

Returns ran at 31% and refund cost consumed the entire paid media margin. One size chart image served 40 different fits, and 62% of add-to-carts started on a collection page that never showed variant availability. The named constraint: no new product photography budget, so every fix had to come out of the existing asset library and the review corpus.

+29%sitewide conversion rate1.71% to 2.21%, five-month average
+14%average order value$84 to $96 once the threshold bar and cross-sell shipped
31% → 22%return ratenine-point drop, roughly $310k/yr in recovered margin
1.9x → 2.4xblended MERwith paid spend held flat throughout
Engagement Conversion-led rebuild + paid mediaTimeframe 5 months

Home Goods & Furniture

~$11M/yr, 2,300 SKUs, configurable upholstery, US · Shopify Plus + Hydrogen storefront (Oxygen)

Fabric, leg and size options turned 2,300 SKUs into more than 40,000 variant permutations, and the Liquid theme rendered a configurable PDP in 6.9 seconds on mobile. Collection filtering ran client-side, so 40% of shoppers left before the first product painted. The named constraint: the ERP stayed. It was the single source of truth for stock and lead times and was not up for replacement.

6.9s → 1.4smobile LCP75th-percentile field data on configurable PDPs
+64%CVR on configurable products0.44% to 0.72%. Sitewide conversion rate rose 23%
+52%organic sessionsserver-rendered facets made 1,900 filter combinations indexable for the first time
+$2.4Mincremental annualized revenuemonth-8 run rate vs. the pre-build baseline
Engagement Paid growth audit → headless buildTimeframe 8 months (6-week audit, 6-month build)
In their words

Clients on this work

AOV $58 → $79

“Full rebuild in 11 weeks, launched two days before Black Friday, which was an aggressive ask and probably a stupid one on my part. They pushed back hard on three homepage ideas I was attached to and were right about all three. AOV went from $58 to $79, mostly off the bundle builder they put on the product page.”

CEOHome fragrance brand, ~$6M/yr · Phoenix, AZ
Verified via Shopify Partner referral
FAQ

Design & Build in Milan — your questions

Yes, but not through the variant grid alone — Shopify's variant limits will not carry forty fabrics across nine frames. The pattern is a smaller variant set for the things that genuinely change price and stock, with the rest handled through line-item properties, metafields and a configurator front end that writes a clean order the warehouse can read. We also make the choice visible in cart, on the order confirmation and in the invoice data, because a finish that only exists in the customer's head becomes a dispute later.

Usually yes, on the same store with a separate path. Splitting them into two sites doubles your maintenance and halves your SEO for no benefit at the size most Milan brands are. What we build is a distinct route for trade — line sheet, minimums, terms, an enquiry form that captures partita IVA — while retail buys normally. If the wholesale book is big enough to need real pricing tiers and payment terms, that is a Shopify B2B conversation rather than a theme one.

We write and structure the English, and we work with your team or a translator on the Italian rather than pretending otherwise. What we always own is the structure: which questions a product page has to answer, in what order, and where reassurance about lead time, delivery and returns needs to sit. Translation of a badly ordered page just produces a badly ordered page in two languages.

That is a build requirement, not a bonus. Every section is a native Online Store 2.0 block with sensible settings, so a new landing page for a Fuorisalone collection or a saldi banner is assembled in the theme editor. We hand over documentation of each template and a short recorded walkthrough in English, and we deliberately avoid page-builder apps that would make you dependent on us or on a monthly subscription to change a headline.

Eight to twelve weeks for most brands, from kickoff to live. A single-catalogue store with clean product data lands closer to eight. Add subscriptions, B2B, or a multi-market rollout and you are looking at fourteen to eighteen. We give you a dated Gantt in week one and update it weekly.

We build on Shopify's Dawn reference theme and replace the sections we need. That gives you Shopify's own performance and accessibility baseline plus a codebase that survives platform updates. Premium themes carry code you will never use and cannot safely delete.

That is the point. Every content block is a native theme section with a schema your merchandiser can configure in the theme editor. You get a written guide and recorded walkthroughs. If you still need us for a homepage change, we built it wrong.
Next step

Design & Build for your Milan brand.

Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.

Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead

Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.