Case study 05Dust Arrest · UK and EU · 2022 – present

Selling dust control to whole industries

A specialist dust-control store with industry landing pages, deals the team runs from the Commerce Toolbox, clear lead times, and a cart that stays accurate however many tools update it.

Role
Sole engineer
Owned
Landing pages, merchandising, cart reliability, stock messaging
Stack
Shopify · Liquid · JavaScript · Shopify APIs
Buyers
Contractors, industrial and facilities buyers across the UK and EU
Interface
Problem

A technical range most buyers do not know well

Dust Arrest sells extractors, air scrubbers, filters and parts to contractors and industrial buyers across the UK and Europe. Most arrive knowing their dust problem, not the product that solves it.

Offers and deals also change often, and the team needed to run them without waiting on a developer each time.

Constraints
01
Each industry needed its own case, on pages the team could change without a developer
02
Pack sizes and offers had to use the store’s real stock and prices
03
Deals had to end on time or when stock ran out, whichever the team chose
04
Several tools update the cart at once, so none could be trusted to keep it accurate alone
System

The platform sets the rules, the storefront sells

Pack sizes, upgrade offers, recommendations and sale countdowns run on the Commerce Toolbox, a Shopify app I built. The team sets them up and changes them there, with no developer involved.

Industry and launch pages are built from ready-made sections the team arranges without a developer. Every update to a buyer’s cart, whether from an offer, a bundle or an app, is applied one at a time, in order.

Layers
Landing pagesIndustry pages · product launches · built by the team
Commerce ToolboxPack sizes · upgrade offers · recommendations · sale countdowns
AvailabilityLead times · low stock · discontinued products
Cart updatesApplied in order · checkout waits until done
Buying toolsQuote basket · parts ordering · trade pricing
ReportingGoogle Ads · Google Analytics
Decisions

Six decisions that shaped the build

01

Industry pages that start with the risk

A bakery cares about flour dust before any extractor, so its page opens on that risk, shows a bakery customer’s story, then groups solutions by where dust gathers.

02

Lead times buyers can plan around

Products that take time to arrive show their own lead time in days or weeks, so buyers know when to expect an order before they commit.

03

Offers the team runs themselves

Pack sizes, upgrade offers and deals are set up in the Commerce Toolbox by the team, so a new promotion goes live without waiting on a developer.

04

Cart updates applied in order

When several tools update a cart at once, they can clash and show the wrong items. Each update now waits its turn, and checkout waits until the cart is ready.

05

A launch page that still sells

The DB650 launch tells the product’s story, lets buyers explore each part of the machine on the image, and ends with the range to buy, one step from the cart.

06

Sale countdowns that create urgency

A countdown shows buyers how much sale stock is left, with an optional timer, and the team chooses whether the deal ends when time runs out or stock sells out.

Landing pagesFig. 02 – 04
Industry and product launch pages
Results

More of the sale made on the storefront itself

Buyers from an industry or product campaign land on a page that argues their case and ends one step from an enquiry or the cart.

Deals and offers are run by the team in the Commerce Toolbox, and cart updates are handled in one place, so new features do not bring back old problems.

Measured
Industry and launch pages the team changes without a developer
Pack sizes, upgrade offers and sale countdowns run by the team in the Commerce Toolbox
Lead times and discontinued products shown on each product, set by the team
Cart updates applied in order, with checkout waiting until they finish
Judgement

Trade-offs

Running deals through the Commerce Toolbox means Dust Arrest works within the options the app offers, rather than getting one-off features. In exchange, the team launches promotions themselves, and each improvement reaches every store using it.

What I would do differently

I would put one-at-a-time cart updates in place first, so every new tool starts with them rather than being moved over later.

Previous case study · 04Selling through distributors, not around themMAXVACNext case study · 06Earning enterprise trust before the first callLeach’s corporate homepage hero reading Your Global Scaffolding Partner, trusted for over 100 years in over 80 countriesLeach’s