LiveNCTS6 transit declarations are now live — alongside CDS, GB ENS, EU ICS2, GB GVMS and French ELO
Register
Platform · Product updates

See What Is Changing in the CDUK Platform

The CDUK platform keeps improving the work your team does every day: preparing declarations, reviewing documents and working through shipment detail. Each highlight explains what it does, where it appears and how much time it saves you when you file in-house. Everything described here is part of the account you already file from.

  • Document review
  • Duplicate handling
  • Commodity search
  • Bulk item editing
  • Browse platform highlights by moduleFilter updates to the modules you use and see what is available now.
  • Document conflict reviewValues that differ between documents sit side by side, and your operator confirms the one to use.
  • Commodity requirements mappingThe data and documents the selected code asks for appear beside the item.
  • Know what each update note tells youEvery note states what changed, who it applies to and any action you need to take.

In a nutshell

These are the platform's current capabilities in the places where preparation takes the most effort: reading documents with Intelligent Document Processing (IDP), reconciling repeated goods, searching commodity information, and completing multi-item CDS (Customs Declaration Service) declarations. Each one removes repeat typing or double-checking.

The highlights describe current capabilities, not release notes, so they carry no release dates or order. When dated release notes are published, each one will identify the release and its availability.

In every case your own person reviews the output and has full control of the declaration. Our team can show you any feature on your own documents. Start with the highlight that matches your busiest workflow.

Platform highlights

Five highlights at a glance.

Each highlight belongs to a module and appears at a particular stage of preparation. Find the one that matches the job your team does most often, then follow the link to the page that explains the workflow.

HighlightAreaWhere to explore it
Conflicting document informationAI and document processingDocument review in IDP
Repeated goods and final linesAI and document processingGoods-item review in IDP
Commodity searchCommodity searchCompliance and validation
Bulk item editingDeclaration preparationDeclaration workspace
Shared commodity requirementsCDS commodity requirementsCompliance and validation

The order is not a release sequence. Tell us the services you file and we will confirm how each highlight applies.

Document processing

Review what the documents say.

Two highlights sit in the document review stage of the AI document processing workflow. Both save your team from reading documents line by line, and both put the decision in front of your operator.

Document conflict review

Review conflicting information across documents

Invoices, packing lists and transport documents do not always contain the same values. Document conflict review brings differing information to your operator's attention before the draft is prepared, so a mismatch is found at the desk, not at the border.

Your reviewer compares the source values side by side, settles the correct information and confirms what belongs in the filing. It is quicker than comparing PDFs by eye.

  • Area: AI and document processing
  • Where: the document review stage in the supported IDP workflow
  • Effect: differing values reach your operator before the draft, saving rework
Explore AI document processing
Duplicate handling

Review repeated goods and reconcile the final lines

The same goods can appear in multiple documents for one shipment. Duplicate handling brings those repeated entries together for review. You can keep lines separate or group and reconcile them.

Your operator checks the final quantities, weights and values before confirming. This gives a tidier starting point for the declaration, especially on shipments with long packing lists.

  • Area: AI and document processing
  • Where: goods-item review and duplicate handling in IDP
  • Effect: a tidier set of goods lines to check, with your choice kept
See the document-to-draft workflow
Declaration preparation

Less repeat entry, more attention for exceptions.

Three highlights speed up larger CDS declarations, where repetitive entry can pull attention away from the lines that really differ. Your team spends its time on the exceptions, and the platform handles the repetition.

Commodity search

Search commodity information during preparation

Description search and partial-code lookup let your operators investigate commodity information without leaving the goods data. Moving from an incomplete reference or a product description to the information needed for classification review takes minutes, not a trawl through tariff pages.

Classification stays your decision. Your team confirms the selected code against the actual goods and the requirements of the declaration.

  • Area: commodity search
  • Where: the supported commodity-search tools in the preparation workflow
  • Related: compliance and validation
Bulk item editing

Apply common information across selected CDS items

Where multiple commodity lines share the same information, bulk item editing lets your operator apply it once to the selection instead of line by line. Individual items remain available for separate review when their details differ.

On larger declarations that saves time and lowers the chance of a slip on line 40. Your operator reviews the selected items and the changes before continuing. Items that differ stay separate, so exceptions are never overwritten by accident.

