Case Study: A Cosmetics Brand Automated Black Friday Pricing Across 12,000 SKUs

A cosmetics brand with 12,000 SKUs across skincare, makeup, fragrance, and haircare was approaching its third consecutive Black Friday campaign. The previous two years, the pricing team had manually applied discounts via bulk CSV uploads — applying them over a three-day window before the event and spending another two to three days reversing them afterward. The process was slow, error-prone, and tied up the entire pricing team during one of the highest-traffic weeks of the year. This year, they implemented automated product pricing rules with scheduled activation and deactivation.

The Challenge

The brand’s Black Friday strategy involved differentiated discount tiers by category. Not all 12,000 SKUs received the same discount — the commercial team had negotiated different promotional terms with suppliers by category, and some product lines had margin constraints that capped the maximum discount. The pricing structure for the campaign:

• Skincare: 25% discount across the full category, excluding products launched within the past 90 days.
• Makeup: 30% discount on core lines, 20% discount on premium lines, no discount on limited edition items.
• Fragrance: 15% discount only on items with stock above 50 units.
• Haircare: 20% discount on shampoos and conditioners, 25% on styling products, 10% on professional treatments.

This was not a flat “apply X% to everything” operation. It was a set of conditional product pricing rules that needed to be applied selectively based on category membership, product launch date, stock level, and product tier classification.

In the previous two years, the process had been:

1. Export the full catalog to CSV (approximately 2 hours).
2. Apply discount formulas in Excel per category tab (approximately 6 hours across two analysts).
3. QA check on a sample of products per category (approximately 3 hours).
4. Bulk import back into the ecommerce platform (approximately 2 hours, plus time to resolve import errors).
5. Spot-check live prices on the storefront (approximately 2 hours).

Total to apply: approximately 15 hours. Then, after Cyber Monday, a reversal process:

1. Re-import pre-promotion price lists (approximately 3 hours).
2. Verify that all prices had reverted correctly (approximately 2 hours).
3. Manually correct any products where the reversal had not processed correctly (approximately 2-4 hours depending on error count).

Total to reverse: approximately 7-9 hours.

Combined: 22-24 hours of pricing team time for a promotional event that ran for 4 days.

In 2024, the reversal process had a documented failure: 214 products in the fragrance category retained their 15% Black Friday discount for 11 days after the event because an import error during the reversal upload was not detected until a margin review the following week. The revenue impact of selling those 214 products at a 15% discount for 11 extra days was calculated at approximately €3,800 in lost margin.

[SCREENSHOT: MicroPIM pricing rule configuration for Black Friday campaign, showing four category-specific rules with their discount percentage, eligibility conditions, and scheduled activation/deactivation dates set to November 28 at 00:00 and December 2 at 00:01]

What They Tried First

After the 2024 reversal incident, the pricing manager explored several options before settling on MicroPIM.

The first was their ecommerce platform’s built-in promotion engine. The platform supported coupon codes and percentage discounts applied at checkout, but did not support automatic price reduction displayed on the product listing page. Their Black Friday strategy specifically required the discounted price to be visible on the product page — not hidden behind a coupon code — because analytics data from previous years showed that coupon-based pricing significantly reduced add-to-cart rates compared to visible price reductions.

The second option was a third-party Shopify app that managed sale prices with start and end dates. Testing revealed that the app worked well for simple flat-discount campaigns but could not handle the conditional rules the brand needed — specifically the stock threshold rule for fragrance and the product age exclusion for skincare. The app could not evaluate dynamic conditions at the time of rule application.

The third option considered was building a custom script to handle the price update logic via the platform API. The development estimate from their agency was €2,800 for a one-time script and €600 for a re-run procedure each year. The total over three years was competitive in cost terms, but the solution would be fragile: any significant platform API change could break the script, and the brand’s technical team was not resourced to maintain custom code.

The Solution

The brand configured MicroPIM’s pricing rules engine to handle the entire Black Friday campaign lifecycle: rule creation, scheduled activation, monitoring during the event, and automatic reversal.

Step 1: Building the Promotional Pricing Rules

The four category-level rule sets were configured in MicroPIM’s pricing rule editor. Each rule set specified:

• Target segment: The product set to which the rule applied, defined by category + any exclusion conditions.
• Discount formula: A percentage reduction applied to the base price.
• Floor price protection: A minimum price floor equal to cost + 8%, preventing any discount from pushing a product into margin loss territory regardless of what the percentage rule calculated.
• Scheduled window: Activation at November 28, 00:00 and deactivation at December 2, 00:01.

The skincare exclusion — no discount on products launched within the past 90 days — was implemented as a product attribute condition on the target segment filter. Any product with a launch date within 90 days of the rule evaluation date was excluded from the segment automatically. This required the product launch date to be populated in the MicroPIM catalog, which was already the case for all skincare SKUs.

The makeup category’s split between core lines, premium lines, and limited edition items was handled through product tier tags that were already applied in the catalog for a separate merchandising purpose. The pricing rule referenced those tags as segment filters rather than requiring any new data entry.

The fragrance stock threshold — only discount items with inventory above 50 units — required a live inventory feed. MicroPIM’s inventory integration with the warehouse management system provided current stock counts at the product level, which the rule engine evaluated at the time of rule application.

Step 2: Running the Pre-Campaign Validation

Two weeks before the campaign, the team ran a dry-run validation of all four rule sets. This produced a preview report showing:

• The number of products each rule would affect.
• The calculated sale price and discount percentage for a sample of 20 products per category.
• Any products that would be blocked by the floor price protection.
• Any products where required data (launch date, tier tag, or inventory count) was missing and would cause the product to be excluded from the rule.

