Release notes RetailVista update November 2016 v.16.30

General / miscellaneous

Version 16.28.6143.25791 Task 16318 - Localizing revision of file names

The various file names that arise when downloading reports, statistics, and various exports used to be very messy, not always in Dutch, etc. This has been changed everywhere to correct naming. 

Product maintenance

Version 16.28.6143.25791 Task 16350 - Please also show the 'own purchase price' in the product search results

In the product search results, the 'own' purchase price can now be chosen as a column.

Version 16.27.6135.23246 Task 16283 - Please show the selling price from the product in the detail window of scheduled selling price, see binaries

In the detail screen of the scheduled selling price, the normal gross selling price of the product is now also shown for information purposes.

Version 16.28.6143.25791 Task 16152 - When purchasing given (detail info field), please also mention the total number of units in a package

In the purchase data grid in the product card, the total number of consumer units of that package is now also shown in the 'Purchase details' column.Previously, for example, '4 boxes of 2 pieces' was shown and you had to calculate that it is 8 consumer units. From now on, it will say '4 boxes of 2 pieces (8)'.

Version 16.26.6128.15470 Task 16062 - Please realize percentage support in purchase information between gross and net

In the purchase data of a product, a discount percentage can now be specified between gross and net. By specifying a discount percentage, the net field is blocked for mutation and always calculated. This possibility can be useful if agreements have been made with suppliers about a specific discount based on the standard gross (list) price. The discount percentage is per product (per purchase data).

Version 16.15.6004.28510 Task 16021 - Margin% in article search results is not shown

In the search results in the article search screen, no value was shown in the 'margin%' column. This error has been fixed.

Version 16.24.6107.18212 Task 16020 - Ability to display purchase price comment field in article search screen

In the search results in the article search screen, the 'purchase price comment' can now also be chosen as a column. This column was missing as a selectable column.

Version 16.15.6004.28510 Task 15978 - When adding purchase data from RV, suggest the default purchase status

When creating a purchase line for an article, the default purchase status is now suggested by default. The default purchase status can be set via settings, section 'Articles'.

Version 16.12.5987.28030 Task 15947 - Also able to import net unit price in article list Excel import

In the article list Excel import, the 'net' price can now also be imported as a column.

Version 16.8.5941.28510 Task 15733 - Scheduled sales prices can be activated by the store itself earlier

Scheduled sales (and purchase) prices can be automatically activated overnight. However, it is also possible to manually perform the posting. From scheduled sales prices, you can choose to post the available data in the left taskbar. It is now possible to indicate that scheduled activations that are further in the future, will also be made active. By default, the date is filled in with the system date. However, by shifting that date to the future, more scheduled data will be eligible for processing.

Version 16.7.5934.20806 Task 15618 - Ability to set default sales quantity to 2 decimals

From now on, decimal values can be specified for the default sales order quantity.

Product Lists

Version 16.29.6149.29238 Task 16320 - Retrieve price from barcode for classic price barcode (XXYYYYYPPPPPC) and regular barcode in various modules

When adding a product in, the product list, the price was not taken from the barcode. In the case of a classic price barcode (where the price is part of the barcode number), the price had to be determined from that barcode, and for new style price barcodes, the price had to be retrieved from the record of the respective barcode. This issue has been resolved in, among others, product lists and Excel imports.

Version 16.28.6143.28510 Task 15836 - Non Sale products history not showing graph in product statistics

For non-sale products, we also print a graph from now on in product statistics.

Task 25791 - Product list imports do not take into account the specified barcode

When importing a scanner, the scanned barcode from the handheld scanner is now also saved with the product list item.

Version 16.15.6004.28510 Task 15965 - Ability to import CSV or Ascii file according to scanner definition

It is now also possible to import a file from a scanner into a product list. This can be a CSV or an SDF file. A new scanner can be created under Administration, Scanners with the type 'Ascii file' or 'Comma separated file'. An Ascii file contains barcode, price, and quantity at fixed positions. In the scanner definition, it can be indicated for each of these 3 fields where the field starts and how long it is. In a comma separated file, these data are located in different columns, separated by a , symbol. In the scanner definition, it can be indicated in which columns these 3 data are located.

Then go to Product Lists -> Import product list from file or select an existing product list and choose 'Import text file' in the left menu 'Import tasks'.

In the screen that appears, specify the file to be imported and select the scanner that contains the correct file definition. The file will then be imported and a report will be made available after the process is completed.

Version 16.24.6107.18212 Task 15958 - Expand export capability of scheduled price changes to product list

From scheduled selling prices, an export can now be made to a product list.

Authorization

Version 16.29.6149.29238 Task 16388 - Password reset does not work

