EC-Booking B2B One-Stop Logistic Booking Solution for Amazon FBA

Streamline Amazon FBA Shipping from China to the US

My Role
UX/UI Design, Design Research, Design QA, Data Analysis
Year
2022
Time
3 months
Company
GoFreight
Team
1 Product designer 

1 Product manager
1 Front-end developer
2 Back-end developers
Background
Goal
Problem Diagnosis
Results of Problem Diagnosis
Flow Chart
Deliverables - Amazon Seller
Deliverables - OP
Outcome
Background

EC-Booking is a system to help Chinese Amazon E-commerce seller ship their products from China to Amazon warehouses in the U.S.A

Our VIP customer, a major freight forwarding company specializing in ocean import and export business, also offers e-commerce shipping services. They have an existing system for e-commerce sellers to create shipping orders, but they believe it involves too much repetitive work in building order documents.

As a result, they have entrusted us with the development of a new e-commerce booking system to streamline the process and reduce time spent on repetitive tasks.
The EC-booking aims to support the initial stage of the Amazon e-commerce business where inventory needs to be shipped from China to Amazon's warehouse in the U.S.A.
🙋🏾  How Amazon E-commerce(FBA) works?
One of e-commerce business service provided by Amazon is Fulfillment by Amazon (FBA), which allows sellers to ship inventory (products) to an Amazon warehouse at a competitive cost. When an order comes in, Amazon delivers the product to the customer. Sellers can take advantage of Amazon’s distribution network, infrastructure, world-class delivery service, returns system, and customer service process.
Goal

What exactly does the service provided by EC-booking?

The process of shipping inventory to FBA warehouses involves multiple roles, complex paperwork, communication, and navigating customs regulations, which can be challenging for sellers due to the significant effort required to manage these tasks.
Problem Diagnosis

Why did forwarder want to change the existing booking system?

As mentioned on the first paragraph, our clients want to change the old system, based on the user interviews, we found there are some problems on the existing one:

Existing problems of old booking systems

After conducting user interviews, it has become apparent that there are several issues with the previous booking system that are causing problems for users. As a result, the users have expressed a desire for a change to be made to the system in order to improve its functionality and address the problems that have been identified.
⏱ Spend a lot of time on building documents
Normally it takes an operator 10-30 minutes to create a booking document depending on the complicity of booking details.
📑 Repetitive tasks in transforming data from Booking system to FMS system
As the old booking system and FMS (Working) System are separate, operators have to transfer the booking data to FMS system. Repetitive tasks aren’t just an annoyance – they can harm work performance.Performing the same booking tasks repeatedly can lead to mistakes and oversights, as the mind may wander during routine work.
💻 Manual cargo status tracking everyday
Operators are required to track the status of cargo on carrier/terminal/rail websites and manually update the latest status to shippers on an old booking system. However, this process can be time-consuming, taking approximately 7 minutes from tracking to updating, and can lead to errors and disparities in data updates. The reliance on manual updates presents a significant challenge for the industry in terms of efficiency and accuracy.
💬 High cost of poor communication
Some of sellers relied on email or messaging apps to make booking orders, which can be inconvenient for OP to build booking documents on system. This may result in misunderstandings due to the informal messages.
Results of Problem Diagnosis

2 roles: E-commerce sellers & OPs in Freight forwarder company

From this study, we could further segment our main user into four groups: Amazon E-commerce sellers and OP(operators) working in freight forwarder company.  We also broke down the users by their responsibilities, pain points, and needs. This helps us gauge user needs and pain points.

Persona: Amazon E-Commerce Seller

Pain Points
Based on the user interview, we found seller has pain points as bellow:
  1. Transportation delays leading to missed deadlines and increased costs
  2. Inaccurate tracking causing confusion and delays
  3. Challenges in navigating U.S.A customs regulations and compliance
  4. Product damage or loss during transit leading to customer complaints (Not solved in this scope)
Need
To address the pain points of our users, our goal is to design a booking portal with the following focus areas:
🚀  Goal
1. Book shipping orders easily without many paperworks
2. Track shipment status immediately without calling OP privately

Persona: Forwarder - Ocean Export OP

Pain Points
Based on the user interview, we found OP has pain points as bellow:
  1. Repetitive tasks in transforming data from Booking system to FMS system
  2. Manual cargo status tracking and updating everyday
  3. High cost of poor communication (WeChat, email)
