RA Case Study: Solving Unproductive Inventory Challenge with Dynamic Markdown Pricing

RA Case Study: Solving Unproductive Inventory Challenge with Dynamic Markdown Pricing

Revology Analytics Case Study series in Outcome-Based Analytics?


Problem

A leading $5B consumer durables wholesaler in North America wanted to unlock significant liquidity tied up in unproductive inventory by deploying in-house markdown optimization capabilities.

The Company had significant warehouse space and cash tied up in discontinued or inactive inventory, representing ~ 15% of on-hand quantities at any given point. It bought up too much stock: the Company would jump on the inventory purchase when manufacturers gave out pricing deals for bulk buys. They often bought 5-20x more than they could sell in a calendar year.

The Company didn’t have a good process or underlying analytical method to price the unproductive inventory created by aggressive buying habits. The existing pricing system was unsuitable (Oracle-based) for a clearance price management platform. To upgrade or customize it would have cost the Company $1MM+ and over a year to deploy.

To fix this massive unproductive inventory problem, the Company wanted to implement a robust and automated pricing markdown capability that balanced the need for incremental cash while minimizing price investments. They also wanted to take into account inventory rebalancing opportunities across the network.


What exactly is “unproductive” inventory?

No alt text provided for this image


Pains

Four key pain points resulted from this Problem:

  1. The Company was forecasted to have an EBITDA shortfall due to ~ $150 million tied up in unproductive inventory.
  2. The Company could not borrow money from banks against inventory deemed obsolete or dormant. It not only hurt holding costs and liquidity position but prevented the Company from maximizing its short-term borrowing base, which is essential for wholesalers.
  3. The lack of clearance pricing processes and guidelines caused friction between the Company’s Customer Development Managers (CDMs) and their customers. It gave the impression to the marketplace that the Company didn’t have its act together on clearance pricing or price markdowns.
  4. Some Distribution Centers were running into warehouse space issues due to unproductive inventory. They were also incurring wasteful labor costs as warehouse associates needed to constantly move the unproductive inventory from the front to the back of the warehouse.

?

Obstacles

The Company historically tried to deplete unproductive inventory through manual, bulk price discounting efforts based on intuition and corporate lore, creating two painful situations.

  • Pricing too low: $ millions left on the table in missed Gross Profit $.
  • Pricing too high: Inactive products piling up in warehouses.

No alt text provided for this image

While great at foundational Margin Analytics and Pricing Execution, the existing Pricing team did not have the data science skills to build a dynamic price markdown solution.

Pricing solutions of leading vendors were not flexible enough to build an effective markdown capability or were too costly with lengthy implementation times.

?

Why Revology Analytics?

The Company needed a partner to architect the Clearance Strategy, the technical solution to the Problem, and map out the process end-to-end.

More importantly, they needed someone with deep functional and domain expertise to implement an 80-90% total value realization solution from start to finish in under four months.

The Company chose Revology Analytics given our Revenue Management and Data Science expertise, combined with our ability to interact with the C-suite and frontline employees in Sales and Operations.

While other firms had turnkey solutions emphasizing Machine Learning and AI, Revology focused on delivering a pragmatic solution that drove business outcomes. We used technologies that the Company was already familiar with:


Popular tech stack used to build and deploy the Dynamic Clearance Pricing solution.

No alt text provided for this image


Process

Our engagement process lasted four months and comprised of the below crucial steps:

Sample Markdown Optimization project timeline (click the image to view details).

No alt text provided for this image

I.?????Understand (Week 1)

In the first few days, we spent time understanding the Problem and quantifying the opportunity of solving it (i.e., what is the ‘Size of the Prize’ for the organization).

We aligned with the project’s Executive Sponsor and formulated a working core team comprised of Sales, Supply Chain, and Finance team members.

The following questions guided us in the initial few days of engagement:

  1. Why does the Problem exist – what are the root causes?
  2. Who do we need to meet, and how often?
  3. Who should be in our Core project team vs. part of our Executive sponsors?
  4. What is the list of business outcomes we wanted to achieve?

?

II. ???Decompose (Weeks 1-2)

As a next step, together with the Core Team, we split the Problem into the below sub-components and tied them to the outcomes we wanted to achieve. We identified the critical data elements needed for each sub-component, including what data was easily accessible vs. what data we needed to extract from other sources.

Drive additional Cash and Gross Profit $ by fixing the pains (manual, gut-based clearance pricing):

  • Build a semi-automated, dynamic Clearance Pricing solution incorporating a Pricing Manager review step. The dynamic piece should include differing discount curves by product group while paying attention to competitive prices, inventory days on hand levels, cumulative price investments, and accounting reserve considerations.
  • Develop an accompanying Clearance Pricing Guideline for the Sales Organization. It should include additional bulk purchase discounts to help offload the most problematic inventory to willing customers.

