One connection for customers and partners. The right carrier and rate on every parcel
A carrier engine with AI at the centre connects a logistics operator's customers and partners for parcel orders. It selects the carrier dynamically on weight, volume and destination, validates addresses with AI, and handles events with AI.
- Carrier and rate selection
- Per parcelCarrier and rate selectionDynamic, on weight, volume and destination
- Client and vendor onboarding
- FasterClient and vendor onboardingOne connection to the engine replaces a bespoke integration per partner
- Address validation and event handling
- AIAddress validation and event handlingBad addresses caught before dispatch; carrier events handled without a person
- Customer
- Cross border parcel logistics operator
- Status
- Live in production
The express e-commerce pain point
Express parcel operators sit between two crowds. Customers on one side, each with its own order system. Carriers and partners on the other, each with its own API, rate card and event feed. Every new relationship on either side became an integration project, and once connected, someone still chose the carrier by hand.
Two further problems compounded it. Bad addresses went out and came back as failed deliveries. And carrier events, the constant stream of scans, exceptions and delays, needed people to read them and act.
What we built
A carrier engine with AI at the centre.
One connection for customers and partners. Customers send parcel orders once. Partners connect once. The engine holds the mapping in the middle, so a non-standard system on either side connects with far less integration pain.
Right carrier, right rate. For each parcel the engine selects the carrier dynamically on weight, volume and destination, against the current rates, rather than a default set by habit.
AI address validation. Addresses are validated and corrected before dispatch, which is where a failed delivery is cheapest to prevent.
AI-handled events. Carrier events are read, classified and acted on by the engine, and escalated only when a person is needed.
Why it matters
Clients and vendors onboard faster, because a connection is a mapping rather than a project. Non-standard systems connect with far less integration pain. And the end customer gets a better experience: the right carrier, a deliverable address, and exceptions handled before they become complaints.
It is live today, running RSA XB's own cross border operation. The cross border network is the engine's first customer.
Products used
- Carrier Engine
- Middleware