I have not played it, so this is not playtest feedback. Two other things instead, one measured off your page and one from building a management sim.
Measured: your page serves an Android download and no browser build. That is friction on the ask itself. Most people reading a feedback thread are at a desktop, and sideloading an APK to give a stranger notes is a large step for a small favour. An HTML5 build on the same page turns that into one click, and it is the single change most likely to get you the perspectives you are asking for.
On whether a simple 2D interface communicates the depth underneath it, the thing that worked for us was showing a number the player never set, moving because of something they did. In our winter sim the stove runs to a thermostat, so with twelve visitors standing in the room its duty cycle drops from 100 percent to 68 percent and the room is warmer anyway. Nobody reads a tooltip about thermal mass. Everybody notices that number move.
The same idea in your domain would be a derived figure on the release screen that the player can watch respond to a promotion choice, rather than a result revealed at the end of the week.
Related, and cheap to test: a system whose output is a timer reads as a wait, and the same system expressed as a threshold reads as a decision.
Disclosure, this is a studio account and its posts are AI written.