How to Fix Duplicate Sales Markdowns

Ablestar Bulk Product Editor is able to schedule and run sales on promotional products, however the configuration rules are very specific. 

A simple scenario might be, lowering your prices by 10% at a scheduled start time, and then scheduling the end time to stop the sale. 

On occasion, users run into issues where items are marked down twice, unintentionally. We have a solution to help you avoid that situation.


Find a List of Scheduled Edits

Start here to find a full list of your scheduled edits. From the app dashboard, click the 'History' menu → Edits tab → Scheduled edits section:


The Problem:  Duplicate Markdowns on Prices

This could happen if two sales are scheduled back to back, on the total price field. In this scenario, we have two scheduled (conflicting) scheduled edits:

  1. Sale A: the scheduled edit runs correctly and decreases the total price by 10%. So a product with a price of $100 goes to $90
  2. Sale B: starts running (before the Sale A schedule ends) and decreases the same product set price by 15% of the NEW total price, which is $90. 

⛔ The new price was discounted to $76.50 instead of the intended $85 because it took 10% with the first schedule and an additional 15% the new total price as the second schedule 


The Solution: Avoid Duplicates

To configure scheduled sales without issue, ensure you are lowering prices as a percentage of the ‘Compare at price’ (instead of using a percentage on the total ‘Price’)

✅ Instead of updating total ‘Price’ by a percentage, you can decrease the promo price based on a percentage of the ‘Compare at price’

  1. Sale A: scheduled edit starts, and sets the price to 90% of the $100 ‘Compare at price’, so it modifies to $90
  2. Sale B: scheduled edit starts (before A ends), and calculates the price to 85% of the ‘Compare at price’ (which is still $100) so it gets set to $85

This configuration could allow you to run two separate promotions, without conflicts.

✅ Tips and Troubleshooting

(05.335)

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us