We will be introducing an improvement to our SOAP API to further strengthen data consistency and overall platform reliability.

What is changing?

To prevent conflicting updates, simultaneous API calls of the same type using the same API key will not be processed in parallel.

For example, if a product-related operation such as storeFullProductSet is running and another product update is sent at the same time (such as updateStock, updatePrices, or product relation updates), the second request will not run in parallel.

Instead, one request will proceed while the other will return:

500 – Another 'products' call is already in progress; simultaneous calls are not allowed.

Integrations that currently send overlapping product updates using the same API key may now receive this response when calls are submitted concurrently.

This ensures predictable processing and protects data integrity during write operations.

What does this mean for you?

• This is not a hard failure.

• The rejected request can safely be retried.

• The in-progress request will complete normally.

• Calls of different operation types can still run in parallel.

For example, product updates and order retrieval calls can run at the same time without issue.

Recommended handling

If you receive this response, and have not already done so, implement a retry mechanism with short backoff (a few seconds) and resend the request. The retry will succeed once the previous operation has completed.

This update improves reliability and prevents inconsistent updates caused by overlapping requests.

Release timing

This change is scheduled to be deployed on Monday, March 23, 2026.