Standard Fusion covers most of a process. The rest usually ends up in a spreadsheet, an email chain or a customisation that breaks every quarter. Oracle Visual Builder (VBCS) builds that missing screen outside the core, using Fusion's own data and security.
Extensions, portals and mobile front ends that sit beside Fusion, inherit its permissions and survive its updates.
Low-code web and mobile applications on Oracle Cloud, inside OIC or Fusion.
Reads and writes through Oracle's supported interfaces, not the database.
Extensions are regression-tested against each quarterly release.
Fusion functional and technical teams on the same project.
Visual Builder is the right answer when the requirement is real, the standard product cannot meet it, and a customisation would turn every update into a project.
New pages and redesigned flows over Fusion ERP, HCM and SCM objects, using Fusion REST services and the user's own roles.
The user stays inside the Oracle experience; the extension stays outside the code Oracle updates.
The missing step, without a customisation.
Forms and approval flows for the requests that live in email today: capex, supplier requests, master data changes, exceptions.
Combined with OIC Process Automation where the flow spans systems.
A request with a status, an owner and an audit trail.
Supplier, customer and employee portals over Fusion data, with authentication through your identity provider.
External users see only what their role allows, enforced by the service, not the screen.
Partners serve themselves instead of emailing your team.
Responsive and installable applications for warehouse, field and approval tasks that are awkward on the standard Fusion screens.
Designed for the device the job is done on.
Work recorded where it happens.
Visual Builder business objects for data Fusion has no place for, with REST access for reporting and integration.
Kept small and documented, so they never become a shadow ERP.
A proper home for the spreadsheet data.
Automated checks of every extension against Oracle's quarterly update in the test pod, before production is updated.
Breakages are found by us in test, not by users on Monday.
Quarterly updates without a fire drill.
How a Visual Builder engagement runs
Where Visual Builder earns its place in a Fusion estate.
| Use case | Typical data | Users | Model |
|---|---|---|---|
| Page extension | Fusion ERP, HCM, SCM objects | Internal | Project |
| Approval flow | Requests, exceptions, master data | Internal | Project |
| Portal | Orders, invoices, onboarding | Suppliers, customers | Project or managed |
| Mobile task app | Receipts, counts, inspections | Field and warehouse | Project |
| Extension support | All of the above | All | Managed |
Every extension is software you will own and support for years. The cheapest one is the one you did not need, so each request is checked against standard Fusion before anything is designed.
When an extension is the right answer, it is built on supported APIs, outside the core, under source control and with a regression check for each quarterly update. That is the difference between an extension and a liability.
Discuss an extensionScope and estimate follow the prototype, not the first conversation.
No. Both are Oracle low-code tools. Visual Builder is aimed at extending Oracle Cloud applications through their REST services. APEX is strongest over data in an Oracle Database. We use whichever fits the data and the users.
They are far less likely to, because they use supported interfaces and sit outside the core. We still regression-test every extension in the test pod before each quarterly update reaches production.
Often not. Visual Builder is included with several Oracle Cloud and OIC subscriptions. We check what you already have before recommending anything.
Yes, with authentication through your identity provider and data restricted by role on the server side. Portals for suppliers and customers are a common use.
Your team, with the source and documentation we hand over, or us under a managed service alongside Fusion support.
The one that holds the step Fusion does not cover. We will tell you whether it needs building, configuring or leaving alone.