← Back to Supply Chain Review Logistics Technology

Hapag-Lloyd Partners with WiseTech to Publish e-BLs via Galileo, Targeting 100% Digital Adoption by 2030

Source: PortCalls Asia / WiseTech Global · 2026-06-15 · 18 min read
中文

Supply Chain Action Points

Read this first — the conclusion, and the moves to make:

  1. By 30 June, pick the two or three lanes where document late arrival has actually cost you detention money, using your own last twelve months of files rather than impressions, and for each one write down the four counterparties you depend on, your forwarder, your consignee's forwarder, the destination agent and your bank. Then get the release terms in writing for each lane too: how many free days the destination terminal grants for demurrage and detention, and what your carrier's tariff charges per container per day after that. Target: dated written answers from all four counterparties per lane, no verbal answers accepted, plus a per container per day number for every lane, because if your free time exceeds the document gap the largest part of the saving case is zero.
  2. Ask your bank one narrow question before the goods sail, not after: will it act on a document issued through this platform, on this trade, under your existing facility, and what does it need from you in advance. Target: one written answer per facility, dated, with the name of the person who gave it, and every shipment going to paper until that answer exists.
  3. By 15 July run one live shipment of deliberately low invoice value end to end through the electronic document path and record eight timestamps: instructions sent, draft received, draft approved, issued, amendment requested, amendment confirmed, transferred, surrendered. Target: eight timestamps captured on one real file, and draft approval inside four working hours of receipt as your own internal standard.
  4. By 31 July set internal response thresholds and name who owns them: draft approval within four working hours, amendment instruction acknowledged within eight working hours, and a named backup with platform signing authority for every person who has it. Target: no file waiting overnight on a single person's availability, and one dry run per quarter to prove the backup can actually act.
  5. Write three mandatory fields into your booking form and standard operating procedure before the third quarter peak: whether this consignee accepts an electronic document, who holds release authority on your side, and what the fallback route costs and how long it takes. Target: every new booking carries all three, and every quarter you exercise the fallback once on paper and record the hours.
  6. Export each shipment's full document audit trail to your own storage within forty eight hours of issuance and keep it with the commercial invoice and the booking file. Target: every file retrievable eleven months later from your own system without logging into anyone else's platform, checked once a month against a random sample of two shipments.
Skip to the detailed analysis ↓
Summary

Hapag-Lloyd, one of the world's top five container shipping lines, has partnered with WiseTech Global to publish electronic bills of lading through Galileo, a cloud-native platform unifying trade finance and electronic document workflows. The first milestone was a live eBL issued to GEODIS, demonstrating end-to-end movement of a verified electronic document from carrier to freight forwarder. The integration is built on DCSA API v3.0 standards and connects Hapag-Lloyd to roughly 22,000 logistics providers covering approximately 90% of global ocean container capacity. Customers can manage eBLs within CargoWise, INTTRA, or directly in Galileo, enabling banks to act on verified shipping documents in real time and cargo owners to access financing against goods still at sea.

The Analysis

The news reached me with a file open on my desk, which is how I read anything to do with bills of lading. The announcement itself is not hard to state: Hapag-Lloyd, one of the top five container lines by capacity, has partnered with WiseTech Global to publish electronic bills of lading through Galileo, described as a cloud native platform that pulls trade finance and electronic document workflows into one place. The first milestone was a live electronic bill issued to GEODIS, which demonstrated end to end movement of a verified electronic document from carrier to freight forwarder. It runs on DCSA API v3.0 standards, and it connects Hapag-Lloyd to roughly twenty two thousand logistics providers covering about ninety per cent of global ocean container capacity. A customer can handle the document inside CargoWise, inside INTTRA, or straight through Galileo. The stated ambition is full digital adoption by 2030.

