TotalApp Docs

Import & Export Execution

The four working screens the Customs Declarant and Compliance Officer use to prepare, screen and clear cross-border shipments.

What this group does

Operational Setup defines the HS codes, Incoterms, brokers and compliance rules the organization runs on. Import & Export Execution is where that configuration gets used day to day: preparing and filing declarations, screening them against trade compliance and sanctions rules, tracking each shipment through the clearance pipeline, and attaching the certificates and origin documents that support them.

Export Declarations
→
Import Declarations
→
Clearance Status
→
Certificates & Origin Docs

Screen preview

A quick look at the screen. Use the toggle in the corner to switch between the dark and light themes.

app.totalapp.app/customs/clearance-status
EXP-88213 — HS 8471.30
FOB Seattle — Broker: Pacific Customs
Cleared
IMP-40217 — HS 3926.90
CIF Rotterdam — Sanctions screen OK
In Transit
IMP-40218 — HS 8517.62
DDP Hamburg — awaiting cert of origin
Held
EXP-88214 — HS 8708.29
FOB Long Beach — Broker: Harbor Customs
Filed

Import and export declarations with clearance status

1. Export Declarations

Purpose: Prepare, submit and track outbound customs declarations.

Each declaration records the HS-classified goods, the destination and applicable Incoterm, the declaring broker or agency, and its approval status — giving the Declarant a single place to move a shipment from draft to submitted to approved.

2. Import Declarations

Purpose: Prepare, submit and track inbound customs declarations.

Mirrors Export Declarations for goods entering the country — classification, origin, applicable duties and the compliance screening every inbound shipment needs before it is approved for clearance.

3. Clearance Status (Hat Takibi)

Purpose: Live tracking of shipments through the customs clearance pipeline, lane by lane.

Gives Logistics and Compliance a shared, real-time view of where each shipment sits in the clearance process, so a delayed lane or a held shipment is visible before it becomes a missed delivery.

4. Certificates & Origin Docs

Purpose: Certificates of origin and supporting trade documentation per shipment.

Keeps the certificate of origin and the other supporting documents a shipment needs attached to its declaration, so the Declarant and Compliance Officer always have the paper trail a customs authority may request.

Who can do what

StepTypical role
Prepare and submit an export or import declarationCustoms Declarant / Broker Liaison
Screen a declaration for compliance/sanctionsCompliance Officer
Approve a declarationCompliance Officer, Customs Manager
Track clearance statusCustoms Declarant / Broker Liaison, Logistics Coordinator
Attach a certificate of originCustoms Declarant / Broker Liaison

AI Assistant — Export Declarations

The Export Declarations screen ships with an embedded AI Assistant — the same right-edge panel used across TotalApp. Open it from the vertical AI Assistant tab on the right of the screen; it understands what is currently on your screen and answers in Markdown, matching the language you write in (Turkish or English).

Because a low-readiness declaration filed too early risks rejection or delay, the assistant is tuned for filing-readiness review:

  • Low compliance-readiness scores — flag declarations whose readiness score suggests they are not yet fit to file.
  • Pending Exporter Association approvals — surface declarations stuck waiting on an association sign-off.
  • Missing-document review — point out which supporting documents a declaration still lacks.
  • Filing-priority guidance — suggest which declarations are closest to being ready and should be filed first.

Tick one or more rows in the table to scope the conversation, then use Analyze selected or Summarize selected. Any answer can be saved via Save as Report (it lands in My Reports), and Add Knowledge lets you attach reference documents to ground the reply.

Engine-aware

The assistant respects your Settings → Agentic writer engine: Ollama / local-LLM / in-browser models run entirely on your machine, while API routes through the server — the panel never leaks your data to a server the selected engine can’t reach.

AI Assistant — Import Declarations

The Import Declarations screen ships with an embedded AI Assistant — the same right-edge panel used across TotalApp. Open it from the vertical AI Assistant tab on the right of the screen; it understands what is currently on your screen and answers in Markdown, matching the language you write in (Turkish or English).

Because clearance delays and duty exposure add up fast on the import side, the assistant is tuned for customs clearance and duty-risk review:

  • High duty liability — flag declarations carrying an unusually large calculated duty burden.
  • TAREKS inspection holds — surface declarations currently held for a risk-based inspection.
  • Bonded-warehouse bottlenecks — highlight declarations stuck in bonded warehouse longer than expected.
  • Clearance-timeline guidance — explain what is blocking a specific declaration from clearing.

Tick one or more rows in the table to scope the conversation, then use Analyze selected or Summarize selected. Any answer can be saved via Save as Report (it lands in My Reports), and Add Knowledge lets you attach reference documents to ground the reply.

Engine-aware

The assistant respects your Settings → Agentic writer engine: Ollama / local-LLM / in-browser models run entirely on your machine, while API routes through the server — the panel never leaks your data to a server the selected engine can’t reach.

AI Assistant — Certificates & Origin Docs

The Certificates & Origin Docs screen ships with an embedded AI Assistant — the same right-edge panel used across TotalApp. Open it from the vertical AI Assistant tab on the right of the screen; it understands what is currently on your screen and answers in Markdown, matching the language you write in (Turkish or English).

Because a disqualified or improperly stamped certificate means a preferential duty rate is lost, the assistant is tuned for preferential-duty-claim review:

  • Disqualified / expiring certificates — flag certificates that no longer qualify or are close to expiry.
  • Missing chamber-of-commerce stamps — surface certificates lacking a required chamber stamp.
  • Unclaimed potential duty savings — point out shipments where a valid certificate exists but its preferential rate was never applied.
  • Origin-rule guidance — explain which origin criteria a certificate needs to satisfy for a given trade agreement.

Tick one or more rows in the table to scope the conversation, then use Analyze selected or Summarize selected. Any answer can be saved via Save as Report (it lands in My Reports), and Add Knowledge lets you attach reference documents to ground the reply.

Engine-aware

The assistant respects your Settings → Agentic writer engine: Ollama / local-LLM / in-browser models run entirely on your machine, while API routes through the server — the panel never leaks your data to a server the selected engine can’t reach.

Frequently Asked Questions

Do I need to configure Setup before using these screens?
You can create a declaration immediately after the Customs team is onboarded. The Operational Setup screens (HS codes, Incoterms, brokers) become useful once you want full classification and compliance context, but they aren't a hard prerequisite for opening a first declaration.
What's the difference between Export and Import Declarations?
Export Declarations track outbound shipments leaving the country; Import Declarations track inbound shipments entering it. Both feed into the same Clearance Status pipeline.
Who can see these screens?
Anyone holding a Customs role can use all four screens once the Customs package is active on your tenant — see Roles & Capabilities for how to assign one.