Cargo Management Software for Nepal: What Courier Systems Miss

Cargo companies are often sold courier software with the weight limit raised. It does not work, and the reason is not size. It is that cargo and courier are different businesses with different units of account.

A courier moves a parcel from one person to another and charges for that movement. A cargo operator moves goods that belong to a consignor, on behalf of a consignee, across a border or a long domestic leg, usually as part of a consolidated shipment, with documentation that has legal weight. Almost every field in the system means something different.

Chargeable weight, not weight

The first place courier software breaks is pricing. A courier charges by weight, sometimes with a volumetric fallback. Cargo charges by chargeable weight — the greater of actual weight and volumetric weight, where the volumetric divisor differs by mode and by carrier.

That means the system has to store:

• Actual gross weight
• Dimensions per piece, not per shipment, because a consignment is usually several pieces of different sizes
• A volumetric divisor that varies by mode (air freight and sea freight do not use the same one) and sometimes by carrier agreement
• The computed chargeable weight, and a record of which basis was used

If the system stores one weight number, every quotation is wrong and every invoice is argued.

A shipment is not one parcel

Courier systems model one consignment as one thing that moves. Cargo consignments are almost always multi-piece, and the pieces do not always travel together.

The model needs three levels, not one:

• Shipment — the commercial unit. This is what the customer booked, what gets invoiced, what the documentation refers to.
• Piece — the physical unit. Each has its own dimensions, weight, marks and numbers, and its own scan history.
• Consolidation — the container, ULD, pallet or master airway bill that pieces from several shipments travel inside.

Consolidation is the part courier software has no concept of at all. A cargo operator’s margin often comes from consolidating several customers’ shipments into one carrier booking, and the system has to track which house shipment sits under which master booking, and allocate the carrier’s cost across them.

Documentation is the deliverable

For domestic courier, the paperwork is a waybill. For cargo — especially import and export — the documentation is a substantial part of what the customer is paying for, and getting it wrong costs real money at a border.

Depending on the movement, a shipment may need:

• Commercial invoice and packing list
• House and master airway bill, or house and master bill of lading
• Certificate of origin
• Customs declaration reference and, in Nepal, the relevant clearance documentation
• Insurance certificate
• Any product-specific permits

A cargo system should generate these from shipment data rather than having someone retype the same consignee address into six documents. Retyping is how a consignee name ends up spelled two different ways across a document set, which is how a shipment ends up held.

Each document should also carry a version and a timestamp, because they get amended, and the question “which version of the invoice went to the carrier” comes up more often than anyone would like.

Multi-leg movement with different parties

A courier parcel is handled by your staff for its whole life. A cargo shipment is handled by your staff, then a carrier, then a customs broker, then a foreign agent, then a final-mile partner. You are responsible to the customer for all of it and in direct control of very little.

The system needs to record legs with the party responsible for each, and to distinguish clearly between:

• Events your own staff generated
• Events a partner or carrier reported to you
• Events you are inferring because nobody has told you anything

That third category is the honest one and almost no system models it. A shipment that has been “with the carrier” for nine days with no update is a different operational situation from one that was scanned yesterday, and the customer service team needs to see the difference.

Rates are agreements, not a price list

Courier pricing is mostly a rate card. Cargo pricing is a set of negotiated agreements — with customers on one side and carriers on the other — layered with surcharges that move.

Realistically the system has to handle:

• Customer rate agreements by lane, mode and weight break
• Carrier cost agreements on the same lanes
• Fuel and security surcharges that change periodically
• Ancillary charges: handling, documentation, customs, storage, demurrage
• Currency, because international cargo is frequently quoted in USD and settled in NPR at a rate that has to be recorded

Margin per shipment is then computable rather than estimated at month end. Cargo operators who cannot see margin per shipment are usually surprised by which lanes are actually making money.

Where courier and cargo do overlap

None of this means a cargo operator needs an entirely separate system from a courier one. Many operators in Nepal run both — domestic courier alongside import and export cargo, sometimes for the same customers.

What they share is real: customer records, branch and staff structure, custody scanning, cash handling, invoicing and the ledger. What they do not share is the shipment model, the pricing engine and the documentation layer.

The right architecture treats cargo as its own shipment type on a shared platform, not as a courier consignment with extra fields. Operators running both should be able to see one customer’s domestic parcels and international shipments in one place, on one statement, without the cargo side being crippled by courier assumptions.

Practical starting point

If you are running cargo on spreadsheets and a courier system, the highest-value things to fix first are usually, in order:

1. Chargeable weight computed by the system rather than by a person with a calculator
2. Documents generated from shipment data rather than retyped
3. Piece-level tracking, so a partial arrival is visible
4. Margin per shipment, so lane decisions are made on data

Each of those removes a category of recurring error rather than adding a feature.

We build logistics and cargo software for operators in Nepal, including consolidation, chargeable weight, document generation and multi-leg tracking — and our clients include cargo and import-export businesses running exactly these flows. If any of the above sounds like your week, talk to us.