Trade software should connect the commercial order to cross-border evidence and landed cost
An import, export or trading platform can connect counterparties, products, quotations, contracts, purchase and sales orders, licences or permits, consignments, transport documents, customs status, warehouses, payments and finance. Stable order, shipment, consignment, document and transaction references prevent the same trade from becoming several disconnected files.
The platform is not a customs authority or customs-clearance system. It does not classify goods, issue licences, determine origin, calculate a legally binding duty, approve foreign exchange or establish that a shipment is compliant. Authorized customs, trade, legal, tax, banking, inspection and logistics professionals retain those responsibilities.
Trading parties, products and governed master data
- Buyer, seller, supplier, customer, agent, broker, carrier and consignee references
- Product identity, description, units, packaging and approved commodity codes
- Country, currency, location and transport references
- Approved licences, permits, certificates and effective periods
- Banking, payment and trade-finance references where authorized
- Restricted-party or controlled-goods decisions supplied by qualified owners
Master data should show its source, effective date, approval and change history. A code or flag entered in software is not independent proof that a product or party is legally eligible for a transaction.
Quotations, contracts, orders and delivery terms
Commercial workflows may connect enquiries, quotations, purchase or sales contracts, quantities, prices, currencies, delivery terms, milestones, tolerances and amendments. Any use of Incoterms or other trade terms should record the exact agreed version and wording; the legal and commercial teams remain responsible for interpretation.
Licences, permits, certificates and document readiness
Document requirements can be configured by approved trade route, commodity, transaction and procedure. The system may track applications, references, versions, validity, responsible owner, due dates, attachments and verification status. It should distinguish an internal checklist from a document issued or accepted by an authority.
Shipments, consignments and transport documents
A shipment can connect order lines, consignments, packages, weight, volume, container or vehicle, carrier, route, border or port milestones and responsible parties. Bills of lading, airway bills, road documents, packing lists and other records should retain version and source. Shipment and consignment views must not be collapsed when different parties or systems use them differently.
Customs declarations and ASYCUDA boundary
The enterprise system can prepare approved data, preserve document packs, record declaration references and statuses, and reconcile responses. ASYCUDA or another official platform remains the authoritative customs environment. Submission, integration or status exchange is included only where the responsible authority permits it and the interface, authentication, data ownership and error handling are formally defined.
Brokers, agents and accountable handovers
Broker or agent work may connect instruction, documents supplied, declaration reference, queries, fees, advances, receipts, decisions and handover history. The system should show who holds the next action without presenting a broker’s update as an official customs decision.
Inspection, quality and release evidence
Where inspection, laboratory, phytosanitary, origin, conformity or other certificates apply, the platform can retain the approved requirement, issuing party, reference, result, validity and linked lot or shipment. Qualified authorities and professionals determine applicability, sampling, acceptance and release.
Warehouse, transit and delivery control
Goods may pass through origin storage, in-transit locations, bonded facilities, destination warehouses and final delivery. Quantity, unit, lot or serial where required, condition, custody, holds, damage, shortages and proof of delivery should remain traceable. Customs status and inventory availability are related but not interchangeable controls.
Landed cost, currency and financial reconciliation
Approved product cost, freight, insurance, duty, tax, handling, storage, broker charges and other expenses can be allocated through documented rules. Finance owners approve currency rates, valuation, duty and tax treatment, accruals, inventory value and posting. Estimates must remain distinguishable from final assessed and invoiced amounts.
Trade finance, payments and settlements
Depending on the approved scope, records may connect advance payments, documentary collections, letters of credit, bank charges, guarantees, supplier balances, customer receivables and agent settlements. The application can organize evidence and due dates but cannot issue a banking instrument or determine sanctions, AML/CFT or foreign-exchange compliance.
Exceptions, claims, returns and disputes
Delays, holds, document discrepancies, inspection failures, damage, shortages, demurrage or storage charges, rejected deliveries and returns need reason, owner, evidence, cost and resolution history. Claims should reference the commercial and logistics records without overwriting the original event.
Data exchange, security and continuity
Integrations with supplier, customer, logistics, warehouse, accounting, bank or government systems require agreed identifiers, fields, versions, acknowledgements, duplicate protection, errors and support ownership. Commercial terms, identity documents and regulatory evidence need role-based access. Downtime procedures should preserve document and shipment continuity for later reconciliation.
Implementation, migration and UAT
Implementation maps trade models, routes, parties, products, documents, procedures, warehouses, finance, roles and integrations. Migration should validate active parties, product codes, open orders, consignments, documents, advances, balances and inventory. UAT should cover amendments, partial shipments, missing documents, customs queries, corrected statuses, landed-cost adjustment, claims, failed integrations and recovery.
Cross-border data reference
The information model was cross-checked against the WCO Data Model, which provides harmonized data definitions for Customs and other cross-border regulatory agencies, and the official ASYCUDA programme. Actual Afghan requirements must be confirmed with the responsible authorities and authorized advisers.