6/9/2026 Release Update
The following updates were released to production on June 9, 2026.
IMPROVED & BUG FIXES:
Order Automation
🔧 Fixed: Reassigning a Quote to a Different Contact Now Works Correctly
When a quote was reassigned to a different contact, the order was being sent to the ERP but all item quantities came back as zero — and the quote stayed stuck in Draft status with no link sent to the contact. Reassigning a quote now processes as expected: the status updates to Pending or Confirmed, and the contact receives their link.
Note: The selected contact and company should be linked to each other and have valid external IDs.
🔧 Fixed: Replacing a Line Item Now Swaps In Place
When replacing a matched line item on a quote, the replacement was showing up as a new row at the bottom of the list instead of taking the original item's spot. On top of that, closing and reopening the quote caused the Matched badge and matched text to disappear. Both issues are resolved — the replacement now lands in the correct row, and match information stays visible whether the replacement came from the suggestions list or a manual search.
🔧 Fixed: Quote Submission Errors Are Now Surfaced
When sending a quote with a delivery option, certain errors — like a missing shipping address or a location not approved for delivery — were either being silently swallowed or triggering a vague secondary error. Counter reps had no clear signal that something went wrong or what to do about it. Counter reps will now see a clear error message when a quote can't be sent, so they know what to correct.
Data and AI Platform
🚀 Product Match Rankings Now Reflect Each Location's Own Order History
Sales volume boosting — which places frequently-sold products higher in match results — now works at the individual location level rather than across the whole account. Previously, high sales volume at one branch could influence product match rankings at other locations in the same account. Each branch's results now reflect its own ordering patterns only.
🚀 Location-Specific Quick Codes No Longer Conflict Across Branches
Quick codes (short identifier codes assigned to products) were previously stored and searched globally, which caused incorrect matches when different locations used different codes for the same product. Quick codes are now managed at the individual location level, so each branch only matches against its own codes.
🚀 Search Match Indicator Now Appears in the Quote Flow
The match quality indicator — the label that shows how a product result was matched — is now visible inline within the quote flow. Previously it was only available in the thread view. Counter reps creating quotes will now have the same match context available at the point of decision.
Conversation Hub
🔧 Fixed: Search Filter Switching No Longer Loses Results
On the Search page, toggling between the "Threads" and "All" filters was causing results to progressively drop off with each switch, eventually showing "No results!" even when matching content existed. Search results now correctly update to reflect whichever filter is selected, regardless of how many times filters are toggled.
Prokeep
🔧 Fixed: Error When Adding a Corrected Part to a Quote
In the Order Automation unified workflow, searching for a corrected part number and clicking "Add" was returning an "Error saving quote. Please try again" message in the live P21 environment. This no longer occurs when adding a corrected or replacement part to an existing quote.
🔧 Fixed: Save Button Now Available After Entering Quote Information
In the Order Automation unified workflow, the Save option was remaining unavailable even after a Territory Manager filled in all required fields (customer name, PO number, and shipping address). The issue was tied to the delivery vs. pickup selection state. Save is now enabled once the required fields are filled in.
🔧 Fixed: Emails via Microsoft Graph API Now Appear in Prokeep
Emails delivered to a mailbox connected through Microsoft Graph API were not showing up in Prokeep, even when those emails had confirmed delivery to the Inbox and met all expected requirements. Customers using the Microsoft Graph API email integration will now see inbound emails appear in Prokeep as expected.