Skip to content

One system, thirty-four modules

Modules are not separate applications, and they are not separate deployments. They are parts of one system that shares one ledger, one database and one set of permissions. What you subscribe to opens its screens; what you do not stays closed, with its data intact.

Restaurant switched on: its screens and permissions open.

  • Restauranton
  • Cateringoff
  • Productionoff
  • Distribution & deliveryon
The modules and their counts are from the real module registry; which one is switched, and when, is illustrative.

Kernel

Always on, and never bought separately. No system can compute without accounting, inventory, units of measure and master data.

  • Accounting

    Always on

  • Inventory

    Always on

  • Units of measure

    Always on

  • Master data

    Always on

  • Accounts & sign-in

    Always on

  • Background jobs

    Always on

  • Integration events

    Always on

  • Files

    Always on

  • Imports

    Always on

  • Documents

    Always on

  • assistant

    Always on

  • Help & support

    Always on

Core

What any business needs: settings, the dashboard, sales, purchasing, finance and e-invoicing.

  • Settings

    Licensable

  • Dashboard

    Licensable

  • Privacy

    Licensable

  • Integrations

    Licensable

  • E-invoicing

    Licensable

  • Sales

    Licensable

  • Purchasing

    Licensable

  • Finance

    Licensable

Operational

What depends on your line of work: restaurant, events, distribution, livestock, production, human resources and others.