The fastest way to choose the wrong import-export software
If you choose based on a feature checklist or a demo, you will likely end up with software that stores records but does not improve execution.
Import-export operations are not “one module”. They are a chain: deal → documents → shipment → customs → landed cost → invoicing → settlement → margin.
The best systems behave like an operating system for that chain.
What “best” means for a trading desk (not for a factory)
Trading desks win on:
- faster deal cycles
- fewer document errors and rework
- predictable landed cost
- clean settlement follow-up
- accurate margin per deal (not just per month)
So “best import-export software” means software that makes those outcomes more consistent.
Non-negotiable capabilities
1) Deal-first data model
Everything should attach to a deal:
- counterparties
- line items
- shipments/containers
- documents
- costs
- invoices and payments
If you need three tools to answer “what is the current margin on this deal?”, you will bleed time and make mistakes.
2) Deterministic landed cost and responsibility boundaries
Your landed cost logic depends on the commercial terms.
Incoterms® rules exist specifically to clarify who is responsible for costs and tasks in a sale transaction, which is why you cannot treat landed cost as a flat “shipping + duty” number.
Start here if you want the calculation template: /resources/how-to-calculate-landed-cost
3) HS code support that matches reality
Classification is not optional.
The Harmonized System (HS) is a standardized product nomenclature developed by the World Customs Organization; it’s the base layer behind customs tariffs and trade statistics in most of the world.
A tool does not need to “auto-classify” to be useful, but it must:
- store HS codes per item
- track versions/changes
- attach codes to documents, certificates, and customs steps
4) Documents as first-class objects (with validation)
Import-export teams don’t just store PDFs. They need document control:
- who generated it
- which shipment it belongs to
- what changed
- whether it satisfies requirements (LC terms, customs, buyer requirements)
If you handle documentary credits, documents must be treated as compliance artifacts. ICC’s trade finance guide highlights letters of credit and export documents as part of executing transactions.
Related reading: /resources/what-is-letter-of-credit
5) Settlement workflow and audit trails
The most expensive mistakes are not obvious ones. They are small ones:
- FX conversion applied on the wrong date
- cost line duplicated
- payment received but not allocated
- invoice issued with a mismatched description
“Best” software keeps an audit trail so you can answer: who changed what, and why.
Scorecard: how to evaluate vendors in 30 minutes
Use this scorecard across vendors. Score each 0-2.
Data model (0-10)
- Deal is the primary record (0-2)
- Items and costs are normalized (0-2)
- Shipment timeline exists per deal (0-2)
- Documents attach to shipments and deals (0-2)
- Payments link to invoices and deals (0-2)
Finance math (0-10)
- Landed cost is computed from structured cost lines (0-2)
- FX conversions have explicit dates/sources (0-2)
- Margin per deal is deterministic (0-2)
- Multi-currency settlement is supported (0-2)
- Reports match persisted records (0-2)
Execution (0-10)
- Document checklist per deal (0-2)
- LC tracking (if needed) (0-2)
- Trade agreement / CEPA workflow (if needed) (0-2)
- Collaboration (roles/permissions) (0-2)
- Alerts for deadlines and missing steps (0-2)
How Tijara fits
Tijara is built for trading desks that want product + education in the same workflow:
- Deal-first operations
- Landed cost visibility as the deal evolves
- Document control (including LC workflows)
- CEPA/trade-agreement execution steps
- Settlement follow-up and margin clarity
If you’re evaluating tools right now, start with one high-leverage workflow:
- Create a deal
- Add items and HS codes
- Attach shipment costs
- Track documents
- Close settlement and compare expected vs actual margin
Then decide.