All Articles
Product Update

Three Data Errors to Stop Before They Reach CargoWise

Duplicate house bills, bad container check digits and arrival-before-departure dates all slip through manual entry. Here is how to catch them first.

The demo above shows three errors getting caught before they ever reach CargoWise: a house bill already sitting on another job, a container number with the wrong check digit, and an arrival date keyed before the departure date. None of these look wrong at the point of entry. They only look wrong once someone downstream has to unpick them, usually a few days later, usually under time pressure.

I want to walk through why each one slips past manual entry, what it actually costs once it's inside a job, and what has to happen before it to stop it reaching CargoWise at all.

Why these three, specifically

Most data errors in freight ops fall into two camps: the ones a mandatory field catches immediately, and the ones that are syntactically fine but semantically wrong. A house bill number that's already in use is a perfectly valid string. A container number with a transposed digit still looks like a container number. A wrong date is still a date. None of them trip a "required field" validation. They need a check against something else: other jobs, a checksum, a second date on the same job.

That's the common thread. Each one needs context the data entry screen doesn't have in front of it.

1. The house bill reused on a second job

This happens most often with repeat shippers or when a job gets re-keyed from a quote. Someone pastes the house bill number from the last shipment, or a template, and doesn't notice it's identical to one already live on another job.

CargoWise doesn't stop you entering it. It's a valid reference. The problem only surfaces later, when someone queries the shipment by house bill number and gets two jobs back, or when a carrier or customs broker rejects a submission because the reference is already on file against a different consignment.

Work out what this actually costs you. Say you catch one duplicate house bill a month, and by the time it's found, documents have already gone out under it: a bill of lading, maybe a customs declaration. Tracing which job is correct, re-issuing paperwork, notifying the customer, and re-submitting to customs or the carrier is not a five-minute fix. If that's two hours of someone's time at a fully loaded cost you already know, multiply by however many of these you actually get a month, and that's your number, not an industry average.

The fix has to happen before the house bill is written to a job: check the number against every open job before it's accepted, not after.

2. The container number with the wrong check digit

Container numbers follow ISO 6346: four letters (a three-letter owner code plus a category identifier, usually U for freight containers) followed by six digits, followed by one check digit. The check digit is calculated from the first ten characters, so a single mistyped or transposed digit anywhere in the number will usually produce a check digit that doesn't match.

Here's the calculation, so you can run it yourself:

// ISO 6346 check digit calculation
const letterValues = {
  A:10,B:12,C:13,D:14,E:15,F:16,G:17,H:18,I:19,J:20,K:21,
  L:23,M:24,N:25,O:26,P:27,Q:28,R:29,S:30,T:31,U:32,V:34,
  W:35,X:36,Y:37,Z:38
}; // multiples of 11 (11, 22, 33) are skipped on purpose

function checkDigit(containerNumber) {
  const first10 = containerNumber.slice(0, 10).toUpperCase();
  let sum = 0;
  for (let i = 0; i < 10; i++) {
    const ch = first10[i];
    const value = /[A-Z]/.test(ch) ? letterValues[ch] : Number(ch);
    sum += value * Math.pow(2, i);
  }
  const remainder = sum % 11;
  return remainder === 10 ? 0 : remainder;
}

checkDigit('XXXU123456'); // returns 1
// so XXXU1234561 is valid, XXXU1234562 is not

Run that over XXXU123456 and you get a check digit of 1, so XXXU1234561 is the valid number. Change that last digit to anything else and the container reference is wrong, even though it still passes a basic "is this 11 characters" test.

Manual entry misses this because nobody recalculates a checksum by eye while keying in a booking. It's exactly the kind of arithmetic a computer should be doing and a person shouldn't. If you want to check a number right now without writing the function yourself, the free tool is at /tools/container-validator.

Once a bad container number is inside a job, it can carry through to the booking confirmation, the manifest, and the customs entry before anyone notices, usually when the terminal or carrier system rejects it. By then it's a phone call to the shipper, a correction, and a resubmission, on a container that was never going to match to begin with.

3. The arrival date keyed before the departure date

This one is almost always a keying slip: a date picker defaulting to the wrong month, or a copy-paste from a template job where only one date got updated. Nothing in a single date field looks wrong. It only becomes visibly wrong when you look at the two dates on the same job together, and in manual entry nobody is specifically checking that relationship at the point of keying.

Left in place, it quietly throws off ETA calculations, demurrage and free time tracking, and anything downstream that assumes departure comes before arrival. It's also the kind of thing a customer or broker will spot before you do, which is worse.

How CargoMode stops all three

The pattern across all three is the same: catch the error against context the entry screen doesn't have, before the record is written to CargoWise. That means checking a house bill against every open job, not just the one in front of you. Running the ISO 6346 check digit on every container number before it's accepted. Comparing the arrival date against the departure date on the same job rather than validating each field in isolation.

None of that needs a human to notice the pattern. It needs the check to run automatically, every time, before the data leaves the queue and becomes a CargoWise record someone has to fix by hand later.

If you want to see the check digit logic on a container number you're not sure about, run it through /tools/container-validator. It's free, and it's the same check described above.

Ready to automate your document processing?

Join freight forwarders saving hours every week with CargoMode.

Start for free