The validation found 89 skincare products without a launch date populated — they had been imported from a legacy system before the launch date field was added to the catalog schema. These products would have been excluded from the discount application without the validation step, which would have resulted in them remaining at full price during Black Friday. The team populated the missing launch dates in a bulk edit session before the campaign.

The validation also found 34 products in fragrance where the stock level was exactly 50 units. Since the rule specified “above 50,” these products were correctly excluded. The commercial team reviewed the list and decided to lower the threshold to 45 units for this campaign, which was a 30-second change in the rule configuration.

[SCREENSHOT: Pre-campaign validation report in MicroPIM showing 4 rule sets evaluated against 12,000 SKUs, with summary counts per rule showing products included, excluded by condition, blocked by floor price, and flagged for missing data]

Step 3: Scheduled Activation and Monitoring

At November 28, 00:00, MicroPIM activated all four pricing rules simultaneously and pushed the updated prices to the connected storefront. The system processed all 12,000 SKUs — applying discounts where the rule conditions were met and leaving full-price products unchanged — in approximately 22 minutes. The pricing manager monitored the activation log in real time and confirmed that the expected number of products per category had received updated prices.

During the campaign, the pricing dashboard displayed live metrics: number of products at promotional price, any floor price triggers, and the discount distribution across categories. No manual intervention was required during the four-day campaign period.

Step 4: Automatic Reversal

At December 2, 00:01, MicroPIM deactivated the pricing rules and reverted all affected products to their pre-campaign base prices. The reversal processed in the same timeframe as the activation — approximately 22 minutes for 12,000 SKUs. A post-reversal audit report confirmed that 100% of discounted products had reverted correctly.

The Results

Measured outcomes from the 2025 Black Friday campaign implementation:

• Campaign pricing setup time: reduced from 15 hours to 2 hours. The 2-hour figure covers rule configuration, validation review, and approval for activation. The export-reformat-import cycle was eliminated entirely.
• Campaign reversal time: reduced from 7-9 hours to 0 hours of human effort. Reversal was automatic; the pricing manager reviewed the post-reversal audit report in approximately 15 minutes.
• Zero post-campaign pricing errors. The 2024 incident of 214 products retaining promotional pricing for 11 extra days did not recur.
• 89 products with missing launch dates identified and corrected before launch — data quality improvement that would not have surfaced without the pre-campaign validation step.
• Estimated margin recovery: €3,800 compared to 2024, by eliminating the reversal error. This figure alone is a meaningful multiple of the tool’s annual cost.
• Pricing team availability during Black Friday week increased significantly. In previous years, both pricing analysts were occupied with monitoring and correcting the manual process throughout the campaign. This year, both were available for other commercial work during the event period.

Key Takeaways

• Promotional product pricing rules that involve conditional logic — stock thresholds, product age exclusions, tier-based discounts — cannot be handled reliably by flat CSV bulk uploads. The complexity requires a rules engine that evaluates conditions at the product level.
• Pre-campaign validation is as important as the campaign itself. Running a dry-run two weeks out catches data quality gaps (missing launch dates, untagged products) before they affect the campaign, not during it.
• Scheduled activation and automatic reversal eliminate the most failure-prone steps in a promotional pricing workflow. The 2024 reversal error was not a human mistake — it was a predictable outcome of asking humans to execute a complex, time-pressured operation with no automated verification.
• Floor price protection should be a standard component of any automated pricing rule. The cost of a formula error that prices a product below margin is higher than the cost of the small number of products blocked from promotion by a floor rule.
• The operational benefit of freeing pricing team bandwidth during peak commercial periods — when staff time has the highest opportunity cost — is a real but often underquantified value of pricing automation.

Managing promotional pricing for a large catalog manually is a high-effort, high-risk process. The failure mode is not hypothetical — it happened, and it cost €3,800 in one incident. MicroPIM’s automated product pricing rules handle conditional logic, scheduled activation, automatic reversal, and pre-campaign validation in a single workflow. You can configure your first promotional rule at app.micropim.net/register.

Related Reading

• Bulk Edit 10,000 Products in Minutes
• Case Study: Supplement Brand Tiered Pricing
• Case Study: Auto Parts Dynamic Pricing

Frequently Asked Questions

Can the pricing rules engine handle different discount levels for different products within the same category?

Yes. Rule conditions can filter to product-level attributes — tier tags, launch date, stock count, supplier reference, or any custom attribute in the catalog. Within a single category, you can have multiple rules applying different discounts to different product segments, as long as the segment filters produce non-overlapping product sets. If a product matches more than one rule, a priority order setting determines which rule takes precedence.

What if we need to manually exclude a specific product from a promotional rule at the last minute?

Individual product exclusions can be added directly to a rule’s exclusion list at any time, including during an active campaign. The excluded product reverts to its base price within the next scheduled push cycle, which runs at configurable intervals (typically every 15 or 30 minutes).

Does the system support “was price / now price” display — showing both the original and the discounted price?

Yes. When a promotional pricing rule is active, MicroPIM stores both the base price and the promotional price as separate fields. Channel templates can map both fields to the appropriate “compare at” price field in Shopify, the “old price” field in WooCommerce, or the equivalent in other platforms. The visual presentation of the price comparison on the storefront depends on the platform’s theme implementation.

How does the stock threshold condition work if inventory changes during the campaign — can products be added to or removed from the promotion automatically?

The stock threshold condition is evaluated at the time the rule is applied, not continuously during the campaign. If a product’s stock drops below 50 units during the campaign after the rule has already been applied, the promotional price remains in place until the campaign ends. Real-time dynamic rule re-evaluation based on live inventory changes is a more complex configuration that can be set up using MicroPIM’s webhook triggers, but it is not the default behavior for scheduled promotional rules.