Spreadsheets don't fail loudly. That's what makes them dangerous for running an import business. Nothing crashes, nothing throws an error — the sheet just quietly drifts away from reality, and you find out weeks later when a number doesn't reconcile.
Here are the specific ways it happens, from watching one business run on spreadsheets before I rebuilt it as software.
1. The same payment gets knocked off twice
When bank remittances are logged manually against purchase orders, it's easy to mark the same payment as settled against two different POs — especially when two orders to the same supplier go out close together. Nobody does this on purpose. It just happens when you're moving fast and the sheet doesn't stop you.
2. AD code mismatches go unnoticed until customs flags them
Your bank has an AD (Authorized Dealer) code on file for foreign remittances. Customs has one too, tied to the Bill of Entry. If they don't match — because a payment went through a different bank than usual, say — that's a compliance issue. On a spreadsheet, there's no automatic way to catch this. You find out when someone flags it, which is always later than you'd like.
3. Duty calculations are only as good as whoever typed them in
BCD, SWS, and IGST all apply at different percentages depending on the product, and they stack in a specific order. Calculating this by hand for every shipment means every shipment carries the risk of a fat-fingered percentage. It's not that people are careless — it's that a formula typed fresh every time has more chances to go wrong than a formula that's tested once and reused automatically.
4. Two firms means two sets of everything — or a merge job nobody wants to do
If you're running two firms, you either keep two completely separate spreadsheets (and lose any combined view of your business), or you try to maintain one shared sheet with a "firm" column and hope nobody filters it wrong. Neither is good. What you actually want is what a real system gives you for free: switch between firms, or see them combined, without merging anything by hand.
5. "Where is this shipment" becomes a WhatsApp search
Shipping status, ETA, CHA documents sent, delivery confirmation — when none of that lives in one place, "where is this shipment" turns into scrolling back through chat history. That's not a data problem, it's a findability problem, and it costs time every single day, not just when something goes wrong.
None of this means spreadsheets are bad
They're genuinely great for a lot of things. They just weren't built to enforce the rules a real import operation needs enforced — one payment can't settle two orders, an AD code mismatch should raise a flag, duty math should be automatic. That's the actual argument for purpose-built software: not that it looks nicer, but that it makes certain mistakes structurally impossible instead of hoping everyone stays careful forever.