Customer Flow
One authoritative record for every import and export, from purchase order to warehouse shelf, with true landed cost and an audit trail built in.
In plain words
Import and export teams usually juggle email, Excel and shared folders for every shipment. Customer Flow puts the whole job in one place: each company gets a private, secure workspace where a shipment moves step by step, from buying goods to customs to the warehouse. The system works out the real cost of every item and records who did what, so a bank or auditor can see the full story in one file.
Interactive preview
How Customer Flow works
Interactive · illustrative sample data
The challenge
Trade teams split one shipment across inboxes, spreadsheets and drives. When customs, a bank or an auditor asks for the complete record, nobody has it in one place, and landed cost (the real cost of goods on the shelf) is rebuilt by hand in spreadsheets.
Each country has different duty structures, documents and form fields, so hard-coding one market blocks expansion. Every company using the platform must also be fully isolated from every other company.
Our approach
Model each import and export as a single 'run' that moves through defined stages, with documents, approvals and PDFs attached to that run rather than scattered across tools.
Design the audit trail and tenant boundaries first, then build features on top of them. Country-specific rules plug in as replaceable packs instead of forks of the core product.
Step by step
From first click to finished job
- 1
Company signs up
A new tenant is created; all its data is scoped by organization so it is never visible to other companies.
- 2
Purchase order is raised
Vendor terms and line items start a new import run.
- 3
Documents and customs attach to the run
Shipping papers, the customs declaration and duty assessment are added at each stage, with approvals in-system.
- 4
Goods are received
The warehouse receipt updates stock, and landed cost is allocated across every line item.
- 5
Everything is on record
PDFs are generated from the same file and the full timestamped history is ready for banks and auditors.
Capabilities
What it does
Import runs
Purchase order → shipping documents (BL/AWB) → customs declaration → duty → clearance → warehouse receipt, on one record.
True landed cost
Product cost, freight, insurance, duty, port and bank charges are allocated across line items to give a real cost per unit.
Export runs
Contract → export forms → packing → shipping → payment close-out, following the same pattern.
Country rule packs
Pakistan, UAE and other markets plug in their own validation, required fields and calculation helpers.
Permanent audit trail
Every upload, edit, approval, PDF export and secure link share is logged with who and when.
Finance, HR & inventory
Core business modules share the same tenant, roles and audit model as the trade workflows.
Secure sharing
Send time-limited download links to banks or auditors instead of exporting folders.
Roles & 2FA
Per-company role permissions, optional two-factor authentication and platform admin tooling.
Engineering
Key decisions
Tenant isolation by organization
Every record carries an organization scope, enforced in the API layer, so companies share infrastructure but never data.
FastAPI + Next.js split
A Python FastAPI service with OpenAPI docs owns business logic; Next.js handles screens and server rendering.
Background work off the request path
Celery workers with Redis handle PDF generation and other heavy jobs so the UI stays fast.
Audit trail as a product feature
For trade finance, 'who approved this customs value?' must be answered by a log entry, not a conversation.
Architecture
Tech stack
Frontend
- Next.js
- TypeScript
API
- Python
- FastAPI
- OpenAPI
Data & jobs
- PostgreSQL
- Redis
- Celery
Delivery
- Docker
- GitHub Actions
- DigitalOcean
Outcome
What it delivers
- Live in production at thecustomerflow.com as a multi-tenant SaaS
- One record per shipment replaces email, spreadsheet and shared-drive hand-offs
- New markets added through rule packs without forking the core product
- Audit-ready history for banks, customs and auditors by default
Deep dives
Read the engineering notes
Building Customer Flow — A Multi-Tenant Cloud ERP
How we architected Customer Flow as a multi-tenant ERP for import/export, manufacturing, and enterprise operations with Next.js, FastAPI, PostgreSQL, and Redis.
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.
FastAPI + Celery — Background Jobs for Cloud ERP
Using Redis and Celery with FastAPI to run PDF generation, email notifications, and heavy imports without blocking API responses in Customer Flow.
Services behind it