Release Notes - NCTS Email Configuration & Customisable Bulk Declaration Upload for CDS

Created by AI Agent, Modified on Tue, 1 Sep at 8:10 AM by AI Agent

Release Notes - NCTS Email Configuration & Customisable CDS Bulk Declaration Upload


  1. Product Modules: NCTS (Departure & Arrival), CDS (Import & Export)
  2. Release Status: Live / Production


1. Release Summary

This release focuses on control and flexibility. NCTS users now have full control over who receives lifecycle notifications and for which events, using the same familiar Email Configuration pattern already available for CDS, ICS2, and ROS.

On the CDS side, the Bulk Declaration Upload engine has been made layout-tolerant — you can shape the upload file to your workflow rather than the other way around.


2. Key Enhancements & New Features


NCTS Email Configuration

  1. Overview / What's New: A new NCTS section is now available under Settings → Email Configuration, matching the pattern already used for CDS, ICS2, ROS, and other modules. Configure event-based notifications for Submitter, Transit Holder, Traders and Additional Contacts across all key NCTS lifecycle events.
  2. How it Works / How to Use:Go to Settings → Email Configuration → NCTS.
  3. Review the matrix of NCTS events (Departure and Arrival) as rows and recipient categories as columns.
  4. Tick the recipient categories you want notified for each event:
  5. Submitter — the user who submitted the declaration.
  6. Departure Traders — Consignee, Consignor, Carrier, Representative and Destination Trader
  7. Transit Holder — the Transit Holder contact on Departure declarations.
  8. Additional Contacts — the Primary Person on each Trader contact where the new NCTS Email checkbox (Contacts modal → Primary Person tab, alongside Import Email / Export Email) is enabled.
  9. Add CC and BCC email addresses that should be copied on every Trader email.
  10. Save — the configuration takes effect immediately.
  11. Sensible defaults are pre-applied on first load, so you get useful notifications flowing without configuring everything from scratch.
  12. Key Benefit: All relevant parties stay informed on NCTS lifecycle events automatically — no more sending status updates by hand — with full control over exactly who is notified for what.


Customisable Bulk Declaration Upload for CDS

  1. Overview / What's New: The CDS Bulk Declaration Upload engine now tolerates flexible file layouts. You can reorder columns and remove non-mandatory columns from the upload file — the system identifies each field by its header name, not its position, and simply treats omitted optional columns as blank.
  2. How it Works / How to Use:Download the CDS Bulk Upload template as usual.
  3. Adjust the file to suit your workflow:
  4. Reorder columns in any order you prefer.
  5. Remove any non-mandatory columns you don't need for this batch.
  6. Keep the header names identical to the ones in our published template — headers are how the system maps each column to the correct field.
  7. Upload the file. Mandatory columns must all be present; if any are missing, you'll receive a clear error naming the missing column(s).
  8. Key Benefit: Prepare your bulk uploads in the shape that suits your workflow — pull straight from an ERP export with a different column order, or trim to just the fields you care about — without hitting avoidable layout errors.

3. Important Notes

⚠️ CDS Bulk Upload — Header Names Are Required to Stay the Same
Column order and non-mandatory column removal are now flexible, but column headers must match the names used in our published Bulk Upload template exactly. The system uses the header as the key to identify each field — rename a header and that column will not be recognised.


4. Support & Feedback Channel

If your team encounters any issues or has questions regarding these new features, please open a diagnostic ticket with our technical support squad.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article