PUBLISHED ON
6 April 2020
Upgrading ODIN - The Marketplace Cerebrum
What is ODIN?
Odin serves as a web-based portal utilized by the employees of WeFreight, a sub-division of Wheelseye Technologies operating within the logistics marketplace.
In the logistics world, we have Shippers, Brokers, Transporters, and Operators. WeFreight acts as a transporter, and Odin helps manage the balance of supply and demand, connecting shippers with operators. Different teams handle tasks like logging demands, assigning vehicles, tracking, and finalizing trips. Odin has a complete setup with features like account and profile management, itinerary tracking, and more.
To understand Odin better, let's get familiar with the people involved and the common terms used daily in the logistics industry.
Projects covered in this article
Enhance the format for creating demands and ensure responsiveness.
Modify the operator's profile.
Automate the shipper’s invoice system.
Demand Creation
Brief
The shipper communicates their requirements and demand, which the employees log into Odin. Subsequently, a truck is assigned to fulfill the specified supply and is directed to reach the loading point. Upon reaching the loading point, the goods are loaded, marking the commencement of the trip.
Problem
The previous iteration of the "Create Demand" tab featured a form with numerous entries, as illustrated in the provided image. However, it suffered from being unresponsive and disjointed. The form lacked a well-defined structure, and similar types of entries were not appropriately grouped.
Solution
The new design of the form is segregated into four parts:
Demand Information
Vehicle Information
Time Stamps
Shipper’s Requirements
Grouping similar entries together reduced the cognitive load of the user. It made it easier for them to fill the form, and the design became responsive. Below is the mobile version of the new flow.
There is a team that logs in the demands into Odin. After they create a demand, they have to do this again using the tab from the hamburger. To eliminate this extra step and complete the flow, I added a “Create New Demand” Button at the end, that allows them to work swiftly.
Similarly, I changed a few input options as well, like count, vehicle type, tire count, etc. using icons and sliders to make the form more intuitive.
Operator Profile
Brief
The operator profile comprises crucial details such as type, name, contact number, trip specifics, account details, and more. This information is stored in the database and utilized as required, including tasks like mapping transactions, settling bills, and contacting drivers.
Problem
The operator profile had some missing elements crucial for verifying and storing the operator in the database. This included defining the mode of operator verification, creating a distinction between settled and unsettled trips, and maintaining a comprehensive track record of accounts.
Solution
Following discussions with my mentor, Vaibhav Rawat, and the finance team, we identified essential documents needed for operator verification, to be submitted in PDF format:
Pan Card
Aadhar/Driving License
TDS declaration form
A canceled cheque/passbook
Initially, all the operator's trips were consolidated under a single tab, even after the accounts were settled. To address this, we segregated the trips into two tabs: "Settled Trips" and "Unsettled Trips." Once a trip is settled, all transactions for that trip are frozen, preventing any further changes.
As many operators possessed multiple bank accounts, it was imperative to facilitate transactions accordingly. Recognizing this, the account section was incorporated into the "Basic Details" tab, considering it a fundamental aspect of an operator's basic information.
Shipper's Invoice
Brief
The shipper's invoice is a commercial document meticulously detailing and recording transactions between the shipper and Wheelseye. This tangible document is generated by the Finance Team.
Problem
Everything was handled manually on paper! The Finance Team put in significant effort to record all data manually, creating their methods for tracking invoices in Odin. In Odin, only a tally of the number of invoices made was maintained under the appropriate status tab.
The invoices followed a fixed format with variables available in Odin's database. The main challenge arose from the GSTIN(s) of the shipper not being mapped in ODIN. The finance team kept a separate record for this information.
To automate Shipper’s Invoice in Odin, a few changes need to be implemented.
Solution
Two significant changes were made in the flows:
Shippers must now register with Wheelseye, providing their GSTIN(s) during onboarding. A new tab, named the "GSTIN" tab, was added to the Shipper's Profile to manage this information, including GSTIN(s), state, state code, and corresponding addresses.
A new, unique system-generated number, similar to the Trip ID but specific to each invoice, was introduced. Each number has a status (used or null) to track discarded and used numbers. This addition allows tracking in all mentioned cases.
There are three types of GSTINs: CGST, SGST, and IGST. If the state codes of Wheelseye Technology and the shipper match, CGST and SGST are added; otherwise, only IGST is added to the final amount. This process is automated as shippers now provide GSTIN details.
To generate an invoice, shippers only need to fill a small form, as illustrated below.
Final Thoughts
The primary goal of implementing the changes discussed in this article is to enhance Odin's capability in handling a larger volume of demands, aligning with Wheelseye's current focus on scalability. As an intern, I didn't have the opportunity for direct user testing. However, being in close proximity to users, the employees, facilitated swift iterations and improved outcomes.
In summary, this internship proved to be fruitful, contributing to my growth as a product designer
