RetailVista ERP v24.1 - Release notes spring 2024 update

20389) Taak 21806 - Adding threshold stock for webshop inventory levels

From now on, a threshold stock can also be specified in the webshop article definition. This threshold stock is subtracted from the inventory level communicated to the webshop. With the webshop threshold stock, it can be ensured that the inventory is always slightly lower on the webshop than the actual inventory. This can prevent the last article from being accidentally out of stock, and it can slightly better prevent orders for (in-store) fast-selling articles from resulting in a 'no sale' for the webshop consumer. 

(Version 23.23.8727.27895) Task 21822 - Resending outgoing email

In the maintenance of outgoing emails, an email message can now be resent.

(Version 24.1.8770.20389) Task 21828 - New status table for customer service rule type

In customer CRM maintenance, a status can now be linked to a rule type. This rule status can, for example, be set to determine whether a CRM rule can be considered completed.

(Version 24.1.8770.20389) Task 21883 - Capturing email address on the sales order

This new feature ensures that it is clear on a sales order which email address was provided when creating a sales order. Any future correspondence will also be carried out using that email address.

27398) Task 21710 - Ability to link invoice to a relationship

Previously, invoices could only be linked to a debtor. However, with 'collective' debtors, it was not clear who the original customer was. This caused problems, especially when printing invoices. From now on, an invoice can be linked to both a relationship and a debtor.

(Version 23.19.8657.27398) Task 21709 - VIES check during pack & ship process

For processing VAT exempt sales orders in the Pack & SDhip application, a VIES check will now be performed to verify the VAT number of the debtor on the sales order. If the VAT number is incorrect, the reservation processing will be aborted. If the VIES service is not accessible, the processing will continue. As part of this change, it will also be tested whether the debtor is allowed to buy on credit. There are debtors who must pay in full immediately. In that case, a reservation that is not paid or not fully paid will be blocked for delivery. The only alternative in that case is to make a cash on delivery delivery.

(Version 23.19.8657.27398) Task 21708 - Working with a real debtor instead of a collective debtor for B2B in the Pack & Ship application

If a delivery on credit is offered with a real debtor, the Pack & Ship application will now take this into account and the reservation will no longer be processed on a collective debtor. This adjustment also allows for processing reservations that are not paid or not fully paid yet, as an invoice will be sent later due to the presence of a 'real' debtor.

(Version 23.19.8657.27398) Task 21706 - Automatically generate invoices for deliveries on credit

A task schedule can now be created to automatically generate invoices for deliveries on credit.

(Version 23.19.8657.27398) Task 21703 - Ability to disable MX check per webshop on incoming messages

For each webshop, an MX check on the delivery of correct email addresses can now be disabled. Especially if a webshop has already done an email address validation itself (via MX check or for example actually sending an email), an additional check in RetailVista is unnecessary.

(Version 23.19.8657.27398) Task 21398 - Show notifications everywhere that it is a deleted product. (Booking, purchase, sale, product)

A proper notification is now shown in various places in RetailVista when a product is deleted (marked as deleted in product maintenance).

(Version 23.10.8501.27680) Task 21130 - Allow different sender per webshop

In webshop maintenance, a different contact can now be specified to be used as the sender address for packages originating from that webshop. In the SendCloud integration, the contact name and address of this contact are used as sender information.

(Version 23.9.8493.27718) Task 21100 - Improved support for duplicate barcodes

RetailVista ERP now has improved support for duplicate barcodes. To be able to use duplicate barcodes, it is necessary to activate it in the RetailVista settings. Once that is done, the same barcode can be specified for multiple products. However, from now on, only one of the same barcodes can be active, the rest are passive. For this purpose, a new field 'passive' has been added to the barcode maintenance screen. From now on, only one active barcode can exist for the same barcode, the rest are all 'passive'. With this functionality, it becomes possible, among other things, to receive EDI messages referring to a barcode that was not previously unique. From this update onwards, in such cases, the only active barcode will be found, and the other passive variants will be ignored.

It basically comes down to double barcodes that the barcode for the product  that should be applied in such a case is not marked as passive (so it becomes active).

(Version 23.8.8483.27307) Task 21036 - Journal export to Expert/M deliver

