VARStreet Release Note - Version 25.9

Published on Monday, 25th December 2023

Enhancements

Introduced the ability to retain information on Send Tab of Quote when moving to another Tab within Quote

Before Release

  • Previously, the users were losing the email body entered on the "Send" Tab of Quote whenever they moved to another tab within Quote.

After Release

  • Now the system will retain the email body on "Send Tab" even if the user moves from one tab to another within the quote.

Avalara tax is now available for Canada Resellers for tax calculations

  • VARStreet is now integrated with Avalara for Canada accounts. This will allow Canada resellers to use Avalara tax for tax calculations.
  • Under the "Avalara Account Setup" tab, the user has to enter the details required to complete Avalara setup like Account No. Company Code, License Key, User Id, etc., to import sales tax data from Avalara into VARStreet platform
  • Sales tax will be automatically calculated using Avalara tax codes on eCommerce stores as well as while creating quotes/SO/PO. This is applicable only for those Canada accounts where Avalara has been enabled.

Introduced the Ability to Create Tax Rules for Canada Resellers

  • Now Canada resellers can create their own tax rules in VS back-office.
  • A new tab called "Tax Rules" has been introduced under Tax Settings.
  • To access this feature go to BO>>Admin>>Account Settings>>Tax Settings>>Tax Rules
  • The user has the flexibility to create the following types of tax rules:
    • Product-based tax rule
    • Category / Sub-category-based tax rule
    • Location-based tax rule
    • Customer-based tax rule
  • The user also has to specify Title, Tax Code, Country, City, Province, and Postal Code to define tax rules.
  • Tax rules will be applied as per the priority given below:
    • Tax defined at Address Level
    • Tax defined at Address Level
    • Tax defined at Address Level
    • Customer-based tax rule
    • Tax Tables
    • Product-based tax rule
    • Category-based tax rule
    • Location-based tax rule

Now the User can decide to whom the "Customer Login Details" Email Notification shall be sent

Before Release

  • Previously, the user could assign a default sales rep through eCommerce store setup in the back-office

After Release

  • Now there is one more way wherein the user can assign a sales rep that would be notified about customer login details.
  • Now the user can decide to whom the "Customer Login Details" email Notification shall be sent.
  • A new "To" field has been introduced in the "Customer Login Details" email notification template.
  • To access this field go to
    BO>>eCommerce>>Store>>Setup>>Notification>>Customer Login Details Template>>To
  • The user has to enter the "Email ID" of the sales rep to whom the email should be sent.
  • The user has the flexibility to enter multiple email IDs in the "To" Field.
  • In case, the "To" field is blank, the customer login details will be sent to the default sales rep assigned in the eCommerce store set up page.

Introduced Scroll option on the Configuration details page to view Configuration components/Summary

  • A new scroll bar has been introduced for the "Configuration Summary" section on the configuration details page. This will allow the user to scroll and view the configuration components easily.

Modifications to Existing Features

System will not show RFQ Status on the Transaction Listing Page in the Back-Office when $0 products are added to the Cart

Before Release

  • Previously, the system was showing RFQ status on the transaction listing page in the back-office when the cart containing $0 products was created/confirmed or closed.

After Release

  • Now whenever a cart containing $0 products is created/confirmed or closed, the system will not show RFQ status on the transaction listing page in the back-office.

P.S.----> This is applicable only if the flag "Allow user to check-out $0 product" under eCommerce store setup is checked.

System will show the "Customize and Buy" button for $0 price Configuration Products on the Product Listing Page on the Latest Version of the Store

  • Now if the configuration product has $0 price and the "Allow user to check-out $0 product" flag is enabled on the eCommerce store setup page, then the system will show the "Customize and Buy" button on the following pages
    • Product Listing page
    • Product widget page
    • Recently searched page
    • Search results page
  • The $0 price of the configuration product will be visible only on the product details page.
  • If a configuration product has a $0 price on the product details page and the "Allow user to check-out $0 product" flag is enabled on the eCommerce store setup page, then the system will not show the RFQ button. Instead, the system will show an "Add to Cart" button.

Changes in the UI Structure of Store Catalog in the Back-Office

Before Release

  • Previously many columns were combined to form a single column in the Store Catalog under Product Listing Page. For instance, the columns like Part#, SKU#, and CLIN# were combined to form one column, and was labeled as Part#/SKU#/CLIN#.
  • Similarly columns like Category and Subcategory were combined to form a single column and labeled as Category/Subcategory.

