Module Store module Available in the base edition

Build your ERP module by module, as you need it

The Module Store is where your admin sees every Fidar module, understands its status and switches on the ones you need. Dependencies are resolved automatically and each new module sits on the same data and the same permissions.

Free in every subscription’s core · you only pay for active modules

Problem and solution

Why “big bang” ERP projects usually fail

Buying and rolling out every part of an ERP at once is expensive and risky: the team has to learn ten new processes at the same time and half the features never get used. A modular approach means starting with today’s problem and moving forward step by step.

Problem

Paying for features nobody uses

Full ERP bundles include modules the company may never touch.

In Fidar

Each module is switched on separately and only active, available modules appear on your bill.

Problem

Adding an area means a migration

Buying a separate inventory tool means re-entering products and customers and maintaining a fragile integration.

In Fidar

A new module activates on the same database, contacts and permissions — no data transfer.

Problem

Dependencies are unclear

Nobody knows which other parts are needed to switch one on.

In Fidar

Each module declares its dependencies and the store shows them before activation and enables them in the right order.

Problem

Switching off means losing data

Cancelling a module takes years of work offline or deletes it.

In Fidar

Deactivation only closes access and keeps the data; full removal requires explicit owner approval and an export first.

Capabilities

Module Store capabilities

Discover and activate

  • Full module catalogueCategory, description and a clear “Available” or “Coming soon” status.
  • One-click activationMenus, permissions and seed data register automatically.
  • Automatic dependency resolutionPrerequisite modules are enabled in the right order.
  • Register interestSign up to hear when a coming-soon module ships.

Module lifecycle

  • Automatic upgradesModules update without losing your customisations.
  • Safe deactivationData is kept and access is closed.
  • Controlled removalOnly with explicit owner approval and after an export.
  • Change historyWho enabled or disabled which module, and when.

Extend without breaking

  • Explicit extension pointsModules extend each other without changing each other’s code.
  • Added buttons and tabsFor example, Sales adds a “Create quotation” button to CRM deals.
  • Custom fieldsCompany-specific fields on any extensible record.
  • View customisationForm and list changes are stored separately and survive upgrades.

Subscription and cost

  • Transparent pricingSee the effect on your bill before confirming activation.
  • No charge for unreleased modulesComing-soon modules never appear on the bill.
  • Free coreContacts, Activities, Reports, Access and the store itself come with every plan.
  • On-premise editionLicensed modules are defined in a signed licence file.

Recommended activation order

Companies usually start with Contacts, CRM and Activities, which have the fewest dependencies and the fastest payback. Reporting and access control are there from day one.

Next comes the financial and supply-chain backbone: Accounting, then Purchasing and Inventory, then Manufacturing. That is also the order in which Fidar modules ship on the roadmap, because each relies on the previous one’s data.

Activate each module with a small pilot team, then extend it to the whole company after two to four weeks. Because deactivation never deletes data, trying a module has no irreversible cost.

Before activating a new module, review its default roles with the department head and decide who becomes a user and who a manager of it. Activating without that decision usually leads either to excessive access or to users who can’t do their work.

Look at the module usage report every quarter. A module that is active but where nobody creates records either needs training or isn’t needed yet — either way the decision is based on data.

Finally, communicate each activation to the team before it happens: what the new module does, who will use it and where to find help. A short announcement prevents the confusion of new menus appearing unexpectedly.

Integration

Access layer one: which modules are active

In Fidar’s six-layer access model, the first question is whether a module is active for the organisation. The Module Store manages that layer, and every other module appears or hides accordingly.

Status and release order of each module are on the roadmap.

Reports

Module usage reports

See which modules are actually used so subscription decisions are based on data.

Management dashboards and report builder
  • Active modules

    Active modules, activation date and who enabled them.
  • Users per module

    People who used each module in the last month.
  • Usage

    Records created in each module per month.
  • Cost per module

    Each module’s share of the subscription.
  • Change history

    Module activations, deactivations and upgrades.
  • Awaited modules

    Coming-soon modules you registered interest in.

Access

Who can activate modules

Activating a module creates cost and access, so only specific roles may do it and every change is logged.

Security and user access
Organisation admins onlyActivation requires the system admin roleRole
Cost confirmationBilling impact shown before activationLimit
Default module rolesUser and manager roles created automaticallyRole
Removal needs owner approvalAnd a full export beforehandRule
Audit-loggedEvery module status change is recordedAudit

Module Store FAQ

What does modular ERP mean?

Each part of the software, such as CRM or inventory, is switched on independently, but all of them run on one database and one access system. You only enable what you need. For background, see what is ERP.

Which modules can I activate today?

The platform core, Contacts, CRM, Activities & Calendar, Reports & Dashboards, Users & Access and the Module Store itself. The rest are listed as “Coming soon”.

What happens to data when I deactivate a module?

The data is kept and only access is closed. Reactivate it and everything is back. Full removal requires explicit owner approval and an export first.

Can third-party modules be installed?

A third-party module marketplace is part of Fidar’s long-term plan and hasn’t launched yet. Today the store contains official Fidar modules only.

Will upgrades wipe our customisations?

No. Your form and list changes are stored separately from the base definitions, so they survive module upgrades.

How are modules enabled on-premise?

Licensed modules are listed in a signed licence file and the admin enables them from the same store. See cloud or on-premise deployment.

Start with the module you need today

Start with CRM and reporting; every new module that ships plugs into the same data with one click.