From now on, RetailVista ERP has an export of cash accountabilities and invoices to Expert/M.

General

(Version 23.23.8727.27895) Task 21832 - Improve Belgian VAT number check

There have been some changes in the VAT number notation for Belgian customers. It also appeared that some VAT numbers were rejected despite a valid format, while the VIES check accepted them. Both issues have been resolved.

(Version 23.26.8755.29691) Task 21825 - Resolve grid distortion

In some situations, a search results grid was distorted, with some columns becoming very narrow or remaining empty. Although this problem was difficult to reproduce, a solution seems to have been found.

(Version 23.18.8629.28627) Task 21469 - Revise administration screens

The display of the administration screens has been revised, as the old way of display was no longer sufficient.

(Version 23.18.8629.28627) Task 21445 - Enable login via alias and without company number

In the company maintenance, an alias can now be specified. This alias can be placed -before- the URL of the RetailVista website and eliminates the need to log in with a company number.

Example: If 'tuincentrum' is specified as an alias, the login URL would be: https://tuincentrum.retailvista.net/global. (Or instead of /global, the instance code currently used).

(Version 23.16.8602.27728) Task 21360 - Reset expired password does not work when using 2FA module

Resetting a forgotten password in combination with the active 2FA now works correctly.

(Version 23.6.8475.25195) Task 21115 - Packaging application can now also work without carriers or with a combination of carriers and no carriers

The packaging application could only handle reservations that were picked in carriers until now. From now on, it is also possible to work without carriers or with a combination of carriers and no carriers. The latter is intended for situations where part of a reservation is picked and placed in a carrier (for example, for items transported from the store to the central warehouse) versus items that are picked without a carrier in the central warehouse. A setting has been added to the RetailVista ERP settings that makes this behavior adjustable.

(Version 23.6.8475.25195) Task 21111 - Control on number of webshop cals

When creating a new webshop, the license check did not properly verify if there were enough cals available to add the new webshop. This issue has been resolved.

(Version 23.6.8475.25195) Task 21038 - Add 2FA (Two-factor authentication) to login procedure

From now on, it is possible to use 2FA in RetailVista. 2FA requires a user to provide an activation code in addition to a correct login name and password when logging in. This activation code must be generated by an authenticator app on a mobile phone. There are different authenticator apps available, RetailVista has been tested with the Apple, Microsoft, and Google authenticator apps. These apps are all free of charge. 2FA can be activated during company maintenance. Every user who logs in afterwards will be asked to scan a QR barcode displayed by RetailVista. This QR code adds RetailVista to the authenticator app, and from that moment on, the authenticator app displays a unique code that changes every 30 seconds. A user who does not have the authenticator app cannot log in with an account, even if the login name and password are known.

The application administrator can exclude certain user accounts from requiring 2FA on certain accounts. A license is required to use 2FA in RetailVista.

(Version 23.25.8749.27095) Task 21012 - Integration with CDN provider

An integration has been implemented between RetailVista and Sirv.com, a Content Delivery Network (CDN) provider. A CDN provider ensures that images are stored there, instead of in RetailVista ERP itself. This allows a webshop to use the exact same images and display webshop pages faster. Other software, such as a PIM, can also store images on the same CDN provider, so that these images can be automatically displayed in RetailVista without the need to exchange the image itself between systems. It is sufficient to exchange a URL where the image can be found.

Product Maintenance

(Version 23.3.8433.29764) Task 21002 - Search on combination of description and note 1

The search worked as an 'OR' filter, resulting in too many results being displayed. All search screens and all fields specified in RetailVista are always considered as an 'AND' combination. Therefore, the retrieved data must meet all specified criteria. From now on, this is also the case for the combination of description and note 1.

(Version 23.2.8419.28448) Task 20842 - Make a readonly variant of the order code field without punctuation, only A-Z and 0-9.

By making this adjustment, the search on the order code has been greatly improved. This 'readonly' variant is not visible but is used for searching. It now only searches for A-Z and 0-9, even if an order code contains other characters and/or if a search is performed with a special punctuation mark. This has greatly improved findability.

(Version 23.9.8493.27718) Task 20841 - Order code unique within the same product

