Short answer
LaycanMatch features are built around broker email workflow.
LaycanMatch features include mailbox import, AI cargo and vessel extraction, searchable offer records, ranked matching, saved positions, Telegram alerts, source email review and export.
Feature map
One workflow from mailbox to matched opportunity.
LaycanMatch is not a generic CRM. It is a focused desk tool for transforming broker emails into searchable cargoes and vessel data, then finding usable commercial matches.
Email processing
Controlled import, clear statuses, no silent failures.
The broker decides what to import. The system shows what was found, checked, imported, processed, duplicated or failed, so nobody has to guess whether sync is alive.
Connect mailbox
Use Google authorization for Gmail or encrypted IMAP credentials for other providers.
Select scope
Choose mailbox folders and date range before import. Start small, then widen the history when ready.
Download and classify
New and historical messages are checked for cargo/vessel relevance and duplicates.
Extract and log
Relevant emails create structured records. Errors, retries and low-confidence cases stay visible.
Structured extraction
The fields brokers need are extracted into usable data.
LaycanMatch keeps the original email context, but gives brokers clean fields for filtering, matching and exporting.
Offer typeCargo typeQuantityToleranceVessel nameDWTLoad portDischarge portRoute zonesLaycan datesBrokerCompanyRaw source textConfidence score
Matching engine
Two search modes, one commercial goal.
The system does not just search exact ports. It uses zones, route direction, laycan overlap, size fit, cargo type, extraction confidence and recency to rank opportunities.
Find cargo for vessel
Use open port, DWT, laycan and direction to rank cargo offers that could fit the vessel.
- Route and zone compatibility
- Quantity vs vessel size
- Freshness and confidence
Find vessel for cargo
Use cargo type, quantity, load/discharge ports and laycan to rank suitable vessel offers.
- Vessel availability and DWT
- Laycan overlap
- Port and regional fit
Saved positions
Keep matching after the broker closes the page.
Create a vessel position or cargo requirement once. Existing matches stay saved, new matches appear separately, and Telegram can notify the responsible broker with a direct link.
Saved vessel positions
Keep open tonnage visible without rebuilding filters every morning.
Saved cargo requirements
Monitor repeated chartering needs across route, size and laycan combinations.
Telegram alerts
A broker can turn alerts on for one saved position and receive only the new matching offers for that exact workflow.
Direct source review
Alerts link back to the matching record so the broker can open the source email before calling.
Example: a broker saves a 58k Black Sea to East Med vessel position with a 10 to 20 June laycan window. When a new matching cargo email appears, LaycanMatch can send a Telegram alert with a direct link to the saved position and the new matching offer.
Broker control
Security remains part of the feature set.
LaycanMatch features are built around explicit authorization, visible source email review and clear processing states, not silent background automation.
Authorized mailbox access
Mailboxes are connected only through user-approved Gmail or IMAP credentials.
Visible source email
Structured records remain linked to the source email so extraction can be checked before outreach.
Encrypted secrets
Mailbox credentials, OAuth tokens and AI keys are stored encrypted and masked in the interface.
Clear processing states
The desk can see duplicates, failures, retries and low-confidence records instead of guessing what happened.
Tables
What is extracted and what affects the match score.
Features matter only when they improve a broker workflow in a way that can be checked. These are the fields and signals that actually drive the product.
| Field | Example | Why it matters |
|---|---|---|
| Cargo | Wheat | Identifies the commodity type |
| Quantity | 45,000 MT | Helps compare vessel capacity |
| Load port | Constanta | Used for route fit |
| Discharge port | Alexandria | Used for voyage direction |
| Laycan | 22–28 July | Checks date overlap |
| DWT | 56,000 | Checks vessel suitability |
| Source email | Broker circular | Keeps the workflow auditable |
| Confidence score | 87% | Shows extraction reliability |
| Matching signal | What it checks | Why brokers care |
|---|---|---|
| Route zones | Load and discharge direction | Removes obviously weak voyages |
| Laycan overlap | Date window intersection | Shows whether timing is realistic |
| DWT / quantity fit | Capacity against cargo size | Improves shortlist quality |
| Confidence | Extraction reliability | Flags review-required cases |
| Recency | Freshness of the offer | Old circulars lose value fast |
Limits and fit
What the feature set is designed to do, and where it stops.
Strong feature pages should explain what the workflow improves and where the broker still has to think.
What LaycanMatch does not do
The platform does not send broker replies automatically, negotiate rates, pick counterparties or replace chartering judgment. It prepares the shortlist and keeps the evidence visible.
Who this is for
It is built for desks that receive enough broker email volume that manual search, spreadsheet copying and missed follow-up have become expensive.
Who this is not for
If a desk receives only a few useful emails per week or already relies on a separate structured offer feed, the workflow change may not justify the setup.
FAQ
Feature questions
Can brokers review the source email behind an extracted offer?
Yes. Source subject, sender, fragment and body remain visible when available.
What happens when extraction confidence is low?
The offer can still be stored, but it should be marked for review so the broker checks the original circular before acting.
Can I match cargo and vessel positions without exact port equality?
Yes. Zone logic is part of the matching workflow because route fit often matters more than exact port text.
Do the features include Telegram alerts?
Yes. Alerts can be enabled per saved cargo or vessel position so only new relevant matches are sent.
Further reading
Related guides for extraction, matching and review.
These pages explain how the workflow behaves in practice, how confidence is handled and how brokers can evaluate the fit before rollout.
AI email parser for shipbrokers
Overview of how broker emails are classified, parsed and reviewed.
Feature: AI email parsing
Go deeper into how emails become structured cargo and vessel records.
Cargo-vessel matching software
Explains route, laycan, DWT and confidence-driven ranking.
Feature: matching engine
Focused explanation of the ranked cargo-for-vessel and vessel-for-cargo logic.
Feature: offer database
How structured offers stay searchable, filterable and linked to source review.
Feature: map and routes
How ports, zones and routes become visible for broker workflow review.
Methodology
How extraction confidence, saved matches and review states work.
Inbox automation guide
Operational walkthrough of import, statuses, dedupe and review.
Start testing
Start with 1,000 free processed emails.
Connect a mailbox, process a controlled date range and see whether the feature set fits your desk before scaling.