Most platform comparisons get written from the safety of generic features. The real comparisons happen in client conversations where five specific business requirements pull the decision toward one side or the other, and either platform “could work” until they do not. This is a walkthrough of one of those conversations, generalized enough to be useful without exposing the client.
The merchant was a $32M annual GMV B2B distributor of industrial parts, serving 4,200 net-30 account customers across the US, with a legacy Magento 1 store that had been limping along for three years past end-of-life. They were evaluating Shopify Plus and Adobe Commerce with Hyvä for the replatform. After a four-week discovery and a thirty-page assessment, Bemeir’s eCommerce team recommended Adobe Commerce + Hyvä. The reasoning matters more than the conclusion.
What the merchant brought to the conversation
The initial brief from the merchant’s leadership was performance-driven: their Magento 1 site had a Lighthouse Performance score of 19 on mobile, the checkout was abandoning at 78%, and customers complained the site felt “slow.” The CMO had been hearing pitches from Shopify Plus sales for eight months and the merchant was leaning toward replatforming there.
Their five-year business plan also called for: doubling their B2B account base, adding three new product lines that doubled SKU count to roughly 24,000, integrating their ERP (Microsoft Dynamics 365 Business Central) directly with the storefront for real-time pricing and inventory, supporting customer-specific catalogs and pricing per account, and adding a kiosk-based ordering tool for their warehouse customers who came in person.
Standard performance was the loud problem. The business roadmap was the quiet problem. The platform decision needed to honor both.
The five requirements that drove the decision
Five specific requirements moved the decision toward Adobe Commerce. None of them are deal-breakers for Shopify Plus on their own; the combination is what tilted the scale.
Customer-specific pricing at scale. The merchant runs negotiated price lists per account, with discounts that vary by SKU, by volume tier, and by contract date. Shopify Plus B2B handles customer-specific pricing through its catalog and price list system, but at 4,200 accounts with multiple price tiers per account, the catalog management overhead was significant. Adobe Commerce B2B handles this natively through shared catalogs and customer-specific catalogs, and the Adobe Commerce B2B documentation describes the customer-group-based pricing model that fit the merchant’s workflow more directly.
ERP real-time integration. Real-time inventory and pricing from Microsoft Dynamics 365 Business Central was a hard requirement. Both platforms can connect to D365 BC, but the integration patterns differ. Shopify Plus’s API rate limits (the Shopify Admin API rate limits cap calls at 2 requests per second on standard plans, higher on Plus) made real-time per-product price queries during catalog browsing structurally difficult. Adobe Commerce’s flexibility in how the ERP integration is architected (queue-driven price sync to the database, or direct REST calls from the price renderer) gave more options for the specific D365 BC connector the client had in mind.
Catalog complexity at 24,000 SKUs. The forecast catalog size was within both platforms’ technical limits. The difference was in catalog management ergonomics. The merchant’s product team was already comfortable with Magento’s attribute set and attribute group model, and they had two years of clean product data structured for it. Migrating to Shopify Plus’s metafield-based product model would have required significant data restructuring and retraining for the product team. The cost of forcing that change was higher than the cost of staying with the data model they had.
Customer account hierarchies and multi-user buying. The merchant’s larger accounts have multiple buyers, with approval workflows where a junior buyer creates an order and a procurement manager approves it before submission. Both Adobe Commerce B2B and Shopify Plus B2B support this, but Adobe Commerce’s company-account model (companies, divisions, roles, requisition lists) had a closer fit to how the merchant’s largest accounts actually wanted to buy. This came out in user interviews during discovery, not from feature comparison.
Total cost of ownership over five years. The Shopify Plus license cost is more predictable but higher at this revenue tier (typical Shopify Plus pricing for a $32M GMV B2B account is in the $24K-$72K/year range based on Shopify Plus public pricing tiers plus per-app costs). Adobe Commerce on-premise hosting and license is more variable but, at this catalog size and integration depth, came out approximately 25% lower on a five-year TCO model when we included the implementation cost, ongoing engineering, and the cost of the apps and integrations needed on Shopify Plus to match the B2B feature parity.
What Shopify Plus would have won on
Worth being explicit about what we would have given up by recommending Adobe Commerce.
Operational simplicity was the largest concession. Shopify Plus removes a meaningful amount of infrastructure ownership: no hosting decisions, no Varnish to tune, no Redis to manage, no PHP version upgrades, no patch management. For this merchant’s three-person internal IT team, that was a real benefit.
Time to launch was second. A Shopify Plus implementation of this scope would have shipped in 4-6 months. The Adobe Commerce + Hyvä build we scoped was 7-9 months, with the longer timeline driven by the ERP integration and B2B account migration.
Marketing tool ecosystem was third. The Shopify app store has more native marketing integrations (email, SMS, loyalty, reviews) than the Magento marketplace, and the merchant’s marketing team had built a roadmap that assumed access to that ecosystem.
These were not small concessions. They mattered to the decision and were treated honestly in the recommendation. The Adobe Commerce path was right because the business roadmap leaned heavily on the strengths Adobe Commerce had and accepted the operational cost.
How the build actually played out
The Adobe Commerce + Hyvä build for this client ran 32 weeks from kickoff to launch. Phased timeline:
| Phase | Duration | What was delivered |
|---|---|---|
| Discovery and architecture | 4 weeks | Functional spec, data migration plan, integration architecture, design system brief |
| Hyvä theme + component library | 6 weeks | Brand-aligned design system, Tailwind config, reusable components |
| Page type migrations | 10 weeks | Category, PDP, search, account, requisition list pages |
| Adobe Commerce B2B configuration | 4 weeks | Companies, customer groups, shared catalogs, approval workflows |
| D365 BC integration | 5 weeks | Real-time inventory + price sync, customer + order sync |
| Hyvä Checkout + payment methods | 3 weeks | Net-30 payment, ACH, credit card via Authorize.Net |
| QA, performance tuning, soft launch | 4 weeks | Lighthouse 95+ mobile, INP <100ms, soft launch on 10% traffic |
| Full cutover and stabilization | 2 weeks (post-launch) | Issue resolution, customer support handoff, performance monitoring |
The launch delivered Lighthouse Performance of 96 on mobile, Largest Contentful Paint of 1.4 seconds (down from 6.8 on the legacy Magento 1 site), and a conversion rate lift of 31% in the first 60 days. ERP price sync ran at 95th percentile latency under 600ms. Customer service tickets related to checkout dropped by 41% in the first quarter.
What the merchant said at the six-month mark
The most useful feedback came at the six-month review. Three things stood out.
The internal IT team had grown by one engineer specifically to own the Magento stack. That was an honest cost the Shopify Plus path would have avoided. They considered it worth it for the business control they got.
The customer-specific pricing implementation had let the merchant launch two new account tiers in the first six months without engineering involvement. The product team owned the price list management directly, which was the specific scenario the Adobe Commerce B2B model had been chosen for. This was the moment the decision rationale paid off in revenue.
The Hyvä Checkout had measurably reduced cart abandonment at the checkout step, and the merchant’s customer service team had received unsolicited customer feedback about how much faster the site felt. The performance investment landed for the customers, not just for the dashboards.
The honest decision pattern
When Bemeir’s team advises merchants on Adobe Commerce vs. Shopify Plus, the recommendation comes down to a small number of questions that genuinely move the answer.
How complex is the catalog and the pricing model? Above a threshold of customer-specific complexity, Adobe Commerce’s data model becomes a better fit than Shopify Plus’s.
How deep is the ERP/back-office integration? Real-time price and inventory from a complex ERP is structurally easier to implement on Adobe Commerce, especially under high catalog query loads.
How disciplined can the team be about apps and extensions? Both platforms degrade with extension sprawl. Shopify Plus degrades more visibly because every app adds to the storefront JavaScript bundle; Adobe Commerce + Hyvä degrades less visibly because the impact is on backend performance and maintainability.
How important is operational simplicity vs business control? This is the cleanest single question. Shopify Plus trades control for simplicity. Adobe Commerce trades simplicity for control. The right answer depends on the merchant.
For this client, the business control was the decisive factor and the operational cost was acceptable. For other clients, the answer flips. Bemeir’s Shopify Plus practice recommends Shopify Plus when the trade-off goes the other direction, which it does for most stores below $5M GMV without complex B2B requirements.
The piece most evaluation processes miss
Most platform evaluations weight the demo experience too heavily. Shopify Plus demos beautifully because the product is opinionated and most of the demo paths have been polished. Adobe Commerce demos badly because the product is flexible and the demo paths depend on what the demo agency chose to configure. The merchant who chooses based on demo quality often regrets the choice at month nine when they discover the platform’s opinion does not match their business.
The evaluation that actually works is a discovery built around the merchant’s five hardest business requirements, with both platforms evaluated against those requirements using their actual production capabilities, not their pitch decks. For this client, the discovery process took four weeks and cost the merchant a small fraction of what the wrong platform decision would have cost over five years.
Our team runs that discovery as a standalone engagement when merchants ask for help making the platform decision honestly. The output is a recommendation document the merchant can defend internally, whether it points at Adobe Commerce or Shopify Plus. The right choice is the one the business roadmap actually supports.