Why Vietnamese Forwarders Are Outgrowing Excel and Zalo Groups

Ask most Vietnamese freight forwarders how they run their shipments and the answer is remarkably consistent: a shared Excel file, a handful of Zalo groups, a stack of handwritten manifests, and a lot of memory. For a two-person operation moving a few parcels a week, that stack works. But the moment you grow past a handful of shipments a day, across several destinations and a team that has to hand work between sales, warehouse, documentation, and accounting, the cracks start to show.

The hidden cost of the spreadsheet-and-Zalo stack

Excel and Zalo are not the problem on their own. The problem is that a shipment does not live in any single place. The quote sits in one spreadsheet. The intake photos live in a Zalo thread. The customs paperwork is on someone’s desktop. Payment status is in the accountant’s own file. No one document tells you the full story of an order, so staff spend their day re-keying the same information into the next tool and chasing colleagues to fill the gaps.

That fragmentation has a real price:

• Invisible handoffs. When sales closes a deal, does the warehouse know it is coming? When goods arrive, does the documentation team get notified? In a Zalo group, these handoffs depend on someone remembering to post a message and someone else remembering to read it.
• Version chaos. Two people edit the same rate spreadsheet and quote the same customer two different prices. A weight gets corrected in one file but not the other.
• No audit trail. When a customer disputes a charge or a parcel goes missing, you scroll through weeks of chat history hoping the evidence is still there.
• Knowledge that walks out the door. When the one person who knows how a market’s paperwork works is on leave, the whole desk slows down.

Why Excel breaks exactly when you grow

A spreadsheet is a grid of cells. A shipment is a living process with a dozen states, several people touching it, documents attached at each step, and money that has to be reconciled at the end. You can force the process into a grid, but the grid does not enforce the process. It will happily let a shipment skip inspection, ship without a packing list, or close without payment confirmed, because a cell does not know what a shipment is supposed to do next.

Zalo has the opposite problem. It is wonderful for talking to customers and quick internal chatter, but a conversation is not a record. Decisions scroll away. Photos expire. There is no structure to say “this parcel, this quote, this document, this payment” belong together.

What changes when a shipment is a single record

The fix is not more spreadsheets or more Zalo groups. It is a shift in the unit of work: from scattered files to one shipment record that every team writes to and reads from. This is the idea at the center of TalentShip.

On a shipment-centric system, the lead that came in over Zalo, Messenger, Facebook, or the hotline lands in one inbox and is routed by destination to the right salesperson. The quote is built from a shared rate card (per country, by service level, by weight band) so two staff quote the same customer the same price. When the customer accepts, the warehouse already sees the job. Intake, inspection, and packing are captured photo-first at each step, so the evidence is attached to the order, not buried in a chat.

Documentation and customs prep work from that same record: confirming HS codes, filling the fields a given market requires, and generating the commercial invoice, packing list, and handover manifest without re-typing the shipment details. And at the end, reconciliation happens against the same order the whole time, so payment status is never a separate mystery in the accountant’s private file.

From memory to a system of record

The practical difference is that nothing depends on someone remembering to forward a message. The handoffs between sales, warehouse, documents, and accounting become part of the record rather than favors traded in a group chat. When a customer asks where their parcel is, or why a charge is what it is, the answer is one place, with the photos and documents attached and a history you can actually trust.

Growing out of Excel and Zalo is not a failure. It is a sign the business is working. The question is whether your tools grow with you or quietly cap how much you can handle.

Coming soon: join the early-access waitlist

TalentShip is being built specifically for Vietnamese forwarders and cross-border logistics SMEs who have outgrown the spreadsheet-and-Zalo stack. It is coming soon, with a limited beta planned for a small group of logistics SMEs later in 2026. If you would like to be among the first to try a single shipment record for your whole operation, we would love to have you on the TalentShip early-access waitlist.