API Instability & Onboarding Failure

We attempted to implement Oliver POS (v2.4.2.6) on a WooCommerce site and were unable to complete the initial connection process.

After entering the subscription key, the plugin simply spins and returns:

{"exceptions":null,"Message":null,"opConnect":"noResponse"}

To rule out local configuration issues, we conducted direct server-level testing of the API endpoints used by the plugin. From our production server, the Oliver endpoints revealed in their plugin consistently return HTTP 500 (Internal Server Error).

This confirms the failure is occurring server-side within Oliver’s API, not within WordPress or WooCommerce.

Additionally, the plugin does not surface meaningful error messages. Instead of reporting the upstream 500 response, it returns a generic "noResponse" result, which makes troubleshooting unnecessarily difficult.

Oliver advertises 24/7 support, yet when attempting to contact support during this issue, we were informed no one would be available for approximately 15 hours. For a POS system that relies on external API connectivity, that level of responsiveness is concerning.

We cannot recommend a POS solution where:

• Core onboarding endpoints return 500 errors,
• Errors are suppressed rather than properly reported,
• Support is not immediately accessible despite 24/7 claims. (also see all none responsive requests in other reviews!!)

Until API reliability and support responsiveness improve, we would advise not to consider this as a reliable POS solution!!