In December 2023, we changed our pricing policy.

Our prices were specifically per user.
Now to date, we have three packages in which we already have 5 users included!
The two lower packages have limits on some of the features, while the price of additional users is identical on all packages.

Please view the following link for detailed information:

Focus of Development


The current focus of our development is the evolution of features that will significantly increase the efficiency and productivity of every company that uses ERPAG !

Features that we have developed can be divided into the following categories:

  • Customization
  • Automation
  • Smart API

Until now, the industry standard for software application billing was usually associated with the person who physically uses the application on a computer (or other digital devices, e.g. phone). The more users of the application, the higher the fee for using the application.

Based on the number of users, it was possible to calculate the impact on computing costs or pressure on support. It functioned while man worked directly with the machine (e.g. computer) however, progressively speaking there is the increased work of machine with machine simultaneously (e.g. computers exchange data with each other via API service).

Reason for the Price Change


Currently, one BOT (i.e. automated program script) in ERPAG can enter more data in one hour than 10 users enter in a month. Companies implementing automation and API integration will lose the need for additional user account licenses (e.g. instead of 10 user account licenses they will pay for 3 licenses).

The impact on performance will be significantly greater (BOT does not have its own working hours, it can work continuously) as will the need for a higher level of support (questions and issues will be more programmer-related). Software developer companies face a decline in revenue on the one hand and an increase in costs (computer power cost, support cost) on the other.

The development of features for automation threatens them to threaten themselves economically, that phenomenon is called Product Cannibalization. There are examples with a negative result; the most famous is Kodak, who invented the digital camera and that invention led to their end.

One of the positive examples is Apple and the famous story of how the iPhone “ate” the iPod.

This phenomenon is the reason for our change in price policy.

Backward compatibility


Currently speaking, users who have no need to use the mentioned features are left with the option of paying only for what they use.

It is our business practice that all of our users have the right to keep the conditions they had at the time they started with us (legacy).

However, they always have the possibility to choose which conditions are more favorable & beneficial to them, i.e. should you wish to switch to a new Price Policy, you can do that at any moment!

What is next?!


Our goal is that each of our users can undertake customization and automation independently. The basis for automation and customization is Google’s visual programming called Blockly Script. Regardless of the fact that the programming code is visual, at first glance, it can seem complicated to someone who has no experience.

With the further development of AI, this knowledge gap will be overcome.

Even now it is possible to easily generate Blockly Script with ChatGPT, simply copy/paste the generated XML text.

Note: The current application of AI in programming is at the level of proof of concept – the technology is still in development.

Start NOW

Read More

Related Posts

How Great Inventory Software Can Help Fight Inflation

In today's rapidly fluctuating economy, businesses face the daunting challenge of fighting inflation. Rising costs can erode profits and disrupt operations, making it essential to adopt strategies that mitigate these impacts. One powerful tool in this battle is...

read more
​ERPAG API – Xero OAuth 2.0 authorization

​ERPAG API – Xero OAuth 2.0 authorization

In this instruction blog, we will describe how to create OAuth 2.0 API keys on your Xero account. These API keys are necessary in order to make API calls from ERPAG via Blockly scripts. The instructions show how the process itself currently looks. If in the meantime...

read more