Ocean freight

FCL and LCL through Indian gateways, planned as one movement from origin port to the Nepal delivery point.

  1. Origin port
  2. Indian gateway
  3. Border
  4. Nepal delivery

What it covers

  • 20ft, 40ft and 40HQ containers, plus LCL consolidations.
  • Gateway handling at Kolkata, Visakhapatnam and Haldia, with rail-linked movement to ICD Birgunj.
  • Bill of lading review, endorsement, delivery orders and de-stuffing coordination.
  • Draft bill of lading review before release, then original document follow-up and endorsement.
  • IGM amendments, transit paperwork and empty-container return after de-stuffing.
  • Destination and local charge reconciliation, so the invoice matches what was quoted.

How it runs

Full container and consolidated cargo both move through an Indian gateway before they reach Nepal. The draft bill of lading is reviewed before release rather than after, originals are endorsed and chased, the manifest is amended where it needs correcting, and the delivery order is arranged with the handling parties at the port. Rail-linked movement under liner haulage to the inland container depot at Birgunj is routine, and de-stuffing is planned for the border or the consignee warehouse before the container gets there.

Where it runs

Imports come from Shanghai, Ningbo, Qingdao, Shekou, Shenzhen, Hong Kong, Bangkok and Port Klang, routed through Kolkata, Haldia or Visakhapatnam. Exports go out through Kolkata to the United States, Canada, Mexico, the United Kingdom, Germany, the Netherlands, Switzerland, Australia and Indonesia.

Documents and records

Master and house bills of lading, draft review and endorsement, manifest amendment, transit and ECTS paperwork, delivery order, letter of authority, de-stuffing record and empty container return.

Plan the container, gateway and inland leg together

FCL and LCL should be compared using the actual volume, weight, packing, handling sensitivity, origin charges, gateway arrangement and final Nepal delivery point. The India–Nepal transit protocol identifies Kolkata, Haldia and Visakhapatnam for Nepal transit, but a permitted port is not automatically the right gateway. Confirm the carrier service and current inland route for the shipment.

Before bill release, check the consignee, goods description, package details, container and seal data, and transit destination against the commercial file. The operating plan should cover release, port handling, transit filing, rail-linked or road movement, Nepal clearance, de-stuffing or delivery and empty return where applicable. Carrier and terminal free time, storage, demurrage and detention come from the applicable terms, never from a generic estimate.

  • Make document approval a milestone before release, not an amendment task after arrival.
  • Name who owns each handover from origin agent to gateway, border, clearing party and receiving site.
  • Keep the empty-return instruction with the booking when carrier equipment travels inland.

A related documented movement

Six containers unloaded at Nepalgunj

Sources

General procedures can change. Check the current source and the requirements for the specific shipment before acting.

Planning questions

Should I use FCL or LCL for a Nepal import?

That depends on cargo volume, packing, handling risk, origin charges and the final Nepal delivery point. KCPL can compare a full-container movement with consolidation when you provide the CBM, weight, piece count and destination; neither option is automatically cheaper or faster.

Why review the bill of lading before release?

The consignee, cargo description, container details and destination must agree with the commercial documents and the intended transit route. A discrepancy found after release can require an amendment and hold up the gateway or border handover.

Useful to tell us

Container type and count or CBM, origin port, incoterm, final delivery address.

Request a quote

Resources

Often planned with

Tell us the cargo, the route and the date.