Module
Forwarder Job File
The forwarder's job: what you quoted, what you bought, what you sold, and the margin between them — computed, not typed.
Watch demo
The box has sailed. What the company made on it, nobody knows until the month closes.
The running product against the demonstration tenant — every figure on screen was computed while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.
What it produces
- A job register with every open job ranked worst margin first — revenue, cost, gross profit and margin per job, each carrying its arithmetic
- Two sides on every job: what was bought from the carrier, the CHA, the transporter and the agent, and what was sold to the customer
- A quotation that becomes the job when it is won — every quoted line lands as an estimated sell charge, so the job starts from what was promised
- A foreign-currency line without its exchange rate refused from the total and named, never converted at one
- What is accrued and what is unbilled, per job and across the book, so month-end is a page rather than a spreadsheet
- A job that will not close over a bought line with no supplier invoice, or a sale nobody invoiced
A worked example
JOB-00042 · Weber Kunststoffe · INNSA → DEHAM · 2 × 40HC
sold ₹1,50,000 · bought ₹1,22,000 · gross profit ₹28,000
÷ revenue × 100 = 18.67% against a target of 12%
1 line refused: an agency fee in USD with no rate on it
→ 2 bought lines still accrued · the job cannot close until they are invoiced
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A forwarder's month is decided by a figure nobody sees until it is too late: the margin on each job. The quote sits in a mailbox, the carrier's cost in one spreadsheet, the customer's invoice in another, and the two are reconciled weeks after the box has gone. The job file puts both sides on one page as the work happens — what was promised, what was bought, what was sold — and refuses to close a job over a cost nobody has invoiced, which is how a month's profit turns out wrong three weeks later.
Opened by the logistics manager, the finance director, the sales manager and the administrator — what each of them sees first.
Said before you ask
What is not finished.
Phase 1 of docs/FORWARDER.md: the job file, the quotation, charges on both sides, the profit with its arithmetic, and the register. Not yet: house and master consolidation over one voyage (Phase 2); the documents a job produces — house bill of lading, arrival notice, delivery order, manifest and the invoice itself (Phase 3); customs brokerage as its own lane, the overseas agent network and EDI (Phase 4). Tax is recorded as a flag and computed nowhere: Indian GST on freight has place-of-supply rules that deserve their own pass. SIAARU raises the invoice and records the payment; it is not the book of record, and a real accounting system still is.
Where this sits
One of 26 modules, on one engine.
Forwarder Job File reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 25 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.