How getting started with CoreDLS works
Updated:
The start depends on whether the company already has an ERP. With an ERP, it begins with a technical call, continues with a lightweight service on the customer network and ends with binding the devices. Without an ERP, data is loaded with a template and preview, the AI consultant configures the company and everything is rehearsed in a test company.
There are two paths and the steps are not the same. This guide describes them in order, without timeframes: how long it takes depends on the customer system and on how many modules are activated, and it is estimated in the technical call.
If you already have an ERP: mobile and web extension
- Technical call, no commitment: the customer system is reviewed, the version, where the server is and what data is needed. If the system runs on SQL Server, it can most likely be connected; if not, the connector is developed for that case.
- Service on the customer network: a lightweight Windows service runs next to the ERP server. It only talks outward, so there are no ports to open and no server to publish, and it does not write to the ERP tables.
- Reading and sync: the service reads what the field team needs (prices, stock, customers, customer accounts) and syncs it with the app by differences.
- Device binding: an administrator enables each phone once; after that each person gets in with fingerprint, face or PIN, with no username or password. The web is entered by scanning a QR code from the app.
- Permissions: it is defined which modules each person sees. There is no data migration or "before and after": the ERP remains the one in charge.
If you have no ERP: the CoreDLS native ERP
- Bulk import with a template: customers, products, balances and more are loaded from a file, with an error preview before applying.
- AI consultant: from the chat it builds fields, price lists, rules, workflows and reports. Each change is shown first in a preview and applied only on confirmation; anything high-risk is approved by an administrator.
- Test company: everything can be rehearsed in a separate company, without touching the real one.
- Cleaning up test records: when going live, the test records are deleted with a preview and written confirmation.
- Devices and permissions: same as in the other path, each phone is enabled once and each person sees only their modules.
The two paths, side by side
| Step | With an existing ERP | Without an ERP |
|---|---|---|
| First contact | Technical call with no commitment | Half-hour demo and setup with the consultant |
| Data | Stays where it is; not migrated | Import with a template and error preview |
| Configuration | Permissions per module and authorizations as data | The AI consultant builds fields, lists, rules and workflows |
| Rehearsal | Tested with enabled devices | Test company, with cleanup afterwards |
| Devices | An administrator enables each phone | An administrator enables each phone |
What is not promised
This guide sets no timeframes or prices. The timeframe is estimated in the technical call after seeing the system, and the plan is built from the number of users and the modules activated.
Frequently asked questions
- How long does getting started take?
- It depends on the customer system and on how many modules are activated. It is estimated in the technical call, after looking at the database.
- Do I have to migrate the data from the ERP I use?
- No. The data stays where it is; the customer database is not copied or converted.
- What if my ERP does not run on SQL Server?
- The connector is developed for that case. It is confirmed in the technical call, with no commitment.
- What happens to the test records I entered?
- They can be cleaned up when going live, with a preview and written confirmation. Testing is best done in a test company, separate from the real one.
- Do rules and workflows have to be programmed?
- No. They are configured as data, from the administration or by asking the consultant in the chat, always with a preview before applying.
You can request a half-hour demo: the app is shown with test data and technical questions are answered on the same call.