EvolutionX has many ways you can specify pricing for a particular product/customer - at some point you may see a price which you do not recognise and would like to find in the system & rectify. - Not to worry! These below checks will sort you out ๐
**Please Note - if you use Live Pricing from your back office ERP and can see the wrong price being returned on the storefront, you'll need to review the back office set up for this code and/or customer. As soon as you have Live Pricing switched on, EvoX is overwritten!**
Have you used the โPricing Checkโ tool?
The 'Pricing check' tool can be located at the top right of the screen within the 'Pricing' section (see below image). This tool allows you to search for a product on its own or against a customer to find out exactly where the system is generating the price. It includes the name of the pricing rule and even the pricing method being used! - this is a lifesaver ๐
Have you made sure the priority of your pricing rule trumps any others?
Another common reason your expected price isn't pulling through is due to the priority you have set against the Pricing rule. You'll want to make sure your prioritising the correct rule and this can be done by adjusting the 'Priority' number here within the rule๐ (see below image)
If pricing via Markup/Margin - have you made sure the product(s) have a cost price against them?
If you decide to price using our Markup/margin method, make sure you have your cost price(s) set up against the items you're targeting. You can do this via the product details page (see below image) or alternatively using our cost price import routine! - The system will use the cost value in place to calculate against the percentage you set.
Have you checked your pricing rules start/end dates?
Upon first creating a pricing rule you are required to add a start/end date - this can be a powerful tool, but it is important to keep yourself reminded on when these dates will expire. - As soon as the end date is met your rule will no longer be applied. - This is a common culprit, so always be sure to check this out within the pricing rule settings ๐ (see below image).