We’ve set up new customer groups in Oracle Fusion Cloud 22D for regional pricing, but pricing rules aren’t applying as expected. The pricing rule assignment seems correct in the setup, but orders from the new groups default to standard pricing instead of the designated discount tiers.
I’ve verified the customer group mapping in the pricing module, and all customers are properly assigned. The rule precedence appears logical - regional rules should override standard pricing. However, when I test orders, the system ignores the regional pricing rules entirely.
This is causing revenue accuracy issues as we’re not applying agreed-upon discounts. Has anyone encountered similar problems with pricing rule assignment for new customer groups? Any insights on what might be causing the rule precedence to fail?
The segment qualifier issue is likely your problem. In Setup and Maintenance, search for ‘Manage Customer Group Segment Qualifiers’ and note the exact qualifier code used for your new groups. Then in your pricing rules, edit the rule conditions and ensure the customer group condition is filtering on that exact qualifier code. There’s also a known issue in 22D where newly created qualifiers don’t immediately sync to the pricing engine cache - you may need to run the ‘Refresh Pricing Setup’ scheduled process to force synchronization.
I’ve seen this before. Check if your pricing rules have effective dates set properly. Also verify that the customer group assignment is at the account level, not just the contact level. The system might be looking at the wrong hierarchy level for rule matching.
Check your pricing strategy sequence. In 22D, if you have multiple pricing strategies active, the system evaluates them in order. Your new customer group rules might be getting evaluated but then overridden by a subsequent strategy with higher precedence. Navigate to Pricing Administration > Manage Pricing Strategies and review the sequence numbers. Lower sequence numbers execute first, but the last matching rule wins unless you have ‘Stop Further Processing’ enabled.
Based on your description, this is a classic pricing rule assignment and precedence configuration issue. Let me walk through the complete resolution:
1. Customer Group Mapping Verification:
First, confirm your segment qualifier alignment. Navigate to Setup and Maintenance > search ‘Manage Customer Group Segment Qualifiers’. Document the exact Qualifier Code used for your regional groups (e.g., ‘REGIONAL_DISCOUNT_TIER’). This must match exactly in your pricing rules.
2. Pricing Rule Assignment Check:
Go to Pricing Administration > Manage Pricing Rules > Select your regional pricing rule. In the ‘Applies To’ section, verify:
Customer Group condition uses the exact qualifier code from step 1
The group values match your newly created groups
Effective dates span your testing period
Rule status is ‘Active’
3. Rule Precedence Configuration:
The key issue is likely in your pricing strategy sequence. Go to Pricing Administration > Manage Pricing Strategies:
Note the sequence number of your standard pricing strategy
Your regional pricing strategy must have a HIGHER sequence number (evaluates later)
Enable ‘Stop Further Processing’ on your regional pricing rules to prevent standard pricing from overriding
If ‘Stop Further Processing’ isn’t visible, you need to enable it in the pricing rule itself under the ‘Actions’ section
4. Cache Refresh (Critical for 22D):
Run these scheduled processes in order:
Refresh Pricing Setup
Refresh Pricing Segment Data
In 22D, there’s a known delay in pricing engine cache updates for new segment qualifiers. This refresh is mandatory.
5. Testing Protocol:
After the refresh completes:
Create a new test order (don’t reuse existing orders)
Use ‘Simulate Pricing’ feature to see which rules are being evaluated
Check the pricing details log to confirm your regional rule is matching
The root cause is typically either incorrect segment qualifier mapping or missing the ‘Stop Further Processing’ flag, combined with the cache synchronization delay in 22D. After implementing these changes and running the refresh processes, your regional pricing should apply correctly and resolve the revenue accuracy issues.