Skip to main content

Blackpurl Release Notes — Rich Text Fields & Blackpurl Classic Retirement

A summary of new features, improvements, and bug fixes in this Blackpurl release.

What's New

This release introduces rich text support for customer-facing fields and Blackpurl Classic Customer Order, looking to retire and be replaced with BP2CO

Rich Text Fields — Phase 1

The Notes for Customer field on a Customer Order now supports rich text formatting, allowing you to apply styling such as bold, italics, and lists to customer-facing notes.

Blackpurl Classic CO Retiring / Introducing the new BP2CO

With the introduction of the new BP2CO, we will be looking to retire the Blackpurl Classic Customer Order version shortly.

Please give BP2Co a go - click here to find out more


If you used Blackpurl Classic CO and cannot find a feature in the new Blackpurl 2 CO, the team wants to hear from you. We would love it, if you could provide us with your feedback

What's Improved

This release includes the following fixes and changes.

  • Resolved — Changes have been made to the Yamaha Australia vendor export files to allow users to define order types through configuration settings during file export.

  • Resolved — An issue where card-not-present processing was not working for Preferred Payments.

  • Changed — Implemented a solution that allows the DevOps team to rename the FTP feed file using new configuration settings based on user preferences.

  • Resolved — An issue where the flag on the Hour Logged entry was being enabled unexpectedly, causing those entries to appear in integrity script results.

  • Changed — Added a new optional field AG/Other ID# in the customer report.

  • Resolved — An invoice journal error that occurred when Actual Cash Value exceeds the Agreed Value for a unit.

  • Resolved — An issue where WIP Labor Inventory was not displayed when technician hours costing was enabled.

  • Resolved — An issue where trade-in unit deals showed a positive amount in the invoice detail report instead of a negative value.

  • Resolved — An issue in the Product History Detail report when searching by category.

  • Resolved — An issue where cost and price changes for default factory options were not persisting after a page refresh once added or updated.

  • Resolved — An issue where the Part Movement report displayed an incorrect location.

  • Resolved — An issue where customer order invoices and payments could not be synced when warranties were included in service jobs.

  • Resolved — An issue where BRP unit details were not populating after entering the VIN on the Unit Ordering and Unit Receiving screens.

  • Changed — Implemented updates for Honda integration as Honda Australia upgrades its APIs to enhance security and performance.

  • Resolved — An issue where the vendor product cost was not reflected in the Invoice Detailed report.

  • Resolved — An issue where Customer Deposit and Checkout Clearing accounts were not balancing upon finalizing a customer order.

  • Resolved — An issue where customer phone numbers were not being fetched from Shopify to Blackpurl for Australian numbers starting with +61.

  • Changed — The Invoice History section on a Customer Record will now display "Multiple" when both parts and service jobs are invoiced in a single invoice.

  • Resolved — An issue where quantity was not updating correctly when adding a part to a vendor order and modifying its quantity.

  • Changed — Enabled price editing for temporary units in cases where no submodel is available in Blackpurl.

  • Resolved — An issue where invoice and journal entries were not syncing and a SOQL error appeared in the Apex job when more than 120 trade-ins were added to a deal.

  • Changed — Users can now remove loan terms and rates from the financing section.

  • Resolved — An issue where an appointment was not created for a service job if the concern field contained more than 2,000 characters.

  • Resolved — An issue where the legacy home page URL was redirecting users to the old home page.

  • Changed — The accounting reconciliation tool now uses a custom setting to determine how many rows are displayed per page in pagination.

  • Resolved — An issue where an incorrect amount was returned when processing payments via the Fiserv method in card-not-present scenarios without surcharges.

  • Changed — Added a post-install script to create a scheduler that fetches tax rates from Zip Tax on the first day of every month at 12:00 AM. This job runs only when the Automatic Tax Rate setting is enabled in configuration.

  • Resolved — An issue that prevented moving line items from one service job to another service job.

  • Resolved — An issue where Concern/Cause/Correction (C/C/C) fields for service jobs were printed incorrectly in related documents.

Did this answer your question?