The Automated Price File tool now supports 11 markup tiers (previously 3) when the dealership configures their own MSRP, Price, and Cost calculations. For details, see Automated Price Files Tool (Automated Price File Imports) (no longer available).

The Manual Price File Import tool now supports up to 11 markup tiers (previously 1) when Calculated Values is selected as the column mapping for Retail and MSRP. For details, see How to Import a Vendor Price File (no longer available).

Vendor record controlled retail price calculations now support up to 11 markup tiers (previously 1) when calculating Retail price. For details, see Vendor Part Pricing: Setup and Overview.

Resolved — an issue with selecting a unit year when adding a customer-owned unit or a temporary unit.

Resolved — an issue with the estimated labor cost shown in the Customer Order (CO) profitability screen when viewing it from a Quotation.

Resolved — an issue where switching a CO back to a quote did not remove special order needs from that CO from vendor ordering.

Resolved — an issue where the options status on a deal was not being set to fulfilled after resolving fulfilments.

Resolved — an intermittent issue that prevented a financed deal from being checked out.

Resolved — an issue which allowed a deal to be approved and invoiced even if it contained uncommitted options.

Resolved — a discrepancy between the technician hours logged on a job and the reported hours for that same job.

Resolved — job costing issues caused by allowing users to modify or remove clocking entries from a finalized job.

Changed — Concern, Cause, and Correction fields can no longer be modified on finalized jobs.

Resolved — an intermittent issue that caused the Concern to be dropped from a service job.

Resolved — an issue when printing or emailing an invoice that contained more than 100 service jobs.

Resolved — an issue where the invoice preview was allowing already-invoiced service jobs to be included.

Resolved — an issue with posting consignment credit notes from a deal into the accounting package when multiple consignment units were sold on a single Customer Order.

Resolved — an issue where a consignment unit that was sold remained flagged as a consignment unit under the new owner.

Changed — Part Vendor Invoices sent from Blackpurl to QuickBooks Online or Xero will no longer include a line for cost variances between the Vendor Invoice (VI) and Vendor Receiving (VR). The variance will now integrate as a separate journal entry.

Updated — all accounting entries sent to QuickBooks Online now handle currency codes, in preparation for a future multi-currency feature in Blackpurl.

Resolved — an issue when reopening an invoice that had been manually altered or paid in QuickBooks Online or Xero. Invoices in this state can no longer be reopened in Blackpurl because they are no longer in the same state as when Blackpurl originally posted them.

Resolved — an issue where tax rate names were appearing on CO invoices instead of the Form Label as defined on the tax rate.

Changed — added validation when mapping parts from different vendors on website products.

Resolved — an issue in kit management that prevented users from entering a fractional quantity without a leading zero before the decimal point.

Resolved — an issue on the tax detail report where taxable and non-taxable amounts for items from kits were not being reported correctly.

Resolved — an issue where CSV exports for parts reports dropped leading zeroes on part numbers when opened directly in Excel.

Updated — SOM part indexing logic.

Updated — SOM credentials requirement for changes to the Heroku code base.

Resolved — an issue with the BRP GetPartsMaster API that was failing as a result of changes made for the Markup Tiers feature.

Resolved — an issue with BRP vendor availability results showing a quantity of 99,999 for parts only available by backorder. These parts now correctly show zero availability.

Resolved — an issue with CO deposits where the system incorrectly allowed a user to reverse an already-reversed checkout payment.

Resolved — an issue in Accounts Receivable (AR) payments where a negative payment on account could be incorrectly processed.

Resolved — an issue that allowed a CO to be open in two browsers simultaneously, where finalizing checkout in one browser still allowed a checkout payment to be added in the other.

Resolved — an issue in the homepage Store Summary tile where the Payments amount was not including all payment types. Payments on Account and entries from Preferred Payments were previously excluded.

Resolved — an issue with Preferred Payments where a customer's credit card was charged for a duplicate payment.

If the Preferred Payments integration is enabled but no terminals are defined, users are no longer blocked from proceeding to checkout — they simply will not be able to process Preferred Payments.

The timeout period is now fixed at the 120-second maximum. Note that the terminal itself does not time out until 5 minutes. If Blackpurl times out before the terminal, manually cancel the transaction on the terminal.

Resolved — an issue when syncing terminals where users were incorrectly shown a success message.

Resolved — an issue when creating and syncing a terminal in Blackpurl that had already been synced to Preferred Payments outside of Blackpurl. Blackpurl now automatically fetches the terminal details from Preferred Payments so that the creation can proceed successfully.

Resolved — an issue filtering unit reports by make, model, or submodel fields when those fields contained a single quote character.

Resolved — User Interface issues in the reporting screen that occurred when the print/export panel was open at the same time.

Resolved — an issue which prevented users from generating a Fusion report.

Resolved — an issue when sending a text where not all available phone numbers were listed for selection.

Resolved — an issue displaying an error when switching an appointment from single-day to multi-day.

Released — mapped forms for specific dealerships. Affected dealerships will be notified directly.