Prevent significant unproductive inventory pile-ups in the future by fixing the root cause (excessive purchasing):

  • Build an add-on solution, a Special Buy recommender tool that Category Managers can use during monthly flash sales (heavy quantity discounts) by Manufacturers. The tool should recommend optimal quantities based on sales history, anticipated demand, and other elements such as inventory carrying costs and price sensitivities. It would alleviate the gut-based purchases made in the past.

?

III. ??Align (Weeks 2-10)

We engaged in several iterative stakeholder alignment sessions and executive roadshows. These are critical to ensure that the analytics solution solves the Problem your stakeholders and customers care about. It will also drive maximum adoption and results by bringing critical people along the journey, creating a sense of shared ownership.

Our alignment sessions followed the below timeline:

  1. Weeks 2-3: Stakeholder?Alignment – Met with critical stakeholders (core working team and executive sponsors) across Pricing, Sales, Supply Chain, IT, and Finance to align on the Concept. It ensured that our Clearance Markdown Solution addressed the right questions and drove the proper outcomes. We also used these sessions to ensure that our solution aligned with the Company’s hub-and-spoke network, competitive pricing, and inventory accounting considerations.
  2. ?Weeks?3-4: Data & User Journey Design – Once we aligned on the Concept, we collaborated with the Core Team on the Solution Design, where we mapped out the data elements and created a high-level data architecture, outlined the markdown algorithm in plain English, and sketched out the rough user journey and UI for data visualization. We typically conduct both the Concept & Design sessions in Miro and devote 2-3 hours for each in a highly engaging, collaborative manner.
  3. Weeks 5-6: Design Endorsement – Once we’ve gathered the Concept & Design input from all relevant stakeholders, we did a final review with the core team and executive sponsors. It helped ensure complete alignment before the solution buildout started. In these sessions, we typically also discuss ways to drive and incentivize Analytics Solution adoption by frontline decision-makers (Pricing Analysts and Managers, Customer Development Managers, and Sales Directors).


IV.???Minimum Viable Analytics Solution (MVAS) (Weeks 7-16)

Weeks 7-10: MVAS buildout (and Pilot design) – For the Minimum Viable Analytics Solution (MVAS) phase, we did two iterative reviews and feedback sessions two weeks apart. Like the Concept & Design stages, we needed to drive full acceptance in the MVAS stage before piloting the solution and launching it nationally. For the MVAS, we delivered a semi-automated Markdown Price Optimization solution that was ~ 80-90% of full Production grade capability. The missing pieces mainly were automation and infrastructure-related).

Clearance prices were automatically calculated based on product category goals, inventory DOH thresholds, competitor prices, margin thresholds, and sellout thresholds. The MVAS Clearance Price Optimization components were simple, easy to understand, and co-created with Core team stakeholders:

  • We created a secure Excel file (aka. “Markdown Optimization Matrix”) in Sharepoint that housed key lookup tables for the Clearance Pricing algorithm. It included margin thresholds, discounting curves (discount levels and discount curve shape over N weeks), sellout quantity thresholds, inventory DOH goals, and others. This Excel file was only accessible by select people in the Revenue Management team.
  • The Clearance Pricing algorithm was written in R, ingesting the “Markdown Optimization Matrix” along with relevant raw data from existing Oracle and MS SQL Server data warehouses. The R script was housed on GCP and ran each Thursday night automatically via a Cron Job.
  • The clearance pricing algorithm ingested Optimal Clearance Prices into a Cloud SQL database. A separate process created an Excel sheet on Sharepoint (for crucial product categories only) to be reviewed by the Regional Pricing Managers each Friday morning.
  • The Regional Pricing Managers uploaded the reviewed Clearance Prices into the Oracle Pricing Engine. Clearance prices for smaller product categories (99% of the items but ~ 50% of the revenue) were automatically ingested into the Oracle Pricing engine with no manual intervention or review.


Weeks 11-16: In-Market Pilot – Once finished with the MVAS build, we conducted a 6-week A/B price test in four different markets. Each Market consisted of Test and Control Distribution Centers (DCs) with similar seasonality and sales patterns. Test DCs were those that received automated clearance prices, and control DCs were those that still relied on manual Clearance prices.

During the pilot, our Markdown Optimization algorithms ran each week automatically, with discounted price recommendations integrated into the central pricing engine in Oracle. We also incorporated a manual review option for each Pricing Manager as needed.

A 6-week pilot showed the Test DCs outperforming the Control DCs in Unproductive Inventory performance by ~ +40% in Gross Profit $ and ~ +70% in Sales $.


