Overview
netERP Manual Overview
Suitable service and technology paths
Key in-depth resources on this topic

netERP explained
Choose a topic. Each guide takes you to the goal in short, clear steps.
What would you like to do?
Start with the installation or open directly the topic you have a question about. Each chapter explains the key steps in plain language and shows relevant examples from netERP.
The chapters do not necessarily build on one another. You can therefore access them at any time via the menu on the left or via one of the tiles below.
Main areas at a glance
netERP connects master data, documents, tickets and customer contacts in a single interface. The following examples show the main areas. All illustrations originate from automated tests using fictional sample data.

Dashboard and interface
Ribbon menu, modules as tabs, and a dashboard with tiles for open tickets, key metrics and links.
More about the interface
Lists and search
Search, sort, select columns and group by any column — fast even with large data volumes.
More about lists
Tickets and email
Emails become tickets with status, priority and deadlines; the entire history remains attached to the ticket.
More about tickets
Master data
Customers, suppliers and items with addresses, prices and history — numbers assigned only on save.
More about master data
Customize forms
Each form can be modified in the built-in designer and extended with custom validations via script.
More about the designerNext step
If you have a concrete modernization, API or platform question, we should establish the technical scope clearly and early.
Net-Base evaluates existing systems, data paths, interfaces and target platforms not in isolation, but in the context of domain logic, operations and future expansion.
- Current state, target state and technical risks are assessed jointly.
- REST, data access, portals and rollout are not deferred to a later stage as secondary consequences.
- You can see early on which path is economically and operationally viable.