case STORIES

Klim: Preseason

Klim: Preseason

Klim: Preseason

Transforming Manual Processes: Enhancing KLIM's Preseason Form

Transforming Manual Processes: Enhancing KLIM's Preseason Form

Transforming Manual Processes: Enhancing KLIM's Preseason Form

Transforming Manual Processes: Enhancing KLIM's Preseason Form

klim.com

Idaho, USA

>

>

Klim: Preseason

Project info

Team Size

3 to 6

Timeline

4 months

TECHNOLOGY STACK

TECHNOLOGY STACK

TECHNOLOGY STACK

TECHNOLOGY STACK

KLIM (from Teton Outfitters) previously managed their entire process manually using Excel spreadsheets. Although a former provider had developed an initial version of the Preseason form, it lacked essential functionalities and was not fully refined. Consequently, it was never adopted for use. The client then approached us to enhance the form with all the necessary features and improvements.

KLIM (from Teton Outfitters) previously managed their entire process manually using Excel spreadsheets. Although a former provider had developed an initial version of the Preseason form, it lacked essential functionalities and was not fully refined. Consequently, it was never adopted for use. The client then approached us to enhance the form with all the necessary features and improvements.

KLIM (from Teton Outfitters) previously managed their entire process manually using Excel spreadsheets. Although a former provider had developed an initial version of the Preseason form, it lacked essential functionalities and was not fully refined. Consequently, it was never adopted for use. The client then approached us to enhance the form with all the necessary features and improvements.

KLIM designs, develops, and manufactures advanced technical riding gear and motor sports apparel for the snowmobile and motorcycle rider. We have been working together for 2+ years, in web design, and web development in SuiteCommerce and NetSuite ERP.

Objectives

Project Objectives: Enhancing Collaboration, Accessibility, and Efficiency for KLIM's Sales Process

  • Sales Representatives and SuiteCommerce (e-Commerce) Customers must collaborate in building an order together from different platforms.

  • Sales Representatives should not need a NetSuite employee license to be able to perform this work.

  • B2B Customers should be able to see these orders in SuiteCommerce.

  • It needs to be fast, intuitive, and easy to use.

  • The solution must allow Sales Representatives to look up items within a 5.000+ SKUs database.

  • Sales Representatives and SuiteCommerce (e-Commerce) Customers must collaborate in building an order together from different platforms.

  • Sales Representatives should not need a NetSuite employee license to be able to perform this work.

  • B2B Customers should be able to see these orders in SuiteCommerce.

  • It needs to be fast, intuitive, and easy to use.

  • The solution must allow Sales Representatives to look up items within a 5.000+ SKUs database.

  • Sales Representatives and SuiteCommerce (e-Commerce) Customers must collaborate in building an order together from different platforms.

  • Sales Representatives should not need a NetSuite employee license to be able to perform this work.

  • B2B Customers should be able to see these orders in SuiteCommerce.

  • It needs to be fast, intuitive, and easy to use.

  • The solution must allow Sales Representatives to look up items within a 5.000+ SKUs database.

  • Sales Representatives and SuiteCommerce (e-Commerce) Customers must collaborate in building an order together from different platforms.

  • Sales Representatives should not need a NetSuite employee license to be able to perform this work.

  • B2B Customers should be able to see these orders in SuiteCommerce.

  • It needs to be fast, intuitive, and easy to use.

  • The solution must allow Sales Representatives to look up items within a 5.000+ SKUs database.

Solution

Solution

We worked closely with KLIM’s sales and eCommerce team for over a month to understand and prepare the core architecture of the tool.


Time was of the essence, so we simultaneously collaborated with the sales team to create mockups that defined some of the tool's features while developing the core components that didn't depend on their input. Once the designs were approved, we moved forward with the implementation.


We wanted to ensure a flawless user experience given the critical nature of this process for KLIM. We meticulously went through the page layout and features, aiming to optimize the current workflow.


Recognizing the scope of work, we identified the need for a technology stack capable of delivering high performance. We chose React and it was an awesome fit.


Together we agreed that we needed a space within NetSuite. The beauty is that we could have Sales Representatives use NetSuite Partner licenses to log in and make use of the tool, for free. Sales Representatives could create orders for their B2B customers without requiring NetSuite Employee licenses, which do run with a cost.


Moreover, the SuiteScript API would be natively available ensuring high security standards when sourcing and storing data into NetSuite.


We could also take advantage of the fact that customers already have a SuiteCommerce login and My Account section where they can see their orders. That being the point of contact between the two processes.

