Blackpurl

In this article, we will explore the advantages of establishing a clean make / model database during your dealership's activation

Clean Database

Opportunity knocks, and it's the perfect time to construct a clean database utilizing structured Make/Model/Sub Model framework data

Furthermore, you will have the chance to import the following data (Note: The Blackpurl Data Import Template is provided at the bottom of this article):

• Make/Model/Sub Model framework
• Factory Options
• Stock Unit Inventory
• On Order Units
• Consignment Units
• Customer Owned Units

Depending on your dealership's requirements, this task may require some heavy-lifting on your end to set up. But rest assured, the long-term benefits of a well-prepared framework will be of great benefit

The benefits of this endeavour include:

• Clean and structured framework data
• The convenience of ordering/receiving units with simple clicks, bypassing the need for tiresome typing
• The ability to quote customers effortlessly by navigating through the data, instead of typing it all out
• A smooth and user-friendly experience for your Service Writers
• Cleaner reporting and accounting

Examples

Now, let's look at some examples. Please note that all names, prices, and costs are entirely fictional and are intended solely for demonstration purposes

Below is an example of how clean Make/Model data can appear when preparing a unit order. Observe how accessible the data becomes with a simple click-through

If the Make/Model/Sub Model & Factory Options Data are not available here, you may need to return and create or amend the Make/Model/Sub Model data. Additionally, setting up Your Unit Pricing and Factory Options might be necessary, depending on your dealership's requirements

Tip:
When processing a Unit Vendor Order, it is not possible to create new Make/Model/Sub Model data. This limitation is in place to ensure that your data remains clean and well-maintained

Now, let's explore the advantages of having a robust and clean Make/Model/Sub Model & Factory Options Data when quoting a customer

Remember, the same rules apply here; it is not possible to create new Make/Model/Sub Model Data when quoting a customer for a deal

Imagine the benefits of swiftly navigating through a quote for a customer. You can easily make adjustments to prices where necessary and promptly send it off via email or print

Included with this article is a quote, generated by the above example, showcasing the swift and orderly creation and delivery of a quote using well-prepared framework data

Now, let's examine the advantages of having clean Make/Model/Sub Model data when creating a service job. The crucial aspect here is that the creation of a new customer unit becomes fast and efficient due to the availability of data, thus contributing to the maintenance of clean framework data

What occurs when the readily available Make/Model/Sub Model is not used while creating a new customer-owned unit?

You have the ability to create a "new" Make/Model/Sub Model when generating a new customer-owned unit. This is necessary because not all units being serviced may exist as standard framework data.

In this scenario, the Service Writer spontaneously created a "new" Make/Model/Sub Model on the spot. However, this is where your data can start becoming messy if proper processes and a solid Make/Model/Sub Model framework are not currently in place.

Here's another example, working with the same type of data as above. Take note of the use of the make "CanAm" in this instance - observe the results?

Connecting This Knowledge to Your Activation

Having covered the advantages of having a strong and orderly Make/Model/Sub Model & Factory Options data in your account, it's crucial to recognize that importing your unit framework data during your activation can be very beneficial

However, it must be emphasized that, unless otherwise agreed upon, the data submitted for import is your responsibility to ensure it is clean

For instance, take a glimpse at a small segment of Customer Owned Unit data below, and observe where the data may become messy right from the beginning (Hint: focus on the make column)

Before submitting your data during the activation process, carefully consider the following points:

1. Are Makes consistent across all the data you are submitting?
2. Are Models consistent across all the data you are submitting?
3. Are there any instances of missing Make / Model data in the submitted data?
4. Would you like to submit prepared Make / Model framework data, or would you prefer to custom-create it in your account? Remember that this data should meet your specific standards
5. Similarly, would you like to submit prepared Factory Options framework data, or would you prefer to custom-create it in your account? Again, keep in mind that this data should align with your specific standards