← All solutions

Clear customs without the fire drills

Declarations, duty and tax calculation, sanctions and denied-party screening, and a complete audit trail - attached to the shipment they belong to.

Get startedBook a demo
Sanctions screening
denied-party checks on every shipment
Duty + tax
calculated from destination rates
Full
audit trail for every declaration
Overview

Customs & Trade Compliance

Every cross-border shipment in QueChains can carry a customs declaration with commodity lines, HS codes, values and the importer and exporter of record. Duty and tax are calculated from destination rates, and the declaration status feeds the shipment timeline so operations sees a hold the moment it happens.

Before goods move, parties are screened against sanctions and denied-party lists. Matches block the workflow and are recorded, so you have evidence you performed the check.

Capabilities

What's included

01
Customs declarations
Structured declarations with commodity lines, HS codes, quantities, values, and importer/exporter of record.
02
Duty and tax calculation
Landed duty and tax estimated per destination so cost is known before the shipment moves.
03
Sanctions screening
Importer and exporter names checked against sanctions and denied-party lists; a match stops the workflow and is logged.
04
Bill of lading and airway bill
Master and house B/L and AWB details captured on the shipment and available to documentation workflows.
05
Status in the timeline
Submitted, at customs and cleared events appear on the shipment timeline and can trigger alerts.
06
Compliance audit trail
Every declaration, screening result and status change is written to the tamper-evident audit log.
How it works

From setup to daily use

1
Build the declaration
Add commodity lines, HS codes and values to the shipment. QueChains estimates duty and tax for the destination.
2
Screen the parties
Importer and exporter names are checked against sanctions lists automatically; a hit blocks progress and records the reason.
3
Submit and track
The declaration status flows into the shipment timeline; a customs hold surfaces as an exception with an alert.
4
Clear and archive
On clearance the event is timestamped and the full paper trail is retained for audit.
Outcomes

Why teams use it

✓
Fewer surprise holds
Screening and complete paperwork up front reduce clearance delays.
✓
Known landed cost
Duty and tax are estimated before commitment, not discovered on the broker invoice.
✓
Defensible compliance
Every check is logged, so an audit is a report, not a scramble.
✓
One record
Customs data lives on the shipment, visible to operations, finance and the customer.
Who it's for
  • Importers and exporters managing multi-jurisdiction trade
  • Trade compliance and customs brokerage teams
  • Businesses that need documented denied-party screening
  • Operations teams that want customs status in the shipment view
Related solutions
Supply Chain Visibility → Documents & Automation → Freight & Cost Management → Risk & Disruption Monitoring →
FAQ

Common questions

Does it file directly with customs authorities?

QueChains prepares and structures the declaration, calculates duty and tax, and screens parties. Filing integrations depend on the jurisdiction and your broker; the declaration data is API-accessible for that handoff.

What sanctions lists are checked?

The major government-published sanctions and denied-party lists your compliance team relies on. If the list data is unavailable the check fails loudly rather than silently passing.

Is the compliance history auditable?

Yes - declarations, screening results and status changes are written to an append-only audit log stored separately from the operational database.

See Customs & Trade Compliance in your operation

Start free, or talk to our team about a pilot for your logistics operation.

Get startedContact sales