A sample workflow illustrating the Clearance Pricing process, driven by business goals, margin thresholds, and other considerations (e.g., discount curves, competitor prices, cross-price elasticities – not pictured here).

No alt text provided for this image

V.????Launch (Week 16+)

After our MVAS pilot, we convened the stakeholders for a post-mortem where we made another round of adjustments to the Markdown algorithm and added additional inventory categories to our scope.

We finalized the data flow with IT between the Pricing Engine in Oracle to our purpose-built Clearance Pricing data warehouse in Google Cloud SQL, and finally back to Oracle for Pricing Execution. As with most dynamic and automated Pricing solutions, a capable internal IT team can make all the difference to timelines and eventual outcomes.

We launched our Clearance Markdown Solution nationwide across 120 Distribution Centers after just four months of project commencement. To ensure value realization and sustainment, we deployed a Tableau Online dashboard for all key stakeholders where they could track progress and critical KPIs.

No alt text provided for this image

VI.???Assess

Ninety days after our national launch, we evaluated business outcomes and conducted another post-mortem with key Stakeholders.

We typically use this engagement phase to ensure that our Pricing or Sales Growth Analytics solution delivers on the initially outlined outcomes. Based on a 90-day post-mortem, we adjust the process or underlying algorithm as needed.


An accompanying Tableau performance dashboard tracked the impact of the Markdown Optimization solution weekly. We created different levels of analytical insights based on function and role (below is an Executive sponsor view).?

No alt text provided for this image


Provisions

Revology Analytics ensured that we seamlessly handed off the Markdown Optimization Solution to IT with the ability to maintain and improve over time. It created significant long-term savings for the Company by not having to spend on expensive vendor support.

As part of our final project deliverables, we shared a detailed Clearance Pricing architecture in Powerpoint that explained everything from Data Architecture to the underlying Clearance algorithm. It ensured that Company staff could go back and modify things very quickly. Additionally, we cross-trained an internal Data Scientist to become the Solution owner (updated underlying Price Elasticities once a quarter, re-wrote the parts of the Solution in Python, etc.).

We also created a transparent Clearance Pricing Guideline for the Commercial team to use and share with Customers if needed. This Pricing Guideline was updated weekly with new prices and explained clearly how various clearance discounts were set by Product and Customer category. It helped the Sales team tremendously since they could see how they could drive better outcomes through previously unproductive inventory. It enabled them to generate higher Sales and Gross Profits $ and ultimately increased bonuses.

?

Results

After four months, the Company had a systematic solution to manage the $150 million+ unproductive inventory problem with surgical Markdown Pricing.

The Clearance platform was dynamic and automated, paying attention to inventory levels, margin thresholds, discount time horizons, and competitive pricing. But it also incorporated a manual price review step for key item categories by the Pricing team and Category leaders to drive further accountability and a sense of solution ownership by frontline stakeholders.

Significant Reduction in Wasteful Manual Labor

Our Markdown Optimization Solution improved overall inventory liquidity by + 30% and Gross Profit $ by 5% annually. We saved 80+ hours of work each week for 6 Pricing Analysts and Managers as they no longer had to formulate Clearance prices using disparate data sources and Excel sheets. We also helped eliminate hundreds of hours spent on price negotiations with customers by a 200-member Sales team by giving them a turnkey Clearance Pricing Catalogue.

Improved Forecasting

The Markdown Optimization Solution also helped the Finance and Executive team as they could now provide more accurate and transparent forecasting of inventory and cash. It enabled better, more empirical conversations with the Board, generating valuable investor goodwill.


This article was originally published in Revology Analytics. Visit our Pricing & Promotions Excellence practice area to learn more, or contact us with any questions or comments.

Great case study Armin. Clearance/Markdown optimization can be a big unlock for many retailers. Especially in the current environment which could potentially be seeing a significant softness in demand. I think the challenge many of the companies/retailers face are the following 1) A broken incentive structure - Typically with an eye for near term profitability there is pressure to avoid selling products at deep discounts - hence hurting margins and leading to a glut of inventory 2) Over reliance of merchandise teams - Clearance/Markdown should be led by Pricing/Finance teams; not reporting to merchant teams. Inputs are fine, but over reliance on the merchant teams who usually are 'over' optimistic how their product would sell usually leads to bad decisions. 3) Controlling the controllable - Products tend to be bought so much in advance, changing consumer preferences, macro conditions etc. are difficult to forecast that ahead in time. This could lead into glut of inventory. unfortunately leadership teams have already guided the street etc. on what to expect financially leading to challenges in taking the right actions.

Rak-Joon Choi

Business Development | Strategy & Transformation | Asian-American Ally

2 年

Love the charts, very insightful!

要查看或添加评论,请登录

Armin Kakas的更多文章

社区洞察

其他会员也浏览了