EWD

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.