News

Mago Introduces 3 New Modules Based On API Communication

An important element in the evolution of the program within the digital business, based increasingly on the so-called API Economy.

OpenPOS, Open eCommerce and MAGOAPI

Mago is increasingly an open and innovative software thanks to the presence of three new modules: Mago API, OpenPOS and Open eCommerce. These modules are based on communication via API (Application Programming Interfaces) which allow a complete integration with third-party applications.

This solution represents an important element in the evolution of the program within the digital business based increasingly on the so-called API Economy. Indeed, APIs are an indispensable tool for quickly delivering those services that the business requires.
Mago allows you to work more and more in security, calls to the API are subject to authentication which guarantees security in the exchange of information. In fact, anonymous calls are not allowed and can be rejected if the user's security profile used for authentication does not allow the use of the API.

Mago's on-site Store Management has been enhanced thanks to the OpenPos and MagoAPI modules, which through the APIs satisfy the main needs common to all POS. The available APIs allow you to obtain information about the store and the items, in particular, about the retail categories, the tax codes, the sales prices lists and the images. 
But that's not all, in addition to this information Mago can manage the import of documents from POS using two specific APIs to import fiscal bills, uncollected receipts, invoices and credit notes. Furthermore, the import of documents also includes a series of information such as items, payments, discounts and fiscal data.
Nowadays it is essential for the companies to have an e-commerce, Mago, using the Open eCommerce module, can integrate itself with external e-commerce platforms, receiving information from customers registered on the e-commerce and importing their respective orders, thanks to the use of specific APIs.

These three modules enrich the Mago backend with new master data. Data entries typical of the store management are added, such as the retail categories with their hierarchical structure, attributes and assortments, while among the documents we find, for example, the fiscal bills and cash transactions.

By activating the Accounting module in addition to the MagoAPI module, Mago is also able to import accounting documents issued by an external program. In particular, the import of pure accounting entries, issued documents and received documents is managed with the contextual generation of the ledger and analytical entries.

If external programs should send changes for the journal relating to the received accounting documents issued by Mago, these will be taken in account through the use of APIs, also considering the management of analytical entries. Furthermore, Mago is able to return the totals of the open accounting offsets for each customer in order to evaluate any operational blockage.

We can conclude that the strengths acquired by Mago thanks to these three new modules are greater security, information sharing between different systems, greater flexibility and the possibility of combining with API Management solutions that allow centralized governance and monitoring from a single platform.