Industries
Built for how your buyers buy.
A distributor's buyer and a fashion customer share almost nothing — not the catalog, not the pricing, not the checkout, not the reason they came back. We build commerce around the purchasing behaviour of your sector rather than retrofitting a DTC template to it.
Why Sector Matters
The catalog is the giveaway. So is the checkout.
You can usually tell within a minute whether a store was built by people who understood the sector. A parts retailer whose search cannot filter by vehicle. A distributor whose trade customers have to phone in for pricing. A university shop that cannot separate a department's purchase order from a parent buying a hoodie.
None of these are platform limitations. They are the result of a build that treated commerce as generic — catalog, cart, checkout, done — when the actual work sits in the details of how that industry's buyers make decisions and how their back office expects an order to arrive.
Sixteen years across these sectors means we usually recognise your constraints before you finish describing them, and we know which of them are genuinely hard versus which are a solved problem on the right platform.
Sectors
Seven verticals, each with its own hard part.
What actually makes commerce difficult in your industry — and what we build to handle it.
B2B eCommerce
The hard part is that price is not a property of the product — it is a property of the relationship. Contract rates, volume breaks, negotiated terms, and an approval chain standing between the person who needs the goods and the person allowed to commit spend.
- Quote-to-cart with multi-step approval routing
- Customer-group and contract pricing synced from ERP
- Requisition lists, fast reorder, and rep-assisted ordering
- Credit terms, purchase orders, and partial shipments
Built for: Wilmot Harvey, ISIC Systems, BFX Furniture — trade and account-based purchasing on Adobe Commerce.
Enterprise eCommerce
At enterprise scale the storefront is the small problem. The real work is a catalog spanning regions, currencies, tax regimes, and warehouses — kept consistent across brands and channels while the business keeps reorganising underneath it.
- Multi-store, multi-region, multi-currency architecture
- Multi-source inventory and warehouse-aware fulfilment
- Headless frontends where one catalog feeds several channels
- Peak-traffic load testing before the trading season, not after
Built for: Food Service Direct (headless, large US food-service catalog) and Aelia Duty Free (global travel retail).
Manufacturing & Distribution
Technical catalogs where products have specifications, not marketing copy — and buyers who search by part number, spec range, or compatibility. Behind it, a dealer network that each needs its own pricing, and an ERP that has always been the source of truth.
- Spec-driven search, filtering, and datasheet management
- Dealer and distributor portals with per-account catalogs
- Real-time ERP sync for stock, pricing, and lead times
- Bulk ordering, minimum quantities, and pack-size rules
Built for: Engineering & Lubricating Supplies — a UK industrial supplies distributor on Hyvä-powered Adobe Commerce.
Fashion & Apparel
Merchandising is the product. Size and colour variants multiply the catalog, returns are a designed experience rather than an edge case, and a drop can put a season's traffic through the checkout in ten minutes.
- Variant-heavy catalogs with size, colour, and fit logic
- Drop and pre-order mechanics that survive traffic spikes
- Headless and Hydrogen storefronts for editorial-grade design
- Subscription, bundling, and loyalty mechanics
Higher Education
One storefront serving three completely different buyers: students on personal cards, departments on internal budget codes, and alumni buying merchandise. Each needs its own pricing, permissions, and paperwork — inside one institution's brand.
- Department accounts, budget codes, and internal purchase orders
- Course-material and bookstore catalog workflows
- Spirit-shop merchandising alongside academic supply
- Term-driven traffic peaks planned for in advance
Sports & Outdoors
Customers who research hard before they buy, gear that must be matched to body, terrain, or discipline, and demand that swings violently with the season. The store has to educate as competently as it sells.
- Product configurators and guided selling by use case
- Team and club stores with group ordering
- Seasonal scale planning and peak-traffic hardening
- Deep technical content wired into commercial pages
Built for: Paddy Pallin (Australian outdoor and adventure retail), RK Guns, and GreatSkate.
Automotive & Powersports Parts
The industry where the wrong search result becomes a return. Hundreds of thousands of SKUs, each valid only for a specific set of year-make-model combinations, sitting on fitment data that is never quite clean when it arrives.
- Year-make-model and VIN-based fitment search
- Fitment data ingestion, normalisation, and QA pipelines
- Very large catalog indexing kept fast under load
- Dealer pricing and cross-sell by compatible part
Built for: Big Bike Parts (motorcycle and powersports parts, Hyvä) and Leatt (global protective gear).
What Carries Across
Different sectors. Same engineering discipline.
Catalog architecture first
Attributes, taxonomy, and search are designed before the theme. In every sector, the catalog model is what makes a store feel fast or feel broken.
The back office is part of the build
An order that lands correctly in the ERP matters more than one that looks pretty in the confirmation email. We design the integration alongside the storefront.
Built for the peak, not the average
Term start, drop day, race season, Black Friday — every sector has a week that decides the year. We load-test for that week specifically.
FAQ
Industry questions.
We're B2B but our customers expect a DTC experience. Can we have both?
That is now the default expectation, and yes. The pattern is a consumer-grade storefront on the front with account-aware pricing, approvals, and reordering underneath — so a logged-in trade buyer sees their contract terms while a guest sees list price. All four platforms we build on can support it; how cleanly depends on the platform and your ERP.
Our fitment or specification data is a mess. Is that a blocker?
No, but it is real work and we would rather price it honestly up front than discover it in sprint three. We build ingestion and normalisation pipelines with validation and QA reporting, so bad rows are caught before they reach the storefront and turn into returns.
Do you only work in these seven sectors?
These are where we are deepest, but the underlying problems — complex catalogs, account-based pricing, ERP integration, peak traffic — recur across many industries. Tell us how you sell and we will say plainly whether our experience transfers.
Which platform suits our industry best?
Catalog complexity and B2B requirements usually decide it. Very large, spec-heavy, or deeply B2B catalogs tend toward Adobe Commerce or BigCommerce; brand- and content-led retail often fits Shopify Plus or WooCommerce. We are certified across all four, so the advice is not steered by what we prefer to build.
Can you handle our peak trading season?
We plan for it explicitly — load testing against modelled peak, caching and indexing strategy, a freeze window before the season, and follow-the-sun cover across US, NZ, and PK time zones so an incident does not wait for one office to open.
Start a Project
Tell us how your customers buy.
Describe the catalog, the buyers, and the systems behind the checkout. We will come back within one business day with a straight read on what your sector actually needs.