An option has been added to RetailVista to enforce a unique order code within the same product. This means that if there are multiple purchase data, an order code can only appear in one of those purchase data. This adjustment ensures that when searching for an order code, the correct (and only one) purchase data can always be found, and not multiple ones. This option should only be enabled after cleaning up existing data from duplicate information.

(Version 22.23.8377.26019) Task 20526 - Ability to click on article number in related products

In the product card for related products, it is now possible to click through to the corresponding related products, and back. The stock, free stock, and forecast stock of the related products are now also displayed as grid columns.

(Version 22.18.8315.27996) Task 20421 - Displaying cost price from recommended price in product maintenance

If a recommended price changes, the date since when that price has been modified is now also displayed.

(Version 23.3.8433.29764) Task 20158 - Ability to set permission for deleting products

A new permission 'MarkProductsDeleted' has been introduced to grant certain users the right to delete products.

Product Lists

(Version 23.19.8657.27398) Task 21181 - Report 182 product list - Locations not displayed

A location is now displayed on this report again.

Thermal Labelling

(Version 23.2.8419.28448) Task 20924 - Discount amount on product label

There was already a field netPcePrice on a product label, but this field did not contain all the discounts that RetailVista knows. The calculation of this field has been improved to match the price field in the cash register.

It should be noted that, for example, relationship-related discounts do not affect this field on a product label. If this label is scanned at the cash register for one item without specifying a customer, loyalty card, or similar, the price displayed by the cash register will be the same as what is stated on the label. If a discount is only active during a certain period, it is also possible that this period has passed at a certain point, making the discount no longer valid.

Exchange

(Version 22.18.8315.27996) Task 20420 - Enable automatic transfer of suggested prices from Exchange

It is now possible to create a separate task schedule so that suggested prices from Exchange are always transferred separately from other data.

Exchange Excel import

(Version 23.10.8501.27680) Task 21047 - Reject and skip duplicate barcode rows

If support for non-unique barcodes is enabled in RetailVista and 2 products are found with a certain supplied barcode in the Exchange Excel import, that Excel row will now be rejected.

Invoicing

(Version 23.18.8629.28627) Task 21251 - Include task scheduler administration email address when sending outbound emails

When sending outgoing email messages through the task scheduler, the BCC field specified in the task scheduler settings was not being copied, causing the BCC function to no longer work. This issue has been resolved.

Financial exports

(Version 23.23.8727.27895) Task 21835 - Integration with ExactOnline

RetailVista ERP can now be linked with ExactOnline. This includes cash journals and sales (invoice) journals, along with an export of debtors to Exact Online.

(Version 23.11.8518.27485) Task 21231 - Adjust export to Afas / Use SaleOrder reference instead of deposit reference

In the export of journal lines to Afas, from now on the reference of the sales order will be exported, instead of the deposit reference. This was actually a bug in the past and should always have been the sales order reference.

Gift card / Gift cards

(Version 23.6.8475.25195) Task 21101 - It is not known whether a digital gift card is being sold

In the gift card type table, it is now possible to indicate that a certain type of gift card is 'digital' (and not 'physical'). This adjustment will be used in a future update of RetailVista to determine which cards need to be manually added to a (webshop) order and which gift cards can be automatically sent to a consumer via email.

Purchase orders

(Version 23.26.8755.29691) Task 21401 - Purchase orders can be sent and set to final without printing.

A new setting has been added to purchase orders that allows a purchase order to be set to final immediately upon creation.

(Version 23.19.8657.27398) Task 21400 - Header can be adjusted without reopening, such as date(s) order-ref and other info

Certain less important data of a purchase order can now be modified, even if the purchase order is final. In addition, the ability to reopen purchase orders has been added.

Goods-in

(Version 24.1.8770.20389) Task 21399 - Discount can be applied to the main article and distributed among the underlying articles

If a discount is given on the receipt value of a main set article, that value will now also be applied to the underlying related set articles.

(Version 23.16.8602.27728) Task 21396 - Able to delete selection rules and not per rule

In product receipt, all selected rules can now be deleted at once.

(Version 23.2.8419.28448) Task 20898 - Receipt can be marked as 'Final'