We worked closely with KLIM’s sales and eCommerce team for over a month to understand and prepare the core architecture of the tool.


Time was of the essence, so we simultaneously collaborated with the sales team to create mockups that defined some of the tool's features while developing the core components that didn't depend on their input. Once the designs were approved, we moved forward with the implementation.


We wanted to ensure a flawless user experience given the critical nature of this process for KLIM. We meticulously went through the page layout and features, aiming to optimize the current workflow.


Recognizing the scope of work, we identified the need for a technology stack capable of delivering high performance. We chose React and it was an awesome fit.


Together we agreed that we needed a space within NetSuite. The beauty is that we could have Sales Representatives use NetSuite Partner licenses to log in and make use of the tool, for free. Sales Representatives could create orders for their B2B customers without requiring NetSuite Employee licenses, which do run with a cost.


Moreover, the SuiteScript API would be natively available ensuring high security standards when sourcing and storing data into NetSuite.


We could also take advantage of the fact that customers already have a SuiteCommerce login and My Account section where they can see their orders. That being the point of contact between the two processes.

We worked closely with KLIM’s sales and eCommerce team for over a month to understand and prepare the core architecture of the tool.


Time was of the essence, so we simultaneously collaborated with the sales team to create mockups that defined some of the tool's features while developing the core components that didn't depend on their input. Once the designs were approved, we moved forward with the implementation.


We wanted to ensure a flawless user experience given the critical nature of this process for KLIM. We meticulously went through the page layout and features, aiming to optimize the current workflow.


Recognizing the scope of work, we identified the need for a technology stack capable of delivering high performance. We chose React and it was an awesome fit.


Together we agreed that we needed a space within NetSuite. The beauty is that we could have Sales Representatives use NetSuite Partner licenses to log in and make use of the tool, for free. Sales Representatives could create orders for their B2B customers without requiring NetSuite Employee licenses, which do run with a cost.


Moreover, the SuiteScript API would be natively available ensuring high security standards when sourcing and storing data into NetSuite.


We could also take advantage of the fact that customers already have a SuiteCommerce login and My Account section where they can see their orders. That being the point of contact between the two processes.

We worked closely with KLIM’s sales and eCommerce team for over a month to understand and prepare the core architecture of the tool.


Time was of the essence, so we simultaneously collaborated with the sales team to create mockups that defined some of the tool's features while developing the core components that didn't depend on their input. Once the designs were approved, we moved forward with the implementation.


We wanted to ensure a flawless user experience given the critical nature of this process for KLIM. We meticulously went through the page layout and features, aiming to optimize the current workflow.


Recognizing the scope of work, we identified the need for a technology stack capable of delivering high performance. We chose React and it was an awesome fit.


Together we agreed that we needed a space within NetSuite. The beauty is that we could have Sales Representatives use NetSuite Partner licenses to log in and make use of the tool, for free. Sales Representatives could create orders for their B2B customers without requiring NetSuite Employee licenses, which do run with a cost.


Moreover, the SuiteScript API would be natively available ensuring high security standards when sourcing and storing data into NetSuite.


We could also take advantage of the fact that customers already have a SuiteCommerce login and My Account section where they can see their orders. That being the point of contact between the two processes.

Challenges

Challenges

The collaborative aspect of the tool presented a significant challenge. We needed to ensure data integrity while allowing two different users with distinct roles to modify data. The same order needed to be editable from both the NetSuite back-end and NetSuite SuiteCommerce, potentially at the same time, and this process had to be seamless and user-friendly for both types of users. To address this, we implemented a workflow similar to Git. Users could manage their local changes and shared changes, with options to "push" their local updates or "pull" others' changes to obtain the most current version of the order. This functionality was provided through a modal with three clear and descriptive options, making the process straightforward and transparent for the end user.

When a session is shared, a pop-up window is displayed with options on how to handle the changes made.



Another challenge was handling the loading of a large amount of data without compromising the user experience. Initially, the catalog took nearly 30 seconds to load due to multiple queries. However, we optimized the interface so that the Sales Representatives would see the interface load within 2 seconds, with the catalog continuing to load in the background. This approach ensured a smooth and efficient user experience.

The collaborative aspect of the tool presented a significant challenge. We needed to ensure data integrity while allowing two different users with distinct roles to modify data. The same order needed to be editable from both the NetSuite back-end and NetSuite SuiteCommerce, potentially at the same time, and this process had to be seamless and user-friendly for both types of users. To address this, we implemented a workflow similar to Git. Users could manage their local changes and shared changes, with options to "push" their local updates or "pull" others' changes to obtain the most current version of the order. This functionality was provided through a modal with three clear and descriptive options, making the process straightforward and transparent for the end user.

