What is Oracle Redwood?

Key Technical Pillars of Oracle Redwood

• Oracle JavaScript Extension Toolkit (JET): The core framework of reusable web components that ensures consistency, scalability, and high performance across all Fusion Cloud modules.
• Oracle Visual Builder Studio (VBS): The mandatory development environment for all Redwood extensions, replacing the legacy “Page Composer” for custom UI modifications.
• Oracle Search (Elasticsearch): A high-speed, “suggestive” search backbone that delivers contextual results as users type, significantly reducing navigation time.
• Single-Page Application (SPA) Logic: Utilizes sliding side panels and “guided” task flows to keep users in their current context without reloading entire pages.
• Accessibility by Default: Built from the ground up to natively meet WCAG 2.1 Level AA standards, eliminating the need for custom accessibility patches.
• Mobile-First & Responsive: Engineered as a “one-codebase” solution that adapts fluidly across desktops, tablets, and mobile devices without loss of functionality.
• Role-Based Personalization: Intelligently surfaces only the tools and data a specific user role (e.g., HR Manager vs. Finance Director) needs to see, reducing cognitive load.

What is Redwood UI in HCM?

Oracle Fusion HCM is being progressively redesigned using the Redwood design system to modernize the employee and manager experience. It transforms traditionally complex HR workflows into clean, intuitive, and role-specific interfaces.

Key Areas & Core UX Changes

• My Team & Manager Self-Service: A card-based “My Team” dashboard surfaces direct reports, pending actions, and key tasks in a single view.
• Employee Self-Service (ESS): Provides a consumer-app experience for managing benefits, personal info, and pay details from a single landing page.
• Oracle Journeys: Powers guided, step-by-step workflows for onboarding, offboarding, or role changes with personalized context.
• Simplified Forms: Multi-step transactions (hiring, promotions) are broken into guided, single-topic pages to reduce input errors.

What is Redwood UI in SCM?

As of 2026, Oracle Supply Chain Management (SCM) has moved into its mandatory Redwood transition phase. The focus is on increasing visibility across the “Digital Thread” and accelerating warehouse and procurement velocity.

Key SCM Modules Redesigned

• Redwood Procurement & Self-Service Receiving: Modernizes the requisition and receiving process with a streamlined, “Amazon-like” shopping experience.
• Inventory Management: Replaces dense tables with visual stock-level indicators and intuitive “quick-action” panels for stock transfers and cycle counting.
• Logistics & Transportation Management: Global Trade Management (GTM) and OTM dashboards now use Redwood’s map-integrated layouts for real-time shipment tracking.
• Supply Chain Planning: Redwood provides a centralized “Planning Advisor” dashboard that uses AI to surface supply risks and suggest alternative sourcing.

Oracle Redwood Migration Timeline

Oracle announced the transition to Redwood UI at Oracle OpenWorld in September 2019, with the overall goal to migrate all Oracle Cloud Applications to Redwood UX by 2026. The rollout follows a phased, module-by-module approach across quarterly releases.

Phase 1 – 2024 (Early Adoption)

EPM – Completed July 2024 from the July 24.07 patch, all non-Redwood themes were removed from Oracle Cloud EPM environments, and they were automatically updated to the Redwood Experience. This covers Account Reconciliation, Planning, Financial Consolidation and Close, and Tax Reporting.

HCM & New Implementations In 2024 Q3–Q4, early adoption began for HCM and EPM modules, and new Oracle Cloud implementations defaulted to Redwood UX.

Phase 2 – 2025 (Mandatory Rollouts)

HCM – Release 25B & 25C By Release 25B (April 2025), all Employee Self-Service (ESS) and Manager Self-Service (MSS) pages moved to Redwood. The Redwood migration deadline for HCM was then updated to 25C, covering all HCM pages – including those used by employees, managers, and HR professionals within Recruiting, Global HR, Talent, Absence, Benefits, and Payroll.

Procurement & SCM – Early to Mid 2025 Procurement and SCM transitions began in 2025 Q1–Q3, covering Releases 25A through 25C.

Phase 3 – 2025 Q4 to 2026 (Mandatory for Remaining Modules)

ERP, SCM, and CX The mandatory rollout for ERP, SCM, and CX modules is set for 2025 Q4 through 2026 Q2, with the target for complete Redwood coverage across all Fusion Cloud applications by end of 2026.

SCM Final Deadline Oracle Supply Chain Management (SCM) has a mandatory Redwood deadline of 26D (Q4 2026), with full adoption expected across Cloud HCM, SSP, and SCM by end of 2026.

CX / Sales & Service Oracle has announced a mandatory transition from Classic UI to Redwood for Fusion Sales and Service, with the End of Life (EOL) date set for the 27A update.

Key Risks of Delaying Migration

1. Access Loss: Users will lose access to primary interfaces once EOL dates pass.
2. Customization Breakage: Legacy Page Composer customizations will not carry forward; they must be rebuilt in Visual Builder Studio.
3. Feature Lockout: All new Oracle AI and “Automated Agent” features are developed exclusively for Redwood.

What Organizations Should Do Now

To navigate these mandatory deadlines, organizations should partner with a specialized Oracle expert to audit legacy customizations. This collaboration ensures that Page Composer, Visual Builder, and theme overrides are accurately identified and transitioned to the Redwood standard.

By working with a proven implementation partner, businesses can effectively test quarterly updates in a sandbox environment and develop a readiness roadmap that prioritizes modules by business impact, ensuring no loss of access as Classic UI reaches End of Life.