What's the deal with transactions?


Transactions could be seen as an exchange of a data entity/object between systems. Within Alumio, a transaction is defined as a task and can be found in the 'Tasks' menu on the left side of your screen.

If succeeded, failed or skipped, a task will always be counted as it requires processing power to make the transaction within Alumio. However, data ‘enrichment’/transformation from external sources do not count on top of the already existing transaction.

A single transaction can be split up into multiple routes as you could have a product that consists of various data objects from different sources.

Usually, a system requires a certain entity to be available before it can be referred to by another entity. A perfect example of such integration would be an end-to-end product integration. Products usually exist out of various data objects such as (but not limited to): categories, attributes, images, relationships (such as up-sells, cross-sells, or related products), and finally the product data itself. A product can not be assigned to a category that does not exist yet, so that creates the requirement to synchronise categories separately from the product itself.

The usage of webhooks and HTTP proxies also count towards the transaction metric. Each time a webhook or HTTP proxy is consumed, a task will be created. Alumio offers the ability to purchase extra transactions on top of the complementary transactions offered by your subscription.