Requesting a new password through 'forgot password' did not work correctly, this issue has been resolved.

Version 16.29.6149.

29238 Task 15512 - Enter security schema (authorization intermediate layer)

From now on, it is possible to link users to one security role. Previously, one or more user groups had to be linked to each new user. This was quite a lot of work and there was a high risk that certain users who perform the same role would have different rights in practice. By now working with security roles, for example, a role 'store employee' can be created. The user groups must be linked to that role once. After that, it is only necessary to link a new user to the 'store employee' role, after which that user has the correct rights. The security role can be linked to the user in the 'Security' tab.

EDI

Version 16.17.6019.13876 Task 16078 - If CPS rule is not present, consider first LIN rule as segment 1

When booking an EDI delivery note, the 'CPS' rule normally indicates that the header of the message is finished and that the rules are started. However, there appear to be delivery notes where this code is completely missing. RetailVista did not start booking the rules in these cases. From now on, in the absence of this rule, the first found 'LIN' rule will be considered as the start of the existing rules in a delivery note message.

Version 16.14.5998.20925 Task 15269 - Revision of EDI processing desired

The EDI processing in RetailVista has been rewritten. The new operation assumes that rules or fields that RetailVista does not recognize will simply be ignored from now on. Previously, RetailVista could crash hard on a single field or rule with incorrect information. Furthermore, RetailVista now tests all EDI rules first and displays a status 'Ok', 'Warning', or 'Error' for each rule in the processing report. Rules with warnings do not result in rejection of the message, rules with 'Error' do.

When warnings and errors occur, a clear explanation of what went wrong is provided, including a reference number to the GS1 Edifact documentation.

In the settings of RetailVista, the EDI usage can be set between version 1 (old) and version 2 (new). This setting is temporary and is intended to quickly switch back to the EDI behavior in previous versions of RetailVista if the new approach does not function properly. In the next release of RetailVista, the old functionality will be completely removed if the new functionality proves to be correct. In the rollout of RetailVista, everyone will initially still work with the old behavior, and NedFox will activate version 2 over time.

Labeling

Version 16.27.6135.23246 Task 16334 - Prompt for reference date when printing labels from print queue

When printing labels, a reference date can now be specified. RetailVista will then take into account any scheduled prices. The reference date indicates from which date the prices should be printed on the label. For example, it is possible to specify January 1st as the reference date so that the labels already display the prices that will be effective from January 1st.

Version 16.26.6128.15470 Task 16213 - Better support branch selection during printing and selecting from print queue

When printing data from a print queue, the branch for which the data should be printed is now taken into account correctly.

Version 16.27.6135.23246 Task 16201 - The barcode specified in the article list should be printed

When printing report 96, the scanned barcode will now be printed if it is used to add the item to the article list. If no scanned barcode was used, the default article barcode will be printed.

Version 16.16.6011. Product 38240 Task 16024 - Asking a question after printing labels from the print queue

When printing labels from the print queue, a question is now asked after printing is completed to confirm if the printing was successful. From that moment on, the print queue lines are removed.

Version 16.27.6135.23246 Task 16017 - Reporting needed for print queue and scheduled selling prices

Reports can now be printed for both the print queue and the scheduled selling prices.

Version 16.18.6024.36255 Task 15980 - Expand print queue functionality with scheduling support

The article print queue now also includes support for scheduled prices. In the RetailVista settings, it can now be configured that when a scheduled selling price is created, it should also be added to the print queue. The print queue has a 'Date' column indicating the scheduling date. By default, only the print lines that are currently within 7 days are displayed in the print queue. For example, a scheduling that becomes active on January 1st will not be shown in the print queue in early December.

Version 16.13.5991.26961 Task 15979 - Encode purchase status code and description on a thermal label

The purchase status code and description can now be printed on thermal labels. The fields created for this purpose are called 'purchasestatuscode' and 'purchasestatusdescription'. Furthermore, QA303 has been expanded with these 2 new fields.

Version 16.24.6107.18212 Task 15960 - Perform 'quantity mapping' for label classification

In the maintenance of an article list, 'quantity mapping' can now be used. This means that for a label classification, a value can now be specified for 'mapping quantity'. By specifying '5' for a label classification, the number '5' can be entered in one or more lines in the product list afterwards.

By selecting 'Apply product list translation' in the left taskbar, RetailVista will set the label classification of all products with a quantity of 5 to the label classification where 5 is also specified as the value. Furthermore, it can be specified in the same screen that after processing that value, the quantity of the line will be adjusted to 1.

