Feature - double-dip prevention
EPRlog Double-dip prevention

The same bale can never submit twice.

Every photo is hashed against the whole network the moment it lands. It is mathematically impossible to submit the same bale twice - not by your crew, not by anyone else. Zero ghost tonnage.

For PROs + producers
The field app is free forever for the people doing the collecting.
Duplicate bale submission caught by the EPRlog cross-network photo ledger
BALE-7890-A340 kg cardHashedOK
BALE-7912-C270 kg PETHashedOK
BALE-7890-Bsame photoDuplicate
How it works

Three steps. Zero effort.

1

Hash on arrival

Every photo is fingerprinted the moment it is submitted - cropping, re-shooting the print or tweaking pixels does not change the match.

2

Check the network

The fingerprint is compared against every photo ever submitted across the whole network, not just your own sites.

3

Flag and block

A match blocks the submission and flags both records for review. The duplicate never reaches your filing.

Why it matters

What this buys you.

Zero ghost tonnage

Claims only contain material that physically existed once.

Cross-contractor safety

The same bale cannot be claimed by two different contractors either.

Audit confidence

Your filed tonnage survives the hardest question: did this bale exist, once?

Common questions

Straight answers.

What if someone re-photographs the same bale from another angle?

Angle changes are caught by the layered checks: photo fingerprint plus geo, time, kiosk identity and weight coherence. Suspicious near-matches are flagged for human review in the staging vault.

Does this slow down submissions?

No. Hashing and matching run in the pipeline; honest submissions are unaffected.

Why not use AI to classify material instead?

Classification can be argued with; a duplicate fingerprint cannot. EPRlog prefers evidence that is mathematically checkable over model opinions.

Own the proof.

Put evidence nobody can argue with behind every kilo you touch.

For PROs + producers