Here is what I take from that and what I do not. I take it that a very large carrier issued a real electronic bill to a very large forwarder, on live systems rather than in a sandbox, and that the document travelled. That is not a small thing. Four years ago the same sentence would have described a memorandum of understanding and a slide. I do not take it that my next shipment gets easier, or that the port I ship through is ready for it, or that the bank handling my credit has turned anything on. Those are separate questions and each gets answered by a different person on a different timetable. This depends on the port, and it depends on the counterparty sitting opposite you in the transaction.

So forget the target for a moment. A target belongs to somebody else's press office. What belongs to you is the map, and the reason it matters is that the electronic version walks exactly the same map as the paper one, only faster. Instructions to the carrier or its agent. Draft. Your approval of that draft, which is the last cheap moment you will ever have. Issuance. Amendment, if something is wrong. Transfer to whoever is entitled to the goods. Presentation to the bank where there is a credit or a collection involved. Surrender at destination in exchange for the delivery order. Eight checkpoints either way. The order never changes. Only the gaps between them do, and they do not shrink evenly, which is the thing worth understanding before you volunteer.

Take one shipment and run it through. A container of goods booked on a Hapag-Lloyd service, booked through a forwarder, sold on terms that call for original documents, financed by your bank, going to a consignee who clears customs at destination and then trucks it inland. Nothing exotic. Now ask the only question that pays: on which of those eight checkpoints does this arrangement actually save me hours, and on which does it save me nothing at all? Because the honest answer is uneven, and the even assumptions are where companies get hurt.

Start where the arguments start, which is possession. With paper, an original bill is a physical object, usually issued in a set of three, and holding a full set is what controls the goods. Everybody in this business has lost a week to one of those sets going missing between a desk and a courier bag. With an electronic document on a platform, there is nothing to lose, because control is a record rather than an object. In the systems I have worked with there is a designated holder, the platform knows which party currently holds control, and transfer happens as an instruction written into that record rather than as an envelope crossing a city. The saving here is real and it is large, and it is not the saving people talk about afterwards.

What people talk about afterwards is amendment, and that is where the expectation gap opens. An instruction is instant in the sense that it reaches its destination instantly. It is not instant in the sense that somebody on the other side acts on it, and the platform cannot make them. This is the part I keep repeating to anybody who will listen: the technology removes transmission time, it does not remove decision time. Every hour you sit waiting for a counterparty to click a confirmation is an hour no platform can give back to you, and in my experience that waiting is most of the elapsed time. On the systems and interfaces side, Ravi Chandran understands that layer far better than I do; what I deal with is what the document says and who has committed themselves to it.

So let me answer the question I get asked most often, which is when you can still change things. There are three windows and they are not equivalent. Before issuance you are correcting a draft that nobody outside your own chain has relied on. If the consignee name is spelled wrong, or the notify party is going to the wrong address, or the description of goods is vaguer than your buyer's bank will accept, this is where it costs you an email and twenty minutes. After issuance the document becomes something other people may rely on, and a change now needs the carrier to process it and, depending on what changed, the holder to agree.

After transfer it gets expensive, because the party entitled to the goods is now someone else and they have to give something up for you to change anything. I have watched a single character in a company name take nine days to fix at that stage, not because the system could not do it, but because three organisations each had a person who had to be found, persuaded and then actually authorised. Assume your own numbers here, because yours will differ: assume two hours at draft stage, assume twenty four to forty eight working hours after issuance and before transfer, assume three to five days after transfer. Those are my assumptions drawn from files I have handled, not a service standard anybody promised. One shipment going well once does not make any of it a rule.

Now the arithmetic, and I will write every assumption down because otherwise none of this means anything. Assume port to port transit of eighteen days. Assume with paper originals it takes six days from issuance to the document being usable in your consignee's hands, which is printing, signatures, courier hops and bank handling stacked together. Assume the electronic path takes one day. The gap is five days. Assume the consignee cannot get the container released without the document, and assume once the terminal's free time is gone you are paying one hundred dollars a container a day in combined demurrage and detention. Assume three containers on this shipment. Five days times three containers times one hundred dollars is one thousand five hundred dollars.

