Skip to main content

Hi everyone, 

We are producing and selling large configurable parts. 

Depending to the configuration of the product, the Customs Statistic No is not everytime the same. 

We didn’t found any way to set up this correctly (the Customs Statistic No is fixed for a defined invetory part, on a specific site). 

Did anyone faced this kind of issue already ? Do you have any advice to deal with this kind of problem ? 

@Clément B indeed Customs Statistic No is linked to an Inventory Part and not to a Configuration.

Since you will need that number printed on the delivery documents for customs purposes, probably the easiest way to handle this would be to have a free text custom attribute at Shipment Line level. Users should populate this info before printing the shipping docs and then change the layout of the shipping docs (Shipment Delivery Note / Shipment Packing List / any others as per your need) to show the value of your ‘custom’ customs stat no.

Didn’t had this requirement before, but I’m just throwing some ideas in here.


@Clément B I didn’t had this requirement before, so I’m just pitching some ideas that could work.

Indeed Customs Stat No is linked with the Inventory Part. Since you would need this field on the Shipping Docs for Customs purposes, I would

  • create a Custom Attribute at Shipment Line level
  • users should enter a value in that field before printing the shipping docs
  • change the shipping docs layout (Shipment Delivery Note / Shipment Proforma Invoice / any other doc as per your requirement) to show the ‘custom’ Customs Stat No

Dear @Marcel.Ausan , thank you for your quick reply ! 

We will keep in mind your idea. 

We will try to use as much as possible the standard behaviour of IFS, because most of our parts and product will be compliant with it. 

For derogatory parts, we may have to : 

  • create a Custom Attribute at Shipment Line level
  • User should enter a value only for specific cases
  • Create an event during shipping doc creation : if the custom field is fullfield, then use the custom field value. If the custom filed is empty, use the standard value.

It doesn’t look fantastic, could be a solution….  


Reply