Overview #
If your order statuses are not updating in real time inside the Hippoo mobile app, even though they appear correctly in your WooCommerce dashboard or website, the issue is usually related to server caching.
The Hippoo app communicates directly with your WooCommerce store through the WooCommerce REST API. If your caching plugin or CDN is storing old API responses, the app may continue displaying outdated order data until the cache expires or is purged.
This article explains how to confirm whether caching is the cause and how to configure your cache plugin (for example, LiteSpeed Cache) to ensure that Hippoo always receives up-to-date order information.
How Hippoo Connects to WooCommerce #
Hippoo uses the official WooCommerce REST API to retrieve order, customer, and product data in real time.
The key endpoints include:
/wp-json/wc/v3/orders
/wp-json/wc/v3/orders/{id}
Because Hippoo doesn’t render cached web pages, any cache that affects these API responses can cause a delay in updates appearing in the app.
Step 1: Check if Caching Is the Cause #
You can easily verify if a cache plugin is causing the delay:
- Temporarily disable your caching plugin (e.g., LiteSpeed Cache or WP Rocket).
- Open the Hippoo app and refresh your orders list or a specific order page.
- If the order status updates immediately, caching is confirmed as the issue.
After confirming, re-enable your cache plugin and move on to configuring it properly.
Step 2: Exclude WooCommerce REST API Endpoints from Cache #
To make sure Hippoo always receives fresh data, exclude the WooCommerce REST API routes from being cached.
In your caching plugin settings, add these patterns to the Do Not Cache URIs list:
/wp-json/*
/?rest_route=*
/wc-api/*
If your plugin allows you to target specific endpoints, focus on:
/wp-json/wc/v3/orders
/wp-json/wc/v3/orders/*
These exclusions prevent cached responses from interfering with order updates in Hippoo.
Step 3: (Optional) Automatically Purge Cached API Responses #
If you’d like caching to remain enabled elsewhere but still ensure order data stays fresh, you can make LiteSpeed (or similar cache plugins) automatically purge the REST API cache when an order status changes.
Add this code snippet to your theme’s functions.php or a small custom plugin:
add_action('woocommerce_order_status_changed', function ($order_id) {
$order_endpoint = rest_url('wc/v3/orders/' . $order_id);
do_action('litespeed_purge_url', $order_endpoint);
});
This automatically clears the cached API response for that specific order whenever its status changes.
Step 4: Recommended LiteSpeed Cache Settings for Hippoo #
If you’re using LiteSpeed Cache, we recommend the following configuration:
- Cache REST API: Off
- Do Not Cache URIs:
/wp-json/*,/wc-api/*,/cart/*,/checkout/*,/my-account/* - Do Not Cache Cookies:
woocommerce_cart_hashwp_woocommerce_session_wordpress_logged_in_
- Cache Logged-In Users: Off (unless absolutely necessary)
If you use a CDN (like Cloudflare), make sure to apply similar exclusions there too.
Step 5: Manually Purge the API Cache (if needed) #
If you ever see delayed order status updates again, you can manually purge the cached REST API data by clearing your cache plugin or visiting the following endpoint in your browser:
/wp-json/wc/v3/orders
This forces the cache to refresh with the latest order information from WooCommerce
| Issue | Cause | Solution |
|---|---|---|
| Order status not updating in Hippoo | Cached REST API responses | Exclude /wp-json/wc/* from cache |
| Updates delayed after status change | Cache not purging automatically | Add a purge hook for order status changes |
| Works when cache is disabled | Plugin confirmed as cause | Adjust LiteSpeed Cache exclusions |
Final Recommendation #
To ensure smooth synchronization between WooCommerce and the Hippoo app:
- Keep REST API routes uncached.
- Purge REST data automatically when order statuses change.
- Test updates in Hippoo after each configuration change.
Following these steps will make sure your Hippoo app always displays the most current order data in real time.