The practical application of this adjustment is mainly in reading 'dumb' handheld scanners. With these scanners, a product can be scanned and the type of label to be printed can be indicated in the quantity field using this value. For example, a '5' could be a shelf label. After reading the scanner into the product list, the above screen can be started to transfer all product classifications. Finally, in 'advanced search' in the product list, lines can be displayed for products with a specific label classification. For example, only display the products with label classification 'shelf label'. Then, by printing labels, only products for which a shelf label is desired will be printed, and other types of labels (such as slot labels) will be ignored.

Exchange general

Version 16.29.6149.29238 Task 16312 - Make M3 field available in purchase regardless of container administration license

The 'M3' field in the purchase data is now always visible, regardless of whether or not a container administration license is present.

Version 16.26.6128.15470 Task 16196 - Standard sales quantity does not support -1 in Exchange Excel import

The 'standard sales quantity' column can now also be imported from Excel into Exchange with the value -1.

Version 16.21.6033.26967 Task 15843 - Exchange import is not posted because VAT code does not exist

In the Excel import in Exchange, it is now directly checked whether a VAT code exists in RetailVista. If this is not the case, it will be rejected immediately in the processing report. Previously, this only happened during the posting from Exchange to product maintenance.

Version 16.23.6079.22485 Task 15705 - Excel template gives errors because the style is not unique

The export of statistics to Excel using a template has been adjusted. Sometimes things went wrong if the template already contained certain formatting elements.

Version 16.13.5991.26961 Task 14949 - Suppliers can be completely excluded from exchange

In supplier maintenance, it is now possible to indicate in the 'Advanced' tab that a supplier is completely excluded from Exchange mutations. This concerns the field 'Ignore product mutations in Exchange'. By marking this field, a product mutation will not be placed in Exchange if this supplier is the preferred supplier for that product.

Furthermore, the purchase information screen indicates that any product mutations for this supplier will be ignored.

Version 16.27.6135.23246 Task 7400 - In Exchange, please show information about what will be changed

By opening an Exchange mutation rule (for example, by double-clicking or the 'show' icon), it is now visible which data is different. This is divided into several sections, including product differences, purchase differences, etc.

Exchange Excel import

Version 16.26.6128.15470 Task 16281 - When importing Excel into Exchange, be able to indicate what type of purchase prices are used

Until now, purchase prices per consumer unit were always assumed. From now on, it is possible to indicate the type of purchase price during the import. The choice in this case is per consumer unit, per packaging, or per purchase packaging. The suggested default value is the same as when creating a new purchase data and comes from the default purchase settings in the RetailVista settings.

Version 16.15.6004.28510 Task 16027 - Importing purchase status

Through the Excel import in Exchange, the purchase status can now also be read in as a column.

Version 16.7.5934.20806 Task 15783 - After importing Excel file in Exchange and assigning barcodes to the file, please return correct naming and extension upon download

After importing an Excel sheet in Exchange, it can be set to automatically generate a download of the same file, with the barcode generated by RetailVista added as a column. However, this download resulted in an incorrect file name. This has been fixed.

Billing

Version 16.26.6128.15470 Task 16282 - Allowing 0% storage percentage

RetailVista did not accept 0% as a storage percentage on the purchase price. This has now been adjusted so it can also be delivered at a 1:1 ratio to the purchase price.

Version 16.24.6107.18212 Task 16183 - Showing delivery note and/or invoices in supplier search screen when choosing a relationship

When sending EDI delivery notes and/or EDI invoices, clicking on the magnifying glass next to the 'relationship' field incorrectly displayed the supplier search screen. This has been resolved.

Version 16.26.6128.15470 Task 15504 - Digital invoicing from RetailVista

From now on, it is possible to invoice digitally from RetailVista. To enable this, it must be indicated to a debtor that they want to receive the invoice digitally. This can be done in the 'Digital' tab under the 'Digital invoice' option. The email address to which the invoice should be sent must be entered in the field below. For debtors who prefer not to receive a digital invoice, a surcharge can be automatically added to a product. The specification of the surcharge article is also possible in the same tab. However, the implementation of this surcharge will only be added to RetailVista in 2017.

Now print a trial invoice for this debtor, and then choose to send invoices. Invoices that need to be sent via EDI and/or email will now be automatically sent by the task scheduler of RetailVista. The invoice layout that is used can be specified in Settings, General section, 'Reporting tasks' tab. Optionally, a different invoice layout can be specified for the debtor in the 'Layout' tab.

If desired, the status of the invoice delivery can be tracked via the task scheduler of RetailVista through Extras, Task scheduler. There is a task 'Generate PDF report' and by opening that task schedule, it can be requested in the 'Execution' tab which tasks have been executed or still need to be executed.

