For heritage brands, luxury goods, and craft manufacturers.

Your ERP talks to your warehouse.
Your webshop should too.

I build e-commerce for brands where the product complexity is the point — seasonal collections, configurable variants, wholesale tiers, and supplier systems that were never designed to talk to a website.

Most heritage brands end up with one of two problems: a beautiful site that doesn't work operationally, or a functional one that looks like every other DTC storefront. I build the third option.

Send a project brief

No RFP required. Just tell me what you're running and what isn't working.

Working with:

  • Gössl

    Salzburg's traditional clothing house, making Tracht since 1947. Storefront moved from Magento to Shopify with the Intex ERP kept as the source of truth; I built the bridge between them and have run it since, day to day.

Most agencies build around your complexity. That's the problem.

Your catalog isn't simple. You have:

  • Materials and colorways that map to actual stock codes in a system your warehouse team has used for 20 years.
  • Seasonal sizing — the same jacket in children’s, ladies’, and men’s fits, each with their own size run and their own restock cycle.
  • Wholesale pricing that varies by market, volume, and distributor — maintained, until now, in a spreadsheet.
  • A product launch that requires every variant to exist, be priced correctly, and show accurate stock before the campaign goes live. Manually.

The agency you hired before built a Shopify site. It looks good. And every Thursday, someone on your team spends three hours importing a CSV to keep inventory honest.

That's not a Shopify problem. That's a scoping problem. The agency scoped for the storefront and ignored the data layer.

What it looks like when this is done properly.

Your ERP is the source of truth. When a product is added, repriced, or discontinued in your system, the webshop reflects it automatically. Not after Tuesday’s import. Now.

Your warehouse team doesn't field calls from customer service asking why something shows as in stock when the shelf is empty. The numbers match.

You go into a season launch knowing the catalog is correct. You check the site, it's right, you move on.

No spreadsheet. No Thursday CSV. No last-minute panic before a campaign goes live.

Craft infrastructure. Built for brands with history.

  1. 01

    ERP integration with no manual step

    Problem
    Your ERP was built for your warehouse, not your webshop. Bridging them is usually a batch import that runs at midnight and breaks on the first product with a special character in its name.
    Cure
    I build a real-time middleware layer — Cloudflare Workers — that reads from your ERP's API and writes to Shopify continuously. Product data, stock levels, and pricing stay in sync without intervention.
    Proof
    Gössl's catalogue runs to several thousand SKUs across seasonal collections. Products, prices and stock are created and maintained in Intex, never by hand in Shopify; the bridge carries them across on a schedule, with a nightly reconciliation that logs any drift.
    Offer
    If you're not sure whether your ERP has an API to work with, send a brief and I'll tell you within a week.
  2. 02

    A storefront that looks like your product deserves

    Problem
    Heritage brands end up on Shopify themes built for athleisure DTC startups. The product is extraordinary. The site looks ordinary.
    Cure
    I build from scratch — Webflow or Astro/React — matching the visual weight, typography, and editorial pacing that your product catalog actually calls for. No themes. No layout compromises because the template doesn't support it.
    Proof
    The Gössl storefront moved off Magento onto an editorial-forward build — product photography, heritage storytelling, and collection pages that carry the weight of a house that has made Tracht since 1947.
    Offer
    I scope every project with a design direction phase before development starts.
  3. 03

    Back-office tooling your team will actually use

    Problem
    The storefront is only part of the picture. Your team needs to manage collections, curate editorial content, handle wholesale inquiries, and keep product data clean — without relying on the developer every time.
    Cure
    I build the dashboards, curator tools, and admin interfaces your operations team needs, on top of the same data layer powering the storefront. What they update in the admin reflects in the shop immediately.
    Proof
    For Gössl, the back-office tools sit on the same data as the storefront — product curation, collection management, and the day-to-day order work. The team uses them without a developer in the loop.
    Offer
    What we build here depends on how your team actually works. The infrastructure is the same; the tools on top vary by project.

“Can a solo studio handle something this complex?”

Yes. Specifically because I'm solo.

Agencies spread this kind of work across three people who don't talk to each other as often as they should. The person who wrote your spec isn't the person building the integration, and neither of them is the person managing your account.

I do all three. Every technical decision goes through me. If something breaks at midnight, I'm the one who fixes it — not a support queue.

I've been independent since 2008 and incorporated in 2018; today I work from Salzburg. Gössl has been a client since 2025, and I still run what I built there. That's the track record.

What this costs

Projects in this category — ERP integration, storefront rebuild, back-office tooling — typically run between €40,000 and €150,000. Scope drives the number.

For a rough sense before investing time in a proper brief: a storefront rebuild without integration work starts around €10,000–25,000. Full-platform builds with ERP middleware and custom admin tooling are €80,000 and up.

I don’t give estimates on discovery calls. I give them in writing, after I understand the project.

Ready to talk about it?

Send a brief. Tell me your brand, what you're currently running on, and the specific thing that isn't working. I'll read it and tell you within a week whether it's a fit and roughly what it would cost.

Send a project brief

I work with a small number of clients at a time. If the calendar is full, I'll say so.