Gymshark started life on Shopify. That fact tends to get lost in the version of this story everyone retells, which usually opens with the Black Friday outage and treats Adobe Commerce as the brand's first real platform decision. It wasn't. Ben Francis and Lewis Morgan, two teenage school friends in Birmingham, launched the business in July 2012 dropshipping bodybuilding supplements from a basic storefront, then pivoted in 2013 to designing and screen-printing their own fitness apparel out of Francis's parents' garage, using a sewing machine and screen printer bought with roughly £1,000 in savings. Within a year they'd outgrown that first Shopify setup and made the obvious-seeming, enterprise-conventional move: they migrated to Magento, later rebranded Adobe Commerce, believing a more powerful platform was what a fast-growing brand needed next. Ten months later that decision produced an eight-hour Black Friday outage, roughly £100,000 to £143,000 in estimated lost sales depending on the source, and 2,500 handwritten apology letters from a 22-year-old founder trying to hold his brand together. The platform Gymshark eventually rebuilt on was Shopify Plus — the same platform family it had left in the first place, just at a tier built for the scale it had grown into by then. That loop is the actual lesson underneath the case study everyone cites for the outage alone.
A garage brand that grew faster than its own website
Gymshark's early growth wasn't engineered by a marketing department — it happened because Francis understood, earlier than most apparel brands did, that YouTube and Instagram fitness influencers had real purchasing power over their audiences, and he sent them free product instead of buying traditional ad placements. A 2013 trade-show appearance at BodyPower in Birmingham reportedly sold out the brand's entire stock in a single day, and a viral Facebook post around the brand's Luxe tracksuit generated tens of thousands of pounds in sales within half an hour, per Shopify's own retrospective on the company. Revenue that started at roughly £500 a day was, within a couple of years, doubling year over year. That kind of growth curve is exactly the scenario every commerce-platform vendor pitches enterprise tooling against — and it's exactly the scenario in which Gymshark chose to move off Shopify and onto Adobe Commerce, reasoning that a startup-tier platform couldn't be the permanent home for a brand growing this fast.
It's worth being precise about what "startup-tier" meant in Gymshark's case, because the detail gets flattened in most retellings. This wasn't a brand hitting a hard technical ceiling — cart limits, a lack of API access, a genuine inability to process the order volume. It was a brand making the same judgment call thousands of fast-growing D2C companies make every year: that bigger, more configurable, more "enterprise" software must be the natural next step once the current setup starts to feel outgrown, even before a specific limitation has actually been hit. That instinct isn't irrational — it's just untested against the one variable that ended up mattering most for Gymshark, which was how long a rebuild would take relative to how fast the business kept moving underneath it.
The Adobe Commerce bet, and why it never actually caught up
Building on Magento/Adobe Commerce took Gymshark six to eight months and, per Shopify's enterprise blog, cost the company hundreds of thousands of dollars — a serious capital and time commitment for a business that was still a handful of years old. The problem wasn't that the platform lacked features; enterprise Magento deployments are, on paper, extremely capable. The problem was sequencing: by Francis's own account, "by the time the site was finished we had doubled in size and had already outgrown the site." A build cycle measured in months is a liability, not a strength, against a brand whose demand curve was compounding month over month — the platform was architecturally sound for the company Gymshark had been at the start of the build, and already undersized for the company it had become by the time that build shipped. That gap between build time and growth rate is the root cause everything else in this story traces back to, including the outage.
Eight hours that defined the brand
The incident most people know Gymshark for happened on Black Friday, when a surge of shoppers hit the Adobe Commerce store and the site went down for roughly eight hours. Accounts of the exact trigger and the exact dollar loss vary slightly by source — Shopify's own case study cites an estimated £100,000 loss, while other reporting puts the figure closer to $143,000 — but the shape of the failure is consistent across every account: a relatively minor technical fault cascaded into a total outage during the single highest-stakes trading day of the year. Gymshark's CTO Seb Mills later described the root cause bluntly: "one bug in one app we weren't even using crashed the entire site. It was the lowest of lows." At the time, per Peoplevox's account of the same period, Gymshark was averaging around 500 orders a day and had scaled to roughly 20,000 orders on that particular Black Friday before the platform buckled — proof the demand was real and the infrastructure simply couldn't carry it.
Reflecting on the outage in Shopify's own case study, Francis put the blame squarely on the platform while owning the customer consequence anyway: "That was supposed to be a huge day for us but we let our customers down. It didn't matter that it was Adobe Commerce's fault, it's our brand and customers blamed us which hurt." He responded by personally handwriting more than 2,500 apology notes with discount codes to affected customers — a founder-level repair effort that, by most retellings, did as much to protect the brand's reputation as the eventual platform fix did.
The replatform: ten months, not another multi-year rebuild
What makes Gymshark's move to Shopify Plus a genuinely instructive case study, rather than just a cautionary tale about Magento, is how deliberately fast the second migration was. Ten months after committing to Adobe Commerce, Gymshark replatformed onto Shopify Plus — a timeline that stands in direct contrast to the six-to-eight-month build that had already left the brand undersized on arrival the first time. Francis has since been candid that the failed detour had value: "It's a good thing we went onto Adobe Commerce because otherwise we'd probably take a lot of what Shopify Plus does for granted." The rebuilt operation paired Shopify Plus with Peoplevox's warehouse-management system to handle fulfillment accuracy and speed at the volumes Black Friday now demanded, added Shopify POS for pop-up activations at gym expos and world tour stops, and used Shopify Scripts, at the time, for checkout-level customization such as loyalty freebies and promotional logic — features Gymshark could lean on rather than build and maintain itself, which is precisely the trade the six-to-eight month Adobe Commerce build had gotten backwards.
What the replatform actually unlocked
The results Shopify itself cites are specific rather than vague. By 2017, Gymshark reported £41 million in annual sales and was shipping to more than 131 countries; by the 2018 fiscal year, per Shopify's enterprise blog, revenue had reached roughly $128 million. Black Friday order volume — the exact metric that had broken the Adobe Commerce build — climbed from around 20,000 orders on the disastrous 2015 event to roughly 90,000 orders in a later post-migration Black Friday, handled without a repeat of the earlier outage. Gymshark's own "Blackout" holiday campaign, built around darker imagery and paid social targeting, reportedly drove a 197% year-over-year increase in holiday revenue and a 9.3x return on Facebook and Instagram ad spend — strong enough that Meta COO Sheryl Sandberg cited Gymshark by name on a public earnings call as an example of a European brand using the platform effectively. None of that marketing performance would have mattered if the underlying store had buckled the way it had in 2015; the platform work is what made the marketing work survivable at scale.
Scaling past a single storefront: composable commerce and zero-downtime Black Fridays
Gymshark's platform story didn't stop at the Shopify Plus migration. As the business grew into a genuinely global operation, it moved toward a more composable, API-first architecture — pairing Shopify's commerce core with Algolia for search, browsing and product recommendations, and Contentful for content management, rather than trying to force every function through a single monolithic build the way the Adobe Commerce era had. Rewind's account of Gymshark's infrastructure around this period notes the brand was operating 14 separate Shopify stores by then, serving different regions and channels, which pushed the company to adopt dedicated backup tooling in 2018 after discovering Shopify's own default backups weren't sufficient for a footprint that size — a reminder that even a well-run migration creates new operational risks that have to be managed deliberately, not assumed away by the platform switch itself. By Black Friday 2022, per Algolia's own case study, that composable setup delivered zero downtime, stable API response times under roughly 200 times normal site traffic, a 150% increase in order rate among new users, and a 30% increase in clicks on product recommendations — the almost exact inverse of the 2015 outage, on a business now doing a large multiple of the volume.
From scrappy migration story to a billion-pound business
The platform story eventually became a footnote in a much larger financial one. In August 2020, growth-equity firm General Atlantic acquired a 21% stake in Gymshark for a reported £200 million, valuing the company at more than £1 billion (roughly $1.3 billion) and making it one of the UK's few unicorns built entirely direct-to-consumer. Francis retained a stake reportedly worth several hundred million dollars at the time, and Forbes has since named him one of Britain's youngest self-made billionaires. More recent reporting indicates Francis has been in talks to buy back part of General Atlantic's stake, a sign of a founder wanting tighter control as the business matures rather than a sign of trouble — Gymshark's revenue crossed £556 million in fiscal 2023 and £607 million in fiscal 2024, per UK trade press covering the company's Companies House filings, with gross margin improving to roughly 63% and the business now employing several hundred people from its Solihull headquarters, plus offices in London and Denver, Colorado. The brand has also pushed into physical retail it never had in its Adobe Commerce years, opening a flagship store on London's Regent Street in 2022 that reportedly outperformed expectations, followed by further UK locations.
Gymshark didn't fail on Adobe Commerce because Magento is a bad platform in the abstract — plenty of large retailers run it successfully. It failed because a platform requiring a six-to-eight-month, six-figure build cycle is structurally mismatched to a brand doubling in size before that build even ships. The fix wasn't "a better platform" in some absolute sense; it was a platform whose implementation speed actually matched the brand's growth rate, which for Gymshark's specific situation at the time turned out to be Shopify Plus.
What this means for a Shopify D2C brand
The instinct Gymshark had in 2013 — that a startup platform can't be the permanent home for a fast-growing brand — isn't wrong on its own. Most brands genuinely do outgrow entry-level tooling. The mistake was assuming that "more enterprise-grade" and "right platform for this brand right now" were the same question, when they aren't. A platform decision made under real growth pressure has to weigh implementation speed as seriously as feature depth, because a build that takes half a year to ship is a build that's already behind the business by the time it launches on a compounding growth curve. That's the practical version of what a Shopify Plus migration is meant to solve for a brand in Gymshark's position: not a permanent, one-time platform decision made in isolation, but infrastructure sized and paced to match how fast the brand is actually moving, with room to add composable pieces — search, content, warehouse management — around a stable commerce core rather than rebuilding that core from scratch every time the business changes shape. The other half of the lesson is less technical and more about how a founder handles the failure once it happens: Gymshark's recovery wasn't just a platform swap, it was Francis personally writing thousands of apology letters and being publicly candid about what went wrong, which is very plausibly as responsible for the brand surviving its own outage as any infrastructure fix was.
There's also a quieter, less flattering lesson worth naming: Gymshark got to make this mistake and recover from it while still a private company with a founder willing to personally absorb the reputational hit. A brand evaluating its own platform today rarely gets that same grace period — a public company, a VC board with a growth mandate, or a retailer mid-way through a paid acquisition campaign is unlikely to tolerate a multi-month rebuild that arrives already undersized, or an eight-hour outage on the single biggest revenue day of the year, without real consequences. That's the honest reason "move fast, rebuild if needed" isn't a complete strategy on its own — it worked for Gymshark because the failure happened early enough, and the founder responded fast and personally enough, that the brand's reputation absorbed it. A brand evaluating a Shopify Plus migration today, whether coming off Adobe Commerce, BigCommerce, or a custom build, is better served treating the platform-fit question — build time, peak-load headroom, and total cost against the growth rate actually being underwritten — as a recurring check on the calendar rather than a one-time decision made once and revisited only after something breaks.
About this case study.
Did Carryup work with this brand?
No — Carryup did not work with Gymshark. This is independent analysis of publicly available information (official case studies, press coverage, and reported figures — see the sources cited on this page), written to extract lessons transferable to other Shopify D2C brands. Our own client work lives on the Work page, with real, attributable results.
Does this apply if my brand is a different size or category?
The underlying mechanics — infrastructure readiness, retention systems, platform fit — are largely category-agnostic. The specific numbers will differ, but the diagnostic approach transfers.
How do I know if this problem applies to my store?
The fastest way is a direct diagnostic of your own store, tracking, and infrastructure — we can tell you within a week whether the same pattern shows up.
Related reading.
Want results like these for your brand?
Tell us about your store — we'll review your setup and tell you exactly where the opportunity is.