Enterprise software is no longer judged only by functionality. Today, users expect the same speed, clarity, and intuitiveness from business applications that they experience in consumer apps. In response to this shift, Oracle has been steadily rethinking how enterprise applications should feel and function. That effort is reflected in Redwood, Oracle’s modern user experience framework.
For organizations using Oracle Fusion Cloud Supply Chain Management (SCM), Redwood is more than a new interface. It represents a broader change in how supply chain users interact with applications, complete daily tasks, personalize workflows, and benefit from embedded AI. Oracle’s message is clear: supply chain applications should not only be powerful, but also easier to use, faster to navigate, and more aligned with the way people actually work.
In the latest Oracle session on SCM Redwood User Experience, Oracle explained what Redwood is, how it is being rolled out across supply chain products, how customers can prepare for the transition, and what tools are available to help with personalization and migration planning.
For businesses evaluating Oracle Cloud SCM, or for current customers planning their Redwood adoption journey, this update is especially important. It provides a clearer picture of Oracle’s user experience strategy and what organizations should do next.
This is also where NexInfo becomes valuable. As organizations move from classic Oracle experiences to Redwood-enabled workflows, they need help evaluating readiness, identifying impacted personalizations, planning phased adoption, and aligning Redwood capabilities to real supply chain processes. NexInfo supports that transition with a practical implementation and advisory approach.
What Is Redwood in Oracle?
Oracle describes Redwood as more than a visual redesign. It is a broader experience philosophy intended to improve every interaction customers have with Oracle, especially within Oracle Cloud applications.
The idea behind Redwood started with a simple observation: enterprise users are still people, and people naturally prefer applications that are intuitive, responsive, and pleasant to use. Consumer apps raised expectations across the board, and Oracle recognized that enterprise software should no longer accept poor usability as normal.
That shift led Oracle to define Redwood around a larger goal: creating software experiences that help users do their jobs better while feeling more natural and consistent.
In practical terms, Redwood affects:
- how pages are designed
- how workflows are simplified
- how users search and navigate
- how AI is surfaced in the moment of need
- how analytics and data visualizations are presented
- how customers extend Oracle applications using the same platform
Oracle also emphasized that Redwood is not the responsibility of one team alone. It is intended to be a company-wide commitment to better user experience across every customer touchpoint.
For SCM customers, this means Redwood is not just about modern screens. It is about improving the day-to-day experience of planners, buyers, maintenance technicians, manufacturing supervisors, inventory teams, and order management users.
The Three Core Pillars of Redwood
Oracle summarized Redwood around three foundational pillars. These are useful because they explain not only what Redwood looks like, but what Oracle wants it to achieve.
-
Consumer-Grade Plus
Oracle’s ambition is to make enterprise software experiences as good as—or better than—the best consumer applications people use every day.
This includes visual design, navigation, responsiveness, and interaction quality. But Oracle also frames this as more than aesthetics. The goal is to help users achieve business results more effectively, not simply to make the screen look cleaner.
In other words, Redwood is meant to improve both form and function.
-
Embedded AI
AI in Redwood is not treated as a separate feature bolted onto the side of the application. Oracle’s approach is to embed AI directly into workflows, so it appears where it is most useful.
That might include:
- summarizing work just completed
- helping users search more effectively
- answering policy or document-based questions
- recommending next actions
- surfacing conversational guidance inside tasks
This approach matters because it makes AI part of the business process rather than an isolated tool.
-
A Platform Customers Can Use Too
One of Oracle’s strongest differentiators is that the same Redwood platform used to build Oracle’s own applications is also made available to customers.
That means customers can:
- extend Oracle applications
- personalize experiences
- create adjacent applications
- use Redwood UI elements and services
- build through low-code tools such as VB Studio
This makes Redwood both a design system and an extensibility platform.
What Makes the Redwood Platform Different?
Oracle highlighted that Redwood is not only about interface components like buttons and layouts. It includes a full platform of services and capabilities that sit behind the experience.
Design System and UI Building Blocks
At the visual level, Redwood includes:
- typography
- color systems
- page templates
- atomic components such as text fields, date pickers, and buttons
- composite components such as address fields and currency converters
Oracle emphasized that these composite elements are not just visual components. They are also connected to services behind the scenes.
For example:
- an address field can support auto-completion and validation
- a currency component can support conversion logic automatically
This is an important distinction. Redwood is not just a design language; it is an operational framework for building connected user experiences.
Page Templates
Oracle also pointed to a library of page templates for common enterprise scenarios such as:
- search
- profile views
- foldout pages
- dashboards
- analytics-heavy views
This allows Oracle teams—and customers—to build experiences more quickly while preserving consistency.
Built-In Services
The Redwood platform also includes supporting services such as:
- search
- AI and conversational capabilities
- data visualization
- accessibility support
- telemetry
- business rules
- guided journeys
- low-code development tools
This combination is what allows Redwood to function as a broad application framework rather than just a UI refresh.
Why Redwood Matters for Oracle SCM
For Oracle SCM customers, Redwood matters because supply chain users operate in highly practical, time-sensitive environments. They are not just reviewing dashboards. They are processing work, responding to issues, managing inventory, entering orders, adjusting schedules, receiving goods, maintaining assets, and making decisions under pressure.
If those workflows are hard to navigate, require too many clicks, or make key information difficult to find, the business impact is real.
Oracle made it clear that Redwood is intended to improve how users complete supply chain tasks, not just how pages look. In many cases, Oracle teams have rethought workflows to better match real user needs and common supply chain challenges.
That is why Redwood should be viewed as a business usability initiative, not simply a modernization effort.
Where Redwood Already Exists in Oracle Fusion Cloud SCM
Oracle shared that by 24D, every SCM product has at least some Redwood presence. Some products are further along than others, but the transition is well underway across the suite.
Below are some of the areas Oracle highlighted.
Supply Chain Planning
Planning has made major progress in Redwood, including capabilities around:
- production scheduling
- production analysis
- buyer planning
- demand collaboration
Oracle emphasized the visual and analytical improvements in these areas, particularly where charts, bars, and scheduling views make planning more intuitive.
Order Management
Order Management has been heavily redesigned in Redwood. Oracle highlighted capabilities such as:
- unified search across orders and order lines
- keyword search and saved searches
- mass actions such as cancel, submit, or reprice
- streamlined order creation and revision
- inline entry with extensible flexfields
- easier access to additional order information
- extensibility through business rules and guided journeys
This is one of the most strategically important Redwood areas because order entry and order review are high-frequency activities.
Maintenance
Oracle pointed to strong Redwood work in Maintenance, including:
- smart operations
- mobile-first workbench design
- improved supervisor experience
These are especially important for field and operational users who need faster, more direct interactions.
Manufacturing
In Manufacturing, Oracle highlighted:
- smart operations for manufacturing
- mobile-first design
- redesigned operation workbenches
- improved production scheduling approaches
- updated supervisor workflows
- streamlined work definitions
This reflects Oracle’s effort to modernize both the shop floor and supervisory planning experience.
Inventory
Redwood in Inventory includes:
- mobile-first workflows
- cross-inventory support
- power chart-related support
- production recall management
- self-service receiving enhancements
This is particularly relevant in industries like healthcare, where speed, accuracy, and mobile usability matter significantly.
Product Lifecycle Management
PLM has adopted more Redwood-like patterns with:
- flexible BOM grid experiences
- improved structure visualization
- easier management of delete groups and related tasks
Oracle explicitly noted that these workflows are more streamlined than the older ADF experience.
Procurement
Oracle also highlighted Redwood work in Procurement, including:
- lifecycle improvements in requisitions
- support for special handling scenarios
- self-service supplier registration
Healthcare-Specific Use Cases
A notable part of the session focused on healthcare. Oracle described a commercial-grade shopping experience embedded in self-service procurement that helps healthcare organizations manage non-contract purchases while still maintaining standardized product data and improving buying analysis.
Sustainability: Oracle noted that Sustainability is a newer product built directly on Redwood.
Personalization and the Transition from ADF to Redwood: One of the most practical parts of the session was the explanation of the personalization helper tool. This matters because many Oracle customers have already made ADF personalizations in classic pages using Page Composer. As they move to Redwood, they need a way to understand what was personalized before and what should be recreated, changed, or dropped.
What the Personalization Helper Tool Does
The tool helps identify personalizations made on supported ADF pages. These can include changes such as:
- hiding or showing fields
- making fields required
- marking fields read-only
- adding dashboards or reports to pages
The tool reads an exported ADF customization file and produces output in:
- HTML
- Excel
These outputs allow customers to review the existing personalization inventory in a consumable format.
Why It Is Useful
This is useful because the transition from classic UI to Redwood often involves a shift from Page Composer to VB Studio / Express Mode-based personalization.
Before rebuilding or extending anything, customers need to know:
- what was personalized in ADF
- whether it is still needed
- whether Redwood already handles the need natively
- whether the personalization should be rebuilt in Redwood
The tool supports exactly that analysis.
Separate Tools by Product Family
Oracle clarified in the Q&A that the SCM personalization helper tool is separate from the HCM one. Both are available from the same central location, but they are not the same tool.
Example Use Case
- Oracle demonstrated how a personalization identified in the output report—for example, exposing certain requisition-related flags in an ADF page—could then be reviewed and implemented in the Redwood page through page properties or rules in VB Studio.
- This is an important message for customers: Redwood migration is not a blind rebuild. Oracle is trying to give organizations a methodical way to assess what matters before making changes.
Redwood Rollout Timing: What Oracle Shared
- Oracle also addressed one of the biggest customer questions: when Redwood becomes the default experience.
Redwood Is Being Introduced Alongside Classic UI
- Oracle said it is not removing existing functionality immediately. Instead, Redwood flows are being introduced alongside classic pages, and customers can navigate between them.
- That gives users time to adopt Redwood incrementally.
The “N Plus 2” Rule: Oracle explained a general rule for SCM: once a Redwood feature is introduced and fully covers the functionality of the classic UI, the classic page is expected to remain available for the release in which the Redwood functionality appears, plus two more releases.
After that, Oracle may turn off the classic UI in favor of Redwood, as long as Redwood provides full coverage.
This is important because it means customers need to monitor feature maturity and rollout timing product by product.
Profile Options Control Availability: Oracle said that Redwood availability is typically controlled through administrative profile options. Once enabled, the Redwood pages show up alongside classic experiences.
This supports incremental adoption and controlled testing.
Redwood Does Not Cost Extra: Oracle also made it clear that Redwood does not require an additional license. It is included in the cloud application license.
One Key Prerequisite: Oracle Search: Oracle noted that Oracle Search should be enabled as part of the transition, and customers should review Oracle’s support documentation for product-specific prerequisites and profile options.
Redwood and AI: How They Work Together
- One of the more interesting Q&A moments addressed how AI connects to Redwood.
- Oracle’s answer was that AI is not an afterthought. It is built into Redwood as part of the experience architecture.
That means AI may appear in supply chain scenarios such as:
- summarizing completed work
- making recommendations
- answering document-based questions
- helping with repair or maintenance guidance
- supporting conversational interactions
Oracle also explained that customers can bring their own documents into certain AI agent frameworks. For example, in a maintenance use case, a company could upload a machine repair manual and allow technicians to ask questions conversationally.
This shows that Redwood is both AI-enabled out of the box and extensible for customer-specific use cases.
How Organizations Should Approach Redwood Adoption
The Oracle session strongly suggests that Redwood adoption should be planned, not rushed.
A good approach typically includes:
- identifying which SCM products already have mature Redwood flows
- reviewing classic ADF personalizations using the helper tool
- deciding which personalizations are still needed
- enabling profile options selectively
- validating process coverage before broader rollout
- training business users in the new interaction model
- planning governance for extensions and personalization
This is not just a technical migration. It touches process design, user experience, administration, and business change management.
How NexInfo Helps Organizations Move to Redwood
For many organizations, Redwood raises practical questions:
- Which products are ready for business adoption now?
- Which classic personalizations need to be recreated?
- How should rollout be phased across functions?
- What profile options and prerequisites must be handled?
- How should business users be trained?
- Where does Redwood already solve a pain point without extra customization?
NexInfo helps customers answer those questions in a structured way.
That can include:
- Redwood readiness assessments
- SCM product-by-product adoption planning
- review of current ADF personalizations
- helper tool interpretation and redesign guidance
- VB Studio / Express Mode support
- process alignment workshops for planning, order management, procurement, manufacturing, and inventory
- phased rollout governance
- user enablement and training support
Because Redwood adoption affects both user experience and process execution, it works best when technical configuration is paired with business workflow understanding. That is where a supply chain-focused Oracle partner like NexInfo adds value.
Conclusion
Oracle’s Redwood strategy is a major shift in how enterprise supply chain applications are being designed and delivered. It reflects a broader move away from the idea that enterprise software must be functionally strong but difficult to use. Instead, Oracle is building toward a supply chain experience that is more intuitive, more visual, more mobile-friendly, and more deeply connected to AI. For Oracle Fusion Cloud SCM customers, Redwood is already real. Planning, order management, maintenance, manufacturing, inventory, procurement, PLM, healthcare-related workflows, and sustainability all now have some level of Redwood presence, and Oracle is continuing to expand that footprint.
The Redwood platform also matters because it is not only a new interface. It is an extensible foundation that includes search, AI, telemetry, business rules, guided journeys, accessibility, and low-code personalization. The practical challenge for customers is not whether Redwood matters. It is how to adopt it thoughtfully. That means understanding what is already available, what prerequisites are required, what current personalizations exist, and how rollout should be paced. With the right approach, Redwood can be more than a UI transition. It can become a real improvement in how supply chain teams interact with Oracle Cloud every day.
FAQ – Top Questions on Oracle SCM Redwood UX
What is Redwood in Oracle Fusion Cloud SCM?
Redwood is Oracle’s modern user experience framework for Fusion applications. In SCM, it introduces redesigned workflows, better search, embedded AI, improved visuals, mobile-first experiences, and a more consistent interaction model across products.
Is Redwood only a UI change?
No. Oracle describes Redwood as a broader experience philosophy. It includes workflow redesign, embedded AI, extensibility, telemetry, search, accessibility, guided journeys, and low-code personalization tools in addition to visual redesign.
Which Oracle SCM products already have Redwood functionality?
Oracle said that by 24D all SCM products have some level of Redwood presence. Examples mentioned include Supply Chain Planning, Order Management, Maintenance, Manufacturing, Inventory, PLM, Procurement, healthcare-related procurement experiences, and Sustainability.
What is the personalization helper tool in Oracle SCM?
The personalization helper tool helps customers identify ADF personalizations made in classic pages. It generates HTML and Excel outputs so organizations can review what was customized and decide what should be recreated or dropped in Redwood.
Does Redwood cost extra?
No. Oracle confirmed that Redwood is included as part of the cloud application license and does not require an extra charge.
When does Redwood become mandatory?
Oracle explained a general “N plus 2” approach in SCM. Once Redwood fully covers the classic functionality, the classic UI typically remains available for that release plus two more releases before Oracle may default customers to Redwood.
What isrequiredbefore enabling Redwood?
Oracle highlighted that Oracle Search should be enabled and that customers should review Oracle’s support documentation for profile options, prerequisites, and product-specific setup requirements.
Planning your move to Oracle SCM Redwood UX requires more than turning on profile options. It involves process evaluation, personalization review, feature readiness assessment, and a controlled rollout strategy across supply chain teams.
NexInfo helps organizations adopt Redwood across Oracle Fusion Cloud SCM with a structured, practical approach that balances innovation with operational continuity.
Our team can support you with:
- Redwood readiness assessments
- SCM product-by-product adoption planning
- ADF personalization review and migration support
- VB Studio and Express Mode personalization guidance
- User enablement and rollout planning
- Process alignment across planning, procurement, manufacturing, inventory, and order management
Whether you are just beginning to evaluate Redwood or are ready to scale adoption across Oracle SCM, NexInfo can help you move faster with clarity and control.