“DEFRA Approved” Waste Tracking Software: What the Term Actually Means (and Who's Really on the List)

If you've searched for “DEFRA approved waste tracking software” you've probably noticed something odd. A handful of providers use the word “approved” front and centre. Others avoid it completely. Some talk about being “recognised”. A few just say they “integrate” with DEFRA's system and leave it at that.

None of this is accidental. It comes down to a specific line in DEFRA's own terms of service, and most buyers have no idea it exists.

What DEFRA actually checks

DEFRA's digital waste tracking service works through an API. Software providers connect their product to that API and DEFRA runs a set of production approval tests, known as PAT, to check the connection handles waste movement scenarios correctly. There are 14 of them, covering things like hazardous waste handling and standard receipt logging. Some providers hold exemptions for specific scenarios they don't cater for, hazardous waste being the most common one.

Once a provider's software passes, DEFRA lists it on gov.uk as meeting the digital waste tracking requirements. That's the actual, verifiable thing that happens.

What DEFRA has not done is review the software itself. It hasn't tested the user interface, checked the reporting tools, assessed customer support, or vetted the company behind it. It has only confirmed that data submitted through that provider's API connection comes through in the correct format. DEFRA's own guidance is explicit that buying software is done at the buyer's own risk, and that responsibility for meeting regulatory requirements sits with the buyer, not with DEFRA.

That distinction, tested versus approved, is the whole story.

Why the wording matters more than it looks

Providers accepting DEFRA's terms of service agree to specific rules about how they describe their status. Language implying DEFRA has approved, endorsed, or certified the software as a product is not permitted. Providers can accurately say their software has integrated with the API and passed the production approval tests. That's a different, narrower claim, and it's the one DEFRA is actually willing to stand behind.

The reason this keeps coming up in developer forums is straightforward. “Approved” and “accredited” carry real search value. Buyers type those words because they're looking for reassurance in a market with no formal accreditation body. So there's a genuine commercial pull toward language that oversteps what's actually been confirmed, even though DEFRA has no visibility into which providers are doing this and has given no indication it plans to police the wording.

For a buyer, this is worth knowing before you make a decision. A provider marketing itself as “DEFRA approved” isn't lying about being on the list. It's just describing that fact more grandly than DEFRA itself does.

The current list of compatible providers

DEFRA keeps the list itself and adds to it as more providers pass testing, so the version on gov.uk is the one to check before you commit to anything. The table below is that list as it stood when DEFRA last updated the page on 8 September 2026. It is not a complete picture of the market either: a provider can be perfectly capable and simply not have finished testing yet.

LoadSnap is on the list under Webhero, the company that builds it, which is why searching gov.uk for the product name turns up the company instead. There are no exemptions against it, so it passed all 14 scenarios rather than carrying a carve-out for certain waste types.

How to actually evaluate a provider

Since “approved” isn't a real category, and being on the list only confirms API compatibility, the useful questions are different ones:

• Does the provider hold any PAT exemptions, and if so, do those gaps matter for the waste types you handle
• How easy is the receiving and carrier workflow for the people actually using it day to day, since DEFRA never assessed this
• What happens to your data and reporting once it's submitted, not just whether the submission itself succeeds
• How responsive is support when something breaks close to a reporting deadline
• Is pricing transparent, or does the real cost only show up once you're mid-onboarding

These are the things that separate providers in practice, and they're exactly the things the gov.uk list can't tell you.

Where LoadSnap fits

LoadSnap passed DEFRA's full set of production approval tests with no scenario exemptions and appears on the official register under Webhero. Beyond the API connection, it's built specifically around the day to day reality of receiving sites and carriers, not just the compliance checkbox. That's the part worth looking at once you've confirmed a provider is actually on the list, rather than just claiming to be the kind of thing that would be.

If you're choosing a digital waste tracking provider now that the October 2026 rules are in force, start with the actual gov.uk register, then judge providers on the things DEFRA was never checking in the first place.