Import documents brought together at a port review desk

IMPORT OPERATIONS

Know when your import dossier is ready for review.

Bring documents together, compare their values and assign contradictions to the right owner. Control built around real dossiers, including the TEDI / Delassus case.

Discuss a controlled pilot

From document bundle to named review.

From the TEDI / Delassus case to source review: conflicting ONSSA and CMA CGM bill of lading documents.

Import case · real scenario

SOURCE DOCUMENTSTEDI / DELASSUS

ONSSA document

Case source · value to compare

Received

Bill of lading · CMA CGM

Transport source · value to compare

Conflict

Case linked to sources

TEDI Services / Delassus

Review

Review needed

Two sources. One conflict.

Values and versions retained. Exception assigned to the responsible person.

A person checks the sources and decides the next action.

Inspect the origin and scope

This reconstruction is based on the real case tested for TEDI Services involving Delassus: a discrepancy between an ONSSA document and a CMA CGM bill of lading. It illustrates collection, matching and human review without displaying client documents or assigning a confidential value. Documents and rules follow the workflow; customs decisions remain with the responsible professionals.

Reconstruction of a real TEDI / Delassus scenario. Illustrative interactive states; no client documents displayed.

Real-dossier test

Tedi Services / Delassus: a real document discrepancy

Illustration of the described workflow
  1. ONSSA
  2. Document comparison
  3. CMA CGM

For Tedi Services, Mehdi Kourchal developed an OCR agent and tested it on a real case involving Delassus: a significant discrepancy between an ONSSA document and a CMA CGM bill of lading. The case illustrates the operational and financial risk of conflicting port documents. This was a real-dossier test; no savings amount or wider production rollout is claimed.

Source: Mehdi Kourchal’s field account. Scope and limits are stated in this account.

One dossier. Clear exceptions. Named decisions.

Document register

See what has arrived, the current version, its owner and what is still missing.

Cross-document checks

Compare selected references, parties, quantities and weights while preserving each source value.

Reviewer decisions

Route differences to the right person and record the reason for the final decision.

Start with one representative import flow

  1. Map the dossier

    Agree on document types, ownership, required fields and the point at which a human reviews the case.

  2. Test real exceptions

    Use anonymized examples with missing files, revised versions and conflicting values.

  3. Run a bounded pilot

    Review flagged differences, adjust rules and measure the time and evidence needed to resolve a case.

Questions before a pilot

Does Kaliits replace PortNet or our declarant?

No. The pilot supports your team's internal document preparation and review. The importer and declarant keep their responsibilities.

Will the system decide which document is correct?

It shows the conflict and the source evidence. A named person decides how to resolve it.

Is every import dossier the same?

No. The required documents depend on the goods and procedure. The pilot starts with your actual cases and specialist guidance.

Review one import workflow together

Bring a representative dossier and the people who handle its exceptions. We will define a narrow pilot scope and its limits.

Request a workflow diagnostic