Skip to content
English
  • There are no suggestions because the search field is empty.

Validate data that gets collected

We all make mistakes. Bummer. But we have checks and balances to avoid making such mistakes really costly. Cargosnap helps with "validation".

Has it happened to you that you were working on a couple of shipments and ended up loading product into the wrong truck? Or you assumed a certain container was sealed with a seal with a certain id, only to find out later (detained container) that someone swapped seals? Costly!

If you know what container, seal, barcode, or any field should be handled in a file, Cargonap allows you to 'validate' that value. 

Example case: container code validation

Imagine that you have a container export process that consists of these 3 steps:

  1. Document checks

  2. Container inspection

  3. Container loading

Now, imagine that in step 3 you want to "double-check" that in fact the same container from the provided documents is being used.

In Cargosnap, you may opt for 3 separate workflows to accomplish this (or just one, all on the specific conditions you have). So lets create these 3, looking much like:

Workflow 1: Document checks

- Scan container code from document

Workflow 2: Container inspection

- Scan container code from container door

Workflow 3: Container loading

- Scan container code from container door

Now - by enabling "Validate" in this step:

Scherm­afbeelding 2026-07-10 om 14.48.36

You just turned on a process whereby you validate that the same code as collected in Workflow 1, 2 and 3 is in fact used!

So, in the case the container code used is not the same as in workflow 1 and 2, a warning will be shown, and the operator of the Cargosnap app will not be able to proceed, until the error is corrected. This may avoid costly mistakes!