An invoice will now be received by email. In the invoice itself, it can be seen in the 'Export' tab at what times an invoice was sent by email. Each invoice PDF can also be downloaded there again.

The sender email address is now noreply@retailvista.net. In the next version of RetailVista, this will be adjustable. The email text itself is used as the email template as specified in the task scheduler. By specifying that new template in the task scheduler, that email will be sent.

Gift Card

Version 16.14.5998.20925 Task 15924 - Removing gift card licensing on gift card CALS from RetailVista

The licensing model for gift cards has been adjusted in RetailVista. Previously, a license was required for each 'brand' gift card. This is no longer the case: a license is still required for each gift card provider. If one gift card provider offers different brands of gift cards, they can all be processed within RetailVista without the need for additional licenses.

Version 16.9.5963.28000 Task 15750 - License check also included in gift card maintenance

Due to a change in gift card licensing, from now on, the availability of sufficient gift card CAL licenses will be checked for gift card types. Each active (non-expired) gift card type requires a gift card CAL. Previously, a license had to be obtained for each 'brand' gift card.

Purchase Orders

Version 16.26.6128.15470 Task 16265 - Deleting a purchase order with associated sales orders now displays an error message

Deleting a purchase order that is linked to sales orders no longer displays an error message.

Version 16.26.6128.15470 Task 16258 - Do not suggest CBM -1 when determining purchase information in a purchase order line if there is no CBM

From now on, when creating purchase information, -1 will no longer be suggested as CBM (M3) if there is no M3 information available.

Version 16.20.6031.28542 Task 16119 - Incorrect total amount calculated when importing article list and recalculating purchase order

Sometimes an incorrect total amount was calculated when importing an article list into purchase orders. This only occurred when using purchase prices per packaging. This issue has been resolved.

Version 16.24.6107.18212 Task 16094 - Ability to specify default purchase order classification

In the 'purchase orders' settings of RetailVista, it is now possible to specify a default purchase order classification. This classification will be suggested by default when creating a purchase order.

Version 16.9.5963.28000 Task 15913 - Ability to specify purchase invoice relationship and delivery relationship information at branch

When printing a purchase order, there was a need to specify an address/email/phone block where the purchase invoice should be sent, and a similar block where the order should be delivered. For this purpose, the dataset of the purchase order has been expanded. Furthermore, the relationship numbers can now be specified in the branch information.

Version 16.9.5963.28000 Task 15911 - Adding buyer user assignment to purchase order

When creating a purchase order, a purchase order employee can now be specified. If desired, this employee can also be mentioned in the purchase order report. For suppliers, this indicates who they should contact if more information is needed for a specific order. However, EDI purchase order messages do not provide the ability to include this information.

Version 16.7.5934.20806 Task 15376 - The preferred supplier of the article is shown in the 'Purchase Orders' tab of the article statistics, but not the supplier of the purchase order

In the 'Purchase Orders' tab of the article statistics, the preferred supplier of the article was shown. A new column has been added to display the supplier of the purchase order.

Version 16.17.6019.13876 Task 15073 - Generating purchase order, sales order must lead to 1:1 purchase order

In the settings, 'Sales Orders' section, 'General' tab, it is now possible to choose 'Generate Purchase Order' to generate a purchase order per sales order. The sales order is still split per supplier, but different sales orders with the same suppliers are not merged into 1 purchase order per supplier. Each sales order leads to at least 1 purchase order. In some situations, this behavior may be desired.

Version 16.11.5977.27869 Task 15072 - Purchase order by email to supplier (save purchase order as PDF and send directly by email)

From now on, purchase orders can also be sent to suppliers by email. In the supplier's 'EDI' tab, it can be indicated that the default communication type is 'Email' and the 'Email address' field can be filled in with the email address to which the order should be sent. From this moment on, it works the same as with EDI suppliers: once a purchase order is finalized, it can be sent via 'Send purchase orders'. RetailVista will then determine whether it should be an Email or an EDI message. Depending on the settings, it is also possible to have this sending process automatically triggered when approving the final print.

Once a purchase order is electronically sent (Email or EDI), it will be visible in the purchase order itself in the 'Export date' field.

Version 16.28.6143.25791 Task 14936 - Consider purchase prices on delivery date for purchase orders

For purchase orders, a price level date can now be specified. If filled in, when adding lines to the purchase order, the scheduled purchase prices will be taken into account. For example, by specifying January 1, 2017 as the price level date, the system will determine the purchase price for that date. If there are multiple scheduled purchase prices, it will determine which of those prices would apply as of January 1.

With this adjustment, it is possible to create orders with prices that will only apply from January 1 of the following year. This ensures the accuracy of the purchase value.

