WizMedia WizMediaDIGITAL STUDIO
Home / Insights / Defra DWT
Defra DWT · 6 min read

API, CSV or the portal: which Defra submission route should you actually use?

Defra accepts waste data three ways. They are not equivalent, and the cheapest one to set up is the most expensive one to live with.

Every operator coming into scope asks the same question in a slightly different way: what is the least work we can get away with? It is a fair question. Here is the honest comparison.

The portal

Defra provides a web form. Someone on your team signs in and types each movement into it.

Nothing to build, nothing to buy, and it works on day one. That is the whole case for it, and for a site taking a handful of loads a week it is a perfectly reasonable answer.

The problem is that the cost is a person, and it scales exactly with your volume. Forty loads a day is forty form submissions, every day, for ever. It is also the route where mistakes are most likely, because the person typing is reading off a ticket that already exists somewhere else in your business.

CSV upload

You export a file from whatever system you already use and upload it to Defra.

Better. One action covers many movements, and the data comes out of a system rather than off a clipboard. For a lot of operators this is the sensible middle step, particularly if your software already produces something close to the right format.

Two things to watch. It still depends on a person remembering, which means it fails on the days when everyone is busy, which are the days with the most movements. And export formats drift: someone adds a column, a supplier changes a description, and uploads start failing quietly.

API integration

Your system talks to Defra directly. The movement is recorded once, where your team already records it, and the submission happens without anyone doing anything.

It costs more to set up and it is the only route where nobody has to remember anything. That is the real distinction. With the portal and with CSV, compliance is a task on somebody's list. With an API, compliance is a property of your system.

It also gives you something the other two do not: a record of what was sent and what was accepted, in your own system, at the time it happened. When a regulator asks, you are not reconstructing.

So which one?

  • Low volume, no software worth the name: use the portal. Genuinely. Do not spend money to automate ten movements a week.
  • Decent volume, software that exports cleanly: CSV is a reasonable stepping stone, as long as someone owns it.
  • Real volume, or more than one site, or software your team lives in: integrate. The build pays for itself against the labour, never mind the subscription you are not paying.

The one combination we would argue against is a busy site running the portal manually while already owning a system that holds all the data. That is paying a person to retype your own records.

Not sure which bracket you are in? Tell us roughly how many movements a week you handle and what system records them, and we will tell you which route we would pick, including when the answer is that you do not need us. Ask us

Get in touch

Ready when you are.

A website, an app, custom integrations or a full connected platform. Tell us what you are planning and we will tell you honestly what it takes.

contact@wizmedia.co.uk +44 7415 935604
33 Campshill Road, London SE13 6QU
Mon to Fri, 9:00 to 17:00
Book a free consultation