Summary

To prevent errors when exporting stock and prices, the handling of SKU fields in the OBI module has been standardised and streamlined. In future, it will be clearly defined where the OBI SKU ID must be saved to ensure a correct mapping to OBI offers.

Background: The OBI API stipulates that a valid SKU ID generated by OBI must be used to identify which offer on OBI receives the offer data sent by PlentyONE.

What has changed?

• Primary data source for stock & price: For the export of stock and prices, the SKU field of the offer listing is primarily used as the OBI SKU ID.
• New data field OBI SKU ID in catalogue (as a fallback): The optional OBI SKU ID data field is now available in the OBI offer catalogue. If the SKU field in the offer listing is empty, the export will automatically fall back to this new data field in the catalogue.
• No more automatic VariationID mapping: Newly created OBI offer listings are now created with an empty SKU field so that sellers can enter the OBI SKU ID manually or via mapping in the offer catalogue.
• Discontinuation of the ExternalID data field: The ExternalID data field will no longer be taken into account when exporting stock levels and prices.
• Automatic correction run (13 – 17 August 2026): Offer listings for which the PlentyONE variation ID was automatically saved in the SKU field in the past will be automatically marked with the prefix INVALID: (for example, INVALID:12345).

To-do for sellers (action required!)

Check your OBI offer listings for the prefix INVALID:.

1. Replace invalid entries with the correct OBI SKU ID from the OBI backend (under Produkte » Bestandsführung (Products » Stock Management)).

2. Alternatively, you can save the OBI SKU ID in the PlentyONE system (for example, as a property) and assign it in the offer catalogue using the new OBI SKU ID data field.