Need
To address the pain points of our users, our goal is to design a booking portal with the following focus areas:
🚀  Goal
1. Booking order data send directly to FMS system without duplicating data between 2 platforms
2. Communicate in one place, all information displayed in one place
3. Automatically update latest shipment status on system for both forwarder and seller
Flow Chart

GoFreight have 2 systems based on the needs of users, one is FMS system; the other is  Customer portal.

We decided to make the booking system on Customer portal, where the users can track their shipments. Therefore, sellers can place the shipping order on it, and track the shipping status on the same system.
→ Jump to design outcome for Amazon seller
The booking information will also sent to FMS system, the working system where the OPs manage their shipment information. OP can manage the booking order without duplicating the data between 2 systems.
→ Jump to design outcome for OP
Below is the flow chart how sellers book an EC-Booking and how OPs receive the booking data.
The design points we focused more for the Amazon seller is:
Make the flow as easier as possible
Although it is a B2B system, the Amazon seller may not have professional expertise in the logistics area. To address this, we  designed the order flow as 2C user, with a simplified process that reduces administrative overhead. This allows the seller to primarily focus on their core E-commerce tasks, while easily tracking shipments without unnecessary complexities.
Design Deliverables

Create E-commerce online booking page, make the booking process simpler in 3 steps

🚀  Goal
Book shipping orders easily without many paperworks
There are a lot of fields need to type in to book a shipping order, this may lead sellers to prefer privately messaging OP for help instead of booking online themselves.We have organized the fields into three main categories: Basic Information, Delivery & Receipt Information, and File Uploading Section, to simplify the order process.

Besides, we have visually represented these categories as three easy-to-follow steps, ensuring users are aware that the form can be completed in just three simple steps.
By grouping fields and visualized progress bars, the information hierarchy is made clear, resulting in improved efficiency in filling out forms.
Design Decision

Why did we consider a wizard step?

We have chosen to implement a wizard as a solution to simplify the process due to the following reasons:

1. Users want to accomplish a goal that has many steps.
2. The form is long or complicated and it cannot be simplified.
3. Users are lack the necessary domain knowledge.

Using wizard it’s possible to reduce the seeming complexity of a task and provide a sense of progress at the same time. When users are forced to follow the order of tasks, users are less likely to miss important things and will hence make fewer errors.
Design Decision

Estimated quotes card always fixed on right, let users understand the cost they have to pay for shipment

We designed a card with a clear hierarchy and adequate spacing to differentiate content based on priority. There are some design details:

1. The card displays essential information to ensure users understand that they can influence the final price.
2. The information and price on the card will be dynamically updated, allowing for immediate changes to reflect the chosen preferences.
3. The card is always fixed on right, so users don’t have to scroll on top to check the information.
Design Decision

Auto-complete: reduce data entry time by automatically filling repetitive or regular information fields, improving efficiency.

We added a feature that automatically saves previously entered data for fixed information fields such as tax ID, phone number, and address of trade partner (= shipper, consignee, and notify party)

The propose of the feature is to:
1. Reduce repetitive data entry and saving time for users
2. Reduce individuals or organizations have multiple contacts for the same person or entity with slightly different details which may take efforts for OP to maintain the data.
After users submit a booking, they can track the status and view booking information on the EC-Booking list/entry page. Simultaneously, the OP receives the booking order and verifies the booking information. Based on the verification, the OP can approve or reject the booking.
Design Deliverables

After booking order submitted successfully, seller can track the shipping status on the same platform.

🚀  Goal
Track shipment status immediately without calling OP privately
Design Decision

Effective scanning: let users easy to find out the information

On the entry page of EC-Booking, we have prioritized and categorized information into several cards to ensure users can quickly grasp the information. We have followed the visual guidelines below to facilitate effective scanning:

1. Create Subheadings: We have used clear and descriptive subheadings to promote effective scanning. Subheadings help users quickly identify the content they are interested in and can save them time and effort in searching for relevant information.
2. Use Z-Pattern Layout: We have designed the layout of the page in a Z-pattern, which is a common reading pattern that users follow from left to right and top to bottom. This allows users to see the most important information right from the start, and the next most important information second, following the natural flow of reading.
Design Decision

Track the shipment status easily

Design process
The shipment status card allows users to track the current cargo status. While the original design used a timeline layout to emphasize the time sequence, feedback from the team expert highlighted that events may not always occur in a strict chronological order, such as Customs Declaration happening before or after Vessel arrival.

