A customer may see a different price display on a product card from the one shown later in the basket. That is not always an error: the selected variant, customer context or applicable settings may differ. The journey still needs to be understandable. Check price information as a whole, using predefined scenarios and a clear explanation for every change.
Record what you are comparing
Start with the same item, variant and quantity. Note whether the customer is logged in and which relevant context is known. Otherwise, comparing a product family’s price range with the price of one particular variant creates an apparent discrepancy. The WooCommerce documentation on variations confirms that variants can have their own prices.
Distinguish between the product price, discount and costs determined later. This article concerns the technical and substantive consistency of the display. The appropriate tax settings for the organisation must be established by the responsible specialist. Use those established settings as the basis for the check.
Work through the journey with recognisable data
In a fictional shop, a visitor sees a worktable available in several widths. The overview shows a price range. After selection, the price of the chosen width appears. That can be understandable when the product card clearly indicates that variants exist. A prominent low amount without context may create a different expectation.
Then check the basket and checkout. Are quantities, the variant and any discount recognisable? Is it clear why the total changes? Compare the trial order with the last confirmed summary. Use fictional test data and a suitable test environment when working through the complete ordering journey.
For online store design price context needs to be part of the content. A small label or explanatory sentence may be necessary to interpret the amount correctly. Do not remove that explanation merely to make a product card look quieter.
Investigate differences from their source
Record exactly where a difference first appears. Check whether it relates to another variant, an applied discount, a changed setting or an old page display. Do not change several settings at once; that makes it unclear which cause explains the difference.
If prices come from an external system, check which data is supplied and when. With a WooCommerce–AFAS integration this requires an explicit agreement about the source and processing. Correct transfer and an understandable shop presentation are separate checks that are both needed.
Do not use isolated screenshots without context in the check report. Record the item, selected variant and journey step for each amount. A colleague can then investigate the difference again later. An image of a price without those details often does not show whether the same situation is actually being compared.
Keep a small price-check matrix
Include a simple product, a product with variants and a relevant discount condition. Add only customer contexts the shop actually uses. Record the expected display for each scenario, including the words around the amount. This makes checks after updates or design changes more focused.
Then ask an employee to explain what a customer sees at each step. If that explanation becomes more complicated than the offering, the presentation may need to be simpler or more complete. The aim is not for every screen to show exactly the same amount, but for the same item choice to be processed correctly and every change to be substantively explainable. A customer needs enough information to reach the final order summary and recognise what is actually being ordered.