This is one of the most common questions we hear, and the honest answer is: your weighbridge was never designed to know about EWC codes or Duty of Care paperwork — it doesn’t need to. WasteBolt Import Templates fill in exactly those gaps automatically, the moment your data is imported. Import Templates are the same underlying system as Quick-Fill Templates — here they’re applied by auto-matching a rule instead of a manual selection.

Why the Gap Exists

Weighbridge software is built to do one job brilliantly: record accurate weights, vehicles and tickets. It was never built as a waste compliance system, so it has no concept of EWC (European Waste Catalogue) codes, formal waste descriptions, or the permit/licence numbers Digital Waste Tracking requires from the consignee and carrier. That’s normal, and it’s exactly what Import Templates exist to solve.

What your weighbridge already records:

  • Customer / account name
  • Net weight (kg)
  • Date / ticket number
  • Vehicle registration

What’s usually missing:

  • EWC waste code
  • Formal waste description
  • Consignee permit / EA number
  • Carrier licence number

An Import Template fills in everything your weighbridge captured, plus the EWC code, waste description and consignee/carrier compliance details — filled in the moment the record is staged, based on rules you set up once.

How Import Templates Fill the Gap

An Import Template is a matching rule you set up once — for example, “if the product name contains Mixed C&D, apply EWC 17 09 04 and waste description ‘Mixed construction and demolition waste’.” Every time a CSV row, WasteBolt Gatehouse CSV watch, or Gatehouse SQL Server Sync matches that rule, WasteBolt fills in the missing fields automatically — no manual data entry, no missed compliance details.

The match happens in four steps:

  1. CSV row lands in the Import queue — e.g. “Company Name” reads “ABC Skips Ltd”, “Product” reads “Mixed C&D”.
  2. Matching rule checked — a template says: if Company contains “ABC Skips” → apply this template.
  3. Fields auto-filled — EWC 17 09 04, waste description, consignee, carrier all applied at once.
  4. Ready for DWT — the record shows a Ready badge on the Digital Waste Tracking page.

Setting One Up

  1. Go to Import Hub → Import Templates. Click “New Template” and give it a name that describes the waste type, e.g. “Mixed C&D — ABC Skips”.
  2. Set the matching rule. Choose the field to match on (usually Company Name or Product) and the text it should contain, e.g. Company Name contains “ABC Skips”.
  3. Fill in the compliance fields. Set the EWC code, waste description, and — if this template should also fix consignee/carrier details — pick the correct entry from your Customer pick list.
  4. Set priority and save. If more than one template could match the same row, higher-priority templates are checked first. Save, and it applies to every future import automatically.

See Setting Up Your Customer Pick List and Waste Types for how consignee permit numbers, carrier licence numbers and EWC codes are stored so templates can pull them in.

Frequently Asked Questions

Does my weighbridge need to record EWC codes?

No. Very few weighbridge systems capture EWC codes natively. WasteBolt Import Templates apply the correct EWC code automatically based on the product/material name your weighbridge already records.

What if a load doesn’t match any template?

It still lands in the Import queue, just without the auto-filled fields. You fill in the missing details manually on that record, or create a new template so future loads of that type match automatically.

Do I need one template per customer?

Usually templates are built per material/waste type rather than per customer, since the EWC code and waste description depend on what the load is, not who it’s from. You can combine rules if a customer always sends the same waste type.

Does this work with WasteBolt Gatehouse, or only manual CSV upload?

All three. Templates apply to every route data takes into the Import queue — manual CSV upload, WasteBolt Gatehouse CSV watch, Log Job, and SQL Server Sync — since they all land in the same place.

What’s Next