In this release, we’ve added a new screen titled “Returns” to the Customer Portal that allows your customers to view their previous returns and initiate new returns. Leveraging this feature can help streamline and organize return processes for both you and your customers, saving time and overhead.
Similar to other screens in the Customer Portal, the “Returns” screen offers both grid and spreadsheet views, and your customers can choose the columns/fields they’d like to add to their view (e.g., Web #, Company Name, Status, Last Modified, etc.). On this screen, they will be able to view, search, and filter by their existing returns, as well as create new returns.
When a new return is initiated, the Kodaris system will automatically assign a return number and track the created date, the last modified date, and the status of the return. Customers will be able to add returned products as line items by entering the product code, the quantity they wish to return, the return reason (e.g., overstocked, defective item, poor quality, incorrect item, etc.), and a comment.
Keep in mind that only items associated with paid or invoiced orders will be eligible for returns. Once an item has been added as a return, customers will be able to see the original invoice tied to the return item. They will also be able to attach files to returns if needed.
The “Returns” screen is not automatically enabled. If you’d like to offer this feature to your customers, you will need to enable it. If you have questions, please contact your Kodaris Account Manager.
To learn more about the “Returns” screen, check out the video below:
https://youtu.be/CNLD_Qncb4c
Point-and-click multilingual capabilities added to Customer Portal
To make text translations even easier than before in the Customer Portal, we’ve added a point-and-click, visual translator tool. By using this tool, you can easily translate text in the Portal to any language you see fit, providing a more seamless user experience for customers who are non-native English speakers.
Watch the video below to learn more about this feature and how you can begin using it:
https://youtu.be/Ucq2SvIRiUY
Developer
“Copy Request Payload” feature added to grid screens
When developing in Kodaris, oftentimes, you have to assemble API requests. To make it easier to obtain the API requests you need, we added a “Copy Request Payload” feature on all Search and Data grid screens in the Operations Portal. This enables developers to easily and quickly obtain API requests, which they can then drop into the code, saving them the time and effort it would take to build the API requests manually.
Watch the video below to see how you can access the request payload feature on the Search and Data grids:
https://youtu.be/NbECFeWcqzc
Commerce
Categories included in breadcrumbs when product is selected from search page
Website breadcrumbs typically give users a secondary means of navigating a website by offering a breadcrumb trail. Breadcrumbs can enhance the ability to reference parent pages or the previous pages they navigated to get to their current page.
While your Kodaris website has always displayed product breadcrumbs, the breadcrumbs will now include the product category when a product is selected/viewed from a search page. Listing the category in the breadcrumbs from a product search will allow customers to more easily view and access the assigned product category.
Learn more about this update in the video below:
https://youtu.be/a-v4_kimM8A
Tickets
KOD-14476: Utilizing Pricing Modifiers for Product Pricing
KOD-19137: Add point and click multilingual to customer account portal
Regression Tests
Case 1
Make sure all pages on the customer portal load correctly.
Case 2
Make sure the links under the dropdown by your name still all work.
Tests
Case 1
Log into the customer portal → click on Profile → notice new section called Translation Mode → it should be a dropdown with options Disable or Enable → click Enable → notice all the translatable words/phrases now have a red underline.
Case 2
Make sure translation mode is enabled → hold down the option key then click on whatever word/phrase you want to update → a pop up should appear with a text box to update text → update to whatever you want → click save → notice word/phrase has been updated → reload the page and notice updated word/phrase is still there.
Case 3
Option/click on one of the translatable words → write something in the box → either click out of the box area or click cancel → notice the word has not been updated.
Case 4
Go to Profile → Preferences → update your language → notice the translatable words update to whatever the language is → update one of the words → click save → change back to a different language → see the words change → change back to original language → notice the word you updated is still there.
Case 5
Make sure translation is enabled → update one of the words → disable translation → notice all updated words are still there.
Case 6
Ensure that the employee with the same username as the customer has the customerPortalCustomize role -> go to the customer portal -> profile page -> and make sure the Translation mode section is visible.
If the employee does not have this role, the section should not be visible.
Case 7
Make sure the translation mode is enabled -> navigate to another page (home, for example) -> Option/click on one of the translatable words → write something in the box → save the changes → make sure the word has changed.
Case 8
Confirm that when the translation mode is enabled or disabled, changing the language field will cause the page to reload and will translate the content into that language that we choose.
KOD-21640: Mobile - Customer product #
KOD-22124: Check Breadcrumbs when Category 1 instead of Primary Category is Assigned
Regression Tests
Case 1
Product page was opened from category page.
Expected result: Nothing changes in breadcrumbs displaying: category tree is shown.
Case 2
Primary category was set for a product.
Product page was opened from:
Search page
Recently viewed widget
Expected result: Nothing changes in breadcrumbs displaying: Primary category is shown.
Case 3
Primary category was set for a product
Any category 1-20 was set for a product.
Product page was opened from search page.
Expected result: Nothing changes in breadcrumbs displaying: Primary category is shown.
Tests
Case 1
Primary category was NOT set for a product.
Any category 1-20 was set for a product.
Product page was opened from:
search page
Recently viewed widget
Expected result: breadcrumbs display the first category from the category 1-20 fields, usually it’s category 1.
Case 2
Primary category was set for a product.
Any category 1-20 was set for a product/were not set.
Product page was opened from the customer catalog page.
Expected result: breadcrumbs display the Primary Category.
Case 3
Primary category was NOT set for a product.
Any category 1-20 was set for a product/were not set.
Product page was opened from the customer catalog page.
Expected result: breadcrumbs display the first category from the category 1-20 fields, usually it’s category.
Case 4
Product page was opened from:
Featured products widget
Recommended products widget
Expected result: Nothing was changed in the breadcrumbs displaying.
KOD-22489: Line Level Discount as a Dollar Value (Overall fix for all types of Coupon Codes & Discounts)
KOD-22722: Update order import UX to use correct endpoint
Regression Tests
Case 1
On the Global Orders Data screen make sure all import / export options are available.
Tests
Case 2
On the Global Orders Data Screen: make sure all import options are working with no issues and for import following endpoint is being used: api/system/mapped/any/file/{mapping}/{importType}/{fileType}.
Make sure you can still edit/save/preview a CMS page.
Tests
Case 1
Go to CMS → Pages → Add Page → Gutenberg → can select a layout or just x out of it → click the plus button and start searching for CM: Section: Brand Specific Product Categories →_ click on it → you should be able to update the title and subtitle if you want → click the section and click block on the right hand side → here you can also update the title and subtitle if you wanted as well as select a brand → start searching for a brand and select it (need to make sure there are products under that brand that have categories associated to them) → click save.
Case 2
Click preview → you should see the categories that are associated to products with that brand → if the category has a medium image, it should display, else it will show the standard logo sample.
Case 3
Under each category should say "Shop Now" and should be clickable → click on one → you should be redirected in a new tab to that category and have it filtered down with that brand that you originally chose.
KOD-23378: Kodaris Website Pricing Page Design
Tests
Case 1
Go to /spcu/product-ai.
Check that the page looks like the example figma and looks good on both desktop and mobile.
KOD-23563: Product Regionality Restrictions
Regression Tests
Case 1
As guest and logged in user → Check the category, search and product pages, make sure they all still work as normal.
Tests
Case 1
Go to the operations portal > filter categories > fg_restrictions and create (if needed) a new attribute with the code format → fg_restrictions_state_(state code), e.g. fg_restrictions_state_tx.
Then add some products.
Next, go to the website, login, select a shipto where shipto.state = the state code in the attribute you just created.
You should not see the products that you added to the attribute on the following screens:
Category
Search
Search dropdown
Product Details
Case 2
Go back to the filter categories > fg_restrictions.
This time add (if needed) a few attributes with code format → fg_restrictions_territory_(sales territory code), e.g. fg_restrictions_territory_eng
Add some products.
Now with this setup, only companies with the salesTerritoryCode field = the salesTerritoryCode on the new attribute code, can view the products you’ve added.
Then go to the website, login, and you should be able to see the products you added to the attribute on the following screens:
Search
Search dropdown
Category
Product Detail
Case 3
Follow the same steps as in case 2, except this time, either create a different attribute with a different sales territory code, or change the sales territory code on the company.
On the following screens you shouldn't be able to see the products added to the previous attribute:
Search
Search dropdown
Category
Product Detail
Case 4
And then if you have access to view the product from the salesTerritoryCode attribute, if its in the shipto state attribute, you shouldn’t see the product on the screens.
Case 5
Also, if the same product is in multiple sales territory code attributes, you should still be able to see it on the website if you company.salesTerritoryCode matches one of them.
KOD-23585: Mobile menu updates
Regression Tests
Case 1
Make sure the website loads properly and you can still open the mobile menu both as a logged in and logged out user.
Case 2
Make sure you can still click the shop by category dropdown and the header items on the main page (not in mobile view).
Tests
Case 1
Do not log in → click the mobile menu button → notice the new layout.
Sign in or create account button should be up top → if you click it, it should route you to the login page.
Logo next to the sign in button → if you click the logo, you will be redirected to the home page.
If you can select a warehouse, you should see the shop by store button or if you have a selected warehouse, it should show here. If you click it, it will bring up the select by store modal.
If a row as an arrow next to it, it will bring you to a new menu page. If there is no arrow, it should link you to the appropriate place.
Case 2
If you click into one of the menu items, you will see a new list of items that if you click the link, it should take you to the appropriate place and you will also see a ‘Back to Main Menu’ option → if you click it, it will take you back to the main menu.
Case 3
Log in → this time you should not see the Sign In button, instead you should see ‘Hi, [name]’ where name is either First Name if set in ops portal under the customer or it will be your email if name is blank) the My Account row → click into it and you should see all the items associated with your account. The first two items under My Account are your selected company and selected delivery address → both of these should not be clickable.
Case 4
Under my account, there should be a log out button → click that and it should log you out.
KOD-23590: PIM Integration
KOD-23593: Cash Quote Warehouse is Not Defaulted to arsc Warehouse
Regression Tests
Case 1
Start Company Order in the operations portal.
Case 2
Start Cash Quote in the operations portal.
Case 3
Start Quote in the operations portal.
Case 4
Start Cart and complete checkout.
Tests
Case 1
Start Company Order in the operations portal.
If Company has warehouse set on it and no warehouse is set on Employee - Company warehouse should be used for Order
Use Operations Portal > Logs to see more info on what warehouse is picked up and what is the source.
KOD-23600: Invoices not found - Customer portal
Regression Tests
Case 1
Log in to the payment portal.
Navigate to the orders screen.
Select any order.
Confirm on the detail page you can see order information.
Case 2
Log in to the payment portal.
Navigate to the orders screen.
Select some orders and downloads them as PDF.
Confirm pdf files are downloaded.
Tests
Case 1
On the payment portal search for order with no items.
Confirm this product is displayed on the site at the detail tab.
Click on “Print” button.
Confirm pdf is downloaded properly.
Case 2
On the operations portal find order with no line items.
Navigate to the order and click on “Email Order” button.
Click “Configure”.
Confirm that order email preview displayed properly and there were no issues.
KOD-23644: Enable Consumer Signup
Regression Tests
Open the website.
Attempt to log in using valid credentials.
Verify that the login process works the same as before code changes.
Tests
Case 1
Open the website.
Navigate to the Operational Portal and go to the Settings section.
Enable the following setting: customerRegistrationEnabled.
Verify that the registration button is displayed in the header.
When this setting is disabled, the registration button should NOT be displayed in the header.
Add any product to the cart.
Check whether the registration button is correctly displayed (or hidden) in the cart as well.
KOD-23651: Add Copy Request Payload action on the Account Receivable screen
Regression Tests
Case 1
Open the operational portal.
Navigate to any screen.
Verify page actions, including:
Refresh functionality.
Pagination behavior.
Clicking on a detailed view to check navigation and content display.
Any other available actions (filters, sorting, etc.).
Ensure the system functions correctly without any errors.
Tests
Case 1
Open the operations portal.
Navigate to any screen.
Verify the Search Tab:
Click on the content_copy icon.
The data should be copied to the clipboard.
Open any note-taking application and paste the copied content to verify.
Open the Data Tab:
Click on Edit and select Copy Request Payload from the menu.
Paste the copied content into a note and compare it with the data in the Network tab.
Perform various actions on the page and repeat the process to ensure the functionality works correctly in different scenarios.
Filter the data and then re-check again the copied payload.
KOD-23659: Strip characters from postal code
KOD-23720: Copy Escalation Endpoints for new Price Escalation Screen
KOD-23735: Statement Templates
KOD-23736: Invoice Mailer Template
KOD-23741: Manually adding line item discounts
Tests
Case 1
New endpoints added - create manual OrderDiscount: in Order API, Quote API, VendorInvoice API.
Case 2
OrderItems list endpoint now returns items with orderDiscounts list on each item (if any for a given item).
KOD-23759: Add additional Fraud data to fraud screens in UX - Step 2
KOD-23764: Equipment on Site Updates
Regression Tests
Case 1
Check if you can add items to cart form product list/ product detail page.
Check if data is displaying correctly on product list view (list view, grid view, catalog view).
Mobile / desktop
Check if product detail page is working correctly.
Tests
Case 1
Set header for product on product details in Operation portal, and check if data are reflected in product detail page for customer.
Case 2
In the operations portal go to products, find for one product and display user10 column.
Try to update values for user10 field with “requestQuote“ or “allowFinancing“ or both values separated by comma: “requestQuote,allowFinancing“ and check if you can send request quote or navigate to equipment financing page based on what you decided to provide to user10 field.
KOD-23778: Display additional information on the product details page
Regression Tests
Case 1
Check if product page for customers is displaying information correctly.
Tests
Case 1
In the operations portal → products → in grid display extra2 column and provide some number, then check if this number is reflected on products page for customer.
Case 2
In the operations portal → products → product → country of origin under attributes (extra5 in grid) select country from dropdown.
Check if country origin is displayed on product Page for customer.
Case 3
Check dropdown for countries. There should be only US available to select for customers page.
Checkout view, theme customizer.
You should be able to change country of origin in product details (operation portal) and those country should be reflected on product page for customer.
KOD-23779: Add registration link to Sign In pop-up and Login page
Regression Tests
Case 1
Navigate to the website and open the Registration page.
Fill out the registration form with valid details and click Submit.
Go to the Operations Portal Emails page to verify that the registration confirmation email has been successfully generated.
Tests
Case 1
Navigate to the website:
Click on the “Account” icon and confirm the presence of the “Register for an Account” link within the pop-up.
Validate the registration link functionality:
Click on the “Register for an Account” link.
Verify that it redirects to the registration page successfully.
Fill out the registration form with valid test data on NEW CUSTOMER ACCOUNT and NEW COMMERCIAL ACCOUNT.
Submit the form and verify a successful registration message.
Verify the registration link on the login page.
Repeat steps on a mobile view.
KOD-23785: Easily View and Remove Selected Filters
KOD-23795: Implementation - Specifications tab
Regression Tests
Case 1
Check if tabs on product detail page is working correctly.
Tests
Case 1
Check if specs tab is displayed correctly.
Check if you can update specs for product.
Check if data are reflected on product detail page for customer.
KOD-23804: Update the script
KOD-23822: Sort Blogs by Order and Created Date
KOD-23827: Implementation- ecomm issues
Regression Tests
Case 1
Confirm that the product list page loads without issues and displays content with products.
Case 2
Change the product quantity input, click the "Add to Cart" button, and ensure that the quantity in the cart matches the value selected in the input.
Confirm that this works consistently across all layouts on the product listing page.
Case 3
Confirm that clicking the "Quick Order" button opens a popover with inputs, where clicking the "+" or "-" buttons appropriately increases or decreases the input value.
Tests
Case 1
Confirm that clicking the "+" or "-" buttons appropriately adjusts the input value.
Case 2
Сheck that logic for all pages where you can find the input with + and - buttons.
Confirm that when clicking the minus or plus button, the input value will never exceed the min and max attributes.
Confirm that when changing the input value to something outside the min or max attributes, it will be set to either the minimum or maximum value upon losing focus.
KOD-23829: Add endpoint to display the list of emails on Customer Screen
Regression Tests
Case 1
Test new POST endpoint: /api/system/customer/{customerID}/email/list.
KOD-23835: Display Order Discount in CSD
KOD-23841: Make /api/user/search/product/text server side
KOD-23854: Display Minimum Order Qty in Quick Order Feature
Regression Tests
Case 1
Open the website.
Use Quick Order to add a product that does not have a minimum quantity or step increment.
Verify that the product is successfully added to the cart.
Repeat the same process on the Quick Order page to ensure consistent behavior.
Tests
Case 1
Open the website.
Log in.
Click on the QUICK ORDER button.
Start typing the product code and select the product that has a minimum order quantity.
Verify that after autocomplete, the minimum quantity appears in the input field with the counter.
Change the quantity to a number lower than the minimum and attempt to add it to the cart.
A validation error should appear, stating that the quantity needs to be adjusted.
Verify the step increment for products:
Test a product that has a specific step value.
If step = 5, clicking the + button should increase the quantity by 5.
Add multiple products and click ADD MORE ROWS to check if additional input rows appear correctly.
Repeat the same checks on the Quick Order page.
Test the mobile version to ensure correct functionality and responsiveness.
KOD-23864: Display Customer Project field value on the Search tab on the Ticket Template screen
KOD-23872: Add In Stock Filter
Regression Tests
Case 1
Verify That the Filter is Not Displayed When the Setting is Disabled.
Preconditions:
pimInStockFilterEnabled Is not enabled.
Steps:
Open the website and log in if not already logged in.
Select any product category or use the search function with “*” to display all products.
Ensure that the In Stock filter is not visible when the setting is disabled.
Verify that all other filters function as expected.
Tests
Case 1
Verify the ‘In Stock’ Filter Functionality.
Preconditions:
Should be enabled pimInStockFilterEnabled.
Steps:
Open the website and log in if not already logged in.
Select any product category or use the search with “*” to display all products.
Click on “Yes” in the In Stock filter.
Verify the results:
The number of displayed products should decrease.
Only products that are currently in stock should be visible.
KOD-23878: Enable pickup panel for OAN skus without inventory
Regression Tests
Case 1
As guest and logged in user check:
Category and search grid/list and product detail pages, cart items page are not broken.
If there is possibility to select Pickup and Delivery for an items, you should be able to add this item to a cart. At cart page you should be able to see your selected product with Pickup/Delivery option you’ve chosen.
Case 2
For guest users:
Check devtools → Network tab → response of api/user/product/pricesByCodes endpoint → in that response check skuData field.
If in the skuData each SKU has status “o” or “O” and availability 0 - than Pickup option should not be available for this product on product detail, category grid/list, cart items pages.
Tests
Case 1
Log in.
Make sure Pickup option is available for this product for logged in user. And on Pickup warehouse click - Pickup Panel is opened.
KOD-23883: Move Social Media Icons To Footer
Regression Tests
Case 1
Check that the top bar section is displayed on the page (the section just above the header).
Check that the layout of the main page is displayed correctly (including the mobile version).
Check that there are no errors in the console.
Tests
Case 1
Check that social media icons have been removed from the top bar.
Check that the social media icons in the footer look correct (fills the whole ‘grey’ circle).
KOD-23887: Sync data to customer site
KOD-23893: Customer Returns Screens - Updates
Regression Tests
Case 1
Set customerReturnsEnabled value to 0 or when this setting doesn’t exist in the global settings.
In Customer Portal:
Make sure Returns tab isn’t shown on the left nav.
Make sure in the Orders Tab Returns are shown along with regular orders (except those with the status “Initialized“).
Check spreadsheet view and sticky filters - those should work with no issues.
Check exporting orders:
For the .csv export - returns should be exported along with the Orders.
PDF and Sage - select order and generate file. Make sure for returns files are generated the same way as for the regular orders.
Case 2
Set customerReturnsEnabled value to 1.
Make sure there is Returns Tab below the Orders Tab in the left nav.
On the Orders Tab make sure there are any returns shown within the orders.
Order Export: .csv, pdf and sage - you should be able to export only Orders (not returns). Returns should not be shown on the grid and included to the exported files.
Case 3
Set customerReturnsEnabled value to 1.
Check Returns Tab.
Make sure on the grid only Returns in all statuses are displayed.
Check spreadsheet view. On that view columns should display data the save way it is displayed on the List View.
Test sticky filters for different views. They should work with no issues.
Check .csv export. Make sure all returns (and only returns - not orders) are exported from the Returns Tab.
You should be able to open returns detail with no issues by clicking on the arrow button or web number or ERP number.
On the Return Detail - make sure is is not broken.
Make sure you’re able to attach file to the return.
Case 4
Check autocomplete dropdowns within the customer portal. Make sure they work with no issues.
Tests
Case 5
Set customerReturnsEnabled value to 0.
In Customer Portal Returns Tab should not show in the left nav.
On the Orders tab make sure returns show up under the orders grid and export.
Set customerReturnsEnabled value to 1.
In Customer Portal Returns Tab should show in the left nav below the orders.
Make sure on the Orders grids, Returns are not displayed, and you cannot export Returns from the Orders Tab export.
Returns Tab:
Make sure returns in all statuses are shown there. You should be export them as .csv from the Returns tab.
Returns: check spreadsheet view and sticky filters - they should work the same way as regular list view + sticky filters.
Case 6
Check Return details tab:
"Created" and "Last Modified" dates should be shown with no issues.
Return Items Table updates: Fist Column Invoice should contain originalOrderID column with the link to that order which is opened in the separate Tab.
On successful quantity update Total Column value should be updated automatically.
On error while quantity - quantity value should be reset to it’s original quantity value.
Added Return Comment column which reflects sscReceivedNote field value.
At the end of each table row there was added trash icon button. On click it should delete item from the return items.
All updates should happen on blur.
When Return has ERP # or has status "Received" - Return Items Table should not be editable. All inputs on the page should be disabled.
Case 7
Check product autocomplete input on Return Details.
Make sure it works with no issues.
Make sure after successfully adding a product to the Return via this input - product code and quantity are cleared out and product input is focused but panel is no shown. Panel should be shown only after typing the characters from the keyboard or pasting them.
Case 8
Operations Portal.
Order Items, Quote Items, Cash Quote Items.
Make sure "Return Reason" and "Return Comment" columns are added to the above grids.
Make sure "Return Reason" column is editable.
Case 9
For the Return with extra5 field or order which is in the status “Received“:
Make sure those returns are not editable.
For the Return Items: all fields that were input fields: they should display it’s values as simple text. Delete buttons should be hidden.
Add Return Item input should be hidden.
KOD-23896: Master Catalog - Migrate Images
KOD-23898: Implementation - Purchase Order Parser
KOD-23908: Fix Issue with Add to Cart Disabled for Guest Users for Certain Products
KOD-23920: Site Adjustments - Part 2
Regression Tests
Case 1
Perform all tests as a guest and logged in user on category (search) grid, list, catalog pages, product details pages and cart items page.
Make sure all those pages are not broken.
Make sure you’re able to add products to a cart in the correct quantity.
Make sure + and - buttons near the quantity number input work with no issues.
Tests
Case 2
Configure only Interval Order Quantity on the product.
Check this product on following pages:
product page
category grid/list/catalog view
at shopping cart
Make sure by default minimum quantity shown is interval order quantity (since you haven’t configured minimum order quantity initially)
Make sure that quantity can be updated only by the configured interval on those pages.
Case 3
Configure Interval Order Quantity, Maximum Order Quantity and Minimum Order Quantity on the product.
Check this product on following pages:
product page
category grid/list/catalog view
at shopping cart
Make sure that by default on a product quantity is shown minimum order quantity. Quantity could be updated only by your configured interval and should not be more that your configured maximum order quantity.
Case 4
Configure Maximum Order Quantity and Minimum Order Quantity on the product.
Check this product on following pages:
product page
category grid/list/catalog view
at shopping cart
Make sure that by default on a product quantity is shown minimum order quantity.
Quantity could be updated only by interval of 1 and should not be more that your configured maximum order quantity.
Case 5
Configure Interval Order Quantity, Maximum Order Quantity on the product.
Check this product on following pages:
product page
category grid/list/catalog view
at shopping cart
Make sure by default your minimum order quantity is your interval order quantity.
Case 6
Configure Interval Order Quantity, Minimum Order Quantity on the product.
Check this product on following pages:
product page
category grid/list/catalog view
at shopping cart
Case 7
Configure only Maximum Order Quantity on the product.
Check this product on following pages:
product page
category grid/list/catalog view
at shopping cart
KOD-23921: Implementation - Price issue
KOD-23923: Getting admin access error when adding Secondary Email in Companies>Contact Info
Regression Tests
Case 1
For the next screens check that they work as expected:
Cash quote Details
Company Details
Company Payment Methods
Employee Details
Order Details
Quote Details
Summary Order Details
Vendor Details
Warehouse Transfer Details
Tests
Case 1
For the next screens:
Cash quote Details
Company Details
Company Payment Methods
Employee Details
Order Details
Quote Details
Summary Order Details
Vendor Details
Warehouse Transfer Details
Focus any input and press enter
Make sure nothing unexpected happens(no extra calls are sent, no dialogs are opened, etc.).
KOD-23928: Allow employees to subscribe to order shipment notifications
KOD-23931: Make FAQs Point and Click
Regression Tests
Case 1
Make sure Customize Theme tab and Cart works fine.
Tests
Case 1
Customize Theme Panel.
Expected Results:
New section is available: FAQ.
It’s possible to edit FAQs.
The results are displayed on the FAQ panel on the Cart Payment page.
KOD-23945: Pull POD Signatures from IDM for Invoices
Regression Tests
Case 1
Check that order details in customer portal and order pdf still work as expected.
KOD-23946: Add Export for ALL attributes - do not cap at 20
Regression Tests
Case 1
Export for category assignments should continue working and exporting up to 20 category columns.
If you don’t select any ‘category’ column then those won’t be exported as intended.
Case 2
We have modified attribute assignments for exporting max attributes columns depends on new setting: limitProductAttributeAssignmentsColumnsToExport. However, if the user doesn’t select any column at all then we export file without any attribute column.
Tests
Case 1
The number of ‘attributes’ column setting: limitProductAttributeAssignmentsColumnsToExport indicates the MAX attributes columns. So here, if you fill in with a number bigger than 20, those columns will be generated.
If you populate with a value less than 20, there will be just those columns (So, in other words, it doesn’t mater that UX shows 20 attributes, we will only show as many as the setting value).
KOD-23951: Implementation - OAN Products
KOD-23958: Map Vendor Name and Product Code from the ERP
KOD-23959: Map Sellmult to Kodaris PIM Multiplier Fields
KOD-23962: Display Shelf Pack in Product Specs
Regression Tests
Case 1
For this regression test, we will go to a Product Page and make sure everything loads properly.
Open the Specs tab and make sure everything looks good.
Tests
Case 1
For this test, we will go to a products page and open the Specs tab.
Previously, we were taking the “Shelf PK” from the “Specs” screen on the product page on the operations portal.
Now, we are taking the “user6” value from the Skus screen - Custom Fields grid and renamed it to “Shelf Pack” when it exists. If it doesn’t exist, we should still take the “Shelf PK” value.
Make sure that there are no duplicate Specs on the Specs tab on the product page when we have both a “Shelf PK” spec and a “user6” attribute on the sku.
KOD-23963: Ensure Customer Product Codes are Searchable
KOD-23966: Password Parameters
Regression Tests
Case 1
Navigate to the website.
Fill out the password reset form.
Click Submit and verify that a success message confirming the password reset is displayed.
Tests
Case 1
Preconditions:
Ensure the following settings are enabled:
minimumPasswordLength (value > 0)
customerPasswordRequiresLetterAndNumber
customerPasswordRequiresSpecialCharacter
Steps:
Open the website.
Navigate to the following pages:
Page 1: /account-password
Page 2: /reset-password
Start entering a password.
Check the validation rules.
Test different password scenarios.
Expected Result: Only passwords that meet the requirements are accepted.
KOD-23967: Catalog View Updates
Regression Tests
Case 1
For this regression test, we will go to the Product List page and open the Catalog view.
Make sure that everything loads properly and that you can change the units, Qty and Add to Cart.
Tests
Case 1
For this test, we will go to the Product List page and open the Catalog view.
Now, the attribute columns should be gone and we should have a “Name” column after Part, which contains the product name as a link that redirects you to the product page.
KOD-23969: Recently Ordered Catalogs and Purchase Details
KOD-23979: Typography issue in Gutenberg editor - Button block
Tests
Case 1
Open a page using the Gutenberg editor via Operations portal.
Add a Button Block to the page.
Set a custom text size using the Gutenberg block settings.
Verify the text size updates inside the editor.
Verify Text Size Applies in Preview Mode.
Click Preview to view the page in preview mode.
Inspect the button text size.
KOD-23980: Typography sizing does not work in Gutenberg editor Paragraph block
Regression Tests
Case 1
Check that text on CMS pages still displays as normal.
Tests
Case 1
When setting the text size on a paragraph block, the size should display the same on the website as in the page editor.
KOD-23981: Update Unit Conversions screen - UX
Regression Tests
Case 1
On Unit Conversions global screen:
Make sure it is not broken.
Make sure you’re able to edit/delete/create unit conversion records.
Tests
Case 2
On Unit Conversions global screen:
Make sure Product Code column was added to the grid column list. Select it.
On double click on the Product Code sell or at the footer make sure you can see product autocomplete where you can search by product code.
Case 3
At the grid footer on Product Code cell: select any Product Code from the autocomplete and press Enter to create new Unit Conversion record.
Make sure new Unit Conversion record was created with your specified Product Code.
KOD-23989: Implementation - Purchase Order Parser
KOD-23990: Implementation - Purchase Order Parser
KOD-23991: Add eco fee totals to order email, pdf and thank you page
KOD-23993: Register Account / Contact Pages
Regression Tests
Case 1
Check that the login page appears as normal.
Tests
Case 1
Go to /spcu/request-account.
It should look similar to the current request account page and work fine.
Also check that mobile view looks good.
Case 2
Go to /spcu/contact.
It should look similar to the current contact page and work fine.
Also check that mobile view looks good.
Case 3
Go to the login screen, there should be a new request account link below the forgot password link.
It should redirect to the correct page.
KOD-23997: collect credit memo number
KOD-23998: Design adjustments
KOD-23999: Add customerReturnReceivedReasons setting to employee configuration endpoint
Tests
Case 1
Check setting: customerReturnReceivedReasons whether it returns on endpoint /configuration on employee side.
KOD-24010: Implementation - Branding
KOD-24013: Make "Department" Field Customizable in Settings
Regression Tests
Tests
Case 1
Setting ticketDepartments should appear as a list of string under /configuration in the operations portal.
Case 2
On the Ticket Detail page, the Department field should have a dropdown menu instead of an input field.
In the ticketDepartments setting, we can customize values (should be comma-separated).
The dropdown should reflect the updated options.
Changes should persist after saving and refreshing.
KOD-24017: Add Alt tags to the PIM images
Regression Tests
Case 1
For this regression test, we will go to a Product Details page.
Make sure that everything loads properly and that the images look fine.
Tests
Case 1
For this test, we will go to a Product Details page.
Make sure that product has files uploaded on the Public Files tab on the operations portal.
We will inspect the active image displayed and also the carousel images.
The file name should be now displayed on the alt attribute of the image.
KOD-24022: Company - Operations
KOD-24023: Product Regionality Restrictions
KOD-24024: Customer Comment Date Discrepancy
KOD-24031: Update ERP mapping for companies(credit card)
KOD-24034: Product Detail Page style updating
KOD-24035: Employee App - Simplified consolidated lead details screen
KOD-24038: UX - Add option to combine multiple invoices on invoicing config screen
Regression Tests
Case 1
For this regression test, we will go to the Automated Invoice Delivery screen.
Make sure everything loads properly on the page and that you are able to update settings.
Case 2
For this regression test, we will go to Companies - Select a Company - Details tab.
Make sure you are able to update fields with no issues.
Tests
Case 1
For this test, we will go to the Automated Invoice Delivery screen.
We should see a new setting called Combine Invoices Into One PDF under Send Invoices in Bulk.
Make sure the setting is already created for the environment you are working with. If the setting doesn’t exist, the select should appear empty and trying to change the value will result in an alert message popping up.
After you create the setting, the value 1 should display a ‘Yes’ in the select, and 0 should display ‘No’.
Please test changing the values in both the Settings screen and Automated Invoice Delivery screen.
Case 2
For this test, we will go to Companies - Select a Company - Details tab - Automated Invoicing & Statements section.
You should see a new form field called Combine Invoices Into One PDF.
We will test this field. When we change the selection, the company should be updated with the new value.
KOD-24040: Check PO# not Populating on Parser Upload
KOD-24043: New Residential Embedded Sheet Parser
KOD-24045: Implementation - Spin up system
KOD-24050: Implementation - Install Applications
KOD-24053: Eco fee UX update
Regression Tests
Case 1
Log in to the website as a customer and make sure that the product list page and product details pages are not broken.
Tests
Case 1
Now the eco fee icon will only be shown on a product if users selected shipto state matches the eco fee’s stateApplies field.
KOD-24054: Updates to footer and header
Regression Tests
Case 1
Make sure header menus and footer are not broken.
Make sure sitemap page is displayed with no issues.
Tests
Case 1
At header menus: check that menu tiles are displayed in regular case except for 1st letter.
Case 2
Footer:
Make sure there were added 3 links to the footer. Terms and Conditions, Privacy Policy and Sitemap. All links should lead to the correspondent pages.
There is Terms and Conditions, Privacy Policy and Sitemap, but there are strange symbols between these points.
Case 3
Open Sitemap page.
Make sure at the top of the page breadcrumbs are displayed.
Make sure styling matches Sitemap styling from the Figma.
Sitemap should contain 1 column. All page links should be displayed without bullets.
