What the database stores
Structured cargo and vessel records, source fragments, sender metadata, confidence score and processing status.
Example: a broker can search wheat, Constanta, July laycan and supramax-related offers without reopening old folders manually.
Why that matters
The desk can search historical and fresh offers without relying on folder memory.
Proof point: old email history becomes working data instead of an archive that only the original recipient can navigate quickly.
What stays visible
Duplicates, failures and low-confidence cases remain visible instead of disappearing silently.
What LaycanMatch does not do: it does not hide uncertainty just to make the database look cleaner.
What happens next
The database powers matching, export, saved positions and map visibility.
Who this is not for
If the desk has no need to search historical broker email or review source context later, a searchable offer database matters less.