This is a new status on the receipt which indicates that it is no longer editable, but still open. This is especially desired for purchase invoice control because the corresponding invoice may not have been checked yet, preventing the receipt from being closed as final. However, mutations are prevented in this way.

(Version 23.5.8461.18802) Task 20897 - Permission to reopen closed product receipts

A new permission 'ReOpenClosedReceivedProductHeaders' is now available to allow certain users to reopen closed product receipts.

(Version 22.24.8389.27630) Task 20896 - Permission available to reopen final product receipts

A new permission 'ReOpenReceivedProductHeaders' can be used to authorize certain users to reopen a product receipt that has reached the 'Final' or higher status. Previously, there was no permission to reopen receipts, this has now been made possible.

(Version 22.18.8315.27996) Task 20537 - Receipts receive their own number instead of document allocation

The product receipt worked differently compared to all other modules because it used a so-called 'document' number. This caused various unpleasant side effects while other modules simply use a number. This system has been adjusted in the product receipt so that it now also works with its own number. Of course, there is still support available to add an additional identifier, such as the supplier's packing slip number, alongside the number.

Orderpicking

(Version 24.1.8770.20389) Task 20998 - Generating and printing carriers

In RetailVista, 2 screens have been added under warehouse administration. It is now possible to print stickers of created carriers.

In the carrier maintenance screen, there is an option in the left taskbar to generate carriers.

(Version 23.4.8447.30207) Task 20997 - Virtual carrier lowest number

In the settings of RetailVista, a lowest number can now be specified that is used when creating a virtual carrier.

This number is set to 2500 by default, which means that the first virtual carrier will be assigned number 2500. This allows physical carriers to be created in a range from 1 to 2499 by default.

(Version 23.6.8475.25195) Task 20989 - Improving maintenance of contaminated warehouse locations

The maintenance screen of contaminated warehouse locations has received various improvements, including the ability to click on the article and start article statistics.

(Version 23.9.8493.27718) Task 20812 - Restricting order picking type to transport mode, or vice versa

From now on, it is possible to set the order picking type so that only orders with a specified transport type are eligible, or vice versa, only orders that do not have the specified transport type.

POS

(Version 23.25.8749.27095) Task 21771 - Automatically expire POS terminals

POS terminals can now be set to automatically expire on an adjustable date. This ensures that transaction processing will continue to function when the number of licenses is reduced, provided that the new reduced number of POS terminals matches the corresponding license.

(Version 23.23.8727.27895) Task 21217 - Calculating transaction number per branch instead of per company

From now on, the transaction number is no longer determined continuously per company, but per branch.This adjustment was necessary because calculating a transaction number per company caused too many technical performance issues. The disadvantage of this adjustment is that the transaction number is no longer unique per company, but now unique per branch. Previously, specifying a transaction number was sufficient, but now it must always be done in combination with a branch. Within the RetailVista ERP user interface, a branch is always active, the branch selected in the bottom left corner. This change can cause a problem in BI and other API integrations if matching is exclusively based on company and transaction number. It is therefore advisable to expand it with a branch number, if matching currently works in this way.

Relation Management

(Version 23.25.8749.27095) Task 21830 - Adding revenue type for on-account sales

In the settings of RetailVista ERP, a default revenue type can now also be specified for 'On-account' sales. It is no longer mandatory to specify a revenue type for a relation that is a debtor. The reason for this adjustment is that it does not work well to specify a revenue type for a relation in advance (such as on-account revenue). After all, it is not yet known in what way a relation will make a future purchase. It could just as well be a webshop purchase, for which there is also a default revenue type setting. It is advisable to clear the revenue types for relations and let RetailVista ERP determine the revenue type at the time of sale (cash, on-account, webshop).

Another adjustment has also made it possible to specify a different revenue type per webshop.

(Version 23.4.8447.30207) Task 21037 - Expanding RFM with additional dimension 'Frequency and revenue'

The visit frequency and revenue are now combined into a new dimension/value.The score definition on the other hand does not run from 1 to 5, but from 1 to 10.

In certain situations, steering based on a combination of visit frequency and turnover can yield better results than on separate visit frequency and turnover.

Reservations

(Version 23.25.8749.27095) Task 21935 - HS code support to SendCloud

