Skip to content

Case studies

What we built, and what it cost to get right

No stock photography, no invented percentages. Each of these is a real engagement written up the way we'd want to read it — what was broken, what we did, and what generalises.

Written up

What actually happened on five of them

Gift4SoulBespoke PHP → Shopify

Rebuilding a 7,000-SKU catalogue from a site that had no export

A 20-year-old custom PHP store with no usable export and hundreds of unlinked category pages. We reconstructed the entire catalogue by crawling the live site, then rebuilt it on Shopify — 6,965 products and 165 collections, structure intact.

products migrated
6,965products migrated
collections rebuilt
165collections rebuilt
categories lost in transit
0categories lost in transit
Read the case study
A specialist US retailerMagento 2 → Shopify Plus, Brightpearl ERP

Magento 2 to Shopify Plus, with the ERP left in charge

A high-SKU retailer running Magento 2 on top of Brightpearl. We moved the storefront to Shopify Plus and rebuilt the ERP integration around it — so the catalogue, pricing and fulfilment stayed authoritative in Brightpearl while the store got faster and cheaper to run.

Read the case study
A third-party logistics operatorShopify, WooCommerce, carrier APIs

The order relay that stopped losing orders

A logistics operator was reconciling orders between merchant storefronts and carrier systems by hand. We built a relay that pushes orders automatically, survives rate limits and outages, and — the hard part — proves nothing was silently dropped.

unattended in production
24/7unattended in production
silent drops after the sweep shipped
0silent drops after the sweep shipped
Read the case study
A specialist US retailerShopify Plus + Brightpearl

Stock status that maintains itself

Stock availability and promotion eligibility were being maintained by hand across thousands of variants. We built a scheduled sync that derives both from the source of truth and writes them back to Shopify, so merchandising rules apply themselves.

sync cadence, unattended
Every 30 minsync cadence, unattended
Read the case study
KetoNetWordPress, WooCommerce, BuddyPress

A community site that felt slow because the server was out of memory

A WordPress community and recipe platform was slow in a way that no caching plugin fixed — because the bottleneck wasn't caching, it was PHP opcode cache saturation. We found it, then rebuilt the community layer as a proper social feed on top.

Read the case study

Your project could be next on this page

Tell us what you're running and what's going wrong with it. If we're not the right fit we'll say so on the call rather than three weeks into a proposal.

No obligationNo sales deckReply within one business day