Cash accountability

Version 16.26.6128.15470 Task 16189 - An error occurs when deleting a cash accountability with 'Complete' status

From now on, cash accountabilities with 'Complete' status cannot be deleted.15470 Task 16052 - Number of columns missing in received product grid

The following columns have been added to the received product line grid. This makes it easier to check a purchase invoice through a receipt, in situations where no credit purchases are used.

VAT percentage (VatPercentage)

VAT code (VatCode)

VAT description (VatDescription)

VAT amount (TotalVatPrice)

Purchase price note (from purchase information)

 (OwnPurchasePriceNote)

Total gross purchase price (TotalGrossPurchasePrice)

Total net purchase price (TotalNetPurchasePrice)

Version 16.16.6011.38240 Task 16052 - Number of columns missing in received product grid

In the received product line grid, the following columns have been added. This makes it easier to check a purchase invoice through a receipt, in situations where no credit purchases are used.

VAT percentage (VatPercentage)

VAT code (VatCode)

VAT description (VatDescription)

VAT amount (TotalVatPrice)

Purchase price note (from purchase information)

 (OwnPurchasePriceNote)

Total gross purchase price (TotalGrossPurchasePrice)

Total net purchase price (TotalNetPurchasePrice)

Version 16.16.6011.38240 Task 16052 - Number of columns missing in received product grid

In the received product line grid, the following columns have been added. This makes it easier to check a purchase invoice through a receipt, in situations where no credit purchases are used.

VAT percentage (VatPercentage)

VAT code (VatCode)

VAT description (VatDescription)

VAT amount (TotalVatPrice)

Purchase price note (from purchase information)

 (OwnPurchasePriceNote)

Total gross purchase price (TotalGrossPurchasePrice)

Total net purchase price (TotalNetPurchasePrice)

38240 Task 16026 - Reporting for unordered products

In report 51 for product receipt, it is now possible to set a filter to print only those products that have been ordered or not ordered via a purchase order. This makes it possible, for example, to print a list of products that have been received but not ordered.

Version 16.24.6107.18212 Task 15966 - Taking into account the existence of price barcodes when reading Desadv message

When reading an EDI packing slip, it is now also possible to use 'traditional' price barcodes. These are barcodes where the price is part of the total barcode.

Version 16.21.6033.26967 Task 15780 - The mutation history in received product does not work

Previously, the received product list was mutated by choosing 'record history'. This issue has been resolved, and the history is now visible.

Version 16.7.5934.20806 Task 15706 - Incorrect functioning: when booking EDI packing slip with collections, the inventory of the set/display itself is also booked

Collection items (the display itself) will now be ignored, and no inventory will be booked for them. The idea is that the inventory of the components of a display should be recorded (which was already the case). By booking the display itself in inventory, an incorrect (too high) inventory value is created. This is no longer the case from now on.

POS

Version 16.29.6149.29238 Task 16197 - Assigning a POS terminal to a group

From now on, a POS terminal must be assigned to a group of POS terminals. For example, all central cash registers can be linked to one combined group, so that various settings are always the same for all those cash registers. An important example of this is the layout, it is now sufficient to adjust the layout of one group, after which all linked POS terminals will have that layout.But also other settings have been moved from POS terminal maintenance to POS terminal groups, such as calculating direct discounts, printing receipts, keyboard, numlock status, etc.

During the installation of the RetailVista update, groups of existing POS terminals are automatically created. Attention is paid to the combination of settings that are the same for POS terminals. Groups are created from these settings and assigned to the corresponding POS terminals. The only thing the update cannot do is provide a clear description. For this reason, the groups are numbered from 1 to the number of groups that are automatically created. It is recommended to give each group a recognizable name after the update.

Version 16.24.6107.18212 Task 16194 - Rejected transactions in Ex VAT due to VAT rounding

When working with RetailVista POS ex VAT, rounding differences could still occur, causing a transaction to be rejected. This issue has been resolved.

Version 16.15.6004.28510 Task 15970 - Sending luxury purchase invoice directly to the consumer instead of a receipt

In the 'Purchase confirmation' settings at the location, it is now possible to set that a PDF should be sent directly to the consumer via email. This can be a PDF receipt or the PDF of the luxury purchase invoice. An adjustment has been made in the cash register so that when closing the transaction in this case, an email address is requested where the consumer wants to have the receipt sent. If a purchase confirmation email address is already known for a relationship, this question will not be asked at the end.

Version 16.28.6143.25791 Task 15925 - Retrieving receipts or EFT receipts in a period

In the 'Point of sale' homepage, it is now possible to choose 'Retrieve receipts'.

