Air vs Sea Cargo from Nepal: What Changes in Your System
Logistics, courier & cargo7 min read
Transit time, chargeable weight rules, documentation and cash cycle all differ by mode. What a cargo operator's software has to model differently.
Nepal is landlocked, which makes every international shipment a multi-country movement before it even reaches a port or a plane. That fact shapes both modes, but it shapes them differently — and a cargo system that treats air and sea as the same shipment with a different label will get the economics wrong on both.
Transit time and what it does to your system
Air moves in days. Sea moves in weeks, and for Nepal it moves in weeks plus the inland leg to and from the port, plus border formalities on both sides of the transit country.
The software consequence is that a sea shipment spends most of its life in states where you have no direct visibility, and your customer will ask about it repeatedly during that period. A system that shows “in transit” for five weeks is useless. It needs distinct, dated milestones:
- Cargo received at origin
- Customs cleared at origin
- Inland leg to port or airport
- Border crossing
- Loaded on vessel or flight
- Departed, with an estimated arrival
- Arrived at destination port or airport
- Customs entry filed
- Cleared
- Available for delivery
- Delivered
Each with a planned date and an actual date. The gap between the two is your operational performance and it is also the answer to most customer calls.
Chargeable weight is calculated differently
This is the single most common source of quotation errors when an operator handles both modes.
Air freight uses a volumetric divisor to convert dimensions into a volumetric weight, and charges on whichever is greater — actual or volumetric. Sea freight, for less-than-container loads, is charged on a revenue tonne basis comparing weight against cubic measurement, with a different conversion entirely. Full container loads are charged per container, so the calculation stops mattering and utilisation starts mattering instead.
Three different pricing models. The system must store dimensions per piece and hold the divisor as configuration per mode and per carrier agreement, so the quotation engine applies the right one automatically. Operators who compute this manually will eventually quote an air rate on a sea basis, and discover it after the shipment moved.
Consolidation works differently too
Air consolidation groups shipments under a master airway bill. Sea consolidation for LCL groups them into a container under a master bill of lading, and the economics turn on how full that container is.
For LCL, container utilisation is the profit lever. The system should be able to tell you, per container, the cubic capacity booked against capacity available, and what the unsold space cost. Operators who cannot see this consistently under-fill containers and never find out why margins are thinner than expected.
For air, the equivalent question is whether the consolidation qualified for a better weight break with the carrier. A shipment that lands just under a break point is worth knowing about, because adding a small volume to reach the next break can reduce the total cost.
Documentation overlaps but does not match
Both modes need a commercial invoice, packing list, certificate of origin and customs declaration. The transport document differs and it differs in a way that matters:
An airway bill is a receipt and a contract of carriage. It is not a document of title — the goods are released to the named consignee.
A bill of lading can be a document of title. Whoever holds an original negotiable bill controls the cargo. That has real consequences: originals have to be tracked as physical objects, telex release is a distinct event to record, and releasing cargo against the wrong instruction is a serious liability.
A system built only for air will not model original document custody at all, because air never needed it.
The cash cycle diverges sharply
Air shipments settle quickly. Cargo moves, arrives, gets delivered, gets invoiced, gets paid — a cycle of days to a few weeks.
Sea shipments tie up working capital for months. You may pay the carrier, the inland transporter and the customs broker long before your customer pays you, and the shipment sits on your books throughout.
For an operator running both, this means the system has to show cost and revenue accrued per shipment continuously, not just at completion. Otherwise a profitable-looking month is actually a month where sea shipments consumed cash that has not returned. Ageing of receivables by mode is worth watching separately, because blending them hides the problem.
Demurrage and detention deserve their own mention. Container charges accrue daily after free time expires and they escalate. The system should track free-time expiry per container and alert before it lapses — this is one of the few places where a report genuinely prevents a direct cash loss.
Choosing between them, for a customer
Customers ask which mode to use, and the honest answer depends on value density and urgency rather than on a rule.
Air makes sense when the goods are high value relative to their weight, when the selling season is short, when capital tied up in transit is expensive, or when a stockout costs more than the freight difference. Sea makes sense for bulky, low-value-density goods where the freight difference is large relative to the goods value, and where the buyer can plan far enough ahead.
The genuinely useful thing a cargo operator can offer here is landed cost per unit under each mode — freight, inland, duty, clearance and handling, divided by units. If the system holds real cost data by lane, that comparison is a query rather than a spreadsheet exercise, and it is a much better sales conversation than quoting a rate.
What to hold in configuration
If you handle both modes, these should be configurable data rather than logic in someone’s head:
- Volumetric divisor per mode and carrier
- Weight break tables per lane and carrier
- Free time and demurrage rates per carrier and port
- Standard transit time per lane, per mode, for planning against actuals
- Document checklist per mode and destination
- Surcharges, with effective dates
We build cargo and logistics software for operators in Nepal handling both air and sea, including chargeable weight by mode, consolidation, container utilisation and per-shipment margin. If your quotations are calculated by hand, talk to us.
Read next
- Cash on Delivery Reconciliation for Courier Companies in NepalWhy COD reconciliation breaks down at scale in Nepal, and what a courier's software has to track to close the books daily instead of weekly.
- 3PL Software in Nepal: Running Logistics for Other People's GoodsServing multiple merchants under different rate cards and SLAs needs multi-tenancy, not a bigger courier system. What third-party logistics software must handle.
- Designing Tracking Numbers That Do Not Break at ScaleTracking number schemes fail in predictable ways: collisions, transcription errors, and numbers that leak volume. How to design one that lasts.
