10 Things Shopify Developers Actually Get Right (That Magento and WooCommerce Merchants Discover Too Late)

Thinking about moving from Magento or WooCommerce to Shopify?

You're not alone. And you've probably already read a dozen articles that tell you migration is "straightforward" and Shopify is "easy."

Here's what those articles don't tell you: the platform is only as good as the decisions made on top of it.

The difference between a Shopify store that scales and one that doesn't comes down to ten things. Most merchants discover them the hard way, after the migration is done, after the B2B portal is live, after the ERP is connected with duct tape.

This list is for the ones who'd rather find out now.

Quick reference: The ten items below cover platform migrations (Magento, WooCommerce), B2B and wholesale configuration, ERP integration architecture, high-volume development patterns, and conversion optimization. Each one is a place where we've seen projects succeed or stall.

1. Magento Migrations: The Data You Think You Have Isn't the Data You Actually Have

Magento stores accumulate years of messy data. Custom attributes, orphaned products, duplicate customers, order records tied to modules that no longer exist. If you're still weighing the move, our Shopify vs Magento vs BigCommerce comparison covers the trade-offs in plain terms.

The migration tools will move all of it. That's the problem.

What gets done right: A proper Magento-to-Shopify migration starts with a data audit, not a data export. Before a single CSV leaves Magento, you need to know:

• Which product attributes map to native Shopify fields vs. metafields
• Whether your URL structure can be preserved (it usually can, with redirects)
• Which customer records are duplicates or test accounts
• What your order history actually needs to carry over for reporting vs. compliance

Magento's EAV (Entity-Attribute-Value) database structure is fundamentally different from Shopify's. Direct exports rarely land cleanly. Plan for transformation, not just transfer.

The SEO trap: Magento stores often have years of ranking equity baked into their URL structure. Losing that in migration is a real risk. A redirect map built before go-live, not after, is non-negotiable. Google's guidance on redirects is clear: use permanent (301) redirects, and have them live the moment the new store launches.

Bottom line: Expect the Magento migration to take longer than the WooCommerce one. The platform's flexibility is exactly what makes it harder to leave cleanly.

2. WooCommerce Migrations: Plugins Are Not Features

WooCommerce merchants often don't realize how much of their "store" is actually a stack of plugins held together by hope and a shared hosting plan.

When you migrate to Shopify, those plugins don't come with you.

What gets done right: Before starting a WooCommerce migration, map every active plugin to its Shopify equivalent. Some have direct replacements in the Shopify App Store. Some don't. And some were patching gaps in WooCommerce that Shopify handles natively.

The plugin audit you should run

The performance win: WooCommerce on shared or VPS hosting frequently struggles under load. Shopify's infrastructure scales automatically. Merchants who move from WooCommerce typically see meaningful improvements in page load times without any additional configuration, which directly affects conversion rates (a one-second improvement in load time can raise conversions by up to 7%).

The hidden cost: Custom WooCommerce development, especially anything that touches the database directly, won't translate. Budget for rebuilding custom functionality, not just migrating it. Our Shopify website development service covers replatforms from WooCommerce and Magento, including migration, QA, and a rollback plan.

3. Shopify B2B: Set Up Company Accounts Before You Do Anything Else

Shopify B2B is genuinely good. It's also genuinely different from how most merchants expect it to work.

The biggest mistake: treating it like a wholesale plugin bolted onto a DTC store.

What gets done right: Shopify B2B is built around the concept of Company accounts, not just customer tags. Each company can have multiple locations, multiple contacts with different permissions, and its own price catalog. This is the architecture everything else depends on.

What Company accounts unlock

• Custom price catalogs per company or location, synced from your ERP
• Payment terms (Net 30, Net 60) at the company level, not per order
• PO number fields at checkout, with invoice-style payment flows
• Tax exemption certificates stored against the company profile
• Approval workflows so buyers can place orders that require manager sign-off

If you configure Shopify B2B without setting up Companies first, you'll rebuild it later. The native B2B APIs are all structured around company and location IDs, which means any ERP integration or custom middleware you build will need them too.

One thing Shopify B2B doesn't do natively: PunchOut/OCI for buyers who need to shop from inside their own procurement systems (Coupa, SAP Ariba). This is a common enterprise requirement. It's solvable with partner integrations, but plan for it early, not after go-live. Our free 31-page B2B setup guide walks through exactly what to plan before you build, including the decisions that are hardest to undo.

The real advantage of Shopify B2B over a tagged-customer wholesale setup: your wholesale buyers get a completely separate, properly authenticated experience. No risk of retail pricing leaking to trade accounts or vice versa.

4. Wholesale Pricing: Your ERP Is the Source of Truth, Not Shopify

This is the one that causes the most damage when it's wrong.

Showing retail pricing to a wholesale buyer, even once, erodes the commercial relationship. Showing wholesale pricing to a retail customer is a margin disaster. Both happen when pricing lives in two places.

