Can you keep Shopify and modernise everything around it?
Yes. Shopify can stay your online sales system of record while a bespoke, real-time interface gets built on top of it — no rip-and-replace, no platform migration, and nothing lost from the storefront your business already runs on. This is what Sysgraft calls a graft: a precise join between a new intelligent layer and the systems you already own.
Should you replace Shopify, or build around it?
For most £1.5m–£20m+ UK businesses selling online, the honest answer is: build around it.
Shopify is usually not the problem. It's a genuinely capable storefront and order platform, and for running online sales it does that job well. The problem is that Shopify shows you your online sales — full stop. It doesn't know your stock position in the warehouse, your wholesale order book, or what finance later books against a refund. The frustration leaders feel — "why do I have to check three screens to know if we're actually having a good month?" — isn't a reason to tear Shopify out. It's a reason to add a layer that joins web orders to everything else.
Ripping out a working storefront to solve a reporting and visibility problem is one of the most disruptive mistakes an online business can make: weeks of re-platforming, SEO risk on every product URL, and real revenue risk during cutover — to fix something a graft would fix without touching the storefront at all.
What connecting to Shopify actually involves
The first thing worth knowing is that Shopify itself has moved on from where most integration guides still describe it. The REST Admin API became a legacy interface on 1 October 2024 — new public apps have had to be GraphQL-first since April 2024, and by 2026 several newer capabilities (Shopify Functions, Checkout Extensibility, bulk operations) exist only on GraphQL, with no REST equivalent. Any build starting now should default to the GraphQL Admin API, not the REST one most older tutorials still show.
GraphQL's rate limiting works differently too: rather than counting requests, it costs each query in points against a bucket — 1,000 points on standard plans, refilling at roughly 50 points a second (100 a second on Shopify Plus), with a simple product lookup costing a handful of points and a deeply nested query costing considerably more. Designed well, this rewards asking for exactly the data a build needs rather than over-fetching — which is a genuine advantage over the old REST model once it's accounted for properly.
Common questions about modernising around Shopify
Can custom software sit on top of Shopify?
Yes. A bespoke interface can draw live order, product and customer data from Shopify's Admin API and present it alongside data from your ERP and other systems, giving leadership one real-time view without changing how Shopify itself works.
Can I get a real-time dashboard from Shopify without replacing it?
Yes. A dashboard built on Shopify can show online order and stock data updating live, sat alongside your offline and wholesale figures, so online performance isn't a separate report.
Does it matter which Shopify API a build uses?
Yes, and it's worth getting right from the start. Shopify's older REST Admin API has been a legacy interface since October 2024, with new features shipping GraphQL-first and some — like bulk operations — no longer available on REST at all. Any build in 2026 should default to the GraphQL Admin API, which uses a cost-based points system rather than a flat request count, and scales up automatically for Shopify Plus stores.
Can I see online and offline sales in one place?
Yes. Grafting an interface across Shopify and your ERP or CRM lets web and marketplace orders land in the same joined view as everything else, so online and offline performance aren't two separate pictures.
Does keeping Shopify limit what AI can do later?
Shopify's move to GraphQL if anything helps here — it's easier to request exactly the data a build needs. What limits AI usefulness is fragmented data, not which e-commerce platform you run; join your online and offline data together and AI features have something coherent to work with.
Modernising isn't migrating
The software industry has trained businesses to believe that "modernising" means a large, disruptive replacement project. It doesn't have to. Grafting a new layer onto Shopify is modernisation without the migration — you move forward on visibility and capability while your storefront, your SEO, and everything currently working keeps working.
See how the whole process works, step by step →
Get your AI Exposure snapshot Find out where your real constraint is — most often it isn't AI, and it isn't Shopify