IFS Cloud ERP supports four distinct ways to tailor the system: user personalization, configuration, internal customization, and external extensions. The practical approach is to use standard functionality first, configure what the platform can handle, extend outside the ERP when that is suitable, and write internal code only when a requirement genuinely needs native IFS behavior. The deeper the change, the more ownership, testing, and release work it can create.
What “customization” means in IFS Cloud ERP
IFS uses tailoring as an umbrella term for changes to how its software looks or behaves. It is useful to distinguish the methods: a saved search is not the same kind of change as a new business rule embedded in an ERP transaction.
As an Amazon Associate I earn from qualifying purchases.
- Personalization changes an individual user’s experience, such as bookmarks, saved searches, or navigation preferences.
- Configuration uses supported application tools to change shared pages, fields, workflows, reports, navigation, or process settings without directly changing standard application code.
- Internal customization adds functionality or changes behavior inside the IFS Cloud platform, potentially including new entities, projections, client pages, reports, or business logic.
- External extension builds a separate application, integration, automation, or analytics solution around IFS, using supported interfaces rather than changing its core.
IFS describes these approaches in its tailoring overview. The terms matter because each approach has different development, maintenance, and release implications.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What can be tailored?
User experience and pages
Configuration can change page layouts, field placement and visibility, navigation, and role- or persona-specific experiences. Supported custom attributes can also be placed on IFS Cloud Web and Mobile pages. A user’s personal display preferences are different: those do not necessarily change the shared experience for a team.
#1 Best Overall
Data and fields
Custom attributes let an organization add customer-specific information to supported entities. Depending on the attribute and setup, values can be persistent and can use types such as text, numbers, enumerations, or references to other entities. Adding a field to the data model does not guarantee that it appears in every page or view, or that every integration exposes it. IFS documents the setup and page-placement process in its 26R1 custom-attributes guide.
Workflow and process behavior
Configuration can support process automation such as approvals, notifications, routing, and automated actions. It can be enough when an existing workflow or supported rule expresses the requirement. If a requirement changes standard transaction logic in a way configuration cannot represent, internal development may be necessary.
Frequent workflows and custom queries can affect performance. Query complexity, transaction volume, execution frequency, and data growth should be assessed for the actual workload rather than assumed safe because a change was made through a configuration tool.
Reports, dashboards, and analytics
Organizations can adapt operational reports, lobbies and dashboards, and reporting data sources. IFS Information Sources can support reporting and data-warehouse use; external business-intelligence tools are another option. A substantial block of SQL or PL/SQL hidden in a configuration field is harder to maintain and test than a properly developed customization; IFS recommends using the development path for larger code blocks.
Integrations and adjacent applications
Not every new capability belongs inside the ERP. A portal, mobile app, data pipeline, RPA process, specialist planning tool, or connection to CRM, payroll, e-commerce, logistics, or manufacturing software may be better built externally. IFS identifies REST and OData APIs, events, Information Sources, and IFS Connect among the mechanisms used for integration and extension. Its 25R2 integration and extensibility guidance describes external development options.
Rank #2
Core business logic
Internal customization is the more relevant route when a new rule or domain capability must operate as part of native IFS behavior—for example, a specialized calculation or eligibility rule that configuration cannot express and that must be enforced within an IFS transaction. That added control comes with responsibility for code ownership and future-release testing.
How the tools fit together
Configuration is handled through IFS application tools and designers, including areas for pages, lobbies, navigation, workflows, and entity configuration. Administrative access depends on roles and permissions, and labels or navigation can vary by release and deployment.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchFor deeper development, IFS Developer Studio supports modeling and building entities, logical units, projections, client pages, and reports. IFS’s Developer Portal getting-started guide describes development in a dedicated build environment and setting the target version from the build home. IFS also describes low-code development and its Marble domain-specific language. Low-code can reduce conventional coding, but it does not remove the need for architecture, version control, security review, testing, performance analysis, and release management.
Layered Application Architecture (LAA) is intended to keep customer changes distinguishable from the standard application and assist impact analysis. It does not make every change upgrade-safe. IFS documentation also restricts internal extension of certain Framework components from IFS Cloud 22R1 onward; that is a restriction on specific protected areas, not a ban on all customization.
Example: adding a custom field in IFS Cloud 26R1
The following path is from IFS Cloud 26R1 documentation; menu labels and steps can differ in other releases.
- Open Solution Manager > Configuration > Entity Configurations.
- Select an existing configuration entity or create one.
- In Custom Attributes, add a record and use the Add Custom Attribute assistant to define the attribute, its type, and relevant properties.
- Publish the attribute.
- Use Page Designer to place it on the required IFS Cloud Web or Mobile pages.
- Check other entity views. Some detail views may need explicit approval rather than receiving the attribute automatically.
- If the value must be sent in outbound messages, enable the applicable outbound-message property.
- Test access permissions, validation, page behavior, reports, integrations, and deployment across environments.
Typical misses include publishing a field but not placing it on the page, adding it to a different view than the one users access, or expecting an integration projection or outbound message to include it automatically. A custom field on a high-volume entity can also affect query or page performance. Treat the field’s consumers—pages, reports, APIs, and messages—as one dependency chain.
Choosing the least invasive method
IFS recommends keeping tailoring at the lowest level that genuinely meets the need, while cautioning against forcing a requirement into an unsuitable mechanism. Use this sequence to decide:
- Check standard functionality. Confirm that the relevant process, industry capability, role, report, or API is not already available.
- Personalize for individual preference. Use user-specific settings when only one person’s workspace needs to differ.
- Configure shared needs. Use supported settings and designers for team-wide pages, fields, navigation, reports, workflows, and process changes.
- Extend externally where practical. Prefer a separate app or integration when it can use supported interfaces without duplicating ERP logic or weakening transaction controls.
- Customize internally only when required. Choose internal development when the requirement must add or change native business behavior and configuration or external APIs cannot meet it safely.
For APIs, IFS recommends projections as the first preference when they support the use case, rather than defaulting to lower-level entity APIs. See the IFS API Usage Policy. External development can use technologies able to consume or expose REST APIs, including platforms named in IFS tailoring guidance, but the API contract and implementation still determine compatibility and security.
| Approach | Typical fit | Main consideration |
|---|---|---|
| Personalization | Individual bookmarks, searches, and preferences | Does not solve a shared business-process requirement |
| Configuration | Supported page, data, workflow, reporting, and navigation changes | Still needs governance, testing, and performance review |
| External extension | Portals, integrations, analytics, automation, or specialist applications | Works best when supported APIs expose the needed capability and the process can be decoupled |
| Internal customization | New native capability or changes to standard business logic | Requires technical ownership, impact analysis, and release testing |
What customization means for upgrades and support
IFS groups tailoring broadly into Core, Configured, and Customized levels. Standard use and individual personalization are generally the least invasive; supported configuration and external extensions still need impact analysis and testing; internal code and changes to standard behavior tend to require the greatest release effort. IFS notes that higher tailoring levels can make future updates more labor-intensive, and identifies IFS Lifecycle Experience as supporting impact analysis and automated handling of certain data, configuration, and personalization updates.
Separate four questions when assessing risk:
- Compatibility: Does the extension continue to work with the target IFS release?
- Upgrade effort: How much analysis, adjustment, testing, and deployment work is needed?
- Supportability: Who supports the behavior under the contract and implementation arrangement?
- Operational risk: What is the consequence if it fails in a financial, manufacturing, service, asset, or regulated process?
Using a supported external API can reduce dependence on internal implementation details and may improve compatibility, but it is not a guarantee. Configuration is not automatically harmless either: undocumented dependencies, poor deployment discipline, or performance-heavy queries can create release and operational problems.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #4
Common failure modes to prevent
Customizing a preference into a permanent requirement
Not every difference from a user’s preferred process is strategically important. Treating routine preferences as reasons to alter the ERP can add release work, specialist dependence, troubleshooting effort, documentation, and long-term cost, while also making conflicts with new standard functionality more likely.
Putting substantial code into configuration fields
Large SQL or PL/SQL blocks stored in configuration can be difficult to read, analyze, test, and maintain. Use the proper development path when the logic is substantial enough to need development tooling, static analysis, and controlled testing.
Managing configuration outside the solution lifecycle
Direct production edits, missing source-control records, untracked dependencies, or absent test and rollback plans can leave environments inconsistent. IFS advises treating configurations as part of the full customer solution and documenting purpose, dependencies, and operational effects.
Ignoring query and workflow load
Review query complexity, indexing, data growth, execution frequency, user concurrency, API response size, page-load effect, and batch behavior. Test against representative data volumes, not only a small development database.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Using the wrong API or trusting an undocumented endpoint
Prefer a suitable projection over a lower-level entity API, and do not expose APIs directly to untrusted clients. Account for authentication, authorization, retries, idempotency, and the stability of the particular API contract; avoid dependencies on undocumented internal endpoints.
Overlooking protected framework areas
Check whether a proposed internal change touches a Framework component subject to IFS restrictions. LAA does not override those restrictions.
A governance checklist before approving a change
- Is the requirement already covered by standard functionality?
- Why are personalization or configuration insufficient?
- Could an external extension meet the need without duplicating ERP rules?
- Must the behavior run within a native transaction?
- Which entities, pages, reports, APIs, messages, roles, and environments depend on it?
- Who owns the change after go-live, and who pays for future testing and release uplift?
- What security, performance, regression, and rollback tests are required?
- How will the change be documented, versioned, deployed, monitored, and eventually retired?
A customization register that records the business owner, reason, tailoring type, dependencies, permissions, performance considerations, release assessment, test cases, and retirement or rollback plan makes these questions answerable during implementation and later releases.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
