Open dominikahr opened 2 weeks ago
You do not write how you edit the offer. You show screenshots of the UI when the API method you use would be more useful for verification. Either way, in both cases the process can take a while before everything is processed. In the API via PATCH, you can send a stock and status change in one request. This works asynchronously. More about editing offers. We have no plans to make this change.
Hi @MartaNowaczyk, sorry about the lack of information. With this endpoint we change the availability in bulk for multiple offers (we don't do it one by one) sale/offer-quantity-change-commands/{commandId}
and then with this endpoint we change the status of those offers in bulk to "ACTIVATE" sale/offer-publication-commands/{commandId}
.
If we would update the offers and by one as suggested it would significantly slow everything down and with the limit on requests that you have, we cannot do it that way. So we first bulk modify availability and then we bulk modify status.
Hi! If the first change has not processed yet, then the cases you write about can happen and can be expected.
Hi there,
we were wondering if you are planning in the future to change the process of offer activation. That if the STOCK would change from "-" to positive value, the offer would be activated automatically.
Because we came across an issue with the current process during testing, where we have sent you STOCK update for an offer to 1 and after that we sent a request to activate the offer, but even though we have sent it in correct order, the offer activation was processed sooner then the STOCK change:
I tested it 4 times and out of that 2 times the offer activation was processed sooner than the stock update. Or do you have any suggestions how to ensure this will not happen?
All the best,
Dominika