ENRU Sign in Request a demoDemo

All features · your module

Your process runs inside the ERP, not next to it

A custom module is a separate block of the shared platform: its own screens, documents and calculations, but shared directories, permissions and reports. The core is never forked, so platform updates still reach you.

A custom module in Akeda ERP covers processes the standard sections do not: its own screens, documents, calculations and roles are built as a separate block of the shared platform rather than as a fork. The module is enabled for your workspace only and writes its own tables in your database under row-level protection, yet it takes products, counterparties, employees and legal entities from the shared directories, posts documents like any native operation, and is exposed through the API and MCP. It lives in the same repository and passes the same checks as the standard sections, so platform updates keep reaching it; custom modules for print and manufacturing already run in client workspaces.

Request a demoSee the screens
  • Own tablesmodule data lives in your cabinet's database, with row-level protection
  • Shared directoriesproducts, counterparties, employees and legal entities — the same ones everywhere
  • API and MCPyour module's operations are open to integrations and agents
  • Already runningcustom modules for print and manufacturing run in client cabinets

01Who gets what

  • For the owner

    An off-the-shelf system covers routine work, while the core of the business stays in spreadsheets.

    Your process moves into the system whole: stages, roles, documents and calculations. The result shows up in company-wide reports.

  • For the operations lead

    The status of every order has to be asked for out loud and taken on trust.

    Each role gets its own queue and a clear next action, and the order's path is visible from request to delivery.

  • For the technical director

    “Built for us” usually means a fork that nobody dares to update a year later.

    The module is enabled for your cabinet only and ships in the shared release: the platform evolves and your block is maintained with it.

02Key points

  1. 01

    Your way of working, not a generic template

    • We start by describing stages, roles, documents and the rules for moving between them.
    • Module sections become menu entries and, at the same time, units of access in roles.
    • Each role gets its own queue: people see what is waiting on their decision.
  2. 02

    Shared data, not a parallel world

    • Products, counterparties, employees and legal entities come from the shared directories.
    • Module facts go through a document and posting, exactly like standard operations.
    • Metrics keep the link to the order and document they grew from.
  3. 03

    Growth without forking the core

    • The module is enabled for your cabinet only, with its own tables and migrations.
    • It passes the same checks as standard modules and is updated alongside the platform.
    • We start with the main process, then add workflows, reports and connections.

03One day with the module

  1. 08:40

    Order accepted

    A manager creates the order and several jobs from shared counterparties and products — in one operation, with its own numbering.

  2. 10:15

    Approval

    The approver sees only what waits on their decision: terms, deadlines and real blockers, without other people's stages.

  3. 12:30

    The shop floor

    An operator takes a job from their queue and enters the actual quantity. Anything above the remaining amount is refused.

  4. 15:00

    Materials

    Material consumption and output go through stock rather than a side spreadsheet: balances and cost stay shared.

  5. 18:00

    Result of the day

    Output-based calculations reach finance as accruals, and metrics reach the manager's dashboard with links back to the orders.

04Works together with

05In brief

  • processesYour forms and documentsFields, stages and checks designed around how your team works.
  • accessEmployee permissionsAccess to sections and actions through the shared role system.
  • integrationsConnect your systemsData exchange with the services and equipment your business uses.
  • automationAdditional automationAPI and MCP so connected agents can work with your module.

MCP tools: akeda_go_capabilities akeda_go_catalog akeda_go_core_registers

Integrations: Your systems over API

06Questions

Custom module

What does it cost and how long does it take?

It depends on the process. We estimate after a walkthrough: stages, roles, documents and links to finance and stock. We start with one core process so it works quickly, rather than automating everything at once.

Is this a customised copy of the system?

No. There is no copy: your module is a separate block of the shared platform with its own key, tables and migrations. It is enabled for your cabinet only and does not affect other clients.

What happens when Akeda changes?

It sits in the same repository and passes the same checks as standard modules. Any drift from the platform shows up immediately, so maintenance is planned work rather than an emergency a year later.

Will our data be stored separately?

From other clients, yes: each cabinet has its own database. Inside it your module writes its own tables and uses the shared directories, so no second copy of products or counterparties appears.

We need an app for field staff. Is that possible?

Yes, as a separate app on the same open API: an employee receives a job, ticks off stages, attaches photos and sends the result into the shared system. Scope and timing depend on your scenario.

← Previous sectionFinance Request a demo Next section →Integrations and API

See Akeda
with your workflow.

Tell us what you want to connect or automate. We will show how the process could work in Akeda, what data it needs and where to start.

  • 01Understand your needs
  • 02Explore connected workflows
  • 03Define the next step

By submitting the form you give your consent to the processing of personal data.