Don't Wait for 27A: A Practical Guide to Oracle Redwood Adoption

An Expert Guide to Oracle Redwood Adoption in Procurement & SCM

Oracle’s transition to the Redwood user experience is accelerating across Fusion Cloud Procurement and Supply Chain Management (SCM). What was once considered an optional modernization initiative is rapidly becoming a strategic and operational necessity for customers running Oracle Fusion applications.

For Procurement and SCM organizations, the question is no longer if Redwood adoption will happen — it is when and how prepared your organization will be when Oracle deadlines arrive.

Organizations that proactively plan their Redwood roadmap now will have significantly more flexibility, reduced operational risk, and greater opportunity to maximize the value of Oracle Cloud innovation.

This blog outlines:

• Oracle Redwood transition timelines by module
• Oracle’s latest guidance and recommendations
• The business impact of delaying Redwood adoption
• Risks of remaining on Classic UI
• An example phased transition roadmap
• How our consulting firm helps customers successfully transition to Redwood

Oracle’s Redwood Recommendation: Begin Planning Now

Oracle has recently reinforced its strategic direction for Redwood adoption across Fusion SCM applications.

In Oracle’s recent SCM Redwood Adoption timeline communications, they recommended that customers build their adoption roadmap and deploy what they can with a target of 100% Redwood adoption prior to 27A.

27A will be “General Availability" as of January 2027. It will be delivered to existing customers through their 27A Updates starting in Feb 27 (cohort A), Mar 27 (cohort B) and Apr 27 (cohort C)

More importantly, Oracle advised that customers with in-flight implementations and planned go-live dates on or after March 2026 should pivot toward a 100% Redwood deployment strategy, unless exceptions are advised by Oracle COE (Center of Excellence).

For example, organizations with Supplier Portal deployments targeting go-live in July 2026 should strongly evaluate transitioning directly into Redwood experiences instead of continuing investments in Classic UI configurations.

This is a significant signal from Oracle: Redwood is no longer considered a future-state enhancement — it is becoming the expected deployment standard.

Understanding Oracle Redwood Basics

Oracle Redwood is Oracle’s next-generation UX framework designed to modernize Oracle Cloud applications through:

• Consumer-grade user experiences
• Simplified workflows
• Mobile-responsive design
• Embedded AI and automation
• Consistent navigation across Oracle Cloud applications
• Improved productivity and usability

Redwood is also the strategic foundation for Oracle’s future AI-powered experiences and intelligent automation capabilities across Procurement and SCM.

Additionally, Oracle continues to expand Redwood functionality with every quarterly release.

Oracle Redwood Transition Timeline by Module

Oracle is progressively enabling Redwood experiences by module, page, and feature through quarterly cloud updates. The official Oracle SCM Redwood roadmap is a great reference point for continuous updates, what’s changing, and when these changes are taking place.

Oracle stated on their Cloud Customer Connect (CCC) that all roadmap SCM Redwood features are planned to be available by 26D. A few examples that are complete are Inventory and Costing. SCM Redwood roadmaps are posted on the CCC and list key features by release and in progress of migrating to Redwood. Redwood roadmaps are organized by module and can be found on each of the product Redwood pages in SCM Resources. Fusion SCM products will have to be migrated to Redwood prior to 27A.

According to Oracle’s official guidelines published on Oracle Cloud Customer Connect in April 2026, until Redwood becomes mandatory for all SCM modules, parallel usage of both the Classic and Redwood applications can be utilized, and users will be supported through 26A for SCM, with limited module exceptions extending to 26D. This approach allows customers to gradually adopt and transition to Redwood.

Redwood Adoption by 27A Classic and Redwood Co-existence Deadline by SCM Product/Module

Oracle’s “100% Redwood Prior to 27A” Guidance

Oracle’s recommendation to target full Redwood adoption prior to 27A has major implications for Procurement and SCM customers.

This means organizations should:

• Avoid building new Classic UI customizations
• Align current implementations to Redwood experiences
• Incorporate Redwood into ongoing project roadmaps
• Budget for testing, training, and adoption activities now
• Transition incrementally before mandatory timelines accelerate

Organizations continuing large-scale Classic UI deployments today may face:

• Rework costs
• Duplicate testing efforts
• User retraining challenges
• Accelerated migration timelines later

For customers already in-flight with implementation projects, Oracle’s recommendation effectively changes the deployment strategy conversation from “Should we adopt Redwood later?” to “How quickly can we align our implementation roadmap to Redwood now?”

What Happens If Oracle Users Continue with Classic UI?

Some organizations may delay Redwood adoption because portions of Classic UI still remain accessible today.

However, remaining on Classic UI introduces increasing operational and strategic risks, including reduced Oracle investment in the Classic UI experience.

Oracle’s future innovation investments are centered around Redwood, including:

• AI capabilities
• Intelligent automation
• Embedded analytics
• Modernized workflows
• Improved mobile usability

Classic UI environments may gradually lose access to future innovation benefits and face increased risk of compressed migration timelines

Organizations delaying Redwood planning may eventually face:

• Shortened deployment windows
• Resource constraints
• Higher testing workloads
• Increased user disruption