As a result, the final design now uses green and yellow lights to indicate whether an event has occurred or not, without over-emphasizing the chronology.
Based on the feedback from users, our primary focus on the FMS (Freight Management System) is to improve work efficiency.
Design Deliverables

Quick check new booking orders on list page in FMS system while new booking placed from seller

🚀  Goal
Booking order data send directly to FMS system without duplicating data between 2 platforms
As soon as a new booking is placed by a seller, the data is immediately sent to the FMS system. This enables users to check and take actions on the EC-booking list page. The reasons behind placing action buttons on the list page are:
1. Reduce the need to navigate to multiple pages: By having action buttons directly on the list page, users can quickly view relevant information and take necessary actions without having to navigate to multiple pages.
2. Batch process bookings to improve efficiency: Batch processing allows users to perform actions on multiple bookings at once, such as approving, cancelling. Users can efficiently process multiple bookings in a single operation, further enhancing work efficiency.
Design Decision

Efficient booking approval: grouped fields & fixed approval button for quick action in entry page

When OPs receive booking order, the first task they have to do is approve or reject the booking based on the content of the booking. To let OPs quick scan the booking information and make decision to approve/reject, we have implemented some design improvements :
・By grouping fields and visualized progress bars, the information hierarchy is made clear
・Make the approval button fixed on button, ensure OP take action on it first (usability test)
🧪 Usability test

The readability and feasibility of the approve/reject process.

Show more
Show Less
We conducted an internal usability testing for EC-Booking in FMS system (OP end) as Product managers thought the fields and button is not easy to find. We invited 6 colleagues to participate it.
Task: You got a booking need to confirm, everything is correct, please APPROVE the booking
Result : success rate is 100% 🎉
Participants knew how to complete the task, we are confident OP can find the approval/reject button.
Design Deliverables

Approval feature: Notify the seller of any changes made.

🚀  Goal
Communicate in one place, all information displayed in one place
After a booking is confirmed, the OP will review the booking details and may need to edit certain fields, such as the actual price or additional administrative fees based on the chosen shipping plan. It is crucial to notify the sellers of any changes made to the booking information.

To streamline this process, we have implemented an approval feature that is linked to both the FMS (Forwarder Management System) and customer portal.
Design Decision

Upon booking approval, sellers are required to ship the products to the forwarder's warehouse in preparation for shipment.

During discussions with the team, concerns were raised about the visibility of the "In warehouse" field. It was unclear whether OP would be able to easily locate it. To address this concern, we conducted an internal usability test with 6 colleagues who were not familiar with the project.
🧪 Usability test

Do OPs know how to mark the booking “In warehouse”?

Show more
Show Less
Task: The products are delivered to the warehouse, please mark "In warehouse" in the system
Result: Although success rate is 100%, it took them almost 40s with high misclick rate of 42%
This indicates that the current placement of the "In warehouse" field may not be optimal for ease of use.  
To find out the root problem, I checked the feedback and heat map from participant.
Feedbacks from participants
Here are the feedback:
"Do not know the style of the "In warehouse" component, I thought it is a button"
"The title "Warehouse delivery" misled me to find the field in that section, but "In warehouse" is in "Package detail section"
Refer to the heat map to analyze and monitor the click activities.
The problem made participants hard to find the field:
1. The title "Warehouse Delivery" could confuse users that the fields are related to warehouse information.
2. Original "In warehouse" category is hard to link with "Package Details"
Based on the feedback above, I revised the design:
1. Change the card title to POL Service
2. Move In warehouse field below POL service:
The second usability test showed that participants were able to find the "In warehouse" field in half the time compared to the previous test, indicating successful refinements in the design.
Design Deliverables

When products start to ship, tracking information will automatically updated on both customer portal and FMS system

🚀  Goal
Automatically update latest shipment status on system for both forwarder and seller
Once the products are shipped, the tracking status (EDI)is automatically updated and synchronized across both the customer portal and the FMS system. This streamlined approach ensures that users have real-time visibility into the status of their shipments through both platforms, enhancing the overall customer experience and improving operational efficiency.
Project Outcome

Project in MVP feature was successfully launched in 1 month

Upon launching, the Booking feature received positive feedback from users who found it easy to use. This increased stakeholder interest in the feature's business potential, leading them to invest more effort in understanding users' needs and requirements.
Top
Top