View all releases

October 2, 2025 release notes

Tickets

KOD-17036: Don't take user to website when confirming email address
KOD-23744: Kodaris Content Developer Landing Page and Information
KOD-24966: Create Upcoming Events page
KOD-25440: InvalidKeyMapError
KOD-25579: Documentation for updating ticket templates
KOD-25584: Payment Updates
KOD-25685: Product Configurator Polishing
KOD-25767: Remove the sidebar from the split-view file viewer to save screen space
KOD-26001: Order shipment notifications - Issue with old notifications
KOD-26158: Index incomplete orders
KOD-26818: Set up CSD Payments
KOD-26905: Mock-up Details
KOD-26925: Opportunities (Map) Not Populating
KOD-27043: AR Invoices Not being emailed Created From Ticket 30209
KOD-27066: Provider Updates
KOD-27169: UPS Integration
KOD-27192: Embed Customer Dashboard
- Tests
- Case 1
  - Confirm that the /spcu/dashboard page loads and exists. If you’re not logged in, it should display a button and a message saying you need to log in to view the page. Once you log in, a Power BI dashboard for your company should load. Please confirm that it displays correctly on both large and small screens.
- Case 2
  - Confirm that if the endpoint does not return a token, we display an error window on the screen.
KOD-27223: Master order/budgets - Add UX for customer notes and line comments
- Regression Tests
- Case 1
  - Verify that the Locations page looks good.
  - Verify that the tabs on the Location page look good.
  - Verify that the Actions button is displayed on the page in the top right corner and contains the option "Attach File".
  - Verify that a file is uploaded correctly and displayed on the Files tab.
  - Verify that there are no errors in the console related to the Locations page.
- Tests
- Case 1
  - Verify that the Locations tab displays the Budget and Budget Items tabs.
  - Verify that if a Budget does not exist for a specific location, the Budget tab displays a "Create Budget" button.
  - Verify that if a Budget does not exist for a specific location, the Actions button does not contain the option "Add Budget Item".
  - Verify that when clicking the "Create Budget" button, a "Create Budget" pop-up appears with 2 required fields — Budget Name and Budget Amount .
  - After filling in the data and clicking "Create" , a Budget is created with the previously entered data (name and amount).
  - Verify that on the Budget page it is possible to leave a comment, as well as edit the Budget Name and Budget Amount . The comment is saved correctly and remains visible after refreshing the page.
  - Verify that when selecting the "Add Budget Item" option, an "Add Item" pop-up appears with a required field Unit , as well as fields Product and Expected Budget Amount.
  - Verify that after creation, the Budget Item is displayed on the Budget Items tab with the previously entered data.
  - Verify that for each Budget Item it is possible to add a comment (each item can have its own comments).
  - Verify that the UI of the Budget and Budget Items pages looks correct, without overlapping elements, etc.
  - Verify that Total Spend is displayed next to the name of the Budget Tab.
KOD-27291: Taxes on add-ons calculating differently in trend than in Kodaris on orders
KOD-27372: Test hand pricing items
KOD-27397: Help with translations
- Regression Tests
- Case 1
  - Make sure that all of the pages from the sheet are working without any errors.
- Tests
- Case 1
  - We need to test that all messages from the attached sheet are translatable on the website.
KOD-27407: Insert Authorization from Commerce Checkout
- Regression Tests
- Case 1
  - Having setting: syncPaymentAfterReleasingOrderToERP disabled.
  - After paying an order at checkout with a credit card, the order should go to CSD and tender information should be provided in the request.
  - In the request make sure the field ‘ sxt_header_extra ' GOES to the ERP. (in V6) . Basically, if payment information appears in the request we should be good.
  - You should see the request in SystemEvent under code ' CSD_SyncInsertOrder '.
- Tests
- Case 1
  - Have syncPaymentAfterReleasingOrderToERP and inforCSDTenderPaymentViaAPIs enabled.
  - Create an order and pay at checkout with a credit card.
  - We have to validate 2 things:
  - When the order goes to CSD, tender_payment information should NOT be included in the request.
  - So, in the request make sure the field ‘ sxt_header_extra ' doesn’t contain any value.
  - You should see the request in SystemEvent under code ' CSD_SyncInsertOrder '.
  - After releasing the order (It is an asynchronous process), you should see a log line like this:
  - [JS] inforCSDTenderPaymentViaAPIs is enabled. Using service APIs instead of OrderChange for tendering. Payment ID: indicating the tender process will run using API. And in the System event, a new event called
  - CSD_SyncPaymentV2 or CSD_SyncPaymentV2_Error if something went wrong.
