The connection uses CargoWise eAdaptor
This guide covers CargoWise's legacy eAdaptor connection. If you've migrated to eAdaptor Next, speak to us about your integration setup.
Nexcade exchanges structured XML messages with CargoWise through eAdaptor, its integration endpoint. Your CargoWise administrator or integration partner supplies the connection details. We configure and test the connection in your training environment, known as TRN, before production.
Email and rate sources connect separately. A request can start in a shared Outlook inbox, with rates gathered from your TMS, rate platforms, carrier APIs, portals, files and supplier replies. The sources and CargoWise actions in scope are agreed for your deployment.
See the Microsoft 365 email-access guide for how your IT team controls mailbox access.
From an email request to a CargoWise quote
Read the request
Nexcade extracts the route, cargo, dates and services from the email and attachments, then applies your operating rules.
Gather the rates
Nexcade checks your connected sources and brings the options together. When a rate is missing, it can prepare a supplier request and track the reply.
Build and review the quote
Nexcade applies your pricing policy and prepares the quote. Your team reviews the options, charges and customer response before release.
Keep the records connected
The quote is written into CargoWise at the agreed stage. Nexcade stores the CargoWise reference so the record and email conversation stay connected.
We agree when the quote is created and test the chosen workflow against your CargoWise configuration.
Supporting documents can be filed in CargoWise eDocs using your document-type codes. We agree which quote documents and supplier correspondence belong with the record.
Booking is a separately agreed step
When your customer accepts, Nexcade records the won quote. If your deployment includes Nexcade Booking, it loads the latest information, checks schedules and prepares the booking and shipping instructions for your team to review.
After approval, Nexcade creates the shipment in CargoWise and receives its shipment reference. That reference can be included in the customer confirmation. We agree any existing CargoWise workflow triggers and handoffs with your operations team during setup.
If a booking changes after instructions are drafted, Nexcade can redraft against the new schedule, flag the changes and hold the revised writeback for review. Your team can take over at any point.
What your team supplies
Your CargoWise administrator and operations team help us establish the connection and its rules.
- Connection and test access
- TRN connection details, the enterprise, server and company identifiers, and a dedicated test user. Share credentials through the agreed secure channel.
- Organisation, charge and document codes
- Your reference lists and the rules for mapping customers, suppliers, charges and eDocs. CargoWise stays authoritative for these codes.
- Representative quotes
- Completed quote examples, sample XML where available, pricing rules and customer templates. These show what a correct record looks like in your instance.
- Workflow decisions
- When to create the quote, which fields and documents it must contain, who approves it and whether booking is in scope.
Direct database access is not a standard prerequisite. Where extra reference data is needed, a report or export controlled by your CargoWise team may be sufficient.
Test the stored record before go-live
A successful integration response alone does not establish that a quote is complete. During testing, we create a quote in TRN, retrieve it and check the stored values against the intended result. Your team also checks the record in CargoWise.
The checks cover the agreed fields, charge mappings, references and document handling. A missing organisation code needs resolution through your existing master-data process before the quote can be written. We agree how other missing or unmapped information is returned to the team.
Once the mappings and workflow pass review, we verify the production configuration and compare results alongside your existing process before switching over. Start with one mode and representative lanes, then expand the agreed scope.
Your team controls release
Every desk starts at Level 1: quotes wait before they are sent, and bookings and shipping instructions wait before writeback. Every action is logged and your team can take over.
Further autonomy is earned on your live traffic. Routine legwork can run while outputs still wait for review; later, standard work can run within your rules while exceptions go to people. Your team chooses when to advance.
See freight quote automation for the wider workflow, or request a demo around your systems and requirements.