Most Adobe Commerce projects that go wrong do not go wrong in the storefront. They go wrong where the platform meets everything else: the ERP that owns stock, the PIM that owns product data, the tax engine, the OMS, the twelve extensions installed over five years that nobody wants to touch before an upgrade. Zelpex works on that seam — integrating Adobe Commerce with the systems around it, and untangling the ones already integrated badly.
We work on both Adobe Commerce Cloud and on-premise installations, on B2C catalogs and B2B setups with company accounts, shared catalogs, requisition lists and negotiable quotes. Where a store is already live, we usually start by profiling what is actually slow and what is actually broken, rather than proposing a rebuild — a replatform is sometimes the honest answer, but it should be the conclusion, not the opening pitch.
We map the current integrations, extension footprint, custom code and upgrade debt, then say plainly which parts are worth keeping and which are costing more than they return.
We agree what owns each piece of truth — stock, price, customer, order — and define the sync direction, frequency and failure behaviour before writing a connector.
Connectors ship with idempotency, dead-letter queues, reconciliation reports and dashboards, so operations can see what synced, what failed and what needs a human.
We load-test the paths that matter, tune caching and indexers, and stay available for the first peak season rather than handing over a repo and disappearing.
Usually code, occasionally indexers, sometimes hosting. We profile before recommending anything — full-page cache misses, N+1 queries in a custom module, an extension doing a synchronous API call on product load and unoptimised images account for most of what we find. Moving to bigger servers hides these for a quarter, then they come back.
Depends on what is actually hurting. If the pain is extension conflicts and upgrade debt, an audit and a cleanup is far cheaper than a migration. If the pain is that Adobe Commerce's licence and infrastructure cost outweigh what you use of it, replatforming is a fair conversation — and we will say so, including when that means moving you off a platform we work on.
Yes, and it is common. We tend to take the integration and back-end work while an existing team keeps the storefront and merchandising, or we cover a specific gap such as B2B features or an ERP connector. Clear ownership boundaries matter more than who does what.
We have spent more time in Adobe Commerce integration layers than in its theme files, which is where most of the expensive problems live.
Adobe Commerce is a heavy platform, and it earns its weight only when catalog complexity, B2B rules or multi-region operations genuinely need it. We are comfortable saying when a project does not — and equally comfortable in the deep end when it does, alongside your ERP vendor, your SI or your internal IT.
Tell us what you are building and what is getting in the way. You will get an honest read on scope, approach, and whether we are the right team for it — including when the answer is that you do not need us.
Enterprise-grade e-commerce solutions with Adobe Commerce (Magento). Full integration, customization, and ongoing support for scalable online stores.
Build and scale your online store with BigCommerce. Custom themes, integrations, and performance optimization for growing businesses.
Custom Shopify stores, theme development, and app integrations. From startups to enterprise with Shopify Plus solutions.