KOD-27413: Server side export for stats pages
KOD-27448: Product Configurator - Options to hide configurator variants
- Regression Tests
- Case 1
  - Can test via swagger endpoint: api/system/productPrice/calculatePublicPricesForAllProducts
  - or run the daily interval job but need to turn on the setting: calculatePublicPrice.
KOD-27565: In stock and Warehouse stock for group and customer catalogs
- Regression Tests
- Case 1
  - Check if “in stock“ and “warehouses” filters for company catalogs are still working and showing correct data.
- Case 2
  - Check if “shop by store“ dropdown and left sidebar on the main page is displaying “favorite list“ and “recently ordered“ only for logged in users.
  - Check the mobile view if it’s working correctly.
- Tests
- Case 1
  - Check if the “in stock“ and “warehouses” filters are working correctly for group and customer catalogs.
- Case 2
  - Check if the “shop by store“ dropdown and left sidebar from the main page contains a link to the “limited time pricing“ catalog and if that link is working correctly for the logged in customers.
  - Check the mobile view as well if working the same way.
KOD-27584: Add details screen to Vendor Pricing records on Vendor Pricing screen
- Regression Tests
- Case 1
  - Check that the vendor pricing functionality works correctly on the vendor details screen. You can edit the vendor price fields.
- Tests
- Case 1
  - Check that previously added pricings are displayed correctly on the vendor details screen.
  - Check that when changing the price fields, the data is updated after reloading the page.
KOD-27594: Gift Cards
KOD-27620: Payment receipts question - ACH receipts
- Regression Tests
- Case 1
  - When clicking on the View Receipt button on a payment that was made using a card account from the Payment History screen in the customer portal, the payment receipt must be displayed for that payment.
  - Pre-requirements:
  - A card payment method must be configured.
  - Setting achSendPaymentReceipt must be enabled.
  - Steps:
  - From the customer portal, go to the Open Invoices screen and make a payment, using a card account (you should receive an email with the receipt).
  - Go to Payment History and enter the payment details of that new payment.
  - Click on the View Receipt button.
  - The receipt must be properly displayed.
  - Note : The payment receipt must be different from the one received when paid by ACH.
- Case 2
  - Validating when making a deposit from the operations portal is working as expected when paying using a bank account.
  - Steps:
  - From the operations portal, make a deposit to a company by using a bank account.
  - The receipt must be properly displayed (if the new setting achSendPaymentReceipt is enabled you must also receive an email with the receipt).
- Case 3
  - Validate make a deposit from the operations portal is working as expected when pay using a card
  - Steps:
  - From the operations platform, make a deposit to a company by using a card.
  - The receipt must be properly displayed and you must also receive an email with the receipt.
- Case 4
  - Validating when making a deposit from the customer portal is working as expected when paying using a bank account.
  - Steps:
  - From the customer portal, make a deposit to a company by using a bank account.
  - The receipt must be properly displayed (if the new setting achSendPaymentReceipt is enabled you must also receive an email with the receipt).
- Case 5
  - Validate make a deposit from the customer portal is working as expected when pay using a card
  - Steps:
  - From the customer portal, make a deposit to a company by using a card.
  - The receipt must be properly displayed and you must also receive an email with the receipt.
- Case 6
  - Validate issue charge is working as expected when paying using a bank account.
  - Steps:
  - From the operations portal, issue a charge for a company by using a bank account (if the new setting achSendPaymentReceipt is enabled you must also receive an email with the receipt).
  - Click on the View Receipt button from the display pop-up.
  - The receipt must be properly displayed and this must match with the one received by email (only if the new setting achSendPaymentReceipt is enabled).
- Case 7
  - Validate issue charge is working as expected when paying using a card.
  - Steps:
  - From the operations portal, issue a charge for a company by using a card.
  - Click on the View Receipt button from the display pop-up.
  - The receipt must be properly displayed and this must match with the one received by email.