In the SendCloud integration, HS codes are now also sent for customs deliveries outside the EU. SendCloud does not support multi-collo for these types of shipments. If a package registration is now made for a shipment outside the EU, it will no longer be registered as a multi-collo shipment, but as separate individual shipments. An HS code can be specified for each article in the article maintenance.

(Version 23.24.8741.27342) Task 21881 - Indication that it concerns a pick-up parcel service

From now on, the 'own' RetailVista parcel service is also fully operational. Labels are also printed for packages that are registered with the own parcel service and can be attached to the boxes. For 'own delivery', correct shipping labels with information are also available in this way. In addition, any cash on delivery process (amount to be paid to the delivery person) is also neatly arranged in this way.

(Version 23.26.8755.29691) Task 21880 - Adding condition that all order picking runs are closed for a reservation

By default, a reservation cannot be processed in the pack & ship application if one or more open order picking runs still exist. From now on, there is a setting in the sales order classifications that indicates that a reservation can also be processed with incomplete runs. A notification will then appear in the pack & ship application showing the open runs. It can then be explicitly chosen to continue.If chosen, all open runs will be closed first, after which the packing process will start.

(Version 23.23.8727.27895) Task 21804 - Ability to specify email template for package service

From now on, RetailVista can also send an email when registering a reservation with a package service. This email is sent to the package service relationship, not the original customer of the reservation. This email informs the delivery party about the goods to be delivered. Especially for delivery services that are not affiliated with SendCloud, this is a fairly simple way to automatically inform them digitally about the goods to be delivered.

(Version 23.20.8671.21672) Task 21711 - The packing application should have the ability (configurable) to generate and print invoices

In the RetailVista ERP settings, various settings can now be specified for the behavior of the pack & ship application under 'Logistics'. This adjustment concerns whether or not to automatically print invoices during the pack & ship process.

(Version 23.23.8727.27895) Task 21705 - Add HS code field to product card

For deliveries outside the EU, it is necessary to include an HS code of the items being sold with package services. Therefore, it is now possible to enter an HS code in product maintenance. This can also be imported via Exchange, of course.

(Version 23.19.8657.27398) Task 21700 - Incorrect addition of house number extension to the house number field for SendCloud

For SendCloud, a house number extension (e.g. 3c) should be presented as 3-C. This has been adjusted in the SendCloud integration.

(Version 23.19.8657.27398) Task 21699 - Do not include delivery orders from expired reservations to delivery providers (bumbal)

If a reservation is marked as expired, the task scheduling will no longer create a delivery order from it (unless configured in the sales order scenario).

(Version 23.19.8657.27398) Task 21566 - Add Sendcloud request and response to package registration log if debug mode is enabled

The package service maintenance page now displays a literal representation of the request and response of the communication with SendCloud. This only happens if RetailVista is in debug mode.

(Version 23.21.8685.25412) Task 21403 - Integrate Pack & Ship application into RV

From the 'Reservations' homepage, it is now possible to directly navigate to the pack & ship portal.

In the reservation settings, the URL of the pack & ship portal needs to be provided once.

(Version 23.8.8483.27307) Task 21174 - Ability to scan articles without a carrier

In the RetailVista settings under 'Logistics', it is now possible to indicate whether it is necessary to check articles that are not collected via a carrier within the packing application.

After all, it is still uncertain whether these articles have been picked correctly, as they do not always need to be picked via order picking. However, this control scan also applies to articles that have been picked via order picking but without using a carrier. In that situation, it may still be desired to make sure that the correct articles are being packed.

(Version 23.23.8727.27895) Task 21164 - Add gift card processing to pack & ship application

The pack & ship application can now also handle gift cards properly. This specifically applies to 'physical' gift cards. Digital gift cards are always handled automatically, but for physical cards, it is necessary to scan the corresponding card numbers of the cards. The pack & ship application will now notify about ordered gift cards and support the process of scanning the card numbers and then activating the cards with the desired value.

It is no longer necessary to manually activate gift cards in a cash register environment outside the sales order process.

In the sales order, a separate tab shows which gift card numbers have been sold. If a consumer later complains about not receiving or activating gift cards, it is always possible to find out which gift cards they should be.

