> ## Content Index > Fetch the complete content index at: https://blog.tsd.digital/llms.txt > Use this file to discover other available public pages before exploring further. # The Plug-and-Play Myth: What Shopify's App Store Doesn't Tell You - URL: https://blog.tsd.digital/the-plug-and-play-myth-what-shopifys-app-store-doesnt-tell-you/ - Published: 2026-08-18T07:00:31.000Z - Updated: 2026-08-18T07:00:31.000Z - Description: "Can't we just use a plugin?" Plug-and-play is real, but only for businesses shaped like the plug. Why ERP-connected businesses end up paying bespoke prices for templated constraints, and why the fulfilment integration everyone fears is the easy part. - Author: Tim Gaunt - Tags: 200k Mid Market Ecommerce, Umbraco, Shopify, Plugin One of the better challenges from the Codegarden Q&A went like this: *if a client moves from Shopify to a flexible platform, aren't they trading cheap plug-and-play plugins for expensive bespoke components?* Their fulfilment partner probably has a Shopify integration sitting there ready to go. Why pay to build one? It's the most common objection in mid-market sales conversations, so it deserves a proper answer. ## Plugins assume your business works one way Every Shopify plugin works in a very specific way. That's not a criticism - it's what makes them cheap. One integration pattern, thousands of customers, a monthly fee that covers everyone. The catch is the assumption underneath: that your business operates the way the plugin expects. For a straightforward retail operation, it usually does, and Shopify is genuinely the right answer (we said as much in the first post of this series). But the businesses this series is about have processes the template doesn't fit. Trade pricing held in the ERP. Orders that need approval workflows. Stock split across warehouses that count it differently. When the plugin doesn't fit the process, you've got two options: change the business to fit the plugin, or stack more plugins on top to bridge the gap. The first means bending a working operation around someone else's software. The second is how you end up with a dozen apps that don't quite talk to each other, each taking a monthly fee, with the integration logic spread across all of them and owned by none of them. ## The ERP maths doesn't work in Shopify's favour Here's the part that surprises people: for ERP-connected businesses, the money rarely tips towards Shopify anyway. ERP provision in the Shopify ecosystem is thin. The connectors that exist are shallow, and the moment your setup deviates from vanilla (and after fifteen years of real-world use, every ERP setup has deviated from vanilla), you're into custom development regardless. So the business spends the same, often more, building around Shopify's assumptions - while still paying the platform and app subscriptions on top. Shopify knows B2B is a gap and has been working on it, but it hasn't positioned it convincingly for this market yet. You're not comparing "cheap plugins vs expensive bespoke". You're comparing bespoke-around-a-template with bespoke-on-a-flexible-foundation. The second is the one you get to keep shaping as the business changes. ## The fulfilment fear is overblown And the specific worry about 3PL and fulfilment partners? It made sense ten years ago. It doesn't really hold now. Third-party logistics endpoints aren't complicated anymore. Most fulfilment partners need one of two things: an API call or a list of addresses in CSV format. If a business works with multiple carriers, aggregators like Metapack will interface with all of them through a single integration. The plumbing has standardised. There's also a compounding effect for agencies: in any given country, a handful of carriers dominate (in the UK, think DPD, UPS, DHL and a couple of others). After a few projects you've built connections to most of them, and each new project starts from a springboard rather than from scratch. ## If you're a business weighing this up Ask yourself one question: does my operation fit a template, honestly? If yes, stay on Shopify and don't let anyone (including agencies like ours) talk you off it. If no - if you're already maintaining workarounds, exporting spreadsheets to patch gaps, or paying for five apps to approximate one process - then the plug-and-play saving is already gone. You're paying bespoke prices for templated constraints. ## If you're an agency or Umbraco partner Don't fight the plugin argument by rubbishing plugins. Concede the point where it's true: for template-shaped businesses, the app store wins. Then redirect to the real comparison - what does it cost to make *this* business fit the template, forever? The answer usually involves the workarounds the client is already living with, which discovery will have surfaced. Use their own pain, in their own words. ## The takeaway Plug-and-play is real, but only for businesses shaped like the plug. Once an ERP, trade pricing or a non-standard process enters the picture, the choice isn't cheap-versus-expensive - it's whether the bespoke work fights the platform or builds on it. And the fulfilment integration everyone worries about is usually the easiest part of the whole project. --- *Tim Gaunt is the founder and CEO of TSD, a UK e-commerce agency that's been designing, building and supporting complex commerce platforms for over 20 years. This post is part of a series based on his Codegarden 2026 talk, The €200k Sweet Spot, and the questions that followed it.*