Thanks for sharing this use case with us about the coupons and large volume requirements.
We’ve been working hard to optimize the POS around large stores with thousands of Products and Customers, we are still working to optimize the POS around coupons when a few thousands are available. This is a large amount of coupon data. ??
The error 500 is related to the server response. We suspect as the POS is calling the coupon data, since it’s so large the server is timing out the request causing this behavior. We have plans in our roadmap to optimize the coupon data when hundreds are being used by businesses. Now that we understand a use case where thousands of coupons are being added. Our development and QA team will work to create benchmarks to improve the performance and optimization of data loading.
Before the new performance and optimizations are ready in the POS for large volume coupon date. Right now, our best recommendation would be to make sure you are running a high performance server environment and using good hosting provider, this should hopefully reduce the 500 error on timing out the server for the coupons request.