- Case 8
  - Validate issue credit is working as expected when paying using a bank account.
  - Steps:
  - From the operations portal, issue a credit for a company by using a bank account (if the new setting achSendPaymentReceipt is enabled you must also receive an email with the receipt).
  - Go to Accounts Receivable and look for the latest WebRefund payment and verify that the setting generatedReceipt setting contains the receipt with the proper data.
  - The receipt must be properly displayed and this must match with the one received by email (only if the new setting achSendPaymentReceipt is enabled).
- Case 9
  - Validate issue credit is working as expected when paying using a card.
  - Steps:
  - From the operations portal, issue a credit for a company by using a card.
  - Go to Accounts Receivable and look for the latest WebRefund payment and verify that the setting generatedReceipt setting contains the receipt with the proper data.
  - The receipt must be properly displayed and this must match with the one received by email.
- Case 10
  - Validate paying open invoices using a bank account from the operations portal is working as expected.
  - Steps:
  - From the operations portal, go to a company Open Invoices screen and make a payment using a bank account (if the new setting achSendPaymentReceipt is enabled you must also receive an email with the receipt).
  - Click on the View Receipt button from the display pop-up.
  - The receipt must be properly displayed and this must match with the one received by email (only if the new setting achSendPaymentReceipt is enabled).
- Case 11
  - Validate paying open invoices using a card from the operations portal is working as expected.
  - Steps:
  - From the operations portal, go to a company Open Invoices screen and make a payment using a card.
  - Click on the View Receipt button from the display pop-up.
  - The receipt must be properly displayed and this must match with the one received by email.
- Case 12
  - Validate paying and order from the order screen is working as expected.
  - Steps:
  - From the operations platform, go to an order details screen and click on Pay Order button.
  - Click on the View Receipt button from the display pop-up.
  - The receipt must be properly displayed and this must match with the one received by email.
  - Note: Repeat this test for both Types (SALES and AUTHONLY).
- Case 13
  - Validate paying scheduled payment (with card and bank account) from the operations platform is working as expected.
  - Steps:
  - Schedule a payment from the customer portal with a bank account.
  - From the operations portal, go to the Accounts Receivable screen and go to the scheduled payment.
  - Click on more button and then click the “Process Scheduled Payment” option.
  - The processing of the payment must be done successfully and you have to receive an email with the receipt (for ACH payment this email is only received if the new setting achSendPaymentReceipt is enabled).
  - Repeat the test, but this time scheduling the payment using a card.
- Case 14
  - Validate paying scheduled payment (with card and bank account) from DailyIntervalJob scheduler is working as expected.
  - Pre-requirements:
  - Setting jobPayScheduledPayments must be enabled.
  - Steps:
  - Schedule a payment from the customer portal with a bank account.
  - From the operations portal, go to the Accounts Receivable screen and go the the scheduled payment.
  - Go to tab “development” and change field scheduledDate to today at midnight, e.g.: 2025-09-25 00:00:00:000.
  - Go to the schedulers and look for the DailyIntervalJob scheduler and trigger it manually.
  - After a few seconds refresh the screen and the status must be SchedulePaid and you have to receive an email with the receipt (for ACH payment this email is only received if the new setting achSendPaymentReceipt is enabled).
  - Repeat the test, but this time scheduling the payment using a card.
- Tests
- Case 1
  - When clicking on the View Receipt button on a payment from Payment History screen in the customer portal, the payment receipt must be displayed for that payment.
  - Pre-requirements:
  - An ACH payment method must be configured.
  - Setting achSendPaymentReceipt must be enabled.
  - Steps:
  - From the customer portal, go to the Open Invoices screen and make a payment, using a back account (you should receive an email with the receipt).
  - Go to Payment History and enter to the payment details of that new payment.
  - Click on the View Receipt button.
  - The receipt must be properly displayed.
KOD-27660: Vendor Import Created From Ticket 34354
KOD-27661: Vendor Import Created From Ticket 34385
KOD-27682: Add UX for lockbox EDI 820 file
- Tests
- Case 1
  - Go to Development → Importers.
  - See the new column with the name “Script Type”.
  - In the latest row (for creating a new importer) in the “Script Type” select “Mapping Script”.
  - Try to open the “Script” select and see that the options there are mapping scripts.
  - Change “Script Type” to “User Script”.
  - Open the script selector and see that options changed to user scripts.
