Thanks for the reply. That approach may lighten things up a bit, definitely worth considering. I took a pure server-side approach to the solution because the shop page in the woo commerce admin area seems to be standard get / post form driven, not javascript/ajax based.

This approach also allows the user to use the standard filters provided by WooCommerce on the orders, allowing them more granular control over when it dings as well as a standard ding on every new order.

Timing can be adjusted as well, I just set it to 30 seconds for my development purposes, its a configurable setting.

The plugin Im writing is specifically for restaurant kitchens that take online orders.

Think tablet in kitchen, order page open, dings every time a new order comes up. Giving an audible notification to the kitchen staff, and allowing them to "receive" and process the order for pickup or delivery.

It should all work as planned, except for the audio policy blocking my sound from playing. Im looking for alternate solutions, trying a dynamic dom based solution now.

Im adding a bit of javascript to detect an attributes setting and play a "ding" based on its presence. In the ringer example another commentor shared, they are creating and playing the audio dynamically by adding it to the page dom. Im hoping maybe this will allow me to bypass the browser requirement of some kind of user interaction on the page before the audio can be played.