Add the financing leg, because that is half the point of the announcement. Assume the goods are worth five hundred thousand dollars and assume your cost of capital is eight per cent a year. A day of carry on that money is about one hundred and ten dollars. Getting a verified document into the bank's hands five days earlier means five days of financing you did not have to carry, or about five hundred and fifty dollars. Put them together and you have roughly two thousand and fifty dollars a shipment on those assumptions. Assume forty shipments a year on this lane and you are looking at something over eighty thousand dollars. Now go and replace every one of my numbers with yours, because that is the entire exercise.

And here is the correction I would make before anyone gets excited. If your terminal free time at destination is longer than the gap between the two document paths, the demurrage and detention component is zero and only the financing component survives. Free time is set by the terminal and by your carrier's tariff, it varies by port, and you can find it out in one phone call. I have seen people build a business case on avoided detention they were never at risk of paying. Check that number before you build anything on top of it. This depends on the port, and no amount of platform capability changes how many free days your terminal gives you.

Notice also which part of that two thousand dollars came from speed and which came from accuracy. The financing saving came from the document arriving sooner. The detention saving came from the document being right the first time and not having to go back for an amendment. In my files the second category is usually larger than the first, and it has almost nothing to do with whether the document is electronic. Catching an error at draft stage is free. Catching the same error after the ship has sailed costs you days, and nobody selling you software gets paid for you being careful earlier.

Put that into money with the same assumptions. Suppose you discover four days later than you should have that the notify party details are wrong, and suppose that discovery costs you four extra days before the release can be issued. At three containers and one hundred dollars a day you have one thousand two hundred dollars of detention, plus four days of carry at one hundred and ten dollars, which is another four hundred and forty. Call it one thousand six hundred and forty dollars, on my assumptions, for one mistake that started as a typo in an email. That is the business case. Everything else is a rounding error against it.

Then the bank question, which I am deliberately not going to answer for you. Whether your bank will act on an electronic document issued this way depends on the bank, on the rules chosen to govern your credit, on the jurisdiction, and on the exact words in your instructions. I am not qualified to give you a legal conclusion and I am not going to pretend otherwise. What I will give you is the operational consequence: ask before the goods sail, get it in writing, and file it against your booking checklist. If you ask after the vessel has left, you have lost every cheap option and you are negotiating with whoever happens to be at their desk.

I would ask the question in a specific form rather than a general one. Not whether the bank accepts electronic documents, because the answer will be a brochure. Ask whether it will act on a document issued through this particular platform, for this particular trade, under this particular facility, and ask what it needs from you in advance. Write down the answer, the date, and who gave it. One paragraph in a file is worth ten conversations when somebody calls you in a panic eight months later about the one shipment nobody checked.

Scale deserves a word, because the numbers in this announcement invite a certain laziness. Twenty two thousand logistics providers and about ninety per cent of global ocean container capacity behind the integration tell you the pipes are wide. Coverage is not adoption. The relevant question is narrower: has my forwarder turned it on, has my consignee's forwarder, has the destination agent, has my bank. I would write those four names on a single sheet and tick them one at a time. Roughly ninety per cent of capacity means something if you are shipping with everybody, and it means nothing at all if the two parties in your transaction are in the other ten per cent.

Port variability comes next, and I want to be careful here because this is exactly where people generalise from one good experience. Whether any of this helps you depends on the port and on the country. Some places release against electronic data quickly. Others still want a step that involves a person with a stamp, or a process that was not designed around electronic documents and absorbs them badly. One smooth shipment through one terminal is one data point. I would not rewrite a standard operating procedure on a single data point, and I would not tell you that somebody else's good experience on another lane transfers to yours.

There is also a quiet problem that only shows up later, and it belongs to whoever has to produce evidence. When customs asks a question eleven months after discharge, what do you hand over? With paper you hand over a file with a spine. With a platform you hand over what the platform kept, which depends on retention settings somebody chose at onboarding, on access rights that were set once and never revisited, and on whether the people who did the work still have logins. I have seen a company able to prove a document existed and entirely unable to show who instructed a change to it, because that person had left and nobody kept the audit trail anywhere they controlled.

