So many of you have tweeted this excellent đŸ§”at me. Thank you.

Couple of things to clarify in case you don't know what these systems are

/1

Daniel mentions 2 different systems: EMCS used to register movements of excise goods (wine) and CHIEF for customs.

As excise products are subject to additional controls EMCS was used even when we were in the EU. And it still is now.

/2

https://t.co/0kOziVJsVj
CHIEF is different, it's a customs systems. Reminder, as an EU member we didn't have customs borders with other EU states.

We've now introduced a new customs border so all movements to/from the EU need to be logged in CHIEF AS WELL AS other relevant systems.

/3
CHIEF isn't easy to use. Kudos to Daniel for managing to input directly into it. The additional software helps but yes, there is a cost involved. Or you can pay the broker.

Part of that extra admin cost we've been warning about for the last 5 years

/4
Another issue is that CHIEF will soon (ish) be replaced by CDS. A new version. So even if you learn how to deal with CHIEF now you'll soon need to re-learn on CDS.

/5
And yes, you have to claim the reduced tariff under the UK-EU deal. That's normal.

It's because this reduced tariff is only available for goods that meet rules of origin - which you have to demonstrate.

/6

https://t.co/HYOcacjSGC
The same way the EU supplier needs to demonstrate their goods need to meet RoOs - hence the Rex number

/7

https://t.co/4PBr0qOchT
All this, as well as the various codes and abbreviations you need to know to fill in a customs declaration, is totally normal. It's part of trading internationally. But that doesn't mean it's easy.

/8
@DanielLambert29's company was well prepared for 1 Jan. They've obtained all the registrations, stockpiled. Done as much as any business could have under the circumstances.

/9
But the natural consequence of having a new border is that things that used to be very simple, are now complex and require specialised knowledge. And are only possible provided that all the systems work and are updated.

/10
ThisđŸ§”is an excellent example of how insanely complicated all this is from a business perspective. How it adds to everyone's workload which has to translate into increased costs. For the company and for the consumer.

/11
And again, the scary part is that this is an example of a company that's done well.

There are many businesses out there that are far, far behind and are yet to learn about all that.

/end

More from Business

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.