Explore the workspace
Commodity requirements

Work through shared commodity requirements together

Requirements shared by multiple commodity items can be grouped for completion. Your operator answers the common requirements once and keeps different answers where the goods require them.

A complex entry is organised around the requirements that need completing, instead of repeating the same task on every line. It also makes a long list of requirements easier to track to completion.

How updates are published

What every dated update will tell you.

When release notes are published, each one will state the following, so you can see what changed and decide in a minute whether it affects your team.

FieldWhat it tells you
TitleA plain description of the change
Release dateThe actual date of the release, never an estimate
Affected moduleWhich service or workflow the change applies to, such as CDS, IDP or a safety and security filing
AvailabilityWho can use it and under which service or arrangement
ChangeWhat is different, described specifically
Workflow effectHow the change alters a task your team performs
Action neededAnything your team must do, or confirmation that nothing is required
Resource linkA link to the relevant page or guidance

Security or fix-related changes are described only where a real release record supports them.

From update to practice

Bring each update into your process.

The exact options depend on the service and workflow you use. A short, repeatable routine turns each update into a time saving. Our team is happy to show you a change on your own example.

A simple review routine
  1. Step 1: Read the note

    Check the affected module, who can use it and the stated workflow effect.

  2. Step 2: Match it to your work

    Decide whether it touches a declaration type or task your team uses. If not, skip it.

  3. Step 3: Try it on an example

    Use a representative invoice or multi-item declaration to see the time it saves.

  4. Step 4: Update instructions

    Record any change to who reviews what, and brief the people who prepare filings.

A CDS improvement applies to CDS. Each update names the service it affects.

Your feedback

Help shape what improves next.

Feedback from real declaration work is the most useful kind. Tell our team where preparation takes longer than it should. A specific workflow example helps us build the right thing.

  1. Step 1: Find the friction

    Note which part of preparation takes unnecessary time, where information is hard to review or which repeated task could work better. Say how long it takes.

  2. Step 2: Describe it clearly

    Name the service, the step and the outcome you were trying to reach. A screenshot with sensitive details removed is ideal.

  3. Step 3: Anonymise the example

    Use a redacted or anonymised document where possible, and leave out unrelated personal or commercial information.

  4. Step 4: Send it to us

    Use the contact page to send product feedback to our team. Tell us the outcome you were after, and we will reply with what is possible.

Product update questions

Questions about platform updates.

Are these release dates?

No. These highlights describe capabilities in the platform today. When dated release notes are published, each one identifies the release and who can use it.

Are the highlights listed in the order they were released?

No. The order is for readability only and says nothing about when each capability was introduced. Start with whichever matches the job your team does most often.

Does an update apply to every declaration type?

No. Each update names the service and workflow it applies to. A CDS improvement applies to CDS, while GB safety and security declarations and EU Import Control System 2 (ICS2) follow their own workflows on the same account, each with its own checks and responses.

Does commodity search choose the code for me?

No. Search helps you find commodity information fast, from a description or a partial code. Classification is your decision, so you confirm the selected code against the actual goods and the requirements of the declaration. See compliance and validation.

Does bulk item editing remove the need to check each line?

No. It saves you from retyping. Bulk editing applies common information to a selection you choose, and individual items remain available for review when their details differ. You review the selected items and the changes before continuing.

Does conflict review correct values automatically?

No. It brings differing values to your operator's attention, so the decision stays with your team. The reviewer compares the source values and confirms what belongs in the filing. See AI document processing. The extracted data remains a draft that your team reviews.

How do we get help using a change?

Contact our team through the contact page and name the service and the task involved. We explain the relevant workflow or walk through it with you on a representative example, as part of our UK-based onboarding, training and support.

Are improvements priced separately?

No. Improvements are part of the platform you already use. Pricing is pay as you go with no monthly fee and no minimum volume, plus custom subscription plans with volume discounts, and IDP carries no per-document fee. See the pricing page. Maximum prices per declaration are published for each service.

See the Latest Improvements on a Real Example

Bring a representative invoice or multi-item declaration and our team will walk through the relevant improvement on your own example. Or register now, with no monthly fee and no minimum volume, and try it yourself.