- Case 2
  - Try to Create Mapping and User script importers for the specific entity (ex. Product).
  - Go to the Products/Data page.
  - In the top left side of the table select File dropdown, then Import and try to run each of the importers we created.
  - In the DevTools Network tab we’re using new /api/system/mapped/custom/any/file/{userScriptName}/{importType}/{fileType} endpoint for User Script, and /api/system/mapped/any/file/{mappingCode}/{importType}/{fileType} for Mapping Script.
- Case 3
  - Go to the Importers page.
  - Try to open autocomplete in the row with the mapping script type. See that the options in the autocomplete are Mapping scripts.
  - Go to the other row with “User script” script type and do the same. See that the options in the autocomplete are the user scripts.
  - Try to do the same with the “Add new Importer” row in the bottom.
KOD-27714: Create a user script for sending data via SFTP
KOD-27717: Upload images to S3
KOD-27730: Import Vendor Price file into a Vendor Pricing Record in Kodaris operations portal
KOD-27742: AP-Back Order Quantity Selected Created From Ticket 34837
KOD-27746: UOM added to product page Created From Ticket 34900
- Regression Tests
- Case 1
  - Verify that the search page displays correctly on different device types.
  - Verify that the product details page displays correctly on different device types.
  - Verify that there are no errors in the console.
- Tests
- Case 1
  - Check that UOMs are displayed correctly on the product card.
  - Check that UOMs are displayed correctly on the product detail page.
KOD-27755: parser issue From Ticket 29173
KOD-27838: AP: Exceptions Created From Ticket 35518
KOD-27843: Check on Email Sending Based on Form Inputs
KOD-27855: Update Remittance Address to Show Full Address
KOD-27857: AP: New Mapping-Vendor Updated Invoice
KOD-27860: Needed UX updates for Search screens in the operations portal
- Regression Tests
- Case 1
  - Check that the layout on Search screens looks correct.
  - Check that there are no errors in the console when interacting with Search screens.
- Tests
- Case 1
  - Ensure that the action data column is editable in the product redirect tab.
  - Ensure that “regex” option appears in the pattern column of the product search rules tab in the pop-up.
  - Ensure that supercedesOrReplacement appears in the pattern column of the product redirect tab in the pop-up.
KOD-27861: Create a document controller to generate different types of documents
KOD-27862: Add ship to filtering functionality for return orders
- Regression Tests
- Case 1
  - Create and submit a return with a given OrderID.
  - Start a return with an original OrderID.
  - Add an item to the return order that was in the original order.
  - Submit the return order.
  - This all should work.
- Case 2
  - Create a return with an OrderID and try to add an item to the return that was not in the original order.
  - Create a return with a given original order ID.
  - Add an item to the return order that was not in the original order.
  - This should fail.
- Case 3
  - Try to create a return with an invalid orderID
  - Create a return and give a valid orderID, but one that is not associated with the customer placing the return order.
  - This should fail.
- Tests
- Case 1
  - Create and submit a return order with a companyAddressCode.
  - Create a return order. Do not give them an original orderID, but do give them a companyAddressCode.
  - Try to add a product to the return order that was shipped to that address code and submit the order.
  - This all should work.
- Case 2
  - Create a return order with a provided companyAddressCode and try to add an item to the return that was not shipped to the provided address code.
  - Create a return order. Provide a companyAddressCode but not an original OrderID.
  - Try to add an item to the return order that was not shipped to the provided companyAddressCode.
  - This should fail.
- Case 3
  - Provide a companyAddressCode that the given user does not have access to.
  - Try to create a return but give a companyAddressCode that the current user does not have access to.
KOD-27865: AP- List Price Discounts Created From Ticket 35755
KOD-27871: 403 error when accessing credit application while being logged in to the operations portal
KOD-27878: AP: New Vendor for AP Automation
KOD-27877: AP: New Vendor for AP Automation
KOD-27876: AP - PO Number not Found Created From Ticket 35854
KOD-27883: AP: invoices freight charges are still populating on invoices as a line item
KOD-27902: Add expireOldQuotes job to scheduler
KOD-27915: Punchout
KOD-27918: Tweaks to Substitute parts
- Regression Tests
- Case 1
  - Verify that product details page is still looking good without any errors both for logged in users and guests.
- Case 2
  - Verify that category screen is still working fine without any errors both for logged in users and guests.
- Tests
- Case 1
  - First thing that you’ll need to check is that you don’t see any substitute slider on product details page for guest and logged in users.