With this, all receipts and/or EFT receipts can be requested in one file, for example for verification in case of EFT differences. (EFT = Electronic Fund Transfer, electronic payments / formerly also known as PIN payments).

Version 16.22.6054.22959 Task 15752 - Processing a deposit from another location now results in rejection

Deposits at a location other than the location where a sales order is created are no longer allowed. This causes various problems in transaction processing.

Version 16.13.5991.26961 Task 15416 - Add 'Time Difference' column in POS transaction screen

In the POS transaction overview screen, a 'time difference' column is now shown by default. This column displays the number of minutes between the transaction date/time and the date and time the transaction was received in the RetailVista cloud environment. If the time is greater than 0 minutes, it indicates that there were likely internet issues causing the transactions to not be received in the RetailVista Cloud within a few seconds. The consequences of this can be visible in the cash reconciliation, among other things.

Version 16.22.6054.22959 Task 15324 - Also save specified return reason text in CashSaleRows

The optionally specified free text for a return in RetailVista POS will now also be saved in RetailVista. From now on, on statistic 236, both the selected return reason and the optionally specified free text will be displayed in the form of 2 visible columns.

Version 16.15.6004.28510 Task 14890 - Please save email address with transaction

RetailVista is able to send a purchase confirmation (thank you for your purchase) email message. Currently, this only works for relationships for which an email address is known. Due to this task, RetailVista POS will now ask for an email address when closing a transaction.26961 Task 14422 - Create and integrate return authorization table in RetailVista POS

In the settings, Point of Sale section, 'Returns' tab, it is now possible to activate return approval. By activating return approval, customers must register their returns in advance. When a customer returns to the store with items, those items must already be registered with a pre-notification. The pre-notification itself can now be done in the back office via Start -> Point of Sale -> Return pre-notifications. Within RetailVista POS, users will be prompted to select a pre-notification for returns. If the pre-notification does not exist, the items cannot be returned. This functionality is especially relevant when working with RMA systems, as customers must register in advance what they will be returning or sending back.

Version 16.7.5934.20806 Task 14421 - Returns should go directly to the return administration.

From now on, it is possible to directly place returns in the return administration in RetailVista POS. This means that an item briefly appears in stock and is then immediately removed from stock and transferred to the return administration. By optionally removing an item from the return administration afterwards, the item will be returned to the stock.

Promotions, discounts

Version 16.26.6128.26961

15470 Task 16244 - Punctuation marks, such as an apostrophe, are not supported in the description of customer groups

Punctuation marks can now also be used in customer group descriptions.

Version 16.26.6128.15470 Task 16198 - Transferring article list to mixedmatch does not take into account line selection

When transferring an article list to mixedmatch articles, any selected lines in the article list will now be taken into account. In that case, only those lines will be transferred.

Version 16.28.6143.25791 Task 16018 - Ability to set default discount type when creating an article discount

In settings, under the 'Promotions' section, the default discount type can now be set when creating a new article discount. By default, it works with a 'tiered' discount, but if, for example, 'markdown' is used more frequently, it can be set here that the type 'markdown' is suggested when creating a new article discount.

Version 16.21.6033.26967 Task 15707 - MixedMatch with multiple columns

A mixedmatch with multiple columns is not yet possible in RetaiVista. Such mixedmatches are now also rejected in the business layer.

Version 16.11.5977.27869 Task 14951 - Working with price barcodes for mixedmatches

From now on, barcodes can be used for mixedmatches. This can be either the 'old' price barcodes (where the price is part of the barcode) or regular barcodes of an article. The mixedmatch will only work if that specific barcode is also scanned.

Version 16.12.5987.28030 Task 14415 - Trends and trade suppliers should be able to specify discounts for their customers

From now on, a customer group can also be specified for a price agreement.By doing this, offers from that price agreement group will only be provided to relationships assigned to this customer group.

Version 16.11.5977.27869 Task 14389 - Link promotion voucher to 1 specific discount

From now on, RetailVista supports 'sticker application'. To be able to use this, it is important to first create a type of voucher. Specify that this type of voucher is valid for 1 sales line. Then create the desired vouchers and link each voucher to the previously created type of voucher. After that, the articles to which the promotion should apply can be searched for. For each article, an article offer can be created, where the previously created type of voucher must be assigned as the voucher type.

Synchronize the cash register now and first scan the voucher and then the article to which the voucher belongs. (In fact, the article on which the voucher is applied by the consumer). This article will now receive the assigned discount, provided that the voucher is applicable to that article. It is allowed to apply a different voucher to a different article, the use of vouchers is not limited to only one voucher per transaction.

Reports

