Skip to main content

Blackpurl Release Notes — Customer Order Changes, Website Product Management, and Bug Fixes

A summary of new features and improvements including customer reassignment on Customer Orders, Shopify tag sync configuration, and a wide range of bug fixes.

What's New

Changing the Customer on a Customer Order

Blackpurl now gives dealerships greater flexibility when changing a customer on a pre-existing Customer Order. A number of restrictions that previously blocked this action have been removed.

A new Change customer button is available in the customer section of a Customer Order.

When you change the customer on a Customer Order, you may see confirmation warnings about the following impacts:

  • Units will be removed from service jobs — you will need to reassign them

  • Trade-ins will be removed from deals — you will need to select new trade-ins

  • Related service appointments will be removed from the scheduler — you will need to recreate them

Keep the following in mind when changing a customer:

  • Prices may be recalculated if the new customer has a different price level or tax exemptions. Review all prices after making the change.

  • An internal comment is automatically added to the Customer Order each time the customer is changed.

The following conditions will still prevent you from changing the customer on a Customer Order:

  • The Customer Order is closed

  • An invoice has already been generated from the Customer Order

  • There are active payments in checkout

  • The Customer Order contains completed service jobs

  • The Customer Order contains a unit deal with an Approved status

  • The Customer Order has a unit deal with a trade-in that has been stocked in

  • The Customer Order contains AR credit payments in checkout or deposits

  • The Customer Order contains store credit payments in checkout or deposits that have not been refunded or reversed to store credit

Website Product Management — Shopify Tag Sync Configuration

Website Product Management (WPM) now includes a backend configuration option that controls whether tags on Blackpurl Part Records are synced to their linked Shopify Products.

  • This configuration is disabled by default. When disabled, tags from Blackpurl Part Records will not sync to Shopify Products, and all tag management must be done directly in Shopify.

  • If the configuration is enabled, tags from Blackpurl Part Records will sync to the linked Shopify Products and all tag management must be done in Blackpurl. If tags are edited in Shopify while this setting is enabled, the next Blackpurl sync will delete or override those Shopify-created tags.

Adding Internal Comments on Closed Customer Orders

Users can now add internal comments to Customer Orders that are closed. For full details, see Add Internal Comments to a Customer Order.

What's Improved

The following issues have been resolved or improved in this release:

  • Resolved multiple Website Product Management (WPM) issues:

    • Opening a Customer Order created from a Shopify transaction that had no customer assigned to it

    • Products that failed to sync were not being flagged as errors

    • Sync failures being generated when the deposit amount was zero

    • A time zone issue with Shopify payments that caused them to be back-dated and changed reconciled Cash Reconciliations

    • Duplicate Shopify products being created due to a read timeout error in the API

    • The Shopify ID not always appearing on Blackpurl Part Records

    • An error when searching for products containing special characters in their name

    • Existing variants being deleted when managing product variants

  • Resolved an issue where users received an unsync customer message, caused by the AR credit payment method button failing to access the Customer Record in the accounting package to populate the dollar amount

  • Resolved issues encountered when reopening invoices, caused by an incorrect accounting application transaction type being referenced

  • Resolved an issue that caused some order units to produce a tax-related error and not apply tax to the order unit

  • Corrected an occasional User Interface (UI) issue where warnings were not properly displayed in the date picker

  • Resolved an issue that caused the deal service and merchandise section to not be generated when moving line items using the install flag

  • Resolved an issue that caused the unit to not appear on a deal service job

  • Resolved an issue with fixed price kits where the total of recalculated line items would not equal the fixed price set on the kit

  • Resolved an issue with sales receipts that always showed a 12:00 AM time, and where the tax ID label appeared even when the field was not populated in system settings

  • Resolved issues where the Offer to Purchase and Bill of Sale documents were not providing consistent and correct values for Due from Customer and Due from Financing

  • Released mapped forms for specific dealerships — affected dealerships have been notified

  • Corrected additional logic to ensure that sales tax rates are always referenced by their unique ID in Blackpurl rather than by name, so that correct tax amounts are always applied

  • Resolved an issue where users could generate an invoice preview for a deal that had not been committed or approved

  • Resolved an issue when assigning technicians to an appointment where the date selector used shop hours for the current date regardless of which day of the week was selected

  • Resolved an issue that prevented users from changing the unit on a unit inventory service job

  • Reinstated the ability to select an internal expense job type on a unit inventory service job

  • Resolved an issue importing Partsmart 8 picklists

  • Released changes to mapped forms for a specific dealership — the dealership has been notified

  • Performance improvements to the Customer Order application in the following areas:

    • Creating a job from the service tile

    • Breaking up kits

    • Send a text action

    • Adding and editing pulled quantities

  • Minor UI updates to meet the requirements of the QuickBooks compliance review

  • Resolved an issue importing a .csv file into a Vendor Order (VO) where users could not see all parts that failed to import

  • Resolved an issue when creating categories where users could not select their desired General Ledger (GL) accounts until after saving with the default GLs

  • Resolved an issue that produced an error when users entered a very large amount of text in the Cause, Concern, and Correction fields

  • Resolved an occasional issue where a Customer Order was fully closed but the deal on the Customer Order indicated that options were pending

  • Implemented a new restriction on the Charge on Account payment method. Dealerships can no longer close a Customer Order invoice when the charge on account amount does not match the actual amount owing on the invoice. This situation typically occurred when users reduced the invoice amount after already adding the full payment, which resulted in accounting sync failures.

  • Resolved an issue with barcode labels generated from a vendor return (VR) where the correct customer name was not always included on the label

  • Resolved an issue where the Tax Detail report was not including individual tax amounts on vendor invoices

  • Resolved an issue in the SOM inventory file where the wrong indicator was used for obsolete parts

  • Resolved an issue in the invoice detail report where the correct total profit was not being reported

  • Resolved a rounding issue when adding kits to a Customer Order

  • Resolved an issue with the text template variable [parts_ready_qty_this_CO]

  • Resolved a tax issue on newly created Customer Orders where exemptions from both the default account type and the account type of the customer were being applied simultaneously, requiring users to recalculate pricing to reset the exemptions

  • Resolved an issue where Customer Orders created from Shopify were all being assigned to the Cash Sale customer — a side effect of security review changes

  • Resolved an issue that generated an error when setting a service job status to Quote — a side effect of security review changes

Did this answer your question?