Module
Pending BL
Which bills of lading are not in hand, ranked by what it costs when the vessel lands.
What it produces
- Every sailed shipment with no bill of lading in hand, worst first
- Ranked by time to arrival, not by age — free time runs at the destination
- Issued-but-not-collected kept separate from never-issued, because the chase differs
- Value on the linked purchase orders, and how many carry none
A worked example
11 outstanding · 3 need action today
SHP-4471 · at destination 4 days · no BL issued · ₹12,00,000
SHP-4488 · arriving in 2 days · MSCU8842197 issued, not collected
SHP-4502 · ageing 21 days · vessel due 14 Jul
→ 2 shipments have no departure date and cannot be aged at all
Illustrative figures. On your tenant the same page shows yours.
Why it is hard
The part that is not a report.
A bill of lading not in hand when the vessel lands is expensive in a specific, countable way: demurrage from a fixed date, detention after that, and a customer whose delivery has become indefinite. Everybody knows which documents are outstanding. Almost nobody knows which one to chase first, because the list is usually sorted by how long each has been pending. Ranking by what it costs when the vessel arrives instead changes which phone call gets made this morning, which is the only thing a list like this is for.
Opened by the logistics manager, the supply chain manager and the administrator — what each of them sees first.
Said before you ask
What is not finished.
BETA rather than AVAILABLE: the engine runs against live tenant data today — every field it reads is already populated by the tracking pipeline, which is what lets it ship while EXIMGuard cannot. No customer has yet run it against their own shipments. It moves to AVAILABLE when one has. One honest limitation: value at risk is read from the linked purchase order, so a shipment with no PO linked is counted in the list and excluded from the total, and the page says how many.
Where this sits
One of 16 modules, on one engine.
Pending BL 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 15 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.