Import License & Permit Tracker

More than most teams track: import licenses for restricted goods, product registrations (FDA facility/product, BIS CRS certificates, FSSAI licenses), SPS permits, end-use/end-user certificates, customs bonds (annual), AEO/trusted-trader statuses (revalidation cycles), even IEC details that need periodic confirmation in India. Anything with an issue date usually has an end date — the matrix exists because each authority reminds you on its own schedule, which is to say, often never.

Because regulated renewals aren't transactions, they're projects: re-testing samples, updated factory documentation, consularized papers, authority processing queues. A 30-day warning on a 75-day renewal is a schedule for failure. Ninety days converts every renewal into a routine task — and rows with shorter true lead times simply get acted on later within the window.

The expensive scenario: cargo arrives against an expired authorization and sits — bonded storage accruing while an expedited renewal (where even possible) processes, or worse, re-export/destruction orders for goods that can't legally enter. Authorities rarely grandfather in-transit cargo past an expiry. The operational rule: check the license horizon BEFORE booking anything with a transit longer than the days remaining.

Per document, with scope recorded — that matches how authorities issue and renew them. The scope field then answers the per-product question ('is SKU X covered?') at booking time. Large catalogs sometimes need both views; export the CSV and pivot by scope when product teams ask. The failure mode to avoid is per-product tracking that loses sight of the single document whose expiry kills fifty SKUs at once.