The MagoCloud 1.7 and Mago4 3.5 releases, published a few weeks ago, introduced some significant new features for Store Management, Mago-TCPOS integration, and the InStore and WMS mobile Apps.

Store management
The release of MagoCloud 1.7 and Mago4 3.5 introduced improvements and new features, designed to optimize some procedures and introduce new ones.
In the Supplier Orders, the operator (for each order) can modify the Destinations on the first line of the order, in particular Place of Delivery and Final Destination. All following lines of the order are created with the same fields (place of delivery and final destination) as set for the previous line. This way, if the operator is filling an order for the same final destination, he/ she does not have to specify for each item the destination.

An improvement developed to simplify the Shop Replenishment procedure for seasonal items is the possibility of linking an article to its Season. In Retail > Tables > Seasons, you can assign a specific period (the Season) to articles in which you can place orders to the supplier. For example, a wool jumper will only be available from September 1st to January 31st.

Previously, it was just possible to set the Ordering Dates for individual articles. With the release of the Season feature, once the automatic Shop Replenishment procedure has been launched, the procedure will first check (for each article) the Ordering Dates field and then check the Season field. The application of the Variant Management Grid with matrix display (already available in purchase and sales documents) has been extended also to InterStorage Movement Document and InterStore Movement Document.
We recommend running the Set Variant Management Data in Documents procedure, available from the menu under Services > Retail > Retail, to align the Transfer Documents. 
The latest project is designed for companies in the retail sector, thanks to the Purchase Orders Generation from Shop Transfer Requests they will be able to manage requests for goods from a general HQ to multiple points of sale, using an automated procedure.

Some new courses are available in the My Mago reserved area. These are the topics:

• Acquisition Items
• Base Unit Price Labels
• Fiscal Bills
• Alimentary data

Mago-TCPOS integration
We have added the Set POS Article Parameter in Preferences > Retail > POS Parameters. If the flag on the parameter is enabled, all new articles created are automatically sent to the POS. Whereas if this parameter is disabled, you can define for each article which one to send to TCPOS for sale in the stores.

This parameter allows more flexible management of the articles. Especially if, after an initial in-store sale of the product, I need to make it available for sale only via other channels (e-commerce, direct sale). The system checks whether the product has already been sold in the shops; if movements have been recorded, the article is disabled, otherwise it is deleted from TCPOS (the master data remains active in the ERP). The possibility of filtering by point of sale has been added in Mago, to simplify the management of receipts.

We have updated the Retail Documents check Report in Retail > Documents > Reports. This report monitors the status of the transactions transferred from TCPOS tills to Mago, highlighting any problems in data transfer. Another improvement concerns Invoices and Credit Notes, collected in 3 or more tranches.You can record the 3 or more payments, but only if they were made using a maximum of 3 payment methods (cash, credit card, cheque, voucher, etc.).

InStore App
The InStore App has been updated to version 1.5, which is only compatible with MagoCloud 1.7 and Mago4 3.5. Starting from this release, the application is no longer compatible with the previous versions of the ERP (e.g. version 1.5 of InStore App is not able to exchange data with Mago4 3.4).

You can disable automatic updates if you do not want to update the app to the new version. If version 1.5 is already installed on your devices (and incompatible with Mago), you can uninstall the application and return to version 1.4.12. Previous versions of the InStore App can be downloaded from the My Mago reserved area.

In the new release has been improved the search by code and description with Postgres databases. It is no longer necessary to type upper and lower case letters when searching for articles. In addition, the function Copy from Old to New Item Code (in Logistics > Items) has been updated in Mago. It is possible to copy the data of the InStore Mobile tab and in particular, the settings: InStore Item, Edit Quantity, Check Serial Number.

In Mago Retail > InStore Parameters, new parameters (InStore Item, Edit Quantity, Check Serial Number) have been added to manage the default settings, which you can apply to new items managed in the InStore App. The new procedure Set InStore Data in ItemMaster allows you to massively set these InStore Mobile parameters, even for articles already registered in Mago. This procedure is designed for those customers who only start using the App at a later stage and need to set these parameters for a large number of items.

WMS Mobile App
In the new release of the WMS Mobile App is available a long-awaited feature. We have simplified the transfer of goods between warehouses managed with the mobile WMS and those managed without the dedicated application. You can find the new feature in Manual Transfer Orders > Transf. Item between Storage. You can select all the warehouses connected to your company, both those that use WMS and those that do not, and transfer the goods between the different warehouses. Starting from a WMS depot, I scan the barcode of the location and prepare a list of the items I want to transfer to another warehouse with the relevant batch. In the next step, I select the destination warehouse from those available. Once these steps have been completed, we can consider our transfer mission accomplished. The quantities available in stock are automatically updated and Mago generates the loading and unloading movements of the warehouse.

Some basic settings are required to use the functionality, in particular, some default fields have been added in Preferences > Logistics > WMS Default Codes by User.