Skip to content
Language: English

Custom ERP systems

A custom ERP system that puts your departments on the same data and the same business rules

For companies with more than one department or branch whose operations are split between separate programs and spreadsheets, and that need one system that matches the way they work instead of changing the way they work to fit off-the-shelf software.

Discuss your projectHow we work

01

Problems we solve

  • Sales are in one program, inventory is in a spreadsheet, the accounts are in a third program, and the figures do not match.

  • We tried off-the-shelf software and had to change the way we work to fit it.

  • We buy and sell in more than one currency, and as exchange rates change, we do not know our real profit.

  • We cannot define who sees what, and who approves what, in each branch.

  1. ORD-01Orders
  2. INV-02Inventory
  3. BIL-03Invoicing
  4. ACC-04Accounting
  5. RPT-05Reports

BR-02Business rule: The item is reserved when the order is confirmed, so the same item is not sold twice.

One system that applies the same rule in every module

Modules joining one system, linked by a business rule

02

What the service includes

  • F.01

    Modules based on your business

    Sales, purchasing, inventory, accounting, human resources, and whatever is specific to your sector, with each module built on your procedures.

  • F.02

    Business rules, documented and applied

    We document and number the business rules, and the system applies them in every transaction, so data accuracy does not depend on an employee’s memory.

  • F.03

    Multiple currencies and branches

    Each transaction is recorded in its currency, at its exchange rate when it takes place, and each branch’s data is kept separate and combined when needed.

  • F.04

    Role-based permissions

    Each role has its own view, edit, and approval rights, with a log that shows who carried out each transaction and when.

  • F.05

    Reports and dashboards

    Reports are built from the same data the transactions are recorded in, so they are not compiled by hand in Excel.

  • F.06

    Start with one module, such as basic accounting

    Basic accounting may be the first module: the cash book, receipts, payments, and balances. The next modules are then added to the same system, on the same data and permissions.

03

How it runs

  1. We analyze the processes

    We document each department’s procedures, business rules, and handoff points to other departments, and identify the exceptions.

  2. We design the module map

    We define the modules, their implementation order, and the data they share, and agree on the scope of the first stage.

  3. We build module by module

    We deliver each module in working order for you to review with your team on real cases, before moving on to the next module.

  4. We launch and stay with you

    We migrate the data, train the users, follow actual operation, and address the feedback that comes up.

04

What it looks like in practice

Illustrative example

A distribution company with several warehouses records its orders in one program, tracks its inventory in spreadsheets, and calculates what its customers owe in more than one currency by hand. We start with the orders module and the inventory module, then add invoicing and accounting to the same system, module by module, with documented business rules that the system applies in every warehouse. Customer balances and inventory become available the moment a transaction is recorded, not after they are compiled at the end of the month.

05

What we need from you to start

  • Someone from management with the authority to approve the business rules
  • A representative of each department included in the first stage
  • Samples of the invoices, reports, and spreadsheets you currently use

06

Support and development after launch

Our work does not end when we hand over the system: we keep track of its day-to-day operation and develop it as your business grows.

  • A post-launch support period to fix bugs and monitor stability, as set out in the contract.
  • Keeping track of performance, backups, and security updates.
  • Regular review sessions to rank improvements and the next modules by your priorities.
  • Training for new users when the team grows or branches are added.

07

Common questions

Technologies we work with

  • Vue.js
  • Redis
  • Why a custom ERP system rather than an off-the-shelf one?

    Because a custom system is built around your procedures, business rules, team roles, and reports, so you don’t have to change the way you work to fit the software, and you start with the modules you actually need.

  • Is the whole system implemented at once?

    No. We start with the module you need most, and your team works with it before the next module is added to the same system, on the same data and permissions.

  • Can we start with just a basic accounting system?

    Yes. Basic accounting can be the first module in the system: the cash book, receipts, payments, and customer and supplier balances. When your business needs more than that, sales, inventory, and purchasing are added to the same system, on the same data.

  • Does the system support more than one currency and changing exchange rates?

    Yes, when your business requires it. Each transaction is recorded in its currency, at its exchange rate at the time, and reports are shown in the currency that management chooses.

  • We have accounting software we work with. Do we have to give it up?

    Not necessarily. We decide with you what stays and what’s replaced, and the system can be connected to your current software through an API or a periodic file exchange, depending on what the software allows.

08

Related work and articles

09

Related services

All services

Let’s start with how you work

Describe your processes and the problem you want to solve, and we will define a clear first step with you.

Discuss your projectHow we work