<span class="fr-marker" data-id="0" data-type="true" style="display: none; line-height: 0;"></span><span class="fr-marker" data-id="0" data-type="false" style="display: none; line-height: 0;"></span> New in RetailVista
Reference to (future) new support website behind login name
U-number behind login
Behind the username used for login, there is now a U-number. This number is linked to the new support website that is currently under development. By clicking on this number, the support website will automatically open. The website is not yet operational, so you will currently receive an error message when you click on it. The website is expected to be operational in a few months.
Change in Sales Order menu
Sales Order menu split:
Sales Orders used to consist of 2 parts: Sales Orders and Reservations. The reservation functionality has been expanded so much in recent years that it has now become its own menu item, namely Fulfillment.
RetailVista Mobile X
RetailVista Mobile completely renewed:
Because the development platform we used for RetailVista Mobile stopped further development and support, we had to use a different development platform. The disadvantage of this was that we had to start the development of RM from scratch. The advantage was that we could now overcome some limitations that were present in the previous platform.
We are proud to present RetailVista Mobile X (RMx). Faster, even more user-friendly, and functionally more extensive than RetailVista Mobile.
Functionality of RMx:
• Product info• Arrangement• Product locations
• Product list• Order product • Loss
• marked inventory• Product origin• Inventory
• Warehouse count• Sales statistics• Receipts
• Order picking• Order picking control• Print label
• Print receipts• Issue• Issue control
• Sales order • Move product• Move location products
• Change price• Change inventory • Shopping cart
In development:
• Guided order picking • Pre-scanning
Sales Orders Plus
In addition to the sales order module: Sales Orders Plus
Within RetailVista, there are a number of modules that have undergone significant development, which could not be incorporated into the existing module without significant adjustment to the license price. These new developments have therefore been incorporated into a Plus license. To work with the Plus license, the "Sales Orders" module is necessary.
Plus licenses are invoiced based on usage. For this purpose, counts are made of the number of orders created per period.
SLA is in accordance with the RetailVista SLA.
The following functionality is currently included in Sales Orders Plus:
Sales Orders Plus:
• Pickup locations
If you have multiple pickup locations, such as a store warehouse and an external warehouse, you can indicate the pickup location for each reservation.
• Order picking control
All items of a picked reservation are rescanned to ensure that all items have been picked and that they are the correct items. It is clearly visible which reservation-item lines have not been scanned yet. If the picking is done correctly, there will be no remaining lines after the control.
•Order issuance
When scanning the reservation barcode, it can be checked whether the reservation has already been paid (or whether the delivery can be made on account) and whether the reservation has not yet been picked up.
•Order issuance control
Optionally, it can be chosen to scan all products again upon issuance. This is particularly useful for delivery to verify that the delivered goods indeed match the order.
•Signature upon issuance
A name, receipt, and signature can be recorded on the PDA as proof of delivery. This is stored with the reservation/sales order.
•Cash on delivery functionality
It is possible to pay the amount due upon delivery if the issuance functionality is used. The delivery person is alerted to the cash on delivery amount upon handover. This amount can then be deposited at a designated RetailVista POS installation.
•Fleurop import
The Fleurop import allows for the import of flower orders.
•Order picking
With the "Warehouse" module, it is already possible to define locations in the warehouse. This is now also possible for the store. By recording locations, the order picking process becomes much more efficient as items can be picked in the order of products/locations. The items to be picked are indicated on the PDA. Each picked item is checked off. Once the order is fully picked, the employee receives the next picking assignment.
Order picking is an application within RetailVista Mobile and is included in the number of mobile applications for licensing purposes.
•Still in development: Guided order picking (can be seen as a light WMS solution)
With the "Warehouse" module, it is already possible to define locations in the warehouse. This is now also possible for the store.By capturing locations, the order picking process becomes much more efficient as picking can be done in the order of products/locations. With guided order picking, an employee can pick multiple reservation orders simultaneously. The PDA provides picking instructions for one or more reservations in succession. These instructions are executed one by one. Multiple employees can work on the same reservation order at the same time.
Order picking is an application within RetailVista Mobile and is included in the number of mobile applications in terms of licenses.
RetailVista screens for order picking types, carriers, and rejection reasons - Task 19812 (version 21.1.7675.30807)
For supported order picking, auxiliary tables have been created in RetailVista for the order picking types, carriers, and rejection reasons when an order picking instruction cannot be executed.
The order picking types are intended to create different types of picking strategies, such as discrete order picking, wave order picking, etc.
The carriers table consists of the crates/containers in which reservations can be picked.
The rejection reasons are a pre-defined collection of possible reasons why an instruction cannot be executed.
If there is a need to work with supported order picking, it is best to contact the sales department of NedFox.
Gold SLA
In addition to RetailVista SLA: Gold SLA
There may be situations where RetailVista does not function as it should, causing a halt in business operations and requiring immediate attention. In any case, faster than what is defined in the RetailVista SLA.
Gold SLA is an addition to the RetailVista SLA and RetailVista SLA SupportPlus (Weekend support) contract.If you have signed the Gold SLA contract and the process that is important for your business is blocked or not working as it should, the response time of the NedFox helpdesk is 1 hour after reporting the problem.
The following table is used to determine the priority:
If you would like more information about one or more of the above points, please contact us. Phone +31 (0)527 249 900 or email info@nedfox.nl
General - miscellaneous
Environment support - Task 19429 (version 20.17.7584.27682) + Task 19813 (version 21.1.7675.30807)
With the new environment table, a user can easily select which "environment" he/she is active in. Think of an environment, for example, as departments where a user is located. Certain printers that can be used are located in that department or near that department. The printers to be used can be set per environment. In this case, it concerns the new type of "bridge" printers. The active environment can be chosen in the left column of the start page of RetailVista and is saved per user. The choice of an environment is also supported in the new version of RetailVista Mobile (RetailVista Mobile X).
The A4 printers are created under Administration - Printers.
The Windows printer name can be found by typing "printers" in the Windows search screen and then clicking on Printers and scanners. An overview of the printer names will then appear.
Bridge printing is now an addition to and eventually a replacement for LocalServices. LocalServices is used to print to label printers, to work with a data collector, and to configure price checkers. However, with LocalServices, it is not possible to print documents to A4/page printers.
For this, bridge printing is required.
With bridge printing, sales orders, copy sales orders, and reservations can currently be printed. It can be set up to print the sales order on a printer in the store and a copy sales order on a printer in the office. And this printing can be done from the RetailVista back office and from the new version of RetailVista Mobile.
The environment with bridge printers is already supported in the sales order module. Sales order reports can be automatically printed to these new type of printers. This makes it possible to automatically print sales orders made in RetailVista Mobile to A4 printers.
In the coming period, the entire reporting environment of RetailVista will be converted to bridge printers, taking into account the selected active environment. Therefore, it will no longer be necessary to always first display the printout on the screen and then choose the Windows printer using a trick. Reports can be printed directly to a bridge printer without any further intervention. The bridge printer is actually the successor to RetailVista LocalServices, which means that not only thermal printers are supported, but also A4/page printers.
QA740 has been created about Bridge printing. You can find this in the document screen of the main menu of RetailVista.
IP restrictions per mobile device (RetailVista Mobile) - Task 19631 (version 21.4.7733.20801)
For mobile devices, it can be set up that IP restrictions do not apply to certain terminals. There was a temporary workaround so that IP restrictions for Mobile do not apply at all. That has now been undone: if IP restrictions are active, they will now also apply to mobile devices/RetailVista Mobile.
It is important to select the mobile devices that are used outside the network (either 3G/4G) during this update and mark them as not having IP restrictions. If this is not done, those scanners will report that RetailVista is not accessible due to IP restrictions.
Table for outgoing mail - Task 19896 (version 21.2.7692.27627)
Outgoing emails (whether sent or not) are placed in a table called "Outgoing emails". The reasons for this are:
• External CMS parties can easily hook into this and convert the emails into a final layout and send them to consumers.
In this case, RetailVista does not provide formatted email content, only
"metadata". This allows an external party to compose the email definitively.
• This new table provides insight into the sent (or yet to be sent) emails, which was not possible before.
• Currently, emails for activated gift cards and final delivery schedules are displayed here.
Outgoing emails can be found under Administration - General block - Outbound Email option
In the future, RetailVista will allow the configuration of which types of emails will be sent by RetailVista itself and which will be left for an external party. Currently, RetailVista does not send from this table itself. It is only intended for external CMS parties to read and actually send these emails.
Currently, only created/issued RetailVista gift cards are placed in the outgoing email table, so that a customer can receive a proper email. In the near future, the definitively planned deliveries from the delivery administration will also be added. Eventually, every outgoing email from RetailVista will go through this system (think, for example, of digital invoicing, but also simple things like a password recovery email, etc.).
Currency symbol - Task 19991 (version 21.5.7734.25822)
In the currency table, a currency symbol can be specified. Wherever a euro or dollar symbol is still found in RetailVista, it will be replaced by this currency symbol.
Previously:
Now:
If you add currency yourself, you must enter the symbol yourself.
Product maintenance
Searching for "order code" now also includes non-preferred supplier/purchase data - Task 19262 (version 21.4.7733.20801)
When searching for products using the order code, it will no longer only search for preferred purchase data. Non-preferred purchase data will now also be included in the search for products. This allows for more products to be found than before.
Marking products as "deleted" - Task 19428 (version 21.3.7706.25430)
Products can now be marked as "deleted". A checkmark can be placed in the "deleted" field on the "general" tab.
By marking a product as deleted, the product will no longer be found by default in search queries. Only administrators can still choose the option "Search for deleted products yes/no/all" in the product search screen. This allows administrators to easily undo the deletion of a product. Deleted products are no longer usable for creating new data, such as sales orders, product lists, etc. Deleted products cannot be sold in the cash register.
From product lists, products can be marked as "deleted" in bulk. For this purpose, a new export option has been created from product lists to deleted products.
Specify shopping cart group - Task 19914 (version 21.2.7692.
Product (27627)
For a product, a shopping cart group can now be specified. This allows certain products to be set so that they cannot be ordered in combination with products from other shopping cart groups in the webshop. In addition to a product, a shopping cart group can also be specified for the product category.
These groups have been created because the logistics process through the "Sales Orders" module can be so different for different products that it cannot be handled in one sales order process.
For example: There is a shopping cart group called "Events". Only items (tickets for events) can be sold in this group. If a customer purchases several items on the webshop, including an event ticket, a notification will appear stating that this cannot be purchased in one order. The customer will then have to make 2 webshop transactions.
Further explanation about shopping cart groups is included in section "Webshop - Shopping Cart Groups - Task 19909".
Bulk changes in purchase data: Processing now based on specified criteria - Task 19775 (version 21.6.7741.28554)
When bulk changing the purchase status with the specification of a supplier and the specification of 1 product, all purchases of this product received the specified status. Due to the product selection, the supplier selection was lost. This has been resolved with this task so that only the purchases from the specified supplier of this product will receive a status change.
Menu: Products - Bulk changes in purchase data
Product Lists
Clearer screen when converting a product list to invoice delivery - Task 19101 (version 21.1.7675.30807)
The conversion of a product list to invoice delivery has been improved in terms of user interface. Now only the selected lines can be transferred and the screen for the transfer has been redesigned.
Labeling
Price per ISO unit added for label layout - Task 19884 (version 21.2.7692.27627)
RetailVista can print the price per ISO unit on labels, for example € 4.95/LTR, and then convert the normal gross selling price and specified weight to a price per gross or net unit. This is also described in QA 754.
Two additional fields have now been made available so that no distinction needs to be made between weight or volume indication in the label layout.
The new fields are:
•grosspricepergrossunit
•grosspricepernetunit
grosspricepergrossunit: This field provides the gross price and ISO unit information based on weight if weight information is available.
grosspricepernetunit: This field provides the net price and ISO unit information based on weight or (if weight is not specified) per net volume.
If the weight is specified/available, the unit price per weight will be indicated. If the weight is not specified, the net field will automatically use the net volume information.
Financial exports
AFAS: separate field for deposit reversal reference - Task 19956 (version 21.5.7734.25822)
For the purpose of automatic and manual reconciliation in AFAS, the reference information for a general ledger mutation is now offered in a separate reference field to AFAS.
Purchase orders
Filter search screen "Purchase order printed/not printed" - Task 19742 (version 21.1.7675.30807)
Purchase orders created from drop shipment sales orders are immediately given the status "Final". However, it was difficult to determine which purchase orders still needed to be printed. With this adjustment, the search screen can be filtered for printed or not printed purchase orders.
Purchase order search for "created by scanner" - Task 19804 (version 21.1.7675.
In the purchase order search screen, it is now possible to search for purchase orders created by a specific scanner.
Cash accountability
Unused cash register does not need to be counted - Task 19970 (version 21.7.7748.30738)
When working with a fixed opening cash register, a fixed opening cash register was always placed at each cash register. As a result, that cash register had to be counted.
In the cash accountability settings, it is now possible to set that an unused cash register does not need to be counted. By activating this setting in combination with a fixed opening cash register, an exact counted amount is automatically filled in for an unused cash register, which is equal to the opening cash register. Therefore, such a cash register no longer needs to be counted. It has been deliberately chosen to make this behavior adjustable and explicitly activate it. After all, the fact that a cash register is not used does not mean that the final amount is still in the drawer.
Setting: Extra - Extra/Settings - Cash accountability section - General tab
Warehouse
Filter search screen on a specific product - Task 19803 (version 21.1.7675.30807)
In the warehouse information screen, it is now possible to filter on a specific product.
Promotions
Update existing discounts via product list - Task 19936 (version 21.4.7733.20801)
When converting a product list to discounts, the conversion screen allows you to choose what to do with any existing discounts. You can choose to always create a new discount or update existing discounts. There is also the option to delete existing discounts.
Receipts
Warehouse discrepancy screen clearer - Task 19810 (version 21.8.7758.20716)
There was little text difference between warehouse counts and warehouse discrepancies.
Both screens have been renamed and are still being translated.
Old: Warehouse discrepancies → Now: Packing slip verification
Old: Warehouse counts → Now: Import scanner slip verifications
The menu option for packing slip verification has been moved and is now directly below the first product receipt menu option.
Promotions
Add mixedmatch product multiple times with different barcode - Task 19758 (version 21.7.7748.30738)
For example, for ViridiCode, it is desired that the same product can be added multiple times to the same mixedmatch, but with a different barcode each time. This allows different batches to be added to the same mixedmatch. This is now possible.
Statistics
product statistics: Purchase price visibility follows security role - Task 19689 (version 21.1.7675.30807)
The visibility of purchase prices is a right that can be set in RetailVista. From now on, many overview grids have been cleaned up so that this data is no longer visible. The main screen for this was product statistics.
If a user does not have the right to see purchase prices, generating purchase orders will also no longer be possible from now on. The purchase prices are essential for that, and if someone cannot see them, that person cannot generate purchase orders either.
Original sales order number is statistic 236: Statistics per sales line - Task 19700 (version 21.1.7675.30807)
In statistic 236, an additional column "Order reference" has been added. This column contains the sales order reference if a reservation has been sold. With this order reference, a match can be made to the original sales order.
New statistic 112: Statistic expanded per product category and product group - Task 19890 (version 21.5.7734.25822)
This was a statistic report that did not exist yet.
Product statistic: Period selection on "Receipts" tab - Task 19921 (version 21.3.7706.25430)
The period selection in the product statistic was not yet applied to the rules in the "Receipts" tab. This is now being done.
Sales Orders/Reservations
Specify fiscal country in sales order - Task 19025 (version 20.17.7584.27682)
When creating or maintaining a sales order, the fiscal country must now also be specified. This field is typically automatically filled in from the relationship of the sales order. With the fiscal country, the turnover per country can be calculated using a BI tool (such as Qlik) or later in a yet to be developed statistic. The fiscal country is already used to determine the correct VAT rate for the products. If there is no specific VAT rate for that fiscal country in the product, RetailVista falls back to the standard VAT rate. That is the VAT rate of the country of the establishment.
It is now possible to indicate VAT reimbursement per country.
Editable VAT exempt indication on sales order - Task 19037 (version 20.17.7584.27682)
When modifying a sales order, the VAT exempt indication can now be adjusted. At that moment, all VAT rates/codes are re-determined for the products. Of course, the prices are also recalculated. The VAT rate is determined based on the fiscal country of the order and the product. If no VAT rate is known for that country and product, the VAT rate of the sales order's establishment is used. If that is also not known (very theoretical), that particular rule remains unchanged.
Due to the recalculation, discounts, etc. are adjusted.
Lost (to be determined again), because the gross price changes, causing the discounts to no longer be valid.
Sales order classification expanded with conditions to apply/not apply dropshipment - Task 19495 (version 20.17.7584.27682)
In the sales order classification, it is now possible to indicate how to handle the dropshipment suggestion. Dropshipment can always or never be suggested, or according to a certain calculation. The calculation method can also be set and can take into account the dropshipment indication at the product level, with or without certain stock levels.
"Main product" added to the first possible reservation - Task 19524 (version 20.17.7584.27682)
The "main product" of a set will no longer be added to a separate reservation, but will now be added to a "random" reservation that has been created for the same sales order to which the set main product belongs.
This only applies when working with departments for order picking. Reservations are then split by departments. A main product does not always have a department and would therefore be added to a reservation without a department in such a case.
This issue does not occur when splitting reservations by pickup locations. In this scenario, a main product can also have a pickup location and will automatically be added to the correct reservation.
Automatically reduce down payment request amount when creating or updating a reservation - Task 19525 (version 20.17.7584.27682)
A down payment request will now be automatically reduced when maintaining a reservation if it appears that the sales order amount minus the total reservation amount is lower than the down payment request amount.
This can happen if changes are made to the sales order and/or reservations after the deposit request has been made. What went wrong so far was that the customer in RetailVista POS sometimes had to pay too much in the aforementioned situation, which of course led to complaints. From now on, it will always be ensured that the deposit request amount will not be too high. If the difference between the sales order value and the total amount of all reservations is 0, the deposit request will be removed.
Setting to automatically put on account - Task 19535 (version 20.17.7584.27682)
When generating reservations, it is now possible to indicate that reservations should also be automatically put on account as far as possible.
This has been built in and made possible to ensure that shipping notifications from a WMS environment automatically result in a delivery on account (revenue/sale of the reservation) and thus the closing of the corresponding sales orders.
If there is no WMS connection, this is undesirable because reservations are unintentionally sold immediately and also undesirably put on account. It is then questionable whether a reservation should already be sold, and if so, whether you choose to do so on account. This is a manual choice at the moment the reservation is ready. In addition, the reservation is now closed, so customer service cannot see what is still outstanding and needs to be handled.
From now on, it is possible to set whether automatically putting reservations on account is desired in the sales order classification. The default behavior does not do this, essentially working as it did before. So if it is desired to automatically make a delivery on account from a reservation, it must be set in the sales order classification.
When a sales order is marked as expired, all lines should not automatically be marked as expired as well - Task 19545 (version 20.17.7584.27682)
If a sales order was marked as expired, all lines were automatically canceled as well. This was not the desired behavior, especially because when the expired indication is removed, it is unknown which lines should be restored. After all, there may be lines that were genuinely marked as expired in consultation with the customer. However, if everything is automatically marked as expired, it is no longer visible which lines were originally affected. From now on, the sales order lines will no longer be marked as expired when declaring a sales order as expired. External systems that use the expired indications at line level should take this behavior change into account and pay particular attention to the expired indication of the sales order itself.
Notification for insufficient stock to reserve - Task 19676 (version 21.3.7706.25430)
In the sales order classification, it can be indicated that when adding a sales order line, a check is performed to see if there is sufficient available stock for the requested quantity. If not, a notification can now be displayed on the screen, which must be confirmed by the user. This functionality is a change in behavior of RetailVista and must therefore be explicitly enabled in the sales order classification.
Sales order dashboard - Task 19683 (version 21.3.7706.25430)
From a sales order, a sales order dashboard page can now be launched via the left task menu. This screen displays as much information as possible about the sales order, down payments, linked purchase orders, reservations, and the final revenue (cash/credit) from it.27682)
From now on, when closing sales orders, all outstanding reservations will no longer be automatically deleted. Until now, that was done: if the remainder of a sales order is no longer desired, it can be closed. But that does not necessarily mean that what has already been reserved does not need to be delivered anymore. Or the decision can be made to cancel the reserved items and return them to stock. By deleting the reservations, they are also no longer traceable, so it is no longer clear who made those reservations, what their status was, etc. It is up to the warehouse to decide on the remaining outstanding reservations after closing a sales order.
Specify classification when importing a quote - Task 19732 (version 20.18.7591.29798)
When importing a quote from a sales order, a sales order classification must now also be specified. This determines to a large extent how the sales order is filled and built up.
A quote can be converted to a sales order from:
• Quote maintenance. After selecting a quote on the left side of the screen, in the "Export tasks" section, choose the option "Quote to sales order"
• Quote menu: To sales order
Visible linked tasks - Task 19739 (version 21.4.7720.18568)
A new tab "Tasks" has been added to a reservation. Here, all tasks related to that reservation can be seen. An important task is the automatic printing of the order picking report. The task that does this results in a PDF, making the PDF quickly accessible.
Direct reservation from sales order - Task 19753 (version 21.1.7675.30807)
From now on, it is possible to directly reserve items from the sales order. For this purpose, a new tab "reservation" has been created.
In this, all open and reservable sales order lines are displayed and can be easily reserved. Of course, this page also offers the possibility to ignore the stock and reserve "hard" regardless of stock.
Status of reservation indicated via product receipt - Task 19762 (version 21.1.7675.30807)
In the sales order classification, it is now possible to set the logistical status of reservations created from a product receipt.
Previously, the logistical status in this situation was set to "Waiting for picking". But if automatic printing of order picking reports is used, the logistical status must be "New". This will then be automatically converted to "Waiting for picking" after printing.
Modify sales order VAT indication - Task 19785 (version 21.1.7675.30807)
Several adjustments have been made to be able to modify the VAT indication of a sales order.
Sales order classification: Pickup location adjustable - Task 19826 (version 21.1.7675.30807)
It is now possible to indicate the pickup location for reservations (not to be confused with the delivery location), the location where the reservation can be picked up. For showroom orders, it may be desired to always work with a fixed pickup location, for example "store". By default, a reservation is assigned the pickup location of the branch. From now on, it is possible to set a customized pickup location in a sales order classification. This will then be applied when creating the reservation.
Reservations expire when sales order expires - Task 19828 (version 21.1.7675.30807)
When a sales order is expired, the linked reservations that have not been sold yet will now also be marked as expired automatically.If the reservation has already been sold, this does not happen and a decision must be made manually about what should happen with the reservation (for example, return it). With this adjustment, a sales order can easily be marked as expired when created. All associated reservations are then also marked as expired. However, if a reservation has already been sold, that reservation is ignored. Expired reservations are marked with an 'x' symbol in the sales order screen.
Desired delivery date included in purchase order for drop shipment - Task 19857 (version 21.1.7675.30807)
The desired delivery date from the sales order will now be transferred to the desired delivery date in the purchase order, provided that the sales order is a drop shipment order. In this case, each sales order is transferred 1:1 to a purchase order, instead of "intelling" on existing purchase orders. With this adjustment, the purchase order can be sent to the supplier and they will know on which date a consumer would like to receive the order.
"Expected delivery date" becomes "desired delivery date" - Task 19858 (version 21.1.7675.30807)
An important change has been made to the data fields in the sales order. Previously, there was a field called "expected delivery date". That field in sales orders is confusing because an expected delivery date belongs to a reservation. When writing an order, a customer can only provide a desired delivery date at most. In practice, it was often found that the "expected delivery date" field was also used and filled in as the "desired delivery date". From now on, there is a new field called "desired delivery date". A customer can specify a preference/desired date there. Whether delivery will be made on that date is still uncertain.
The expected delivery date still exists but is no longer available by default.In the settings of "Sales Orders" (Extra - Settings - Sales Orders - Advanced tab), the expected delivery date can still be enabled. In that case, the desired delivery date will not be available.
The reason why the field "expected delivery date" still exists is due to various integrations that still assume the existence of this field. In the 2021 Fall update of RetailVista, the field "expected delivery date" will be permanently removed from RetailVista. It is therefore important to inform your software supplier if you have integrations with other software that this field no longer exists from that moment on and that integrations need to be rebuilt to the new field "desired delivery date".
The desired delivery date is also transferred to purchase orders in case of drop shipment sales orders.
New option for direct reservation quantity type - Task 19867 (version 21.7.7748.30738)
In product categories, it is now possible to set that no inventory is kept for certain categories.
Status "Final and in progress" no longer possible - Task 19878 (version 21.2.7692.27627)
An important change has been made to the status of sales orders. The status "final and in progress" no longer exists and has been replaced by "Final". All orders that were previously set to "Final and in progress" have now been reset to "Final".
Starting from this version, RetailVista knows the link between sales orders and purchase orders. For each sales order line, it is known to which purchase order line(s) this line has been added. The difference compared to before is that if a purchase order is now closed while there are still items needed from that supplier in open sales orders, those sales order lines will be automatically reordered. And this will continue until the desired product is delivered, or until the sales order is modified or marked as closed/expired.
!! If there are still open sales orders in your RetailVista environment that have already been delivered, please close those orders definitively. This can be done relatively easily via the homepage "Sales Orders" and then choose "Close Sales Orders". If this is NOT done, then every time purchase orders are generated from sales orders, the still open lines will be automatically reordered.
It is important to note here that the ordering of purchase orders from sales orders can take place automatically (via the task scheduler), or "manually" from the homepage "Sales Orders" - "Generate Purchase Orders".
Passing on Track & Trace code to sender location - Task 19918 (version 21.3.7706.25430)
From now on, the NedFox XML packing slip message will also include the Track & Trace codes. If the packing slip message arrives at a different RetailVista location, the Track & Trace information will be transferred to the product receipt (shipment reference) This mainly applies to drop shipment orders from one RetailVista location to another.
Set product price distribution across underlying components - Task 19927 (version 21.3.7706.25430)
An important change has been made to the way set products work. The price of a set product is now distributed proportionally among the underlying products. Previously, the price of the set product could no longer be changed and became 0. If you wanted to adjust the price, the prices of the underlying products had to be adjusted. From now on, the price of the set product will remain (of course, no revenue will be generated for the set product) and will remain mutable. The price of the underlying products will always be calculated and therefore cannot be changed.With this change, it has become much easier to change the price of a set afterwards. Something that was almost impossible before. This adjustment now also allows for the conversion of a sales order from ex- to in- VAT (and vice versa).
Automatically register with package service settings - Task 19950 (version 21.4.7720.18568)
Some package services (including Sendcloud) charge money per created label. It is questionable whether you really want to send via Sendcloud in the end. This may depend on the size of the package, but sometimes also on the delivery date. By creating a label directly, there is a chance that the delivery service will be at your door by the end of the day, while the package may not be allowed to be sent until later. For this reason, it is now possible to set whether auto-registration is desired for a package service. NB: Text is still being translated.
"Ready" status for webshop sales orders - Task 19976 (version 21.4.7733.20801)
In the sales order classification, it is now possible to indicate which sales order status an order should have when it originates from a webshop order.
Shopping cart group setting for sales order classification - Task 19980 (version 21.4.7733.20801)
When maintaining the shopping cart groups, it is now possible to optionally set a sales order classification. If set and a webshop order message is received with the shopping cart group indication, the classification of the shopping cart group will automatically be linked to that sales order. This allows certain types of shopping carts to lead to special classifications, which can result in specific behavior. For example, it is now possible to create catering orders that are automatically and directly printed on a printer for order picking reporting.
High priority purchase order when converting sales order to purchase order - Task 19982 (version 21.4.7733.20801)
When converting sales orders to purchase orders, it is now possible to set that purchase orders with high priority should be created in the sales order classification. If this setting is active, the system will first search for purchase orders with high priority. If an open high priority purchase order is found, the sales order lines will be added to that purchase order. If no high priority purchase order is found, a new purchase order with high priority will be created.
Administration - "products" block - Sales order classifications:
Generating reservations now through task - Task 19988 (version 21.4.7733.20801)
Generating reservations now happens through a task. One of the advantages is that there is a report available on how the generation process went.
Searching for reservations that are (not) fully picked - Task 20014 (version 21.7.7748.30738)
In the "Rules" tab in reservation maintenance, it is now possible to choose whether to show the reservation lines that are (not) fully picked.
Inventory
Processing marked inventory - Task 19610 (version 20.18.7591.29798)
From now on, it is possible to work with marked inventory. This is inventory that is still physically present but not immediately sellable. Examples include showroom inventory. It is included in the normal stock quantity and also contributes to the total stock value. However, showroom inventory should not be available for purchase through the webshop. Therefore, it is now possible to mark a certain number of units of an product as marked inventory.
That can be done, among other things, via RetailVista Mobile, or via RetailVista ERP via Start, Inventory, marked inventory. By placing products in the marked inventory, the free inventory decreases. When placing an product in the marked inventory, the type of marked inventory must be indicated. The possible types can be created in RetailVista ERP.
The marked inventory is also a preparation for arrangements: an arrangement that is created consists of products from the regular inventory. But those products are no longer 'individually' sellable at that time. Therefore, there has long been a desire to make an exception in the inventory for arrangements. With the introduction of marked inventory, preparations have been made to be able to set inventory aside. In a future release of RetailVista ERP, arrangements will also use this functionality. It is expected that when an arrangement is sold, it will automatically be deducted from the marked inventory.
Other setup Loss - Task 19733 (version 20.18.7591.29798)
Loss used to only work through delivery on account. However, this is not correct. It is not a form of revenue. And there is also no debtor associated with it. Because of this setup, it was very difficult, for example, to show the number of pieces of loss in product statistics.
Registering loss was also difficult because of the requirement to specify a relationship and debtor, and to prevent a proliferation of deliveries on account.
For this reason, loss has been redesigned and loss registrations now go to a separate table (loss). In RetailVista Mobile, it has now been made much easier to create loss.
As part of this revision, a new table "Loss type" has been created (Menu: Administration - block products - 4th tab: Loss types).30807)
A new tab called “marked Stock” has been added to the product statistics. This tab displays the products that are currently marked to specific locations or sales orders. This provides insight into stock that has already been reserved for specific purposes. It is possible to filter by location, sales order, and product number to obtain specific information.
Product statistics: “Stock Corrections” tab – Task 19857 (version 21.1.7675.30807)
A new tab called “Stock Corrections” has been added to the product statistics. This tab shows all stock corrections that have been carried out for the selected period. It provides insight into any adjustments made to the stock, such as additions or removals. It is possible to filter by product number, user, and type of correction to obtain specific information.
Product statistics: “Stock Movements” tab – Task 19858 (version 21.1.7675.30807)
The “Stock Movements” tab has been added to the product statistics. This tab displays all stock movements that have taken place during the selected period. It provides insight into changes in stock levels, such as incoming and outgoing deliveries. It is possible to filter by product number, user, and type of movement to obtain specific information.
Product statistics: “Stock Valuation” tab – Task 19859 (version 21.1.7675.30807)
The “Stock Valuation” tab has been added to the product statistics. This tab displays the value of the stock for the selected period. It provides insight into the financial value of the stock at different points in time. It is possible to filter by product number and location to obtain specific information.
Product statistics: “Stock Movement” tab – Task 19860 (version 21.1.7675.30807)
The “Stock Movement” tab has been added to the product statistics. This tab shows the development of the stock over the selected period. It provides insight into changes in stock levels, such as incoming and outgoing deliveries. It is possible to filter by product number and location to obtain specific information.
In the “General” tab of the product statistics, the marked inventory is displayed. In the new “marked” tab, a detailed breakdown of the marked inventory is shown, providing visibility into how the marked stock is distributed.
Webshop
Multiple printers can be used for package service integration - Task 19419 (version 20.17.7584.27682)
It is now possible to set up multiple printers for printing package service labels. For example, one printer per cash register terminal.
This can be done through a new environments table. In this table, a default thermal printer and a different package service thermal printer can be specified. If this is not configured, the default printer from the store will continue to be used.
By selecting a specific RetailVista system account in RetailVista POS and setting the correct "environment" thermal printer in that account, the correct printer will be used for printing package service labels when processing the reservation.
This can be set up under "Administration" - Block "General" - "Environments"
Webshop code in XML webshop order message - Task 19835 (version 21.1.7675.30807)
For parties that deliver webshop messages directly via the Retail3000 API integration, it is now possible to indicate a webshop code in the XML message. This allows the sales order generated from the order message to be directly linked to the correct webshop. As a result, the webshop will be linked to the revenue and the statistics will be accurate. For parties using the ShopServer, this is not an issue as a ShopServer in RetailVista is already linked to a webshop.
But even in that case, any potential webshop code in the XML message will still result in the inclusion of that webshop in the sales order.
The webshop code is a new field in the XML message. We can provide further information to third-party developers through the usual channels.
Webshop integration license check - Task 19877 (version 21.1.7675.30807)
A Webshop integration license is required for each webshop that needs to send information to the webshop and send orders back to RetailVista. When processing webshop order messages, there was no check on the number of active webshops in combination with the available license. If there are more active webshops than the number of licenses (Webshop CALS), no order messages will be processed at all from now on. Note: We count the number of webshops and cannot distinguish between webshops. Suppose you have 3 webshops and want orders from 2 webshops to go to RetailVista. We cannot set a filter for that. Therefore, we do not know for which webshop there is actually no license, and therefore, the entire processing will be stalled if there are insufficient licenses.
The webshop builder can, of course, ensure that orders from a specific webshop are not sent to RetailVista.
If this problem occurs, it can be resolved almost immediately by marking webshops that have been newly added and for which no license declaration has been made as "expired". By doing this, the number of active webshops should match the number of webshop CALS in the license. However, any order messages for expired webshops will be rejected. The ultimate solution is to contact our sales department to obtain the correct licenses.
Shopserver integration end-of-life - Task 19908 (version 21.4.7733.20801)
When creating a webshop, it is no longer mandatory to provide ShopServer information.The ShopServer is an additional application that is not always used in webshop integrations. Development on the ShopServer has been discontinued, and as of this release, it is end-of-life. Only existing functionality will be maintained and supported. New features (such as basket groups) will no longer be part of the ShopServer. New webshop integrations should preferably be developed directly on the Retail3000 API.
Basket Groups - Task 19909 (version 21.3.7706.25430)
From now on, it is possible to create basket groups in RetailVista. This functionality allows specifying that certain combinations of products are undesirable in one shopping cart. For example, when ordering hospitality products, it is not desirable to also include other "hardware" products in the same order. It is highly undesirable for the hospitality department to suddenly have to add other products to a hospitality order. By using basket groups, it can be enforced that separate orders are created for, for example, hospitality orders, but also for turf, events, etc. A separate sales order classification can be linked to the basket group, so that, for example, a hospitality order receives separate treatment and is sent directly to the correct printer in the hospitality department.
The basket groups functionality is only intended to indicate exceptions, i.e., "special" products that must not be ordered together with normal products in the same order. A basket group can be specified per product category. In addition, it is possible to deviate per product through this setting and/or mark special products individually.
The webshop linked to RetailVista will of course have to support shopping cart groups and the possible shopping cart group must be included in the webshop order message.
Shopping cart groups: menu "Administration" - block "General" - Shopping cart groups/Basket groups.
In development / Long-term developments
In addition to the above release points, our development department is also working on modules or components that require more time. We are currently working on the following components:
Delivery administration
Reservations that arise from sales orders are eventually registered in the delivery administration. Reservations can be scheduled for delivery via a dashboard. This can be delivery with our own vehicles or registration with SendCloud.
The reservations are then scheduled in "routes".
Once a route is finalized, the routes can be optionally registered with SendCloud and stickers can be printed. Customers receive emails about the delivery schedule, track & trace codes, etc. via Garden Connect / CMS.
SendCloud integration
Sendcloud is a shipping platform for e-commerce. A connection is made from RetailVista to the Sendcloud shipping software. Sendcloud includes various carriers, providing a choice of carriers.
Loyalty Plus
Loyalty Plus is an extension of the Loyalty Card module. Loyalty Plus initially sells discounted items by deducting a certain number of loyalty card points.
The analysis of which types of discounts need to be developed is done with multiple parties. Loyalty Plus functionality is transaction-based.
Spaaza integration
Spaaza is a platform for setting up (personalized) loyalty programs.
A connection is being established from RetailVista.