Bunker Procurement Software: How Shipping Operators Prove Short Delivery and Off Spec Fuel Before the Invoice Is Paid

The claim is won or lost on the barge, not in the office

A bunker delivery is a commercial transaction conducted at night, alongside, under time pressure, by people who are not in your procurement department. The chief engineer checks the barge tanks, agrees a figure, signs a delivery note, takes samples, and sometimes issues a letter of protest. Everything you will later argue about is decided in that hour.

What usually happens next is that the delivery note is photographed and sent to the office, the samples go to a laboratory, the invoice arrives on its own schedule, and the three arrive in different inboxes with no shared reference. When the laboratory reports a sulphur figure close to the limit, or the quantity on the note does not match the vessel soundings, the operator has to reconstruct the event from a chain of forwarded emails. Suppliers know how long that takes. Contractual claim windows are short, and a claim raised outside the window is not a weak claim, it is no claim.

The recurring pattern in every operator we have worked with is the same. The people know exactly what went wrong. They simply cannot assemble proof fast enough, in a form the supplier cannot dismiss, before the window closes.

Why email, spreadsheets and generic procurement tools break here

Bunkering is a buying process where the specification changes while you are buying. The vessel is moving, so the port may change. The quantity needed depends on remaining on board and the next leg, which changes with weather and speed orders. The grade depends on where the vessel is going and which emission control areas it will pass through. A price accepted two hours ago may no longer be available. No general procurement workflow copes with a requirement that is a moving function of the voyage.

Then there is credit. You cannot buy from a supplier you have no line with, or beyond the exposure that supplier is willing to carry, and your own exposure to a supplier who may not deliver is a risk position rather than a payables line. Standard purchasing software has no concept of either.

And there is measurement. Fuel is bought in mass, delivered from tanks measured by volume, corrected for temperature and density, and the difference between an honest and a dishonest delivery frequently sits inside those corrections. A purchase order system that stores one quantity figure has already discarded the fields the dispute will turn on.

Where ClearLynx and BunkerMetric stop

Both products are worth taking seriously. ClearLynx is strong on the procurement cycle, market prices and workflow around enquiries and stems. BunkerMetric is strong on the optimisation question of how much to buy where, given the voyage plan and price differentials between ports. An operator using neither and running on email will get value from either quickly.

What they leave with you is the part that touches your own vessels and your own contracts. Remaining on board figures come from your fleet reporting, in whatever noon report format your operations team uses. Your charter party terms decide who pays for what and who owns the fuel at redelivery. Your claim procedure and your evidence standard are yours. Your credit lines and hedging exposure sit in treasury. So the packaged tool runs the buying and your team runs the aftermath in spreadsheets, and the aftermath is where the money is. A quantity claim is not a procurement feature. It is a case file that has to hold delivery note, soundings, survey report, sample seal numbers, laboratory results, letters of protest and correspondence, all timestamped and all beyond edit.

What a custom build has to include

A requirement engine driven by the voyage. Vessel, port rotation, current remaining on board, consumption model, safety margin, grade constraints for the sectors ahead, and tank capacity. The output is a quantity and a window per port, updated as the voyage changes. Buying without this is buying to a number someone typed.

Enquiry and offer handling built for how the market actually communicates. Some suppliers and brokers will use a portal. Most will reply by email with a price, a barge availability and terms. Extract those into comparable offers, normalise for grade, terms, barging fees and delivery window, and show landed cost rather than headline price. The comparison is the value, not the message handling.

Credit and exposure as a hard control. Available line per supplier, current exposure including stems confirmed but not yet invoiced, and a block when a stem would breach it. Include counterparty exposure the other way, since a prepayment or a stem with a supplier under stress is a risk position your treasury team will want to see.

Delivery evidence capture designed for the ship. The chief engineer needs a simple mobile form that works with no connectivity: quantity figures, temperature and density, tank soundings before and after, sample seal numbers, photographs of the delivery note and the seals, and a letter of protest template that can be issued and acknowledged on the spot. Everything timestamped and written to an append only record so nobody can tidy it later. That immutability is what makes the file worth something in a dispute.

Claim workflow with the clock in it. When laboratory results arrive, the system compares them against the ordered specification, opens a claim automatically when a parameter is out, attaches the complete evidence file, and counts down the contractual window. The most common cause of an abandoned claim is not weakness of evidence, it is that nobody realised the deadline was running.

Reconciliation to the invoice. Delivered quantity at the corrected basis, agreed price, barging and delivery fees, and the emission cost attached to the fuel where regulation now puts a price on carbon content. Recompute what the invoice should say and route the difference to a dispute rather than to accounts payable.

Supplier performance history. Which suppliers deliver short, which barges produce disputed density readings, which ports generate the most letters of protest. After a year this is the single most useful commercial asset the system holds, and it is entirely unavailable to anyone buying on price alone.

What it costs and how long it takes

A first release covering the voyage driven requirement, enquiry and offer comparison, stem confirmation, credit control and the shipboard delivery capture runs $75,000 to $155,000 and ships in 12 to 16 weeks. A full platform adding laboratory result ingestion, the claims workflow with deadline management, invoice reconciliation, hedging exposure reporting and supplier performance analytics runs $200,000 to $460,000 phased across 6 to 12 months.

Cost drivers: fleet size matters less than the number of vessel reporting formats you have to ingest, particularly across managed and chartered tonnage. Whether the mobile capture has to work offline properly, which it does, and offline sync with photographs is real engineering. Laboratory integration, since each testing house reports differently. And treasury integration if hedging positions are in scope, which is a separate discipline and should carry its own budget line.

What keeps cost down: build the delivery evidence capture and claims workflow first, before the buying side. Operators expect the value to be in procurement and usually find it is in the claims they stop losing.

When buying is the right call

Buy if you operate a small fleet on regular routes, buy spot from a short list of suppliers you trust, and rarely raise claims. The optimisation gain from a packaged tool will exceed anything a build gives you at that scale.

Build when you are stemming across many ports and suppliers, when credit lines constrain who you can buy from, when you have lost a quantity or quality claim in the past year because evidence arrived late, or when nobody can tell you which suppliers have historically delivered short. That last one is the tell. If the answer lives in one superintendent's memory, it is not a commercial asset.

How to choose a developer for bunker procurement software

Ask how the mobile capture behaves in a tank top with no signal at two in the morning. If the answer assumes connectivity, the evidence will be entered the next day from memory and will be worth correspondingly less.

Ask how they store quantity. You want volume, temperature, density and the corrected mass held separately with the correction reproducible, because the argument is usually about the conversion rather than the number.

Ask what makes the evidence file defensible. The right answer involves append only records, timestamps that cannot be back dated, photographs stored with their metadata, and a clear chain of custody for sample seal numbers.

Ask how the system knows a claim window is closing. If deadline tracking is not in their first sketch, they have built a document store rather than a claims system.

Ask who owns the code and settle it in writing before kickoff. You should hold the repository, the cloud accounts and the right to bring in another firm. At Digital Heroes the client owns the code from the first commit, which matters when the system is the evidence base behind claims against suppliers.