What gets done right: In a properly architected Shopify wholesale setup, the ERP owns pricing. Shopify is the execution layer. The ERP calculates contract and customer-specific prices, pushes them into Shopify via native B2B catalogs, and Shopify applies them at checkout without recalculating.

The pricing architecture that works

1. ERP as pricing authority - contract pricing, volume tiers, and account-specific terms live here
2. Shopify B2B Catalogs - receive price pushes from the ERP, one catalog per customer segment or company
3. Shopify checkout - applies the correct catalog automatically based on the logged-in company account
4. No manual overrides - pricing changes happen in the ERP and propagate down, not the other way around

The manual CSV trap: Many wholesale merchants start by managing pricing via CSV uploads into Shopify. It works until it doesn't. One missed upload, one pricing change that doesn't propagate, one rep who updates the ERP but not the store. The only sustainable approach is a live sync.

Quick-order interfaces matter too. B2B buyers aren't browsing. They're reordering. Your store needs SKU-level search, variant-level quantity entry, bulk add-to-cart, and CSV upload for large orders. Without these, you'll get phone orders instead of digital ones, which defeats the purpose.

5. ERP Integration: Decide Your Sources of Truth Before You Write a Line of Code

ERP integrations fail for one reason more than any other: two systems both think they own the same data.

What gets done right: Before any integration work starts, define which system is the authoritative source for each data type. Once that's decided, every other system treats that data as read-only and reacts to updates rather than trying to correct them.

The standard source-of-truth map for Shopify + ERP

Three integration approaches, ranked by complexity:

1. Direct App Store integrations - available for NetSuite, Microsoft Dynamics 365 Business Central, Acumatica, QuickBooks Online, and a growing list of ERPs via Shopify's native B2B integrations. Fastest to implement. Best for standard workflows.
2. iPaaS connectors (Patchworks, Celigo, Versori) - middleware that handles data transformation and sync timing. Good when the ERP isn't directly supported or when your data schema is non-standard.
3. Custom middleware - full control over error handling, retry logic, and sync cadence. Required for unusual ERP schemas, complex pricing structures, or strict compliance requirements. Most expensive to build and maintain.

The webhook architecture that scales: At volume, don't send Shopify webhooks directly into your ERP. Pipe them into an event broker like Amazon EventBridge or Google Cloud Pub/Sub first. This decouples the systems, handles retries gracefully, and prevents a slow ERP response from blocking Shopify operations.

6. High-Volume Development: Shopify's Limits Are Real, and You Need to Know Them

Shopify scales. But it scales within guardrails, and high-volume stores hit those guardrails faster than they expect.

What gets done right: Experienced Shopify developers build for the limits from day one, not when they become a problem.

The limits that matter at scale

• API rate limits - The legacy REST Admin API allows 2 requests/second per store (more on Plus). New builds should use the GraphQL Admin API, which uses a cost-based bucket system. Bulk Operations API is the right tool for large data jobs, not looped individual calls.
• Variant limits - up to 2,048 variants per product (the old cap was 100). Stores with configurable products can still hit this. The solution is usually metafields or a separate product architecture, not hacking around the limit.
• Checkout customization - on Shopify Plus, Checkout Extensibility is the right tool. Checkout.liquid has been retired.
• Flash sale traffic - Shopify's infrastructure handles spikes well, but your apps and third-party scripts don't. Audit app load impact before high-traffic events.

The theme architecture decision: For most high-volume stores, a well-optimized standard theme outperforms a custom-built one. Custom themes carry ongoing maintenance overhead and frequently introduce performance regressions. The exception is stores with genuinely unusual UX requirements that can't be met with Sections and Metaobjects.

