Link every overseas partner you already trust, one to one. Each client order is shared live between origin and destination: no network membership, no platform in the middle.
Follow order 00066 from Rotterdam to Busan. At each milestone you see the e-mails the two forwarders send each other today, and what happens on the shared order in Logistics ERP instead.
Shipper data from origin, consignee data from destination.
Rotterdam knows the shipper, Busan knows the consignee. Each fills in its half of the same shipment request: cargo, container, pickup, delivery and import details. Nothing is retyped from an e-mail.
FCL, LCL or air? Agreed on the ticket.
Full container or groupage, which terminal, ocean or air for the urgent part. The modes are proposed and agreed on the shared order, with the wishes of the shipper and the consignee in one place.
Their sell price is your buy price.
Busan prices destination from its own rate template. It arrives on your order as your buy price, your Charge Template adds your margin, and your client discount stays yours alone.
Every offer side by side. Booked once.
Each carrier, terminal and mode with price, P&L and transit time. Both forwarders look at the same offers, so the decision is a short conversation instead of an e-mail chain across time zones.
An update in Rotterdam, seen live in Busan.
Pickup, container loaded, vessel departed, pre-alert. Every service update on the order reaches your partner the moment it is made, with the documents attached to the same ticket.
Nobody has to ask for the status.
Busan clears import customs and plans delivery on the same order; Rotterdam sees it live. The auto status scheduler e-mails the client what changed, at the times you set.
The six threads above, added up.
Each e-mail is written in one office and read, answered and filed in the other. Each question across the time zones waits for the next working day. On the shared order both disappear: every update is there the moment it is made.
Your partner works the order with you. Your agents and automations do the reading, pricing, translating and checking at every milestone. They all read the same live order, so what Busan records is in the next reply from Rotterdam.
Each forwarder runs its own Logistics ERP with its own agents. Both orchestras play from the same order.
From the client's request e-mail to priced offers in about a minute.
The agent reads the request and its attachments and fills in the shipment data. The ERP quote engine prices every service from your own rate templates, margins and charges. The agent never invents a rate.
Plays at 01 Request · 02 Modes · 03 Prices"Has it sailed?" answered from the order as it is now, including what your partner recorded.
Your operator picks the order and the subject. The agent reads the live order, so the import customs step your partner recorded in Busan is in the answer, and drafts a short, a standard and a detailed reply, each marked with how sure it is.
Plays at 04 Booking · 05 Departure · 06 DeliveryRotterdam writes in English. The consignee reads in Korean.
Two forwarders, a shipper and a consignee rarely share one language. The translation agent turns an e-mail or an order report into the reader's language, so nobody pastes text into a website.
Plays at 01 Request · 06 Delivery, and wherever a language differsThe carrier is checked for you. The client is told before they ask.
The carrier's departure and arrival feed the freight steps of the shared order, seen by both forwarders. When something changes, a clear status report goes to your client, on change or at the times you choose.
Plays at 05 Departure · 06 DeliveryThe agents read, gather and draft. Your operator keeps the judgement and the Send button.
Each forwarder prices its own leg from its own rate template, with its own margin. Follow one door-to-door quote from Busan's price to your client's price.
From your partner's rate template, with their margin. For you, a buy price.
Your margin on a service outside your own rate contract.
Your own rate template, contract rates and margin.
Agreed between you and your client only.
Profitable before the client sees a price.
Rotterdam and Busan are seven to eight hours apart. By e-mail, every question costs a day. On a shared order, one side picks up where the other stopped.
Cargo, container and pickup from the shipper, shared with Busan.
Before leaving, Busan adds delivery and import details.
Busan's destination price is already there, from its rate template.
Maersk via Rotterdam, booked once with the shipper.
Busan finds the booking complete and plans import customs.
Keep e-mailing, build a system link with every partner, or share the order in the ERP you both already use for the rest of the job.
| Old styleE-mail, spreadsheets, phone | System integrationEDI or API link per partner | Logistics ERP AllianceOne shared order ticket | |
|---|---|---|---|
| Shipment request | Retyped from e-mails on both sides | Only the fields both systems map | One request: origin adds shipper data, destination consignee data |
| Shipment modes | Long threads on FCL, LCL, terminal or air | Usually outside the link | Proposed and agreed on the ticket |
| Pricing | Rate sheets as attachments, outdated next week | Rates rarely part of the link | Live from each partner's rate template |
| Margin and discount | Calculated by hand, per quote | Calculated in each own system | Each side its own margin and client discount; Charge Template on partner services |
| Offers and booking | PDFs forwarded, answers lost across time zones | Booking messages, once mapped | All offers side by side, booked once, seen by both |
| Service status | "Any news?" e-mails and night-time calls | Status messages, if both sides send them | Every handling update live on both sides |
| Client e-mails | Read, priced and answered by hand | Not included | AI agents draft quotes and replies from the live order |
| Client reporting | Written by hand | Not included | Auto status e-mails the client |
| Set-up per partner | None, but every order costs hours | A mapping and test project per partner | 1 active user at your partner |
The system integration column describes point-to-point EDI or API links in general, not a specific product. Each partner keeps its own Logistics ERP company: the shared ticket connects the two, it does not merge them.
No network membership, no platform in the middle, no integration project. You choose the partners you already trust. The only requirement: each of them has at least one active Logistics ERP user.
Start with the agents you already send orders to: Busan for destination, Shanghai for origin. Lane by lane, at your own pace.
One User Licence is enough to join. They work in their own company, with their own clients, rates and margins.
Add the partner as shared partner on the lane's rate template, and set what is owner bound and what is partner bound.
Share the order. From then on request, modes, prices, booking and status are digital on both sides.
The partners you already trust, each in its own Logistics ERP company.
Each partner keeps its own clients, rates and margins. The shared order connects the two companies for one shipment; it does not merge them.
Rotterdam → Busan. The next order on this lane opens as a shared ticket.
The alliance is not a separate subscription. You work in the Logistics ERP you already have; each partner needs at least one active User Licence, and adds more users when it wants them.
Full ERP for the partner's own orders. AI agents use AI Credits, per company.
Start a free trial, invite the partner you send the most orders to, and work your next shipment together, from request to delivery.