Skip to content

Check collections for problems

Orijin can check every purchase for the usual signs of a mistake or of something to look into: a paper receipt used twice, a purchase recorded far from the farmer, one Bluetooth scale passed between buying officers, and so on.

Open Organisation config → Checks and choose Lots and purchases. Every check is off until you switch it on, except Lost or stolen scale: it is on from the start, because it only flags anything once you mark a scale lost or stolen. For each one you can set:

  • Severity: Warning or Critical. Moisture and brix take their severity from the range: outside Low or High is a warning, outside Critically low or Critically high is critical.
  • Its limits, for example the furthest distance from the farmer, or the highest weight per sack. A blank box uses the default shown in it.

Press Save checks. The checks run when a purchase is saved on the dashboard, synced from the field app, or recorded by the buying bot.

Check What it flags
Duplicate receipt number Another purchase this season used the same receipt. BDG-123456, bdg 123456 and 123456 count as one receipt. On Phone, the field app refuses a receipt it already saved.
Receipt number missing A purchase with no receipt number.
Duplicate collection ID Another purchase this season used the same collection ID.
No location / Poor GPS accuracy No GPS point, or a worse accuracy than the limit.
Far from the farmer Recorded further from the farmer’s farm or plots than the limit.
Far from the buying point Recorded further from the buying point than the limit.
Impossible journey One buying officer recorded two purchases too far apart for the time between them.
Transport, reception and payment locations Runs the location checks on these records too.
Scale shared by buying officers One Bluetooth scale used by more officers than allowed. The officer who used it most is not flagged.
Lost or stolen scale Weighed on a scale marked Lost or Stolen on the Devices page, after the day it was last seen. On unless you switch it off. See Lost and stolen scales.
Weight out of range / per sack / typed by hand Weights outside your limits, or typed in instead of read from a scale.
Moisture or brix out of range A reading outside the range you set.
Backdated, future date, outside the season Purchase dates that are hard to believe.

Open Traceability → Collections. On the Lots tab or the Stages tab, open Filters and pick Checks (Any open finding, Critical, Warning or No open findings), or Check to look for one kind of problem. The Checks column shows a red count for critical problems and an amber one for warnings; hover over it to see which.

Open the lot and its Checks tab. Each problem shows what was measured, for example the distance from the farmer, and for duplicates a link to the other purchase. If a problem is fine (you checked the paper receipts, say), press Dismiss and write why. A dismissed problem stays dismissed when the checks run again, unless what was measured changes. Show resolved and dismissed shows the history, and Reopen brings a dismissed one back.

When a purchase is corrected, for example a receipt number fixed, its problem is resolved the next time the checks run, on both purchases of a duplicate.

After changing a limit, tick the lots on the Lots tab (or purchases on the Stages tab) and choose Rerun checks from the actions. Up to 500 lots at a time. Platform superusers can also rerun a whole season from the bottom of Organisation config → Checks → Lots and purchases.