Regarding the first constraint, if you have a dedicated product code per country (usually the case becasue packing, slip need to be translated in local language) then you can set a mandatory customer referencing to prevent shipping to unauthorized customer/destination.

Or you can set workflow rules upon the sales order creation (this solution is applicable even if same product code is common to multiple countries).

And you can create forbidden price to ensure that a product cannot be delivered in some countries.

Regarding the second constraint, you may want to manage sales order approval workflow as well. Even so this solution is limited because the customer cannot access your system. So you need an internal user to approve based on customer directions. Without additional details, I see no workaround (except for a customization).

Bonjour Julien

Not sure I clearly understand the process you describe using a product code.

May be we can dig this in more details. Also, since I do not have too much experience in X3 I am not sure how to 'set a mandatory customer referencing to prevent shipping to unauthorized customer/destination.

Merci

Patrick

In the past, a pharmaceutical company (my customer at the time) decided to create different product codes per country / region. So we had ITM001A (for FRANCE), ITM001B (for GERMANY), ITM001C (for UK) and so on. This increases a lot the number of products to manage but it allowed to clearly identify the customer authorized per product (using the customer tab in the product record). This link was set as mandatory to record a sales order (I thought it was a standard general parameter but I can't find it anyore so we certainly did the control with a simple customization). 

In this context, managing different product codes was the right solution because the packaging and the instructions for use were different per country (language and local compliancy).

If, you want to keep a single product code for all countries then the sales worklflow would allow to manage an approval before the goods delivery. But clearly, you will request a lot of approval per year and this may need some work around / customization to have an automatic approval of sales order on 'validated' countries. 

Note: the approval of a sales order is managed on the header. This mean you approve all lines or none.

To sum-up no perfect solution exist in standard but setting customized controls is easy (even possible in standard using control table: GESACL). The trick is to identify what is the right level for you to set control.

In the past, a pharmaceutical company (my customer at the time) decided to create different product codes per country / region. So we had ITM001A (for FRANCE), ITM001B (for GERMANY), ITM001C (for UK) and so on. This increases a lot the number of products to manage but it allowed to clearly identify the customer authorized per product (using the customer tab in the product record). This link was set as mandatory to record a sales order (I thought it was a standard general parameter but I can't find it anyore so we certainly did the control with a simple customization). 

In this context, managing different product codes was the right solution because the packaging and the instructions for use were different per country (language and local compliancy).

If, you want to keep a single product code for all countries then the sales worklflow would allow to manage an approval before the goods delivery. But clearly, you will request a lot of approval per year and this may need some work around / customization to have an automatic approval of sales order on 'validated' countries. 

Note: the approval of a sales order is managed on the header. This mean you approve all lines or none.

To sum-up no perfect solution exist in standard but setting customized controls is easy (even possible in standard using control table: GESACL). The trick is to identify what is the right level for you to set control.