The Delivery Layer for Shopware projects
Close the gap between approval and implementation in Shopware projects.
I align client, design and development before handoff, so approvals stick, developers build once, and your margin stays intact.
4.5 years
Principal Design System Architect, Shopware
10+ years
Experience in digital design for companies like Mercedes-Benz, Bosch, Unilever, Viessmann
44
Published e-commerce guidelines
2
Service packages: flat fee & retainer
1.0 / Problem → Result
Without the Delivery Layer
- Revision loops between client, design, and dev eat the fixed-price margin
- “That's not what we approved” — after the build, not before
- Brand customizations land in the wrong theme layer and break on the next update
- Developers translate client wishes — instead of developing
With the Delivery Layer
- One approved build specification, signed off by every party
- Change requests are translated into consequences before they reach the dev team
- Storefront customizations are documented update-safe
- Acceptance against the approval — not against memory
2.0 / Who it's for
Embedded
Shopware agencies
Running larger storefront projects, launches, relaunches, or SW5→6 migrations. You keep your process and your team — I take responsibility for the layer between client requirements and development that nobody officially owns today. Your client sees: the agency brings in the architect who built the system.
Independent
Shopware merchants
Facing a migration, relaunch, or a larger storefront investment. I sit on your side of the table: I translate your requirements into a specification your agency can't misread, assess proposals and migration plans independently, and check that what gets delivered matches what you approved — before the final invoice is paid.
3.0 / Phases of work
Phase 1
Discovery
Service
Stakeholder interviews, audit of theme & storefront
Result
Requirements catalog · as-is analysis of the theme architecture
Package
Blueprint
Phase 2
Specification
Service
Design intent mapped against Shopware reality
Result
Theme layer mapping · effort & update risk per requirement
Package
Blueprint
Phase 3
Alignment & Approval
Service
Workshop with client, design, and development
Result
Build specification signed off by every party
Package
Blueprint
Phase 4
Build Supervision
Service
Ongoing layer between client ↔ development
Result
Translated change requests · decision logs
Package
Retainer
Phase 5
Acceptance
Service
As-built check against the approval
Result
Acceptance report · update-safe documentation
Package
Retainer
4.0 / Packages & fees
Storefront Blueprint
from €4,500 flat
- 2–3 weeks, before development starts
- For a launch, relaunch, redesign, or SW5→6 migration
- Ends with the approved build specification
- Also available as an independent migration assessment
Interface Retainer
from €2,800 / month
- Per project, for the duration of the build
- I take over client communication on the build
- Fixed availability, participation in client calls
- Cancellable monthly
Pilot termsReduced rates apply for our first project together — in exchange for a reference statement on completion.
5.0 / About
Alexander Julian Victor
I spent 4.5 years at Shopware, responsible for the Storefront Design System and the UI foundations of Composable Frontends — the base Shopware agencies build on every day.
Across 10+ years in digital design, I've also worked on digital products and experiences for Mercedes-Benz, Bosch, Unilever and Viessmann.
I know both sides of a project: what gets approved in the stakeholder meeting, and what development can actually build, maintain and update.
7.0 / Getting started
01
30-minute project call
You bring the upcoming project — a launch, a migration, or a running client.
02
Assessment within 48 h
I name where the revision loops will appear in your project — free and specific.
03
Blueprint or Retainer
The right package, a fixed price, start aligned with your project kickoff.