Hi @karthik92,
Thank you for reaching out and providing a detailed explanation of the issue. I understand that problems like this can be frustrating and concerning, especially when your business operations depend on it.
To clarify your request: you’ve integrated your store with Unicommerce using the WooCommerce REST API. While Unicommerce shows that your products are being synced, they are not appearing in WooCommerce.
If that is correct, this is not something we can troubleshoot on our side. Since this involves a third-party integration, it is the responsibility of Unicommerce to help determine why their system, despite showing as synced, is not updating your website.
We understand this may not be the answer you were hoping for, but our support scope is limited to WooCommerce core functionality and issues, not third-party integrations. Please reach out to Unicommerce support to report this issue and get further assistance.
Hello,
I just wanted to link to another ticket that might be relevant.
We also have an external system connected to WooCommerce.
- When it updates the stock quantity via REST API, the WooCommerce REST API returns outdated stock quantity in the response, which is causing a lot of error logging in the external system.
- In our case, it’s the other way around: the data is updated correctly in the WooCommerce shop, but the JSON response that WooCommerce sends is incorrect. It’s essentially returning the outdated product object, or at least not all properties are up to date.
- This causes the external system to believe, when checking the response, that something has gone wrong. (Which it hasn’t, everything is okay.)
We’ve noticed that the error only occurs when we have the “WPML String Translation” plugin active, and therefore we’ve opened a ticket with WPML.
Reading this ticket, I’m wondering if there was a change between WooCommerce versions 10.2.2 and 10.3.4 that might be related to the API. We’ve been experiencing this error since then.
The page is in German and may need to be translated using Google Translate if anyone wants to read it:
I wanted to leave this information here because it seems relevant. I understand that separate tickets should be created for different topics. If this isn’t helpful, please just ignore it. However, since two people are already having problems with the REST API, it might still be of interest to WooCommerce support.
@karthik92 I wish you the best of luck with troubleshooting. Such errors are often not easy to analyze and the fix can be time-consuming.
Hi @robertrosanke
Thank you for sharing this update with us, and I appreciate you taking the time to explain your experience with a similar issue. I’m really glad to hear you were able to troubleshoot the problem and open a ticket with WPML. That’s a great step forward.
To clarify, when it comes to the REST API, the main concern is confirming whether it is successfully sending or receiving requests, as that indicates the API itself is functioning correctly. Issues that stem from third-party integrations or plugin conflicts, however, are best handled by the developers of those tools since we are not able to troubleshoot or fix problems within third-party code.
If WPML’s team determines that the issue is coming from WooCommerce or one of its core features, their developers can reach out to the WooCommerce development team directly so both sides can collaborate on a solution.
Hi @karthik92,
I hope everything’s going well. Since we haven’t heard back in a bit, I’ll mark this issue as resolved for now. You’re always welcome to reach back out if you need anything.
If you found our support helpful, or would like to leave feedback on the plugin, we’d appreciate a review here:
https://wordpress.org/support/plugin/woocommerce/reviews/#new-post
