If a retailer has 1,000 stores, deciding to drop the price of a t-shirt by $1.00 shouldn't require creating 1,000 individual price change records. It is a data maintenance nightmare and a massive performance drag on the database.

Oracle Retail Price Management (RPM) and the modern Pricing Cloud Service resolve this using Price Zones. By clustering stores into pricing tiers, a single price change record can instantly update prices across hundreds of registers.

1. The Hierarchy of Zones#

Oracle RPM forces all pricing events (except extreme exceptions) to be executed at the Zone level, not the location level.

Zone Group

A Zone Group is the highest level of the architecture. Think of it as a "Pricing Strategy Framework". A retailer might have a "Fashion Zone Group" and a "Grocery Zone Group". Zone Groups are mapped to specific Merchandise Departments.

Zone

Within the "Fashion Zone Group", you define individual Zones. Every physical store is mapped to exactly one Zone within that Group.

• Zone 1 (Flagship): 5th Avenue, Beverly Hills.
• Zone 2 (Urban): Downtown Chicago, Downtown Seattle.
• Zone 3 (Suburban): Standard mall locations.

When a pricing analyst creates a Regular Price Change, they select "Zone 1" and input a price of $50.00. RPM automatically pushes that $50.00 price down to every store mapped to Zone 1.

2. Geographic vs. Tier-Based Zones#

There are two dominant philosophies when designing Zone Groups in RPM:

Geographic Zoning

Stores are grouped strictly by their physical location to combat local competition or manage logistics costs.

• Zone A: East Coast US
• Zone B: Midwest US
• Zone C: West Coast US (Higher freight costs = slightly higher retail prices).

Tier-Based (Volume/Demographic) Zoning

Stores are grouped by the demographics of their customer base or store volume, regardless of geography.

• Tier 1 (High Cost of Living): Manhattan, San Francisco, London. (Highest retail prices).
• Tier 2 (Standard): Average suburban stores across the country.
• Tier 3 (Outlet/Value): Stores in lower-income demographics. (Lowest retail prices).

3. Clearance vs. Regular Zones#

A store's competitive landscape for fresh, regular-price merchandise might be very different from its landscape for end-of-season clearance items.

Because of this, Oracle RPM allows you to maintain distinct zone structures:

• Regular Price Zone Groups: Used for base pricing and markups.
• Clearance Zone Groups: Used exclusively when items reach the end of their lifecycle.
• Promotion Zone Groups: Used for temporary promotional offers.

A store in Miami and a store in Minneapolis might share the exact same Regular Price Zone for winter coats in November. But in March, the Miami store will likely be placed in an aggressive Clearance Zone to dump the coats, while the Minneapolis store remains in a standard zone because winter is still active.

4. Core Tables Reference#

(Note: RPM operates on its own schema separate from RMS, though data is synchronized).

Zone Location Mapping (RPM_ZONE_LOCATION)

5. SQL Deep Dives#

Viewing a Store's Zone Assignments

To understand a store's pricing strategy, you must see which zones it belongs to across all groups.

SELECT 
    rzg.zone_group_id,
    rzg.zone_group_name,
    rzg.zone_group_type, -- 'R' (Regular), 'C' (Clearance), 'P' (Promotion)
    rz.zone_id,
    rz.zone_name,
    rzl.location
FROM rpm_zone_group rzg
JOIN rpm_zone rz ON rzg.zone_group_id = rz.zone_group_id
JOIN rpm_zone_location rzl ON rz.zone_id = rzl.zone_id
WHERE rzl.location = 200 -- Querying Store 200
ORDER BY rzg.zone_group_type, rzg.zone_group_name;

6. Official Oracle Resources#

For further reading, consult the official Oracle documentation:

• Oracle Retail Price Management (RPM) User Guide: Zone Structures
• Oracle Retail Pricing Cloud Service: Foundation Data