Skip to main content
New

Aditional Declarations (Customs Text Entries) on Commercial Invoices for Origin Statements

Related products:Orders & Shipment Management
  • January 21, 2025
  • 3 replies
  • 6 views

The commercial invoices created by ShipStation have two sections labelled "Special Instructions" and "Declaration Statements" yet there is no way to edit these sections when processing an international order.

This is causing issues for us as a UK country, as we are unable to declare preferential origin on our UK/EU made products which are being sent to the EU. As such, duties are being charged incorrectly on these shipments. 

We need to add the following text to all commercial invoices in order to be compliant with Annex 7 of the UK/EU Trade agreements following Brexit:

“(Period: from ...................................... to .......................................)

The exporter of the products covered by this document (EORI NUMBER GB....................) declares that, except where otherwise clearly indicated, these products are of ... preferential origin.”

Place and date:

Name exporter (company / name responsible person)

Quite simply, we need to be able to edit the Declaration Statement section of the commercial invoices, and this functionality is strangely missing within ShipStation currently....

3 replies

CaraAdmin
  • Community Manager
  • January 28, 2025

Hello, @Joe912!

 

Thank you for your post in the community! We’ve escalated this to our developers for review and truly appreciate the detailed information you provided. Your feedback helps us continue improving, and we're grateful for your input!

 

Happy Shipping!

 

-Cara


  • February 25, 2025

Hi there! Did you ever get a solution to this?


I am looking to do something similar here in Canada for shipping to the US as US Customs requires all CUSMA exempt products to have a specific sentence in the declaration section on the commercial invoice.  For now I am adding a sticker that I printed to all US-bound commercial invoices but this is frankly a low tech solution and an added step that would easily be resolved if ShipStation developers would actually address this issue raised 8-9 months ago.  To see no response after all this time is rather sad.