Adobe Commerce / Magento 2
Certified. Multi-store, B2B pricing, checkout, catalogue indexing, performance and infrastructure — including builds whose date has already slipped.
I build complex commerce, booking, ERP and automation systems under your brand — a senior engineer inside your delivery, not a vendor beside it. Your client never has to hear my name.
I work under your brand — your repositories, your project tools, your client calls if you want me on them. What ships, ships as your agency's work.
Your client stays your client — during the project and after it. In writing if you want it in the contract; the same either way.
Architecture notes, runbooks and a weekly changelog are handed over as your assets — so your team can carry the system without me.
You get a named senior engineer who owns the technical decisions — not a rotating bench, and not a junior behind a brand.
The work agencies usually cannot staff from the bench: the deep platform layer, the integrations, and the systems that have to hold under load.
Certified. Multi-store, B2B pricing, checkout, catalogue indexing, performance and infrastructure — including builds whose date has already slipped.
GraphQL, PWA and React storefronts where the commerce rules — rental dates, configurators, availability — live inside the transaction, not beside it.
SAP, Odoo or in-house; local gateways and carrier handover. Queued, retryable and observable, so a failed call is visible instead of silent.
Multi-tenant platforms with availability rules, staff calendars, cancellation policies and tenant isolation — calendars that cannot double-book.
Spreadsheets turned into systems, and PLC lines streamed into cloud dashboards — the work that sits between an operation and its software.
A continuous engineering layer across your projects: reserved days each month, architecture, decisions and execution. For agencies with a steady flow of complex work.
Fixed scope and a fixed date. Architecture through handover, delivered under your brand and quoted to your client as your work.
A client's system that has slowed, stalled or falls over on campaign day. Two weeks to an audit and a written plan you can put in front of them.
Five steps, in order. Each one produces something you can forward to your client.
Thirty minutes on the client's system, the constraints and the date. You get a straight answer on fit — and a name to call if it is not me.
The simplest architecture that carries the goal, written in language you can put straight into a proposal.
Deployed weekly with a written changelog your account manager can forward without translating it first.
ERP, payments, logistics and external APIs — the part that usually decides whether the launch date holds.
Documentation, runbooks and your team walked through the system, so support does not route back to me by default.
Some through agencies, some direct. The engineering is the same either way.
| System | Country | Domain | Stack |
|---|---|---|---|
| Frankenspalter | Switzerland | E-commerce | Magento · ERP · Performance |
| Dcey | Türkiye / UK | Rental commerce | PWA · GraphQL |
| SBL Beauté | Australia | Commerce · Booking | Next.js · Payments |
| Hujuzatk | — | Multi-tenant SaaS · Property | Next.js · PostgreSQL |
| Edip Saat | Türkiye | Watch retail | Commerce · ERP · Payments |
| DORTEK | Türkiye | Product configuration · PLC | Commerce · Configurator |
Tell me about the client's system, the date, and what worries you most. You get a straight answer on fit within a day — and a name to call if it is not me.