How to approach it
Inspect default and alternate variants and compare rendered price, currency, SKU and availability to visible content and the feed. Sample sale and sold-out cases. Test after theme or app releases.
Start with the exact variant URL and check the ground truth on the page. Verify the SKU and availability again after selecting another variant, then inspect any structured data emitted by both theme and apps. Compare sale prices and currency separately from shipping or tax information where those details are represented.
Worked example
On an Australian store, check that a displayed AUD price also uses AUD in the relevant offer markup and that selecting a sold-out alternate does not show incorrect availability.
How to verify the change
Use a small recurring sample of edge cases, including a sale ending and a pre-order changing to in-stock. Record the rendered price and source of each markup block before editing. Take care when fixing a theme conflict to avoid removing the only valid offer entity on other product templates.
When price changes on a sale schedule, test both sides of the transition. If the feed updates overnight and the store updates immediately, document the expected lag and check that it clears before treating it as a theme defect.