There are 2 prerequisites for being able to add package components to a variant: The variant that is to become a package must not have any stock. This means the physical, reserved, and net stock must be exactly 0.The future package component must not itself be a product package. Packages may not be added to other packages.

You can conveniently delete SKUs that you want to remove from your variants via the importer in PlentyONE, as long as the variant itself has not yet been deleted.Procedure via the importer Matching ID: Select the variant ID for matching in your import profile. Field mapping: In the mapping of your import profile, assign the following fields that serve to identify the SKU assignment: Marketplace ID Account ID SKU Delete SKU (This field must be filled with the value that triggers the deletion, e.g. true or yes). Additional information Detailed explanations of the required fields for importing article data can be found in the manual in the section: https://knowledge.plentyone.com/en-gb/manual/main/data/elasticSync-item.html#2460

If you delete an item without first removing the assigned SKU, it can happen that the SKU remains locked in the database. When trying to assign this SKU to a new item, you receive the error message: SKU not saved. The specified SKU has already been configured for another variant of this marketplace and account. To avoid this in the future, you should follow the procedure below.Instructions to avoid the errorDelete SKU: Go to the availability of the item and first delete only the SKU itself there.Save: Save the item to ensure that the SKU is cleanly deleted or overwritten from the item database.Delete item: Only then delete the entire item.Manual release of the SKU If the error has already occurred, a manual release of the SKUs via a support ticket is necessary. Support can release all SKUs that no longer have variant assignments.

The stock levels of an item are often not updated after an import because either the import file was not uploaded correctly or important mandatory fields are missing in the mapping, which are necessary for processing the stock levels. Required fields for stock import For a successful stock import, the following three fields must always be present in your import file and correctly assigned in the mapping:Quantity (The new stock quantity)Warehouse IDStorage Location ID Correctly assign Storage Location ID The specification of the Storage Location ID is mandatory.If you work with storage locations: Make sure you assign the correct Storage Location ID from your import file to the corresponding data field in plentysystems.If you do not use storage locations: You must specify the value 0 for the default storage location in the mapping. What to check if there is no update Follow these steps if your stock import did not result in an update of the item stock levels:Check the import file: Make sure that the file for the specified import ID i...