ERP customization has long meant bespoke development: ABAP for SAP, Python for Odoo, AL for Business Central. These are rare, expensive skills — and the talent pool is shrinking every year. By 2026, the major ERP vendors have responded with built-in low-code tools that let business teams create forms, automate workflows and build dashboards without writing a single line of code.
But low-code is no silver bullet. Between marketing promises and on-the-ground reality, this article cuts through the noise: which tools, for which use cases, and with which limitations.
Why Low-Code in ERP Is Happening Now
The ERP Developer Shortage
Specialist ERP developers are among the hardest profiles to hire across Europe and North America. A senior ABAP developer capable of working on S/4HANA can command daily rates above £700 in the UK and €800 in Germany. Python developers with genuine Odoo framework expertise are equally sought-after, with supply well below the growing demand from mid-market companies. On the Microsoft side, AL developers for Business Central remain a niche.
This structural tension creates a bottleneck: business teams identify customization needs, but IT simply doesn’t have the bandwidth to address them. The customization backlog grows, frustration builds, and workarounds (Excel, Shadow IT) proliferate.
Business Teams Want to Adapt ERP on Their Own Terms
A procurement manager who needs an extra field on a purchase order shouldn’t have to wait three months for a developer slot to open up. A sales director who wants a margin-by-customer dashboard shouldn’t have to spin up a full IT project.
Low-code addresses this by giving business users — “citizen developers” — the ability to create simple customizations themselves. According to Gartner, around 75% of new applications will be built using low-code technologies by 2026, and developers outside IT departments will represent at least 80% of the user base for these tools (Gartner via Kissflow).
ERP Vendors Are Investing Heavily in Visual Tools
SAP launched SAP Build by integrating AppGyver into its Business Technology Platform. Microsoft is pushing Power Platform as the native extension layer for Dynamics 365. Odoo has evolved Studio since 2017 and is now adding generative AI. Oracle offers Visual Builder for extending NetSuite and Oracle Cloud ERP.
The vendor message is clear: classic development isn’t going away, but it should be reserved for complex cases. Routine adaptations are now a matter of visual configuration.
Low-Code Platforms by ERP Vendor
Odoo Studio: Visual Customization of Views, Fields and Automations
Odoo Studio is the most mature low-code tool in the SME ERP market. Available since 2017 in the Enterprise edition, it allows users to modify any view (form, list, kanban), add custom fields, build complete business applications and define automation rules — all through drag-and-drop.
Strengths:
- Gentle learning curve: a functional user can become self-sufficient in a few hours
- Wide scope: views, fields, filters, groups, PDF reports, conditional automations
- Native integration: Studio customizations coexist with standard modules and Python developments
- Generative AI: automatic field and attribute generation from a natural-language description (Odoo Studio)
Limitations: Studio does not replace Python development for complex business logic (multi-tier pricing engines, EDI connectors, heavy transactional workflows). Studio customizations can also cause conflicts during major upgrades if they are not documented.
Pricing: Included in Odoo Enterprise (from €31.10/user/month for the Standard plan).
SAP Build: Business Apps Connected to S/4HANA
SAP Build brings together three components on the SAP Business Technology Platform (BTP): Build Apps (visual application development), Build Process Automation (workflows and RPA) and Build Work Zone (unified portal). Since 2025, Joule Studio adds a conversational AI layer for creating business agents in natural language (SAP News).
Strengths:
- Native S/4HANA connection: direct access to business data and standard processes via SAP APIs
- Functional breadth: from simple mobile apps to multi-system approval workflows with RPA
- Pro-code escape hatch: developers can switch to ABAP Cloud or CAP (Cloud Application Programming) when low-code hits its limits
- Joule Studio: creation of AI business agents connected to the Business Data Cloud
Limitations: The learning curve is steeper than Odoo or Microsoft. SAP Build targets power users and functional consultants more than end users with no prior training. BTP licensing costs (licenses, cloud credits) stack on top of S/4HANA licenses and can represent a significant investment for mid-market companies.
Pricing: SAP Build licenses are available free of charge for SAP partners in test and development environments. In production, pricing depends on the BTP plan subscribed.
Microsoft Power Platform: Power Apps, Power Automate and Copilot Studio for Dynamics 365
Power Platform is probably the broadest low-code ecosystem in the ERP market. It comprises Power Apps (applications), Power Automate (automation flows), Power BI (reporting) and Copilot Studio (AI agents). Its integration with Dynamics 365, Microsoft 365 and Azure makes it a natural environment for organizations already in the Microsoft ecosystem.
Strengths:
- Familiarity: the interface echoes Excel and Microsoft tools, reducing change resistance
- Connector ecosystem: hundreds of pre-built connectors (SharePoint, Teams, SAP, Salesforce, SQL databases)
- Copilot Studio: build conversational business agents that query Dynamics 365 data
- Plan Designer (2025): describe an application in natural language, get an automatic prototype (Microsoft Dynamics 365 Blog)
- Built-in governance: Center of Excellence (CoE) with automated policies and app monitoring
Limitations: Pricing can become complex. Power Apps per-user licenses (around €20/month) or per-app licenses add to Dynamics 365 costs. Premium Power Automate flows (with non-standard connectors) are billed separately. Without governance, unchecked proliferation of unmaintained apps (“app sprawl”) is a real risk.
Oracle Visual Builder: Extensions for NetSuite and Oracle Cloud ERP
Oracle Visual Builder Cloud Service (VBCS) enables users to create interfaces and extensions for Oracle Cloud ERP and NetSuite. The tool is built on a drag-and-drop visual editor and generates responsive web applications.
Strengths: Deep Oracle Cloud integration, automatic REST API generation, JavaScript support for advanced scenarios.
Limitations: More closed ecosystem than Microsoft or SAP, smaller developer community, documentation can be patchy for ERP-specific use cases.
Notable Mentions: Axelor and ERPNext
Axelor is a French open-source ERP built natively around low-code. Business object modeling, views and workflows are handled through an integrated visual editor — one of the few ERPs where low-code is the base architecture, not an add-on.
ERPNext relies on the Frappe Framework, which offers a configurable doctype (data model) system without code. Frappe Builder enables visual page and form creation. The ecosystem is more technical than Odoo Studio but offers great flexibility for SMEs comfortable with web technologies.
For a detailed comparison of these solutions, see our open-source ERP guide: Dolibarr, ERPNext, Axelor, Odoo.
Comparison Table
| Criterion | Odoo Studio | SAP Build | Power Platform | Oracle VBCS | Axelor |
|---|---|---|---|---|---|
| Available since | 2017 | 2022 | 2016 | 2018 | 2015 |
| Target user | Business user | Power user / consultant | Citizen developer | Functional developer | Technical consultant |
| Learning curve | Low | High | Medium | Medium-high | Medium |
| Mobile apps | Yes (limited) | Yes | Yes (native) | Yes | Yes |
| Built-in AI | Yes (field generation) | Yes (Joule Studio) | Yes (Copilot Studio) | Partial | No |
| Workflow / RPA | Automations | Yes + RPA | Yes + RPA | Partial | Yes |
| Additional cost | Included (Enterprise) | BTP paid extra | Separate licenses | Included (Oracle Cloud) | Included (open source) |
5 Concrete Low-Code Use Cases in an ERP Project
Custom Business Data Entry Form
A manufacturing company uses Odoo Studio to add a quality control form directly in the production module. Each operator enters inspection results on a tablet, with conditional fields based on product type. Result: zero paper, zero Python development, deployed in half a day.
Multi-Level Approval Workflow
A mid-market company configures a purchase order approval circuit in Power Automate: below £4,000, automatic validation; between £4,000 and £40,000, approval by the procurement manager; above that, dual sign-off from the CFO and CEO. The flow connects Dynamics 365, Teams (notification) and SharePoint (signed PO archiving).
Real-Time Operational Dashboard
A supply chain director uses Power BI connected to Dynamics 365 to monitor service levels, stockouts and supplier lead times in real time. KPIs are calculated automatically and shared with the team via a dashboard embedded in Teams.
Mobile Field Application
A B2B distributor builds an inventory mobile app for warehouse staff using SAP Build Apps. The app scans barcodes, updates S/4HANA stock in real time and triggers replenishment alerts. The prototype was delivered in two weeks — versus two months estimated for classic ABAP development.
Visual Integration Connector
An SME connects its Odoo ERP to its Shopify e-commerce platform via a low-code flow (Make/Integromat or Odoo automations). Web orders are automatically created in the ERP, stock synced every 15 minutes, invoices sent without manual intervention.
Low-Code ERP Limitations: What Not to Ask of It
Performance and Scalability
Low-code automations work well at moderate volumes. But a workflow that triggers 10 cascading actions on every order line can noticeably slow an ERP processing thousands of transactions per day. Low-code engines generally don’t offer the same optimization options (indexing, direct SQL queries, caching) as native development.
Maintenance and “Invisible” Technical Debt
A classic developer leaves versioned, documented, tested code. A citizen developer leaves a visual workflow that nobody else understands. After two years, the organization ends up with dozens of automations whose authors have moved on, and zero documentation.
Low-code technical debt is “invisible” because it doesn’t show up in standard code management tools (Git, Jira, SonarQube). It’s very real nonetheless.
Governance: Who Controls Apps Created by Business Teams?
Without a governance framework, low-code reproduces the same pitfalls as Excel macros from the 2000s: patched-together solutions, unsecured, that become business-critical without IT’s knowledge.
Questions that need clear answers:
- Who is authorized to create an app or a workflow?
- Who approves before going to production?
- Who maintains when the creator leaves the company?
- What naming and documentation policy applies?
Security: Access Rights and Data Exposure
A citizen developer building an app connected to the ERP potentially accesses sensitive data: purchase prices, margins, payroll, customer data. If rights are not properly configured, the app can expose confidential information to unauthorized users.
Microsoft has built guardrails into Power Platform (DLP policies, separate environments, CoE monitoring). For Odoo and SAP, it falls on the administrator to configure restrictions manually.
Making Low-Code ERP Adoption Work: 4 Best Practices
Define a Governance Framework (Low-Code Center of Excellence)
Create a low-code Center of Excellence (CoE) — even a lightweight one. It sets the rules of engagement: who can build what, with which tools, according to which standards. Microsoft provides a CoE kit for Power Platform; for Odoo and SAP, you’ll need to build it internally.
The CoE isn’t extra bureaucracy — it’s what prevents low-code from becoming the new Shadow IT.
Train Citizen Developers
Giving access to Odoo Studio or Power Apps is not enough. Citizen developers need to understand the basics of data modeling, security principles and naming best practices. A 2–3 day training programme followed by IT mentoring is a sound investment.
Document and Version Customizations
Every low-code customization should be documented: objective, author, creation date, data accessed, dependencies. Some tools (Power Platform, SAP Build) offer built-in versioning. For Odoo Studio, manual discipline is required.
Know When to Hand Off to Classic Development
Low-code has a ceiling. When an automation exceeds 15–20 steps, when performance becomes critical, when business logic involves complex calculations or multi-system integrations — it’s time to hand off to a developer. Low-code should accelerate the 80% of simple cases, not try to replace development for the 20% of complex ones.
Key Takeaways
Low-code in ERP is neither a marketing gimmick nor a revolution that makes developers obsolete. It’s a productivity tool that, properly governed, reduces dependency on scarce skills, accelerates business adaptations and frees IT teams to focus on high-value projects.
The platform choice depends on your existing ERP: Odoo Studio for SMEs on Odoo Enterprise, Power Platform for the Microsoft ecosystem, SAP Build for organizations on S/4HANA. In all cases, the tool alone is not enough — governance, training and documentation are what separate an accelerator from a new source of problems.
To go further, see our ERP and artificial intelligence guide and our open-source ERP comparison: Dolibarr, ERPNext, Axelor, Odoo.