When a session is shared, a pop-up window is displayed with options on how to handle the changes made.



Another challenge was handling the loading of a large amount of data without compromising the user experience. Initially, the catalog took nearly 30 seconds to load due to multiple queries. However, we optimized the interface so that the Sales Representatives would see the interface load within 2 seconds, with the catalog continuing to load in the background. This approach ensured a smooth and efficient user experience.

The collaborative aspect of the tool presented a significant challenge. We needed to ensure data integrity while allowing two different users with distinct roles to modify data. The same order needed to be editable from both the NetSuite back-end and NetSuite SuiteCommerce, potentially at the same time, and this process had to be seamless and user-friendly for both types of users. To address this, we implemented a workflow similar to Git. Users could manage their local changes and shared changes, with options to "push" their local updates or "pull" others' changes to obtain the most current version of the order. This functionality was provided through a modal with three clear and descriptive options, making the process straightforward and transparent for the end user.

When a session is shared, a pop-up window is displayed with options on how to handle the changes made.



Another challenge was handling the loading of a large amount of data without compromising the user experience. Initially, the catalog took nearly 30 seconds to load due to multiple queries. However, we optimized the interface so that the Sales Representatives would see the interface load within 2 seconds, with the catalog continuing to load in the background. This approach ensured a smooth and efficient user experience.

The collaborative aspect of the tool presented a significant challenge. We needed to ensure data integrity while allowing two different users with distinct roles to modify data. The same order needed to be editable from both the NetSuite back-end and NetSuite SuiteCommerce, potentially at the same time, and this process had to be seamless and user-friendly for both types of users. To address this, we implemented a workflow similar to Git. Users could manage their local changes and shared changes, with options to "push" their local updates or "pull" others' changes to obtain the most current version of the order. This functionality was provided through a modal with three clear and descriptive options, making the process straightforward and transparent for the end user.

When a session is shared, a pop-up window is displayed with options on how to handle the changes made.



Another challenge was handling the loading of a large amount of data without compromising the user experience. Initially, the catalog took nearly 30 seconds to load due to multiple queries. However, we optimized the interface so that the Sales Representatives would see the interface load within 2 seconds, with the catalog continuing to load in the background. This approach ensured a smooth and efficient user experience.

Results

Results

Accessible with no extra costs

We created a tool that can be accessed within NetSuite’s main menu. The Sales Representative has a table like experience in which they can easily search for an item and add it to a large order in just a few seconds. After the items are added the quantity can be easily updated within the table. Items can also be zeroed out individually or massively by clicking on a useful RESET QUANTITIES button.


Easy to find what you are looking for

The results can be grouped by Catalog, Family, Sub-Family and Gender to facilitate the search for the needed SKUs. And pagination allows for thousands of SKUs to be available without uncomfortable loading times due to big payloads. Sorting was intentionally left out so to imitate the specific order the KLIM PDF catalog has.


Mitigating risks of losing progress

Once the work on the order is done, it can either be shared to the customer’s page in SuiteCommerce’s My Account section or it the session saved if the Sales Representative needs to pick it up later. And to make it extra safe, there’s a service saving the order every 5 seconds so that no unforeseen issue can mess with the progress made.


All the progress made to the order is automatically saved, or can be manually saved with the “Save session” button.


Friendly with current workflows

A good example of how we adapted this solution to KLIM’s specific needs is that some of the Sales Representatives expressed they are used to working on their orders in a CSV. So we added a way to download the order into a CSV, so that they can work on it as they feel more comfortable doing so and then upload it into the system, which in result will automatically update the order.


Communication is key

When a session is shared, a pop-up window is displayed allowing you to ignore the shared changes, or choose how to include the shared changes with your current progress.

When the order is ready, the submit button will prompt you to enter a contact email and an optional message to go along with the order. This email will be used for further communications about the order.


Enter an email and an optional message that will be stored with the order.

Conclusion

Conclusion

We set out on a mission to develop a tool tailored to address the evolving needs of the business in managing large orders. By transforming an outdated process of spreadsheet filling into a collaborative experience for Sales Representatives and Customers, we not only modernized the process but also cultivated seamless interaction between stakeholders. We’ve monitored the results and received exciting feedback from KLIM’s team, driving us into a phase two of development and continuous improvement of the tool to the present day.

test

Test

test

Unlock the power of your business with our experts.

We help streamline your operations, optimizing efficiency and productivity.