Solution Architect · Business Analyst · Delivery LeadMelbourne, Australia

JoeErrington.

12+ years in digital commerce, architecture and delivery.

Explore my work

Selected work

Six projects / My contribution
01

Redarc Electronics

Redarc logo
Business Analyst

Accelerating growth

A lucrative B2B market was being underserved by REDARC’s existing B2C site. Trade customers were expected to complete a lengthy onboarding process before being given access to company accounts and agreed pricing. The convenience of shopping at home wasn’t being matched at work, largely because complex company data and pricing agreements had to be created across the ERP and commerce platform.

A two-way integration between IFS and Adobe Commerce was implemented to fully automate company signup. Both APIs were worked through in detail, and the many dependent steps were mapped into coordinated integration sequences. First-time trade customers were allowed to check out as guests, with their first order data then used to onboard them into IFS.

A simpler route from first purchase to an established trade account was delivered, without the manual onboarding bottleneck. A 100% increase in conversion rate and a 29% increase in new trade accounts were achieved.

  • Adobe Commerce
  • IFS
  • Adyen
  • Avalara
  • 100%increase in conversion rate
  • 29%increase in new trade accounts
Read case study for Redarc Electronics (opens in a new tab)
02

BSR Group

Betta logo
Solution Architect

Doing the impossible

Years of legacy development had been accumulated across Betta’s commerce platform. Features had been stacked on top of earlier features, with conflicting behaviour and custom code that could no longer be maintained reliably. The requirements were considered so bespoke that a platform with direct access to backend code and the database was believed to be essential.

The requirements were revisited from scratch, and a full audit of the existing systems was carried out. Much of the commerce customisation was traced back to misunderstood systems of record or functionality that had already been implemented elsewhere. Those overlaps were untangled, and each requirement was mapped to the system best placed to manage it.

SaaS commerce was made viable where it had previously been ruled out. A simpler architecture was delivered, maintenance costs were reduced by 30%, and a 33% increase in record trading-day revenue was achieved.

  • Shopify
  • Azure
  • BoostAI
  • 30%lower maintenance costs
  • 33%increase in record trading-day revenue
03

La Trobe University

La Trobe logo
Business Analyst

Three days to three minutes

Growing demand for short courses and microcredentials was being handled through university systems built around slower-moving degree enrolments. An instant signup and familiar online shopping experience were expected by students, but a three-day process and significant manual administration were being imposed by the existing setup.

An automated purchase and enrolment journey was designed alongside an enterprise architecture process. Adobe Commerce was fitted into the university ecosystem, with its responsibilities defined against existing platforms. Architectural principles were maintained, and unnecessary duplication or clashes with established technology were avoided.

Enrolment time was reduced from three days to three minutes, and operational hours were cut by 90%. A faster student experience was delivered while the university’s existing systems and architectural direction were respected.

  • Adobe Commerce
  • Adobe Experience Manager
  • SAP
  • Salesforce
  • Moodle
  • 3 minenrolment time, down from 3 days
  • 90%reduction in operational hours
04

Taubmans

Taubmans logo
Solution Architect

Complex trade commerce, made simple

After several unsuccessful B2B shopping initiatives, Taubmans had been left behind its rivals. A straightforward buying experience was complicated by paint being tinted on demand, stock being held in fixed pack sizes, and painters moving between companies while retaining personal email addresses. Subcontractors also needed to be given the main contractor’s pricing for particular jobs. Mobile apps were requested, but separate codebases were to be avoided.

Each custom requirement was carefully mapped to Shopify, and proposed features were worked through with the client until the essential behaviour could be supported. A Hydrogen storefront was wrapped in .NET MAUI to provide iOS and Android apps from a shared storefront codebase, with an app-like interface, push notifications and geolocation. Order management was included so store teams could adjust purchases around stock, tinting and fulfilment needs.

A connected trade purchasing experience was delivered across web and mobile, with the complexity handled behind the scenes. Company access, job-specific pricing and store fulfilment were accommodated, while separate storefront implementations for each mobile platform were avoided.

  • Shopify
  • Hydrogen
  • AWS
  • SAP
  • Salesforce
  • .NET MAUI
  • 100%increase in revenue
  • 3,000trade customers reached
Read case study for Taubmans (opens in a new tab)
05

Dermapen World

Dermapen World logo
Solution Architect

Scaling globally, staying local

Global growth had been made expensive by a growing collection of platforms. Local teams needed control of their own content, while brand standards and shared requirements had to be protected by headquarters. Each new country was being treated as another implementation, adding cost and complexity to expansion.

Shopify, Hydrogen and Storyblok were combined so commerce data could be centralised while marketing content and site structure were managed locally. Purchasing, B2B onboarding, staff training and marketing collateral were brought into one practitioner dashboard. For consumers, the journey was shaped around building confidence in microneedling, with the brand positioned as a trusted authority among cheaper alternatives.

A repeatable foundation for international rollout was established, with local autonomy supported by central governance. Practitioners were given one destination for purchasing, education and equipment support, while consumers were guided through a more reassuring journey. Expansion could be supported through the shared platform rather than another set of disconnected systems.

  • Shopify
  • Hydrogen
  • Azure
  • Storyblok
  • Salsify
  • 30countries reached
  • +30%conversion rate
06

Altura Learning

Altura Learning logo
Solution Architect

Built for the way learning is bought

A highly specific signup journey and product model were being constrained by manual administration. Course access had to be arranged after purchase, slowing onboarding and limiting growth. SaaS commerce was considered a poor fit, while an enterprise PaaS platform would have introduced far more software and maintenance than the requirements justified.

A purpose-built LiteCommerce solution was developed on AWS using Amplify, Lambda and Aurora. The checkout was tailored to the product model, and account creation and course access were connected through an automated onboarding workflow. The customer journey was also shaped to communicate the quality of the learning product in a market crowded with inexpensive AI-generated alternatives.

A lean commerce platform was delivered around the actual requirements, with control retained over checkout, product data and onboarding. Course access was automated, removing the dependency on manual account setup. Signup time was reduced from one working day to five minutes, giving customers faster access to their courses.

  • AWS
  • HubSpot
  • Storyblok
  • Bridge
  • 5 minsignup time, down from 1 day
  • Automatedcourse access after signup
Contact

Let's talk.

Have a project in mind, or a role you think would be a good fit? I'd like to hear from you.