As of 1st of July 2021, all commercial goods imported into the EU from a third country or third territory will be subject to VAT regardless of their value. IOSS (Import One Stop Shop) will allow Shippers and Marketplaces to collect, declare and pay the VAT to the tax authorities, instead of making the buyer pay the VAT at the moment the goods are imported into the EU as was previously the case (for products over 22 EUR).


Below you will find the relevant field where the IOSS Number would need to be passed to for each courier, as well as any additional details that may need to be supplied. You would need to ensure that the order item values passed to the shipping couriers for the IOSS shipments would be Tax exclusive. In order to set this up in Linnworks, you would need to follow the steps described here. 


Order Extended property mapping is done in Shipping > Integrations > Properties > Order Properties. If you need to change the mapping of a property, copy or type the exact name into the Order extended property column and click Save.


Please note! Order extended properties downloaded from the marketplace will display the Property Type as 'Order', not 'Attribute'. Both types will get picked up by the shipping integration, so you may set the manually assigned properties to either of those, however we suggest to use 'Attribute' for consistency.



Important: In order to see which marketplaces support the automatic download of the Marketplace IOSS numbers as well as how to set up rules to assign IOSS numbers for other marketplaces, please review this article.




Australia Post:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the AusPost Config under the IOSS Registration Number field. This value will always be passed to the courier if there is no Order Extended Property added with the MARKETPLACE_IOSS name.




Deutsche Post:


Marketplace IOSS numbers need to be passed to a field called SenderEORINumber in the Order Extended Property mapping, as Deutsche Post does not have a separate field for IOSS numbers. You may change the Order Property mapping from SenderEORINumber to MARKETPLACE_IOSS in order to pick up the IOSS Number supplied by the marketplace automatically. 


Shipper IOSS can be added in the Deutsche Post Config under the EORI/VAT Number field. This value will always be passed to the courier if there is no Order Extended Property added with the SenderEORINumber name (or with the name that is mapped to this field in Order Property mapping).




DHL Express:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order. 


Shipper IOSS can be added in the DHL Config under the IOSS Registration Number field. This value will always be passed to the courier if there is no Order Extended Property added with the MARKETPLACE_IOSS name.


You will need to ensure that the Terms of Trade are set as DDP in DHL config and/or in the service config (Shipping > Integrations > Services > Edit).




DPD Local/DPD UK:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the DPD Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.


Terms of Delivery can be set as both DAP or DDP (DT1). DPD will first check to see if there is an IOSS Number, and will then ignore the Terms of Delivery, and of there is no IOSS Number, the Terms will be used as they are supplied.


Please note that DPD will expect the IOSS Number to be supplied for majority of European destinations. The only countries where the number is not mandatory are France, Germany, Netherlands, Spain, Ireland, Italy and Austria. For further details about these countries and possible errors related to IOSS number please contact your DPD Account manager.




Endicia:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order. 


Shipper IOSS can be added in the Endicia Config under the TaxId/IOSS Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.




FedEx:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order. 


Shipper IOSS can be added in the FedEx Config under the IOSS Registration Number field.  This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the IOSS Registration Number name.


Please note that in order to submit the IOSS Number to FedEx, you would need to ensure that the Duty Payment Type should not be set as 'Recipient'.




GFS:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the GFS Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.




Hermes Corporate:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the Hermes Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.


You will need to ensure that the Duty Paid (Shipping > Integrations > Services > Edit) is set as Duty Paid.




Parcelforce:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the Parcelforce Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.




Royal Mail:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order, however you will need to use one of the supported services. Supported services will be listed below.


Shipper IOSS can be added in the Royal Mail Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name. This will also only apply to supported services that are listed below.


Please note that only the following service codes will support the IOSS Number with Royal Mail: DE4, DEE, DEG, DEI, DEJ, DEK, DEM, DG4, DW1, ITR, MTE, MTG, MP7, MTK, MP9, MTO, MTF, MP8, MP0, OLA, OTA, OTC, OSA


If any other service code is used, the IOSS Number will be ignored and not passed through to Royal Mail. If you are not using any of the above service codes, you would need to contact Royal Mail and set up new contracts for some of these services, as otherwise buyers will end up being charged for the duty payments twice. When the IOSS Number is picked up and passed to Royal Mail, the label will display an IOSS logo on it. 




Spring Omni:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the Spring Omni Config under the IOSS Registration Number field. This value will always be passed to the courier if there is no Order Extended Property added with the MARKETPLACE_IOSS name.


For both scenarios you would also need to include an Order Extended Property called IOSSCountryCode, which will be the ISO-2 code of the issuing authority's country. This property may be assigned to relevant orders using Rules engine, and if not supplied, the Recipient Country Code will be used.




TNT:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called SenderVATNumber, as TNT does not have a separate field for IOSS numbers. They will automatically be passed to the courier if present on the order. 


Shipper IOSS can be added in the TNT Config under the VAT No field. This value will always be passed to the courier if there is no Order Extended Property added with the SenderVATNumber name.


Ensure that the Incoterm (Shipping > Integrations > Services > Edit) has the value of Delivery Duty Paid (DDP).




UK Mail:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the UK Mail Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.




UPS:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the UPS Config under the IOSS Registration Number field. This value will be passed to the courier if the order item value does not exceed €150 and there is no Order Extended Property added with the MARKETPLACE_IOSS name.


Ensure that the Terms of Shipment (Shipping > Integrations > Services > Edit) has the value of Delivery Duty Paid for the IOSS Number to be passed.



_______________________



Asendia:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order.




Landmark:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSS. They will automatically be passed to the courier if present on the order.


You will need to amend the Landmark config and add your business details (Vendor Name , Vendor Address, etc)




The Delivery Group (Secured Mail):


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order. 


Ensure that each service (Shipping > Integrations > Services > Edit) has the value of Commercial Invoice enabled.



_______________________



Parcel2Go:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called MARKETPLACE_IOSSThey will automatically be passed to the courier if present on the order.


Shipper IOSS can be added in the UPS Config under the IOSS Number field. This value will be passed to the courier if there is no Order Extended Property added with the MARKETPLACE_IOSS name.




Trakpak:


Marketplace IOSS numbers need to be mapped to an Order Extended Property called Shipper Reg NumberYou may change the mapping, so that it would pick up MARKETPLACE_IOSS property name and this property will automatically be passed to the courier if present on the order.




NB! Any 3rd party shipping integration being used in Linnworks cannot be updated from our end. You will need to contact the developer of the integration that you are using and ensure that they will add the support for the IOSS Number field in the user config or in the Order Extended properties.