# Customs Product Database functionalities high over
Registration of **Customs Products** (Taric) and Products by their **Trade name**
For example. A company trades in citrus fruits. Then most likely the below Taric codes are relevant:
The Customs Product database should allow the User to register the relevant Taric code(s). Let's say in this case "Fresh Lemons", 0805 50 10 10. This is the classification from a Customs point of view.
A **Customs Product** is considered a 10 digit code (called a **TARIC**) specifying a **Product from a customs point of view**.
The company dealing with citrus fruits obviously uses different terminology regarding their products. Apparently there are at least 40 types of lemons, such as:
- The Baboon lemon;
- The Bush lemon;
- Etc.
So all classified as "Fresh lemons" from a customs point of view, the User should be able to register their Products under there 'trade names'. This means the Taric codes function as a sort of buckets, in which multiple Products can be registered. So effectively, the should be able to register all the Fresh Lemons by their trade name under the Taric code 0805 50 10 10.
Multiple **Products by their Trade name** are considered **the same from a customs point of view**. The Baboon lemon and the Bush lemon are both classified as "Fresh lemons" (Taric).
In the Customs product database this registration will look like:
> **Taric** **Taric description**
- 0805 50 10 10 CHAPTER 7 - EDIBLE VEGETABLES AND CERTAIN ROOTS AND TUBERS; Citrus fruit, fresh or dried; Lemons (Citrus limon, Citrus limonum); **Fresh**.
1. - - - Baboon Lemon
- Bush lemon
- ......
- 0805 50 10 90 CHAPTER 7 - EDIBLE VEGETABLES AND CERTAIN ROOTS AND TUBERS; Citrus fruit, fresh or dried; Lemons (Citrus limon, Citrus limonum); **Other**.
- Lemon Pulp
**Taric data**
For each Customs product (Taric) their are tons of Trade **Measures** that apply:
The Taric service provides all this information through an interface so that this data becomes available in an automated manner.
**Business don't want to be bothered** with customs details.
Now that we have registered all the Products by their Trade name under the respective Taric, the business can just continue to 'talk their own language'. This means that when a Company indicates from their Source system to the Taric Service that they are dealing with Baboon lemons, the Taric service knows this relates to Taric code 0805 50 10 10 and can make a first selection on what data in terms of Trade **Measures** is applicable. An implementation of the Taric Service means that a connection/interface is created whereby the Companies source system can 'talk to' the Taric Service system.
The implementation of the Taric Service means a connection/interface must be established between a Company's source system and the Taric service
Because the data is or can be critical to primary processes of a company, the setup should be a 'satellite setup', whereby the Taric Service is a Package that runs on the local server of the company which coincides with the Taric service we host in the cloud. Updates in versions should be possible touching the code. In terms of content, i.e. Taric data based on the products registered, should be updated daily to ensure the latest information is available to the User.
The current version on ACC covers the registration of Taric commodity codes and thereunder register products!
Optimisation would be in terms of look and feel that on the Product level the columns are separated by Lines improving the readability [To do](https://www.bzctrl.com/app/#/todo/SWA-SWA-SWD-28 "https://www.bzctrl.com/app/#/todo/SWA-SWA-SWD-28")
**Website authorities**
What we want to offer is the combination of the Legal data with the practical business data.
**Overview Page**
Showing the Taric codes created via Create Product i.e. enter 10 digit code which is validate on existence upon save. Indeed existing the related data from the Tariff database is retrieved and stored. On this Page only the Legal description shows , the start date and the Excise additional code. The other columns are manual input in relation to Products by commercial names that are registered by he User under a Taric code. For example, under the Taric code 2707500080, you see multiple commercial Products, such as "Blend TN 160", "C7 "(Toluene)" etc.
**Create Product**
****
Via the Create Product a User specifies the 10 digit commodity code (Taric). Upon save it is validated to verify existence. If existing it is saved.
Consider the Taric code as a 'bucket'.
**In addition to the mock ups, I would like to be able to add a a description describing the characteristics of the Taric code. So effectively on the main page it should show a column called Characteristics next to to the column Legal description.**
After registering the 'bucket' commercial Products can be added with details that are relevant on different levels, such as on the Product level itself, start date, end date, etc. Details on a National level, related to national taxes (Country details). Lastly, details on the company level can be added, such as 'labels' created by the company itself. In this case "Quality group" and "Usual Forms of Handling".
**Excise additional reference (Product Country Detail)**
Below another example. Here you see the "Product Country Details" under Excise Controlled populated with Y, because from the Tariff information it is found that there is an U code, showing under "Excise Additional Reference" for Taric Code 2710201129. It could be that there are more codes available. In that case the User can choose and save his selection here. The U code is an element also showing on the main page in a column.
From the main Page, the User can also enter the Tariff information as provided by the authorities.
When selecting the details are shown similar to the website from Dutch Customs
All Blue text are hyperlinks to underlying data, e.g.
**Here it should also show the duty rates, etc.**
**Tariff Measures Page**
