Check a report or fill the gap between reports
Query supplier/carrier tracking through one interface instead of requesting another manual status exchange.
- Keep planned, estimated and actual milestone dates distinct.
- Inspect the selected container and its latest event.
- Port arrival and warehouse delivery are different milestones.
Look up one container, transport document or booking
Direct search requires the exact reference type and one value.
- Container references are validated; transport-document and Booking lookups use their corresponding API parameters.
- Keep one-off lookup history separate from both batch working sets.
- A direct lookup does not replace a current batch generation.
Validate a batch before starting its run
Import a single-column Container or CBL workbook; its header determines the workflow.
- Validate the input shape and ISO 6346 container identifiers before lookup.
- Booking remains a direct-search option, not a separate batch template.
- Follow import/refresh progress and inspect failures in the request audit.
Keep independent working views
Container and transport-document batches retain their own current generations and view state.
- Filter status, source, supplier and container without another carrier query.
- Choose and reorder columns; export only the filtered rows and displayed column order.
- Refreshing explicitly reuses the source workbook for the selected workflow.
Reopen the evidence behind an earlier result
Immutable run history preserves lookup status, request audit and saved result rows.
- Filter runs by workflow, status or reference/source.
- Inspect request outcome, HTTP result, pagination, event count and duration.
- Download saved results or an individual raw response without running the lookup again.
Keep usable work when a request fails
Stage a new batch before publishing its current generation.
- A failed run leaves the preceding generation available and does not alter another workflow.
- Partial success can publish successful results while retaining individual request failures.
- Investigate and relaunch explicitly; opening a saved result never calls the carrier API.
Who does what
A submitted batch runs lookup, normalization and persistence. Refresh and export are requested by the user.