(Version 23.2.8419.28448) Task 20935 - Able to create shipping label even if reservation has already been sold

This was not possible before, if a reservation was sold, you could no longer add packages. From now on, this is possible. From reservation maintenance, you can create a package and print it directly on a specified (bridge) printer.

(Version 23.8.8483.27307) Task 20688 - Realize packing application

RetailVista now includes a packing application. This is a separate website that is fully designed to handle order fulfillment very quickly and efficiently. In practice, it often involves handling webshop orders. The packing application takes over the role of RetailVista POS, which was a temporary solution for handling webshop orders. An important difference with RetailVista POS is that the packing application books the revenue from webshop orders 'on account'. For this, a collective debtor can be specified per webshop. The packing application performs a series of routine checks, especially whether a reservation has been fully picked and fully paid. With the packing application, shipments can be registered with SendCloud and ultimately revenue is realized.

In a future update of this application, VIES check support will also be added to verify if VAT exempt orders can be picked up. And a control scan will be added for the picked articles.

This check is done in combination with the packages registration, so it is known which package contains which products. Finally, support for gift card handling will also be added. Digital gift cards are processed directly by RetailVista, physical cards must be scanned in the packaging process and then activated.

Statistics

(Version 23.22.8699.25565) Task 21818 - Comprehensive statistics 400 to 404 does not take into account the branch filter for determining receipts

Statistics 400 includes, among other things, the number of received products. However, it has been found that the active branch from which the statistics were generated was not taken into account. In situations with multiple branches, a total of all branches was displayed. From now on, the branch will be taken into account and only the quantities of the active branch will be displayed.

(Version 23.17.8615.28288) Task 21239 - Expand extended statistics with promotion voucher type filter

In extended statistics, a new filter 'promotion voucher type' has been added. This makes it possible to obtain turnover information based on used promotion vouchers.

Task Planner

(Version 23.13.8559.25975) Task 20848 - Remove global task planning

From now on, there are no more 'global' task plannings. Each task planning must be created per company, with some task plannings being automatically created if the configuration and/or license allows it. The great advantage of this adjustment is that the configuration of such task plannings can now be set by themselves. An additional advantage is that all tasks with their corresponding status can be requested at once per task planning.

As part of this update, all global tasks that existed have been converted to tasks per company. It is therefore very likely that some data has been added to the task planning now.

An important task planning is the retrieval and sending of webshop data, which is now visible and adjustable separately for each company.

Sales orders

(Version 23.20.8671.21672) Task 21749 - Expired sales order line should not go to reservation

If a sales order line is marked as expired, it will no longer be carried over to reservations. If there are already reservations, it must be determined separately whether they will still be delivered or not. Canceling a sales order line is actually no more than a consumer indicating that they no longer want to receive the 'remainder'. What is already in the order picking process will be handled as usual.

(Version 23.24.8741.27342) Task 21714 - Expand sales order deposit status

The sales order deposit status has been expanded with a new value 'Approved'. This concerns 'return' deposits, refunds to the PSP. Furthermore, it is now possible to approve series of refunds. Only from that moment on, they will be automatically offered to a PSP via the task planner. Currently, that is Buckaroo. If the refund is rejected by the PSP for some reason, the status will be changed to 'Rejected'. Afterwards, it is now easy to retrieve the rejected refunds and, for example, repay them via a bank transaction. Another adjustment allows a PAIN file to be created for all pending bank refunds, which can be imported into telebanking.

(Version 24.1.8770.20389) Task 21713 - Generate refund rules based on overpayment in sales order via task planner

If it appears from a closed sales order that there is still an excess of deposits, the task planner can now automatically generate refund rules. In addition to this task planning, another task planning has been created to communicate the created refunds with the PSP (payment provider).

In order to automatically create a refund, we look at open sales orders (final) where everything has been delivered from all non-cancelled sales order lines. If there are still open sales order lines that have not yet expired and need to be fully or partially delivered, no refunds will be issued.

In the sales order administration, a setting has been added with a sales order creation date from which date refund payments can be automatically created. Sales orders created before that date will be disregarded.

Specifying this date is mandatory for the refund rules generation to function. Without this date being filled in, nothing will happen.