Version 16.10.5968.26181 Task 15916 - Integrate localization editor into report builder

From now on, custom reports can also be provided with translatable texts. Until now, this was not possible, only the language files of RetailVista were supported. It was possible to place fixed custom texts, but in a multilingual situation, they were not translated. By starting the report designer now, there is a button 'Language' in the top left corner. The active language can be selected there. It is also possible to add languages that are currently not part of the report (NedFox currently only provides en-US, en-GB, and nl-NL).

After selecting an active language, the 'Text' properties can be changed everywhere to the text that needs to be displayed in the active language. This is clearly visible by modifying a text and then choosing a different language. The 'text' properties will suddenly show different texts.

This modification is available in both the reporting designer in RetailVista POS and in the backoffice Report designer.

Version 16.23.6079.22485 Task 15813 - Hiding report indication does not work properly in report maintenance

Reports can be hidden in RetailVista via Extras, Reports. However, the checkbox for 'hide' was not always saved correctly. This issue has been resolved.

Relationship maintenance

Version 16.27.6135.23246 Task 16271 - Allow VAT exempt checkbox to be placed for countries

It is now possible to indicate whether VAT exempt delivery is allowed for a country. This field now only has consequences in the transportation declaration app in RetailVista Mobile. Further processing and consequences of this field within RetailVista will follow at a later time.

Version 16.9.5963.28000 Task 15863 - Default communication type is derivable but GUI does not release this field

For a supplier that is derived, the communication method can now be set.

Version 16.8.5941.36111 Task 15850 - When searching for a relationship from a webshop order, please search based on a combination of postal code and email address

When searching for a relationship upon receipt of a webshop order, it now searches for the combination of email address and postal code at once. If it exists multiple times, the most recently modified relationship is used. Previously, the search was slower and usually linked to the oldest modified relationship.

Version 16.26.6128.15470 Task 15651 - Ability to set email address for debtor digital Invoicing

Prior to task 15504, it is now possible to register an email address for a customer in order to facilitate future digital invoicing. This functionality allows customers to make preparations for when digital invoicing is officially released in 2016.

In addition to the email address, one or more CC or BCC email addresses can now be provided to send a copy of an invoice.

Reservations

Version 16.8.5941.36111 Task 15075 - Reservation message to customer that reservation can be picked up (date message sent, number of messages sent)

Automated email messages can now be sent to consumers regarding an open reservation. This occurs automatically when a task is created in the task scheduler to notify reservations via email. This will be configurable in the next version of RetailVista.

Whether a message has been sent is visible in the 'General' tab of the reservation, where the date and time of the 1st, 2nd, and 3rd notification are displayed. The number of times a reservation is sent will be configurable in the next version of RetailVista.

Returns Administration

Version 16.7.5934.20806 Task 11587 - Return packing slip reporting

In the returns administration of RetailVista, an A4 proforma packing slip can now be printed. This can be sent to a supplier, for example, via fax to indicate what is ready to be picked up.

Statistics

Version 16.24.6107.18212 Task 16144 - Instructed mode invoices are processed

Account invoices created through RetailVista POS in 'instructed mode' were mistakenly being processed. This is no longer the case.

Version 16.24.6107.22485 Task 15718 - Excel template font and font size are overridden

When exporting a statistic to Excel, a template can be used to regulate the default formatting. However, it was found that a font and font size were being overridden. This issue has been resolved.

Version 16.12.5987.28030 Task 15673 - Please add column article-VAT code to statistic 236 'Per sales line'

On statistic 236, a column 'VAT code' is now also included.

Version 16.24.6107.18212 Task 15669 - Cash sales statistics also show terminals from other branches (if a branch is selected in the selection)

In cash sales statistics, only the POS terminals of the selected branch are now displayed.

Version 16.6.5906.23545 Task 15649 - Statistic per cash register group and VAT rate and statistic per VAT rate, please also group by VAT exempted deliveries versus non-exempted and percentage

Statistic 100 and 120, where statistic per VAT rate is shown, are now better split up. It is now also split up by VAT percentage and by VAT exempted versus non-exempted deliveries. To enable this, columns have been added for the VAT percentage and whether a delivery was VAT exempted or not.

Version 16.7.5934.20806 Task 15648 - Statistics can be filtered extensively on VAT exempt yes/no/all

From now on, statistics can also be filtered extensively on the display of sales that were VAT exempt or not. By default, all sales are shown.

Sales orders

Version 16.28.6143.25791 Task 16210 - Show how many times a request has been sent for sales order approval rules

Sales order rules can be sent for approval to relations and/or suppliers. The information on how many times a request has been sent is now also visible in the 'Approval' tab of the sales orders. Whether confirmations are used depends on the approval settings for sales orders.