Headless is not a default. A Hydrogen (Shopify's React-based headless framework) build makes sense for stores with specific performance requirements or complex integrations that benefit from decoupled architecture. For most merchants, it adds cost and complexity without proportional benefit.

The real performance lever at scale isn't the theme, it's the app stack. Every installed app adds JavaScript to your storefront. Audit your app load regularly. Remove anything that isn't earning its weight in revenue. Our guide to fixing a slow Shopify store covers the seven most common causes in the order we find them in audits.

7. Conversion Optimization: Most Stores Have a Leakage Problem, Not a Traffic Problem

An audit of 5,858 live Shopify stores found that 95% had at least one visible conversion leak that could be identified just by loading a product page on a mobile phone.

That's not a traffic problem. That's a store problem.

What gets done right: Start with a conversion audit before spending another dollar on ads. The Shopify admin's Online Store Conversion Rate report (Analytics > Reports > Behavior) shows you exactly where your funnel leaks: sessions, add-to-cart, checkout reached, purchase completed. If you want a structured starting point, our free Shopify store audit covers speed, conversion, and catalog quality in one pass.

The five leaks that show up in almost every store

1. Add to Cart buried on mobile - 73% of audited stores had it below the fold. Your thumb shouldn't have to scroll to buy.
2. No free-shipping nudge - 65% of stores had no threshold banner. A free-shipping nudge consistently drives 10-25% AOV lift.
3. No trust signals near the buy button - 38% showed nothing reassuring (returns policy, guarantee, reviews) near the purchase action.
4. Slow mobile load - 38% loaded a heavy homepage. A 0.1-second improvement in mobile speed lifted retail conversions by 8.4% and AOV by 9.2%, according to a Google and Deloitte study across 30+ million sessions.
5. No A/B testing - only 5% of stores run any testing tool, despite the fact that A/B testing on landing pages can lift conversions by up to 30%.

The fastest wins, in order of effort:

• Enable Shop Pay. It converts up to 1.72x better than guest checkout. It's free and takes minutes.
• Fix your Core Web Vitals. LCP under 2.5 seconds and CLS under 0.1. Both are measurable and actionable.
• Add one sentence of reassurance near the buy button. Returns policy, guarantee, or review count.

Measure revenue per visitor, not conversion rate. A store can lift its conversion rate and still make less money. The metric that matters is how much each visitor is worth.

8. Checkout Optimization: Don't Customize What You Don't Need To

Shopify's checkout is already one of the highest-converting in ecommerce. The Baymard Institute's 2026 checkout benchmark found that 59% of leading desktop and mobile sites had a checkout experience rated "mediocre" or worse.

The instinct to customize it is usually wrong.

What gets done right: Customize checkout to remove friction, not to add brand elements. The highest-impact changes are:

• Removing unnecessary fields - every extra field costs conversions. Address only what you need for fulfillment and compliance.
• Enabling all relevant accelerated checkout options - Shop Pay, Apple Pay, Google Pay. Fewer keystrokes, faster purchase.
• Setting clear delivery date expectations - unclear delivery timelines are one of the top reasons buyers abandon at checkout.
• Removing the account creation requirement - forcing account creation before purchase is a conversion killer. Guest checkout with an optional post-purchase account prompt is the right pattern.

For Shopify Plus merchants: Checkout Extensibility is the supported path for customization. It lets you add custom UI components, loyalty integrations, and upsell offers without touching the core checkout flow. Checkout.liquid has been retired, so any customizations still built on it need rebuilding with Checkout Extensibility.

Why this matters: When a buyer with a saved Shop Pay account hits your checkout, they're one tap from completing the purchase. That's the conversion advantage you're competing with if you don't enable it.

9. Mobile: Where Most Stores Are Leaving the Most Money

Mobile accounts for 60% or more of traffic for most Shopify stores. Mobile conversion rates typically run 30-50% lower than desktop.

That gap is where the money is.

What gets done right: Treat mobile as the primary experience, not a responsive afterthought. The decisions that matter:

Mobile CRO priorities, in order

The speed issue is an app issue. Heavy hero images and stacked app scripts are the most common cause of mobile performance problems. The theme is rarely the bottleneck. Before investing in theme optimization, audit your app JavaScript load with a tool like PageSpeed Insights or Shopify's built-in speed score.

Don't test on your phone. Your phone has a fast connection and a cached version of the site. Test on a throttled connection using Chrome DevTools or a real-device testing service. That's what your customers experience.

Cart abandonment on mobile runs at 85.65% (vs 73% on desktop), according to Barilliance research. The gap isn't inevitable. It's a product of stores that weren't designed mobile-first.

10. The Migration Isn't the Finish Line

The biggest mistake merchants make after a successful Shopify migration: treating it as done.

The platform is live. The data moved. The team is trained. And then the store sits, unconverted, unoptimized, and slowly drifting from the ERP sync that was set up six months ago.

What gets done right: Build a post-launch roadmap before you go live. At minimum, it should cover:

• 30-day: Verify all data syncs are running correctly. Check ERP pricing, inventory, and order flows against expected outputs.
• 60-day: Run your first conversion audit. Identify the top three funnel leaks and prioritize fixes by revenue impact.
• 90-day: Review app stack performance. Remove anything that isn't contributing measurable revenue. Audit Core Web Vitals.
• Ongoing: A/B test one element per month. Checkout, product pages, and free-shipping thresholds are the highest-return surfaces.

The compounding math on CRO: A Shopify store with a 1.5% conversion rate and 10,000 monthly sessions delivers 150 orders per month. Moving to 2.0% delivers 200 orders. At a $75 average order value, that's $3,750 in incremental monthly revenue without spending another dollar on traffic.

That's the case for treating post-launch optimization as a business function, not a project. Our Shopify website optimization service is built around exactly this: measuring where orders leak, ranking fixes by revenue impact, and shipping changes in small, measurable batches.

Need help with a Magento or WooCommerce migration, Shopify B2B setup, ERP integration, or conversion audit? Book a free call and we'll tell you where to start.

Frequently asked questions

Sources

• Redirects and Google Search (Google Search Central)
• External integrations for B2B (Shopify Help Center)
• Ecommerce CRO statistics (Shopify)
• Shopify CRO statistics 2026 (StorePilot)
• Checkout UX: pitfalls and best practices (Baymard Institute)
• PageSpeed Insights

Spotted something wrong or out of date? Email hello@kirkbyconsulting.com with the details and we will correct it.