Software developer

building custom

Hyvä storefrontAdobe CommerceAdobe Commerce

On the Adobe Commerce side, I integrate the platform with ERP, CRM, PIM and other enterprise systems — via REST and SOAP APIs, message queues, or middleware/iPaaS, depending on what the architecture calls for. Customer, product, pricing and order flows all live here.

Integration is where enterprise commerce lives or dies. Picking the right pattern per flow — direct API, queued, or middleware-routed — keeps Adobe Commerce clean and the flows reliable.

Designing where customer identity lives — typically a CRM as the master — and how IDs, VAT numbers, and account states sync between Adobe Commerce, ERP and CRM. Covers first-order ID assignment, lead-vs-account logic, and customer data sync strategy.

One source of truth for customer identity across the commerce stack means no duplicates, no drift. Get it wrong and every downstream flow — orders, pricing, invoicing — drifts with it.

Integrating a PIM with Adobe Commerce on the commerce side — product model design, attribute mapping, taxonomy, and making sure simple products stay simple instead of being forced into complex structures. Works with Akeneo or any equivalent PIM.

Correct product modeling from PIM → Commerce is foundational. Get it wrong and you pollute search, pricing and checkout downstream.

Integrating a dedicated search engine with Adobe Commerce — attribute-driven discovery, faceted filtering, autocomplete, and relevance tuning. Algolia, Elasticsearch or equivalent.

At enterprise catalog size, default Magento search doesn't scale. A dedicated search layer delivers faceted results at latency merchants actually notice.

Full Hyvä and Hyvä Enterprise storefronts. Hyvä Checkout customized at module level to match client-specific business rules, payment flows and B2B requirements.

Checkout is the highest-risk, highest-value surface in commerce. Module-level Hyvä Checkout work requires deep knowledge of both Hyvä and Magento internals — not theme tweaks, real extension of the checkout module.

Full Adobe Commerce B2B surface — company admin with shared address books and role-based permissions, negotiable pricing and quotes, approval workflows, shared catalogs, requisition and quick-order flows — the full feature set.

B2B commerce on Adobe Commerce is its own specialty — merchant org structure, permission models and price list management are where most implementations fail.

International storefront architecture: multi-currency, multi-country, GeoIP-driven routing — one installation, many markets.

Scaling to new countries without duplicating the platform is the whole point. Done right, each new market is configuration, not a fork.

Client discovery, functional analysis, architecture decisions, technical analysis, preparing dev-ready work, team meetings, steering committee attendance.

The bridge between business intent and engineering execution. Being named on project charters alongside PM and PO is formal recognition of that role.