The instruction that follows is unglamorous and I would put it in writing before you ship this way even once: the record must exist in your system, not only in somebody else's. Export each shipment's document trail to your own storage, date stamped, alongside your booking file and your commercial invoice, and make sure you can produce it eleven months later without logging into a portal you no longer pay for. Own your own record. Nobody upstream will do it for you, and nobody will thank you for asking them to.

Consistency across documents is the other one that bites. The party name in the platform must match the party name on the commercial invoice, and both must match what gets declared at destination. Middle initials, punctuation, a trading name instead of a registered name, a branch named instead of a head office: these are the small mismatches that turn into a day of emails at exactly the wrong moment. If the paperwork does not line up, everything downstream is trouble, and an electronic document does not fix that. It just delivers the mismatch faster.

One more thing that does not change, whatever form the document takes. Customs still wants a classification, and the order of work does not move: look at the tariff code first, then at duty relief. None of what was announced touches that. The electronic bill replaces how a title document travels between parties, not what you have to declare, and not the evidence you keep to support the declaration. I mention it only because every time a document goes digital somebody assumes the customs side went digital with it, and then discovers the classification question was waiting where it always was.

Before you assume the electronic route is the answer, price the boring alternatives. A sea waybill, where your customer relationship allows it and your bank does not need a title document, removes the whole question of a document arriving late, because nothing has to arrive. Telex release is older and less elegant than anything in this announcement and remains the thing that gets you out of trouble on the day the system will not do what you need. Paper originals sent by tracked courier are expensive and slow and completely understood by every party at both ends. Each has a cost and a failure mode, and boring solutions have one advantage none of the others do: everybody knows how to operate them at five o'clock on a Friday.

The pitfalls are mostly organisational rather than technical. Who in your company has authority to approve a draft, and who covers when that person is on holiday or asleep, because the platform does not care that it is two in the morning where you are and nine where the counterparty is. What happens when you are running both paper and electronic documents during a six month transition, because double handling is a real cost and it lands on the same person who has to learn the new system. What your fallback costs and how long it takes, measured in advance rather than discovered live. Whether your free time calculation has been redone since your carrier changed its tariff.

There is also the version of this that goes wrong quietly, which is the transition period nobody plans. You will run some shipments one way and some the other, and the people handling them will be the same people, and they will get muddled about which set of rules applies to which file. I would rather see a clean cutover lane by lane than a slow blended rollout across everything at once, even if the clean version takes a month longer. Mixed rules cause more document errors than most systems prevent.

So what I would actually do, starting now. Pick the two or three lanes where late documents cost you real money, which you can only know if you measure how often document arrival is the reason a container sat. Ask the four counterparties the narrow question and keep the written answers. Then run one live shipment of deliberately low value all the way through, and time every single checkpoint, rather than running ten at once and discovering which of them went wrong by accident.

Time it properly. Eight timestamps per shipment: instructions sent, draft received, draft approved, issued, any amendment requested, any amendment confirmed, transferred, surrendered. You will learn more from those eight numbers on one real shipment than from any amount of reading, and you will learn where your own choke point is rather than where a slide says it should be. If draft approval is taking two days inside your own company, the platform is not your problem and no amount of integration will fix it.

My own reading of this is dull and I will leave it at that. A top five carrier issued a live electronic bill to a major forwarder and demonstrated that it moves end to end, which changes what is reasonable to ask your counterparties for and does not change what you should do this week. This week is still: check the free time, check the four counterparties, run one cheap shipment, keep your own copy of every record, and fix how early you catch your own typos. Documents are forgiving early and expensive late, and that was true long before any of this.

↑ Back to the key points

— By Derek Xu

Hapag-LloydWiseTeche-BLGalileoDCSAdigitization