⌘Ctrlk
The price upload has been designed so that no duplicate prices are created in Shopware when price periods change.
Web-ID inheritance (PATCH instead of POST)
Prices that have already been uploaded have a Web-ID.
When a price changes, this Web-ID is reused and the price is updated via PATCH instead of creating a new record via POST.
As a result, no duplicates are created during the transition between price periods.
Currency safety
The price upload uses the currency that is marked as the default in the mapping. This avoids confusion between different currencies. See Currencies.
Forced re-upload
If you deliberately want to transfer prices again, mark the affected lines as not synchronized (for example, using Mark lines as unsynchronized or Mark all prices as unsynchronized). They will be uploaded again during the next run.
In addition, actions such as Upload latest prices (force) and Delete all Shopware prices are available.
Price lines are matched by their “SOUSHW Web ID” (Shopware product-price ID) and updated instead of being created anew. In addition, the NewPriceExists() check detects overlapping tiers based on the starting and ending date. Lines that have expired or are flagged as “Marked Delete” are found via search/product-price and removed with DELETE.
This action removes orphaned Shopware prices for which no matching price line exists in Business Central anymore. This keeps the prices in Shopware consistent and prevents conflicts caused by legacy data.
The package size is controlled by the “Price API Limit” field (default 1). Product prices are transferred in bulk packages of this size via Upload_RuleWithBulkPrice – with large price volumes, a higher value can reduce the number of API calls.