(Version 23.21.8685.25412) Task 21712 - Export to Pain001 instructions file for telebanking for bank transfers resulting from refunds

For bank refunds (e.g. if refund via PSP fails), all these payments can now be written to a Pain001 telebanking file at once.

By importing this file into telebanking, all those transactions can be transferred with a single action.

(Version 23.17.8615.28288) Task 21461 - Make it configurable to exclude generating reservations for sales orders with outstanding deposit requests

In task 21155, the behavior for creating reservations has been adjusted. Now, if there are outstanding deposit requests, no reservations will be created.

This is not feasible for everyone. By making it configurable, old and new methods can be used.

(Version 23.12.8531.26329) Task 21260 - If package registration is not accepted by SendCloud, an error message occurs

From now on, when a package registration is rejected by SendCloud, a proper notification will be displayed stating that the package has been rejected by SendCloud, whereas previously only an error message occurred.

The additional information (technical reason) from SendCloud is also mentioned here, so that in consultation with the SendCloud support desk, it can be determined why the package is not accepted.

(Version 23.9.8493.27718) Task 21179 - Add setting to allow mixed sales orders

In the 'Sales Orders' settings, it is now possible to set that mixed sales orders (orders with both positive and negative quantities) are allowed again. In previous versions of RetailVista ERP, this was also allowed, but since the last update, it was no longer possible. It is still preferable to create separate credit sales orders for return items, but the obligation is no longer present. The reason to continue working with separate orders is mainly related to digital (guided) order picking: this form of order picking is (of course) not able to pick negative sales orders, resulting in an order not being able to be fully picked. It is also not possible to process only a return line if there are also positive lines in that sales order, then a sales order remains open pending the processing of those positive lines. Another and final disadvantage is that return lines should not actually lead to a new negative sales order: There is now a full-fledged return administration available where return items are taken back linked to the original sales order. With this new setting and the earlier adjustment made, it is standard prevented that negative quantities can be entered.

(Version 23.25.8749.27095) Task 21178 - Sales order smart tagging

From now on, RetailVista ERP includes an allocation calculation in the webshop sales order processing. Based on various specified criteria, both the type of transport and the sales order classification can be influenced. It is also possible to only adjust one of these two.

18802) Task 20870 - Make it configurable that closed sales orders cannot be reopened

There is a new permission 'AllowReopeningClosedSaleOrders' that can prevent closed sales orders from being reopened.

(Version 23.7.8479.37464) Task 20756 - Introduce sales channel in RetailVista

Under a webshop, multiple sales channels can exist. An example of this is a marketplace like 'EffectConnect' that serves sales channels such as Fonq. RetailVista recently integrated with EffectConnect, where EffectConnect is the webshop in RetailVista. In a sales order, it is desired to be able to see that an order originated from, for example, Fonq while the webshop is still 'EffectConnect'. For this reason, sales channels have been introduced in RetailVista. This can be seen in the sales order itself. The uniqueness check whether a webshop order has been received before has been expanded from the combination of webshop and order reference to webshop, sales channel, and order reference.

In the fall 2023 update of RetailVista ERP, it will be possible to create revenue reports based on sales channel.

(Version 22.19.8333.18802)24680) Task 20755 - Order picking active on reservations from a certain date

In the sales order classification, it is now possible to set that order picking should only apply to reservations created after a certain date and time. This allows order picking to be introduced at any point in time, with reservations before that moment being ignored.

(Version 22.19.8333.24680) Task 20754 - Create advanced webshop setting to convert based on transport type to a sales order classification

See QA827

(Version 24.1.8770.20389) Task 20752 - When entering sales order lines, it is now incorrectly allowed to give a higher discount than the gross unit price.

A higher discount amount than the gross unit price is no longer allowed from now on.

Inventory / Stock control

(Version 23.25.8749.27095) Task 21886 - Excel export of stock mutations

In stock maintenance, it is now also possible to start an export to Excel of stock mutations.

(Version 23.23.8727.27895) Task 21885 - Introduce checkbox for processing inventories

When processing inventories, they are no longer deleted afterwards but marked as 'processed'.

(Version 23.5.8461.18802) Task 21001 - Virtual stock improvements

