KCB
Also known as: Kwaliteits-Controle-Bureau, Quality Control Bureau
The KCB is the Dutch Quality Control Bureau. It inspects quality and marketing standards of vegetables, fruit and ornamentals, alongside the NVWA. Pre-notification runs through the same Dutch channel, CLIENT PD.
What exactly does the KCB inspect?
The KCB is the Dutch inspection body for quality and marketing standards of plant products, mainly vegetables, fruit, ornamentals and some potatoes. It looks at class, size, colour, defects and whether the consignment meets the EU marketing standards. That is something other than the NVWA. The NVWA looks at plant health and food safety. The KCB looks at whether the peppers are class I, whether the oranges have the stated size, and whether the lot is saleable under the standard. For the importer of fresh product both inspections matter. A consignment can be phytosanitary in order and still be rejected on quality. The other way around, a neat lot can still get an NVWA inspection because of the country of origin. For vegetables and fruit the KCB is therefore a fixed link in Dutch import, not an exception. Anyone who treats that inspection as optional notices it on the first consignment of peppers or citrus that comes back with code 2 while Customs has already released.
How do you request a KCB inspection?
The request runs through CLIENT Import PD, the same Dutch pre-notification channel as to the NVWA. The pre-notification goes out before arrival. The response uses the same coding: code 1 is free without inspection, code 2 is inspection. On a physical inspection the automated declaration chain pauses. Someone schedules the inspector, the lot stays available at the inspection site, and only once the inspector records the result does a message come back into the declaration system. That waiting time is the operational risk for fresh product. An inspection that lasts until the next day costs shelf life. That is why the pre-notification belongs in the same run as the T1 or the IMA, not as a closing item afterwards. Request the inspection on the same ETA as the T1 or the IMA. The KCB plans on what comes in. A notification on the day of unloading pushes the inspector to tomorrow, and the lot stays on site until that result is in.
Which data does the KCB need?
The inspection declaration asks for the product, the country of origin, the weight, the packing, the class if one is stated, and the place where the consignment stands for inspection. Many products have characteristics: for peppers the capsicum type and the colour, for citrus the variety, for tomatoes the type. Two things the declarant can rarely derive alone: the botanical name and the variety. Those must come from the shipper, on the invoice or on the request. An invoice with only peppers or oranges is too coarse for the inspection. The phytosanitary certificate is on the NVWA side. The KCB uses the file, but inspects against the marketing standard. If invoice, packing list and certificate name different varieties or weights, that is a reason for code 2, even if each document is right on its own. Put those characteristics in the article master data, not in a free remark. A next consignment of the same pepper must have the same fields. Otherwise every inspection declaration is guesswork for the declarant again.
How does the KCB relate to the NVWA in the chain?
Both services often sit on the same site in practice and share the pre-notification channel. The results are independent. A consignment can be free from the NVWA and get an inspection from the KCB, or the other way around. For the declarant that means two statuses, not one. The import declaration in DMS waits for the inspection codes. If one is missing, the consignment is not free, even if the MRN is in. The costs also run apart. The NVWA invoices inspections carried out monthly. The KCB has its own tariff structure for quality inspections. Both land with the declarant and are in practice passed on to the importer. Invoice them as two lines as well. Anyone who puts NVWA and KCB on one inspection-cost post cannot explain to the importer why a consignment was touched twice. The codes in the file already make that distinction. The invoice should follow it.
What happens on a rejection by the KCB?
A quality rejection means the lot does not meet the stated class or the marketing standard. The consignment may then not be traded as that class. Re-inspection, relabelling or a lower class are possible, depending on the finding. That is a commercial problem and a customs problem. The goods code and the value on the IMA assume the declared lot. A reclassification of quality does not automatically change the consignment in DMS, but the invoice and the packing list then no longer match what physically lies there. When a consignment is partly rejected, the chain splits. The approved part can go on, the rejected part stays under supervision until there is a destination: repair, re-export or destruction. That destination needs its own declaration. Record the rejection per lot, not only as a status on the container. A part-lot that goes to re-export has its own MRN track. Without that split the whole container stays administratively under the rejection.
Why does the KCB belong in the same monitor as DMS?
Because the truck may only drive once both tracks are green. An IMA that has been released while the KCB status is still on inspection is in order on paper and not on the quay. The pre-notification is cheap, the missed notification is expensive. Without a CLIENT PD message the consignment is not scheduled. A late inspection on the day of arrival shifts unloading, T1 discharge and gate-out. Put the inspection status next to the MRN, not in a separate mailbox. In a well-arranged chain the inspection declaration goes out with the rest of the flow, and code 1 or 2 comes back in the same file. Without that response the file stays open, even if Customs is done. A separate mailbox for inspection codes is how consignments get lost. Code 1 or 2 belongs on the same screen as the MRN. Anyone who does not see it there calls the terminal while the document sits in yesterday's inbox.