• 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!!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Hi, I’m from GetGear Gun Co. We’re currently looking for a POS system for our WooCommerce store, and Oliver POS is one of the options we’ve been researching.

    I came across your review and wanted to ask whether you were ever able to get the issue resolved. Your comments about the connection failure, the API errors, and the support response were really helpful for us to see, because we’re trying to avoid running into the same kind of problem after signing up.

    If you weren’t able to fix it, did you end up moving to a different POS system instead? If so, would you mind sharing which POS you chose and how it has been working for you so far, especially in terms of setup, reliability, and syncing with WooCommerce?

    We’ve been comparing a number of WooCommerce POS options, so any update from your side would be really appreciated and would help us make a more informed decision.

    Thanks in advance.

    Thread Starter EWD

    (@surfshak)

    Hi…happy to share an update.

    We were never able to resolve the Oliver POS connection issue. Despite multiple follow-ups over the past month, we have received no response from Oliver support to date. As far as w can tell, this is now a fully non-working and unsupported plugin.

    From a technical standpoint, the failure was not environmental. We confirmed through direct server-side testing that the core Oliver API endpoints used during onboarding were consistently returning HTTP 500 errors, including /api/v1/Account/Ping/, /api/v1/Account/InitConnection/, and /api/v1/Account/AssignSubscription/. The plugin itself masked these failures and returned a generic “opConnect”:”noResponse”, which made debugging harder, but the root cause was clearly upstream within their API.

    Given that the onboarding process relied entirely on external API availability, those endpoints were failing at the server level, and support remained unresponsive, we decided not to proceed with Oliver POS.

    Our recommendation is that no one considers using this POS plugin on the above basis.

    We also tested YITH POS, but found it far too simplistic for our needs and lacking important functionality such as lay-bys and other fairly standard POS features. We ultimately moved to LightSpeed POS, despite costs, as a temporary measure, and we are now building our own WooCommerce-based POS solution off the back of the YITH plugin.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.