After Release

  • Now these columns will be separated and will be available as individual columns on Store Catalog under Product Listing Page
    • Category
    • Subcategory
    • Part#
    • SKU#
    • CLIN#
  • To view this enhancement go to---->BO>>eCommerce>>Store Catalog>>Product Listings>>Feature
  • The user can also add/remove these columns on Store Catalog using 'Column Chooser'

Increased the Character Limit of "PO Number" Field from 10 to 20 characters

Before Release

  • Previously, the character limit of the "PO Number" field in a PO document was only 10 characters.

After Release

  • Now the character limit of the "PO Number" field in the PO document has been increased to 20 characters.

Bug Fixes

Issues in "Reset Password" Page on the Latest Version of the Store

Before Release

  • On the "Reset Password" page, the user was entering the same password in both the first and second fields, to confirm the password. This was followed by changing the password in the first field and then clicking on the "Change Password" field.
  • For instance, the user enters password as "abcdefgh" in both fields 1 and 2. The user then changes the password in field 1 as "abcdefg" and clicks on the "Change Password" button.
  • Despite having two different passwords in fields 1 and 2, the system was accepting it and displaying the message "Password Reset Successfully"

After Release

  • The issue has been fixed. Now if there are two different passwords in fields 1 and 2, the system will not accept it and display an appropriate error message.

Ratings & Reviews of HP Products not Visible on Latest Version of Store

Before Release

  • Previously, the available "Ratings & Reviews" of HP products in the product details page were not visible on the store.

After Release

  • The issue has now been fixed. When the user views the HP product details page of the store, all the available "Ratings & Reviews" of HP products will be visible on the store.

Issues in the Header/Footer Menu in VARStreet Back-Office

Before Release

  • Previously, in the back-office, the user used to add a product to the existing Header/Footer menu (under Store Customization), click on "Generate Link" and press the "Save" button. The user was then revisiting the menu and then clicking the product link. However, the user could not see the details of the product. Only the generated URL was visible to the user.

After Release

  • The issue has been fixed. Now whenever the user revisits the menu and clicks on the link, the product details will be visible to the user

System not Updating Custom Fields of the Contact on the Cart/Quote

Before Release

  • Previously, the user was updating contact information of an existing cart/quote in the back-office under General Tab. However, even after changing the contact name, the associated custom fields such as "Cost Center" and "Plant Code" did not get updated.

After Release

  • The issue has been fixed. Now whenever the user updates the contact information of the existing cart/quote in the back-office under General Tab, then the associated custom fields such as "Cost Center" and "Plant Code" will also get updated

System is assigning Duplicate Cart Numbers when two different carts are created at the same time on the Latest Version of Store

Before Release

  • Previously, when two different carts were created at the same time on the store, the system was assigning duplicate cart numbers.

After Release

  • The issue has been fixed. Now even if multiple users login on to the store at the same time and create multiple carts, the system will assign unique cart numbers to every cart on the store.

System not showing Sell Rule on the Latest Version of the Store for Custom Catalog Products with Updated Mfr. Part

Before Release

  • Previously, when the user was updating the Mfr. Part of a custom catalog product in the back-office, its associated sell rule was not visible on the store. As a result, the user was creating another sell rule for that product with updated Mfr. Part.

After Release

  • Now when the user updates the Mfr. Part of a custom catalog product in the back-office, its associated sell rule will be visible on the store. And the system will also NOT allow the user to create another rule for that product with updated Mfr. Part.

System choosing the wrong SKU# when importing products into the Quote

Before Release

  • Previously, when the user was importing products into the quote, the system was picking the wrong SKU#. In other words, wrong products were being imported into the quote.
  • This was happening because a product with the same Manufacturer Name and Mfr. Part# was available with different distributors

After Release

  • To resolve this issue, the system will now consider SKU#, apart from Mfr. Part and Manufacturer name to search the product in the database. This will allow the system to import the correct products into the quote.
  • In case the user does not specify the SKU#, then the default SKU# of the product will be taken for searching and importing the products into the quote.

On Clicking 'Convert to Order' button on quote which is created from lead, system not displaying prompt to convert the lead to customer

Before Release

  • While converting a quote, the user was clicking on the "Convert to Order" button. However, as the quote is created from lead, the system was not displaying a prompt message suggesting to first convert the lead to customer.

After Release

  • The issue has been resolved. On clicking the 'Convert to Order' button while converting a quote created from lead, the system will display a prompt message, suggesting to first convert the lead to customer