- Case 2
  - Second thing is for guest and logged in users if Substitute products are available you will see the Substitute Product Available button and navigate to that product details page when you click on this button.
- Case 3
  - If a product with a substitute doesn’t have any inventory, you won’t see add to cart (both for guest and logged in user) and add to catalog for logged in user.
  - Next thing, when the product has availability and substitute products, you will see add to cart (both for guest and logged in user) and add to catalog for logged in user.
- Case 4
  - We’ll need to check that you can see inventory for products when you are a guest.
KOD-27921: Update interceptor to always push in pricing
KOD-27922: Parser request from Ticket 31115
KOD-27931: Update search rule for the Product Code filed on the Price Debug screen
KOD-27937: Update events calendar with solid color background
- Tests
- Case 1
  - Confirm that the event post template page loads correctly and that in the first block there is no background image, only the title, date, and a background color.
KOD-27938: Kodaris - Tickets Analytics
KOD-27949: AP: Investigate Mapping for Vendor
KOD-27952: KOD API user overriding pricing
KOD-27956: Pricing Issue
KOD-27958: Owners Confidential Files
- Tests
- Case 1
  - Check new swagger endpoints:
  - api/account/creditApplication/confidential/customer/file/upload
  - api/account/customer/confidential/customer/file/upload
  - /api/system/customer/{customerID}/confidential/internalFile/upload
  - /api/system/customer/{customerID}/confidential/internalFile/{internalFileID}/view}
KOD-27969: AP - PO Number not Found Created From Ticket 36325
KOD-27971: Add null check to order item weight when create Cash Quote from Quote
- Regression Tests
- Case 1
  - Validate when converting a Quote Request to Cash Quote/Account Quote when there’s at least one Item whose product weight is not set (null), no error is thrown.
  - Generate a Quote Request with at least an item whose product does not have set its weight.
  - Go to that Quote Request and click on the Start Quote button at the top right corner.
  - Select Cash Quote/Account Quote.
  - Click on the Start Quote button.
  - The Quote must be started successfully.
KOD-27976: Implement Blind Drop Ship Functionality via User3 Field
- Regression Tests
- Case 1
  - Check desktop and mobile views.
  - Log in.
  - On the first checkout tab:
  - Make sure it is loaded with no issues.
  - Make sure the styling looks good.
  - Make sure all cart items are loaded in correct quantities.
  - Make sure you are able to update order item quantity, remove item from a cart. update order item → refresh cart page. Make sure all updates are saved and displayed correctly.
  - Make sure you are able to add note, check pricing.
- Tests
- Case 1
  - Please check if the new field Add a Line Reference is visible to the user.
  - It is editable, you can add it, remove, edit.
  - Max 15 characters. Please test that validation works and you are not able to add more than 15 symbols.
KOD-27975: Add line item details to the cash quote screen
- Regression Tests
- Case 1
  - Check that the Cash Quotes > Items page appears correctly.
  - Check that the functionality for adding new items, deleting items, etc., works correctly.
  - Check that there are no errors in the console.
- Tests
- Case 1
  - Check that the “>” icon appears next to the “+” icon in the grid.
  - Check that clicking “>” takes you to the Cash Quote details page
  - Check that breadcrumbs are working correctly.
  - Check that the Cash Quote details page looks and functions correctly.
  - Verify that the icon layout is correct when creating a child item. The link to the Cash Quote details page is also available.
  - On the Cash Quote details page, the Development tab is working correctly.
KOD-27977: Implement Line-Level User Field for Job Reference
KOD-27988: AP: Notification on Internal Comments on Vendor Invoices
KOD-27991: FI Account - Sorting is not applied properly
- Regression Tests
- Case 1
  - Check that the Financial Accounts page looks good in the operations portal.
  - Check that the table fields are sortable and filterable (if the UX allows it), and that the values in the table are displayed correctly.
  - Check that there are no errors in the console.
KOD-27993: Support Email Template Updates
- Regression Tests
- Case 1
  - Check that ticket comment emails are still going out without issues.
- Tests
- Case 1
  - Check that there is now a note above the comments section on the ticket comment emails about “To respond, please reply all to this email or log in to the Kodaris ticketing system.”
- Case 2
  - Check that in the comments, the user displayed for each comment is now a nice name instead of an email address.