The virtual stock is no longer shown separately in article statistics but is simply the stock and free stock. It is no longer possible to modify the stock of a virtual article.

Webshop

(Version 23.23.8727.27895) Task 21889 - Add optional revenue type field to webshop maintenance

For each webshop, an optional revenue type can now be specified. Sales resulting from orders on that webshop will then be booked to that revenue type. Another mutation has also been made, allowing a general revenue type to be specified for all webshops. The advice for this adjustment is to clear the revenue types for relations.

As long as that doesn't happen, that type of revenue always takes precedence.

(Version 23.21.8685.25412) Task 21783 - Ability to indicate alternative inventory to be sent to the webshop

From now on, it is possible to indicate in the webshop configuration that alternative inventory levels may also be sent to the webshop. Currently, this functionality is only implemented in the Magento2 integration.

(Version 23.25.8749.27095) Task 21782 - Export inventory levels from all other locations to webshops

RetailVista ERP is now able to additionally send inventory from other locations to webshops. Currently, this functionality has been added to the Magento2 integration.

(Version 23.21.8685.25412) Task 21770 - Support Sendcloud pickup locations

From now on, the pickup point functionality present in RetailVista will also be correctly passed on to SendCloud for sales orders.

(Version 23.25.8749.27095) Task 21687 - Support VAT exempt orders to consumers outside the EU

From now on, RetailVista ERP supports delivery of sales orders to countries outside the EU. These countries are automatically delivered exempt from VAT, but without a VAT number.

In the country table, it is now possible to indicate for each country whether it is located within or outside the EU. This determines the permission for VAT exemption.

At the same time as this adjustment, it is also possible to indicate for a debtor that VAT exemption checks may be ignored. This specifically applies to the check for a valid VAT number.

This adjustment is intended for diplomats and other special professional groups who are allowed to receive VAT exempt deliveries even within the EU.

The webshop must indicate whether an order is VAT exempt, RetailVista follows the webshop, the webshop is 'leading'.

27895) Task 21160 - Adding support for bank transfer when importing webshop order message

If a customer now chooses to make a bank transfer, the request to webshop parties has always been not to send the order to RetailVista. However, this has proven to be inconvenient because an accountant cannot credit the received payment in RetailVista. Also, the order is not known in RetailVista, so if a customer calls with a question about the order (or wants to make a change, for example), it cannot be done. For these reasons, it is now possible to add an indication in the webshop order message that a payment will follow, with a specified amount. This information is used to create a deposit request with that amount when creating the sales order. The order will only be converted to a reservation / processed once the deposit request has been paid.

(Version 23.23.8727.27895)27895) Task 21052 - Adding support for pickup points in sales order and webshop order message processing

In the webshop order message, it is now possible to add a pickup point. Based on the received pickup point name, postal code, and house number, RetailVista checks if there is a relationship as a pickup point with those details. If that is not the case, the relationship is automatically created. Ultimately, the number of the found relationship is taken over as the delivery address relationship.

(Version 23.8.8483.27307) Task 21042 - Adding support for Intracommunity supplies (ICL) to webshop orders

From now on, RetailVista offers the possibility for ICL deliveries. These are VAT-exempt deliveries to debtors abroad. The fiscal condition for ICL deliveries is that a VAT number is known and that the number is valid. The VAT number can now be included as part of the webshop order message. RetailVista will check during order message processing if a debtor is already linked to the corresponding relationship. If this is not yet the case, it will be checked if a debtor exists with the specified VAT number. If this is also not the case, a debtor will be created with that VAT number. During creation, the debtor is set to require full payment. The indication of whether the debtor receives VAT-exempt delivery depends on the delivery address country of the order compared to the country of the branch where the order is created.

If a debtor is already linked to the relationship, it will be checked if the VAT number matches the order. If this is not the case, the order message will be rejected. If it turns out that the debtor does not yet have a VAT number in the relationship, this number will be taken over from the order.

It is now assumed that the VIES check has already been performed by the webshop and that the VAT number is valid. In a future update of RetailVista ERP, this check will be performed (again) by RetailVista and it must yield a positive result. The VAT number should not only exist, but the debtor's name must also match the registered VIES name.