Keep the filing system. Remove the bottleneck before it.

What does customs clearance software need to cover?

Customs clearance software is an umbrella term. One product may transmit declarations to the Customs Declaration Service, manage authorisations, receive responses, and retain the filing record. Another may organise the work before submission: reading customer documents, structuring proposed values, exposing gaps, and preparing evidence for a broker to review. A buyer should identify which layer is creating the operational bottleneck before comparing vendors.

Declarix automates the document-heavy build before submission. It keeps the broker’s existing customs system and permissions in place, returns CDS-ready output and makes conflicts visible for the clerk who approves the job.

Filing and preparation are different jobs.

HMRC publishes a list of software developers supplying declaration software, while its developer guidance describes APIs and assurance for software that communicates with CDS. That is a distinct technical and regulatory role from preparing source material in front of the filing system.

The entry pack should show its working.

• Keep the source document, page, line, or evidence reference beside each proposed value.
• Present missing, conflicting, stale, unsupported, or unevaluated facts as review work—not completed data.
• Separate document preparation, customer chase, broker review, correction, and filing time.
• Retain the broker’s change and approval path for the agreed workflow.
• Map the Sequoia, Descartes or customer-integration handoff before live volume.

Ask what “integrates” means.

Declarix supports CDS-ready exports for Sequoia, Descartes e-Customs and customer integrations. The 20-minute call maps which route fits the buyer’s current workflow, including how the clerk receives, checks and hands off the entry data.

The pilot then runs the agreed route on one real-shaped job so the desk can see the fields, evidence, conflicts and handoff together before committing to wider volume.

Compare the same ugly pack.

• Use one properly anonymised job with scans, spreadsheets, long line tables, and real conflicts.
• Record the current manual baseline with agreed start and stop points.
• Count unsupported cases, questions, retries, and corrections—not only successful rows.
• Review security, data location, access, retention, deletion, and support for the proposed deployment.
• Keep commercial units, minimums, corrections, service expectations, and exit terms in the written quote.

Use the call to locate the bottleneck.

Bring one week’s approximate volume, current minutes per declaration, loaded clerk cost and the customs system the team runs. The numbers call estimates ROI, maps the integration route and chooses the first workflow most likely to pay for itself.