1b.app
Link copied -

Synchronizing Availability with Vendor File

Recently, a massive problem has arisen when working with synchronization of availability with suppliers via xml. The goods from the supplier are constantly in stock, we get the availability of constantly jumping, that is, it is not. This has a very negative effect on working with the Rozetka marketplace, as it kills the issuance of a product card on the Rozetka. Plus, one more problem, if the goods are running out at the supplier, and we have this product in stock and credited, then it also writes that it is not available, that is, the product lies and is not for sale. How can this issue be resolved promptly, we are losing money because of this problem. And in manual mode, putting down the presence is unrealistic. We look forward to your prompt assistance in resolving this issue.
Original question is available on version: ru

Answers:

Commentary is available in ru and not yet translated to the current language.
08.08.2021, 23:08

Commentary is available in ru and not yet translated to the current language.
08.08.2021, 23:09

Суханіцький Андрій OneBox CORP
OneBox Corp - Інтегратор
Personal license
Good afternoon.
Updating information about suppliers via xml does not trigger price recalculation.
Try to set up an action in the automation once per hour "Price recalculation" you need to set it after loading all the sails, but before the actions of uploading goods to the marketplaces, so the prices will be loaded first, then the prices and availability will be relearned, and after this they will be uploaded to marketplaces
09.08.2021, 12:35
Original comment available on version: ru

Суханіцький Андрій OneBox CORP
OneBox Corp - Інтегратор
Personal license
Also, for recalculation, you must have at least a basic rule, you can check the box "Do not change the sale price" in it, if you have other rules that do this or you set prices manually
09.08.2021, 12:37
Original comment available on version: ru

Victor, did the above solution help you?
10.08.2021, 14:43
Original comment available on version: ru

Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter. Log in and comment