Included in every plan
Customers
One customer book for your whole tenant.
Individuals and companies live in a single record with contacts, addresses, tags and notes — and every other commercial module reads from it instead of keeping its own list.
- 6
- Permissions
- 7
- Integration events
- 5
- Linked-user roles
- 0
- Duplicate customer lists
One customer book
Individuals and companies in a single list, searchable and filterable, with archive instead of delete.
- Individual and company customer types side by side
- Full-text search, status filter and tag filter
- Display name, billing email, phone, locale and language
- Archive and restore — history is kept, nothing is silently removed
Contacts, addresses, billing detail
Each customer carries a primary contact and address; companies add named contacts, and every customer can hold billing, shipping and other addresses.
- Extra named contacts for companies, one marked primary
- Billing, shipping and other addresses with a default per kind
- Separate edit rights per facet — grant “edit billing” without “edit everything”
- Tax identifier and billing preferences: currency, invoice locale, payment terms
Tags and an honest timeline
Tags come from a shared, tenant-wide library. Notes are append-only — written once, never edited away.
- Tenant-scoped tag library with name, colour and description
- Rename a tag once and it updates everywhere
- Append-only notes with author and timestamp
- A separate permission lets front-desk staff add notes without edit rights
Logins linked to customers
Connect a platform login to a customer record — the same person can be a billing contact for one company and an end user of another.
- Five link roles, from primary contact to end user
- Many-to-many: one user, many customers; one customer, many users
- A three-step wizard, and soft unlinking that keeps the history
Merge duplicates safely
A guided three-step wizard shows exactly what moves before you commit.
- The target absorbs contacts, addresses, tags, notes and active links
- The preview shows anything that would be dropped
- The source is archived, never deleted
- Merging has its own permission, separate from editing
Built for the rest of the platform
Customers is the foundation module: Invoicing and Subscriptions require it and read it through a stable contract.
- Seven versioned events published on every lifecycle change
- A stable read contract other modules build on
- Its own database schema, isolated from the host and other modules
- The platform refuses to install Invoicing or Subscriptions without it
Worth knowing: It is a shared customer record, not a CRM — no deals, no pipelines. Tags cannot be deleted yet (rename and recolour only), and duplicates are merged by hand, never guessed automatically.
What every module inherits.
- Installs from the marketplace with no redeploy — the menu and the permission list update immediately.
- Creates its own tables, in its own schema, inside that customer's database.
- Packages are cryptographically signed when they are built, and the signature is checked before the host unpacks one.
- Uninstall switches a module off and keeps its data. Dropping the tables is a separate, deliberate choice.
Works with
Want to see Customers running?
Thirty minutes, a live workspace, and an honest answer about what each module does and doesn't do yet. Missing a module? A custom build is a fixed-scope project, from €25.000.
Book a call