Version 16.24.6107.18212 Task 16147 - VAT exempt not suggested when specifying VAT exempt debtor

When creating a sales order, attention is now paid to the VAT indication of the debtor linked to the relation, if applicable. If it turns out that the debtor is VAT exempt, the sales order is also marked as a VAT exempt order.

Version 16.12.5987.28030 Task 15851 - Please print the delivery address of a relation in the standard address block (postcode, house number) on the delivery list report

From now on, the delivery address of a relation is printed as the address on the delivery list report 111, if available. Previously, only the standard address was always printed.

Version 16.24.6107.18212 Task 15708 - If a sales order has been processed/delivered, you still see 'Outstanding deposit requests' on the 'General' tab.

From now on, no outstanding deposit requests are displayed for a sales order that has been processed, even if they still exist.

Version 16.7.5934.20806 Task 15430 - Reservations can also be automatically registered with DHL

From now on, reservations can also be automatically registered with DHL.The integration at DHL, however, does not work as smoothly as at Post NL. For this reason, implementation time is needed to make this operational. This time mainly depends on the different number of types of labels desired to send packages.

Version 16.29.6149.29238 Task 15071 - Ability to send order acceptance request to consumer/customer and give consumer the option to reject or approve

In settings -> section 'Sales orders' -> tab 'Order approval', it is now possible to set that a customer must approve a sales order. By activating this, RetailVista will automatically send 3 emails to the customer to approve a sales order. If the customer does not approve but rejects the order, the order will be marked as 'Cancelled'.

Version 16.11.5977.27869 Task 15070 - Status of sales order should depend on filled in sales order comment

In settings -> section 'Sales orders' ->tab 'General', with the setting 'Webshop status 'New' for free text', it can now be indicated that a webshop order will receive this status if text is provided in the free information. This functionality is built in so that a webshop sales order is not immediately processed if the customer has added a comment. This comment now leads to a sales order with the status 'New', which means the order must be manually reviewed and the status adjusted.

Version 16.14.5998.20925 Task 15069 - Ability to register order acceptance request to supplier(s)

In settings, section 'Sales orders', tab 'Order approval', it is now possible to set that supplier(s) of sales orders receive an email in which they must approve the order line(s). This notification occurs a maximum of 3 times. Internally, the preferred suppliers for a sales order are determined.Product suppliers will receive an email notification to the preferred email address of the relationship with the supplier.

Currently, it is not yet visible in the sales order line whether the supplier has approved the order, but in the next release of RetailVista, this will be the case.

Inventory

Version 16.22.6054.22959 Task 15873 - Min/max calculation report provides more details when recalculating for a specific product

When recalculating the ideal inventory (min/max) for a product (via inventory, calculate optimal inventory), a log will now always be written for that product. The log shows the calculation of the min/max inventory. Normally, a log is only written if it is activated in the settings. However, there may still be situations where a product is completely skipped due to various settings. By entering a product number in the calculation screen, a log will always be created, which may also indicate why that product is not being calculated.

Version 16.7.5934.20806 Task 15626 - Inventory display in product search screen is incorrect

If it is set for a product that no inventory administration should be kept, the inventory status for that product was still displayed in the product search screen. This has been resolved.

Webshop

Version 16.27.6135.23246 Task 16359 - Sub-location inventories are not properly reflected in the shop server

This issue has been resolved.

Version 16.24.6107.18212 Task 15992 - Expired product indication to ShopServer

The expired product indication is now also sent to the ShopServer for webshops.

Version 16.14.5998.20925 Task 15852 - Deviating delivery address in sales order is constantly overwritten

If a new sales order comes in with a deviating delivery address from the same customer, previously all delivery addresses from other orders from that same customer were also overwritten to the new delivery address. This was incorrect and has been adjusted.

Version 16.14.5998.20925 Task 15849 - When searching for a customer in webshop order processing, do not consider expired customers

When receiving a webshop order message, expired customers are no longer searched for, they are now completely ignored.

Version 16.29.6149.29238 Task 15532 - Barcodes in shop server no longer run exactly parallel with RetailVista

From now on, a deleted barcode in RetailVista will also be transmitted as 'Deleted item' in the ShopServer.

Version 16.24.6107.18212 Task 14996 - Promotional voucher forwarded to ShopServer in case of tiered pricing

From now on, promotional vouchers are also forwarded to the ShopServer. In case of tiered pricing, a promotional voucher ID will now also be mentioned when applicable. By linking promotional vouchers to tiered pricing, it can be ensured that customers only receive a tiered offer if they submit a specific promotional voucher.