KOD-27994: do not send full documents
KOD-28002: Parser request
KOD-28001: Parser request
KOD-28007: Fix for kit products
KOD-28010: Kit builder fixes
KOD-28011: Brass Error Created From Ticket 36649
KOD-28013: Make GL Required
KOD-28014: Add option to Product Display Type
- Regression Tests
- Case 1
  - On the operations portal navigate to the Products Screen.
  - Select any product and navigate to its detail page.
  - Confirm Page is loaded properly.
  - Edit Product properties.
  - Confirm changes are saved by refreshing the page.
- Case 2
  - On the operations portal navigate to the Products Screen.
  - Select any product and navigate to its detail page.
  - Locate “Product Display Type” dropdown.
  - In the meantime navigate to the Settings screen.
  - Search for productDisplayTypes setting.
  - Confirm values from this setting are displayed in the dropdown.
  - Update setting.
  - Confirm dropdown options are updated (refresh product page after each setting update).
  - As part of the feature test, confirm that if the setting is blank, only ‘ None ’ “BuildConfigurator” options are displayed.
- Tests
- Case 1
  - On the operations portal navigate to the Products Screen.
  - Select any product and navigate to its detail page.
  - Locate “Product Display Type” dropdown.
  - Confirm dropdown contains “BuildConfigurator” option.
  - Select this option.
  - Confirm changes are saved by refreshing the page.
KOD-28018: Parser update 3 from Ticket 36614
KOD-28020: Add Field to Customer named department
KOD-28023: Kit builder - A non-stock items
KOD-28022: Hide prices on Purchase History Tab
- Regression Tests
- Case 1
  - On the product details page check if the history product tab is displayed correctly.
- Tests
- Case 1
  - Check the product details page history tab. There should be no price info on the product.
  - Check if the mobile view is looking good as well.
KOD-28027: Shipping Method in ERP
KOD-28032: Update Google Tag Manager
- Regression Tests
- Case 1
  - Check that the website still loads and looks as expected without issues.
- Tests
- Case 1
  - Open the page source for the website and check that the scripts from the ticket description are now added.
KOD-28037: Replatform - Customer's set my warehouse determines initial display of inventory on the PLPs & PDPs Created From Ticket 32345
- Regression Tests
- Case 1
  - Confirm that the product listing page and the product detail page load without errors, and that we can see the content loading there.
- Tests
- Case 1
  - Confirm that on the product detail or product listing page there is a skus element, and that if the pricesByCodes endpoint for the product shows inStock :
  - True → display In Stock
  - False → display Out of Stock
  - If the user has a selected warehouse, then it should also display either Available in [Warehouse Name] or Not available in [Warehouse Name] .
  - Additionally, if there are other warehouses where the product is in stock, a Check Availability button should appear, which opens a modal listing all warehouses where the product is in stock (excluding the selected warehouse). Confirm also that for B2C and Guest users we simply show a checkmark, while for B2B users we show the actual quantity.
- Case 2
  - Confirm that on the product listing page, if a product is out of stock but there are lead times for that warehouse, we display the lead time instead of Out of Stock .
- Case 3
  - Confirm that for B2B users, the availability number is displayed next to the selected warehouses.
KOD-28043: Parser From Ticket 36788
KOD-28044: Enable delete orphan settings globally
KOD-28048: Order Line issue
KOD-28052: Search tuning
KOD-28083: Integrated Device Configuration
KOD-28086: Category search redirects
KOD-28093: Cart Step 2: Make 'Company' field optional for B2C users Created From Ticket 32406
- Regression Tests
- Case 1
  - Confirm that the checkout tabs work correctly, we can switch between them and they load properly.
- Case 2
  - Confirm that for B2B users (customers) the company field should be required.
- Tests
- Case 1
  - Confirm that for consumers the company field in the second tab will be optional, but for logged-in customers it will be required.
- Case 2
  - Confirm that we can place an order and in operations we won’t have a location name in the delivery address if the user didn’t enter it.
KOD-28099: Swiper style
KOD-28098: Breadcrumbs formatting when categories and product name are too long
- Regression Tests
- Case 1
  - Check that the product detail page still loads as expected without issues.
- Tests
- Case 1
  - Go to a product detail page with really long breadcrumbs. The breadcrumbs should now be formatted nicely.
- Case 2
  - Check the same as Case 1 for mobile view.
KOD-28100: CSD order creation
KOD-28109: Catalog Search Displays Error Page
KOD-28118: InforCSD Adjustments