The longer organizations wait, the more complex migration efforts become, and the greater the user adoption challenges. Starting 27A, for SCM, Classic applications will no longer receive fixes or enhancements in maintenance packs or release updates.

Why Users Should Start Their Oracle Redwood Roadmap Now

Oracle Redwood introduces new navigation patterns, updated transaction experiences, enhanced workflows, and new extensibility approaches using Visual Builder Studio (VBS). Without structured adoption planning, organizations may face increased user resistance, temporary productivity declines, and significantly higher support demands.

Organizations that begin early gain advantages:

• Controlled rollout strategies
• Better alignment with Oracle quarterly releases
• Reduced operational disruption
• Improved budget forecasting
• Better change management outcomes
• More time for testing and optimization

Most importantly, early adopters can maximize the business value Redwood provides instead of treating it as a reactive compliance exercise.

Real World Application: Oracle Redwood Transition Timeline

Below is an example of what a phased Redwood transition roadmap could look like and how it aligns with Oracle's recommendation to achieve full adoption before 27A.

Phase 1 — Readiness Assessment (Month 1–2)

Activities:

• Current-state assessment
• Module inventory
• Customization review
• Integration analysis
• Security assessment
• Oracle release alignment review

Deliverables:

• Redwood readiness report
• Risk assessment
• Prioritized transition recommendations

Phase 2 — Strategic Roadmap Planning (Month 2–3)

Activities:

• Define phased rollout strategy
• Align implementation timeline with Oracle releases
• Establish governance and change management plans
• Prioritize high-impact modules

Deliverables:

• Enterprise Redwood roadmap
• Budget and resource plan
• Release governance structure

Phase 3 — Pilot Redwood Deployment (Month 3–5)

Activities:

• Redwood enablement
• Functional configuration
• Regression testing
• UAT
• Training preparation

Deliverables:

• Pilot deployment validation
• User feedback analysis
• Production readiness assessment

Phase 4 — Enterprise Rollout (Month 5–6)

Activities:

• Module-by-module deployment
• User training
• Environment migration
• Integration validation
• Hypercare preparation

Deliverables:

• Production deployment
• Stabilization support
• Adoption metrics

Phase 5 — Post Go-Live Optimization (Month 6–8)

Activities:

• Ongoing support
• Quarterly Oracle update alignment
• AI feature enablement
• Continuous process optimization

Deliverables:

• Stabilized production environment
• Long-term support model
• Continuous improvement roadmap

How Elire Helps Customers Successfully Transition to Oracle Redwood

Redwood transitions are not simply technical upgrades — they are enterprise transformation initiatives.

Our consulting team helps Oracle Fusion Cloud Procurement and SCM customers strategically navigate Redwood adoption while minimizing disruption and accelerating business value.

We provide end-to-end Redwood transition support including:

1. Redwood Readiness Assessments

We evaluate:

• Current Oracle landscape
• Existing Classic UI dependencies
• Integrations and customizations
• Security and business process impacts
• Module-specific readiness

2. Strategic Redwood Roadmaps

We help organizations:

• Prioritize modules
• Align with Oracle quarterly release schedules
• Build phased transition plans
• Reduce deployment risk

3. Implementation & Configuration Support

Our experts support:

• Redwood enablement
• Functional configuration
• Process redesign
• Visual Builder Studio alignment
• Security validation

4. Comprehensive Testing Services

We ensure stable deployments through:

• Functional testing
• Regression testing
• Integration testing
• UAT coordination
• Production readiness validation

5. Change Management & User Adoption

Successful transitions require strong adoption strategies.

We support:

• Training
• Communication planning
• Stakeholder engagement
• Hypercare support
• End-user enablement

6. Managed Support Post Deployment

Our post-go-live services help customers:

• Stabilize production environments
• Support Oracle quarterly updates
• Optimize Redwood experiences
• Continuously improve operations

What’s Next?

Oracle’s guidance to achieve full Redwood adoption before 27A makes one thing clear: organizations should begin planning now. With customer updates starting in early 2027, Procurement and SCM teams have a limited window to assess their current environment, align active projects to Redwood, and execute a phased transition strategy.

Recommended Next Actions:

• Now: Conduct a Redwood readiness assessment and identify Classic UI dependencies
• Next 60–90 Days: Develop a transition roadmap aligned to Oracle release timelines
• Throughout 2026: Execute phased deployments, testing, training, and change management activities
• Before 27A: Complete adoption and stabilization efforts to avoid compressed timelines and unnecessary risk

Organizations that act early will be better positioned to minimize disruption, maximize Oracle Cloud innovation, and achieve a smoother transition to Redwood. Elire can help guide your Redwood journey from assessment and planning through deployment and ongoing support.

Connect with our experts to discuss what Oracle Redwood adoption could look like for your organization. Explore our Oracle Fusion Cloud Services to learn how Elire supports initiatives across the enterprise. Check out Elire’s Oracle Redwood UI demos on YouTube and subscribe to our monthly Cloud Newsletter to stay up to date on the latest Oracle Fusion Cloud updates, insights, and best practices.