What’s new?

Changing the Customer on a Customer Order 

Dealerships will have greater flexibility in changing a Customer on a pre-existing Customer Order as we have removed a number of restrictions previously in place

There is a new option on the Customer section on Customer Orders -

When the Customer is changed on a Customer Order the user may get confirmation warnings that:

• Units will be removed from service jobs and they will have to reassign them

• Trade-ins will be removed from deals and new trade-ins will need to be selected

• Any related service appointments will be removed from the scheduler and they will need to recreate them

A few items of importance:

• Please remember that changing the customer on a Customer Order may also cause prices to be recalculated if the new customer has a different price level or tax exemptions.  Our suggestion is if you change the Customer on a Customer Order please remember to review the prices 
• Internal comments will be added to the Customer Order whenever the customer is changed.

While a lot of the restrictions that stopped the user from changing the Customer on a Customer Order have been removed, these restrictions will still remain in place: 

• The Customer Order is closed

• An invoice has been generated from the Customer Order 

• There are active payments in checkout

• It contains completed Service Jobs

• It contains a Unit Deal with an Approved status

• It has a Unit Deal with trade-in that has been stocked in

• It contains AR credit payments in checkout or deposits

• It contains store credit payments in checkout or deposits which have not been refunded/reversed to store credit

Website Product Management

We have introduced a new backend configuration to control on whether or not the Dealership wants the tags on the Blackpurl Part Records to sync over to the relevant linked Shopify Products

• The default for this new configuration will be disabled.  This means that the tags from the Blackpurl Part Records will not be synced to the relevant linked Shopify Products and that the handling of tags for Shopify Products will need to be done in Shopify itself

• Be aware that if the Dealership want the configuration to be enabled, then the tags from the Blackpurl Part Records will be synced to the relevant linked Shopify Products and all handling of tags will need to be done in Blackpurl.  If the Dealership then decides to change the tags in Shopify, the next time Blackpurl syncs it will delete / override those Shopify created tags

Adding Internal Comments on closed Customer Orders 

Users now have the ability to add additional Internal Comments on Customer Orders that are closed 

For further information, please review our article - How to Add Internal Comments to a Customer Order

What’s improved?

• Resolved - Website Product Management (WPM) issues:
  • opening a customer order which was created from a Shopify transaction which did not have a customer assigned to it

  • products which failed to sync were not being flagged as errors

  • where sync failures were being generated when the deposit amount was zero

  • a time zone issue related to Shopify payments which caused these payments to be back dated and changed reconciled Cash Reconciliations

  • duplicate Shopify products being created due to Read time out error in API

  • which caused the Shopify ID to not always appear on BP part records

  • encountered when searching for products containing special characters in their name

  • with existing variants being deleted when managing product variants

• Resolved - where a user was issued an unsync customer message.  This was 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 while reopening invoices caused by incorrect accounting application transaction type being referenced

• Resolved - an issue which caused some order units to issue a tax related error and thus not applying tax to the order unit

• Corrected - an occasional User Interface (UI) issue which caused the warnings to not be properly displayed in the date picker

• Resolved - an issue which caused the deal service/merch section to not be generated when moving line items using the install flag

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

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

• Resolved - an issue with sales receipts which would always show a 12:00AM time and the tax ID label would be shown even when the org did not have that field populated in system settings

• Resolved - issues where the Offer to Purchase and Bill of Sale documents were not giving consistent and proper values for Due from customer and Due from financing

• Released - mapped forms for specific Dealerships.  The specific Dealerships have been notified

• Corrected - Additional corrections to ensure that sales tax rates are always referenced by their uniqueID in BP logic instead of the name of the rate to ensure that proper tax amounts are always processed

• Resolved - issue encountered when attempting to generate an invoice preview for a deal which has not been committed or approved which should not have allowed them to

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

• Resolved - an issue which caused the user to not be able to change 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 - issue importing Partsmart 8 picklists

• Released - changed to mapped forms for specific Dealership.  The specific Dealership will be notified

• Performance Improvements to Customer Order application:

• Creating a job from the service tile
• Breakup kits
• Send a text action
• add/edit pulled quantities
• Change - Minor UI updates to fulfill the requirements of the QuickBooks compliance review
• Resolved - issue encountered importing a .csv file in to VO where the user could not see all of the parts which could not be imported
• Resolved - issue encountered when creating categories and the user could not select their desired GL’s until after they saved it with the default GL’s
• Resolved - issue which gave the user an error when they entered a very large amount of text in the Cause, Concern and Correction fields
• Resolved - an occasional issue where a CO was fully closed yet the deal on the CO indicated that options were pending
• Change - Implemented a new restriction on the use of the Charge on Account payment method.  Dealerships will no longer be able to close a CO invoice which has a charge on account amount which is not aligned with the actual amount owing on the invoice.  This was typically happening when the user would reduce the invoice amount after having already added to full payment which resulted in accounting sync failures
• Resolved - an issue with barcode labels generated from VR where the correct customer name was not always included on the label
• Resolved - issue where the Tax detail report was not including individual tax amounts on vendor invoices
• Resolved - issue in the SOM inventory file where is was using the wrong indicator for obsolete parts
• Resolved - issue in the invoice detail report where it was not reporting the correct total profit
• Resolved - a rounding issue when adding kits to a CO
• Resolved - an issue with the Text template variable [parts_ready_qty_this_CO]
• Resolved - tax issue on newly created CO’s where the exemptions from both the Default account type and the Account type of the customer were being applied and the user had to Recalculate pricing to reset the exemptions
• Resolved - issue with CO’s created from Shopify all being assigned to the Cash Sale customer, a side effect of security review changes
• Resolved - an issue which generated an error when setting a service job status to Quote, a side effect of security review changes