I appreciated the response, but respectfully disagree on this implementation.
Each shared cart is being stored in the wp_options table with autoload= yes.
Therefore, EVERY shared cart is being loaded for EVERY user on EVERY page load.
This seems a very memory intensive approach, and is a misuse of the wp_options table.
We will likely need to remove the plugin as it has a cumulative negative effect on resource usage across the site.
I did share the issue with your team over a lengthy period of back and forth in email. We were told that you would not refund, and that to get the functionality we needed we would have to purchase a pro version of another plugin, which is a non-starter for our client.
Can you answer publicly if you are refund policy changed?
