Skip Headers
Oracle® Retail Category Management Implementation Guide
Release 14.1
E55388-01
  Go To Table Of Contents
Contents

Previous
Previous
 
Next
Next
 

1 Introduction

Effective category management (also referred to as merchandising) is the cornerstone of a successful retail business because it determines the variety and presentation of merchandise. This determination defines the customer's in-store experience. Category management involves managing individual product or merchandise categories as though they were independent business units, each playing a specific role in the retailer's goal to achieve their established business objectives. Broadly, this practice facilitates the determination of the following:

In recent years, retailers have experienced increased difficulty in achieving desired levels of same store sales growth, gross margin, and inventory productivity. This is partly due to smaller buying staffs, shorter product life cycles, increasingly savvy and demanding customers, and cutthroat competition.

In light of these issues, retailers are looking to service their customers better, drive profitable growth, and further differentiate themselves from the competition by tailoring their product offerings to the needs of their local customers. In the past, micro-merchandising or local market assortments were extremely complex, labor intensive, and yielded marginal results.

Oracle Retail Category Management (RCM) brings in the contemporary best-practices from the retail industry as part of its functionality. RCM is based on the RPAS platform. Key differentiating factors of RCM, that facilitate decision making in the category management business practice, include the following:

RCM consists of the following tasks:

The Category Planning task enables the retailer to perform higher-level category planning activities and Assortment Planning tasks that facilitate the creation of SKU/Item-level Assortment Plans at the cluster and store level.

This solution supports the development of category business plans and assortment plans. It broadly follows the traditional eight-step Category Management business process with the inclusion of the consumer dimension in a few steps to provide the following:

Consumer segmentation and store clustering can be utilized to tailor assortments to specific markets and consumer segments by providing a profile mix of who is shopping the store and trading area. Store clusters are typically created for each product category in a trading area based upon similarity in consumers, stores, product attributes, sales profiles, and demographics so that assortments can be generated at the store cluster level. Assortments can also be generated at the store level.

Visibility into category roles, strategies, tactics, and financial objectives ensure that SKU/Item level assortments align back to overall category-level objectives.

Contents of this Guide

This implementation guide addresses the following topics:

  • Implementation Considerations

  • Build Scripts

  • Data Flow

  • Script Integration

  • Configuration Considerations

  • Batch Processing

  • Internationalization

  • Data

Key Features of Category Management

Category Management is a disciplined process for retailers and their supplier partners to treat each category as a business unit with defined strategies and tactics, leveraging multiple data sources, consumer insights and segmentations, to improve the customer experience while delivering increased sales and profits.

Category Management provides the following features:

  • Packaged POV on leading edge retail business process concerning category management

  • Supports consumer-centric and customer-centric category planning and assortment processes

    • Leverages consumer decision trees

  • Embedded forecasting capabilities

    • Enables forward-looking insights to drive planning decisions

  • Guides category roles and strategies-driven pricing and promotion tactics

Skills Needed for Implementation

The implementer needs an understanding of the following applications and technical concepts.

Applications

The implementer should understand the interface requirements of the integrated applications and data sources for the master data, demand, and inventory history. For Category Management, the implementer needs this knowledge for the following applications:

  • Oracle Retail Predictive Application Server (RPAS)

  • Oracle Retail Advanced Science Engine (ORASE) (optional)

Technical Concepts

The implementer should understand the following technical concepts:

  • UNIX system administration, shell scripts, and job scheduling

  • Performance constraints based on the retailer's infrastructure

  • Technical architecture for Category Management

  • Retailer's hierarchical (SKU/store/day) data

  • Category Management batch processes

  • Setting up an RPAS domain

  • A basic understanding of RPAS configuration and how to use the RPAS Configuration Tools

  • Understanding of how RPAS rule language works

  • Understanding of measures and dimension constructs

  • Understanding of how Fusion Client works