Wow, this is getting to be frustrating. After going through the iterations I addressed in my last post I hit a wall over POS implementation (and pricing). So, I deleted the original POS, again, and decided to migrate to my fall-back position.

Just when I thought things were OK–critical error warning popped, again. Really getting tired of this.

Oh my, I think I see the problem–silly me.

While preparing and testing the potential POS, I forgot one foundational premise: POS implies in-person contact.

In my testing of the POS, I was trying to inject a delivery/pickup process. Silly me, POS is pickup of product!

In my forgetfulness of the foundational premise of a POS, I deleted the app I was working with and tried another. However, the replacement didn’t have the feature set of the initial app. So, now its delete the replacement and go back to the original–silly me.

Just had a long chat with Chatgpt to assess what plugin combinations will work best for what I’m trying to do (which is simultaneously offer on-line ordering with in-person POS). As it turn out, not so simple a task.

Customers who have visited us know that we offer flavors with our citrus squeezin’s. Our software product package does not natively provide options in its base line product. So, we have to add software patches to enhance the baseline software. The first option plugin I tried did not work with POS software recommended, so I backed up to a less robust app to get options to show up in the shopping cart. Oh well, too bad, so sad.

The central distractor is that both the less robust option app and the POS are subscription products. That makes it a bummer when I’m simply trying to prototype and troubleshoot apps.