Skip to main content
ABScaleForge
Back to blog
2 min read

True Landed Cost in Import ERP — One File From PO to Warehouse

Why import teams need purchase, shipping, customs, duty, and warehouse receipt on the same record — and how Customer Flow calculates landed cost in one audit trail.

ERPImportExportPakistanUAESaaS

Import teams track purchase orders in one spreadsheet, freight in another, customs duty in email, and warehouse receipts in a shared folder. When finance asks "what did this shipment actually cost landed?", nobody can answer without a day of spreadsheet archaeology.

What landed cost actually means

Landed cost is the total cost of getting goods to your warehouse shelf:

  • Product cost (FOB/CIF)
  • Freight and insurance
  • Customs duty and taxes
  • Port handling and local transport
  • Bank charges and clearance fees
  • Any adjustments (damage, short shipment)

If these live in separate files, margin analysis is always wrong.

One import run, one record

Customer Flow models an import as a single run from purchase through close:

1. Purchase order and vendor terms 2. Shipping documents and BL/AWB 3. Customs declaration and duty assessment 4. Duty payment and clearance 5. Warehouse receipt and putaway 6. Landed cost allocation across line items

Staff attach documents at each stage. Approvals happen in-system. PDFs generate from the same file. Secure download links go to banks or auditors without exporting folders.

Country rule packs

Pakistan and UAE (and other markets) have different duty structures, document requirements, and form fields. Hard-coding one country breaks expansion.

Replaceable rule packs plug in validation, required fields, and calculation helpers per jurisdiction — without forking the core product.

Audit trail as product feature

When a bank financing a shipment asks "who approved this customs value?", the answer must be a timestamped log entry — not a verbal claim. Every upload, edit, approval, and PDF export is logged permanently.

That is not compliance theater; it is how trade finance actually works.

Export runs mirror the pattern

Export workflows run contract → export forms → packing → shipping → payment close-out on the same principle: one run, full history, no scattered artifacts.

Takeaway

Import/export ERP value is not "digital forms." It is one authoritative record with true landed cost and a defensible audit trail. Build the file model first; country packs and PDF templates attach to it.