Integrations
Connected in weeks, not quarters.
The usual objection is that this takes two quarters. It takes that long when a platform needs to own your master data first. KEEL does not — it reconciles against what you already have.
What connects
Six categories cover most chains.
We list categories rather than logos — the connector that matters is the one your team actually runs, and that is a conversation, not a wall of badges.
ERP
Orders, POs, item master
TMS & forwarders
Bookings, milestones, documents
Ocean carriers
Vessel schedules, container events
Customs brokers
Entries, clearance status
Warehouse
Receipts, on-hand, putaway
Comms
Slack, email, alert routing
Rollout
Four weeks, and you can stop after any of them.
Week 1
Connect
Read-only credentials for your first three sources. Nothing writes back yet.
Week 2
Map
We reconcile your identifiers — PO, container, SKU — until the graph matches your records.
Week 3
Agents live
Exception rules go on watch in shadow mode, so you can compare them to your own calls.
Week 4
Rollout
Alerts route to the channels your team already reads. Write-back enabled where you want it.
Data handling
Three rules we do not negotiate.
Write-back is enabled per source, by you, after the graph agrees with your records.
Read-only by default
Every source starts observing. Write-back is enabled per system, by you, after you have seen the graph agree with your records.
Your identifiers stay yours
We reconcile against your PO, container and SKU keys — no re-numbering, no parallel master data to maintain.
Shadow mode before alerts
Agents run silently first so you can compare their calls to your team’s before anything routes to a channel.