top of page
Cover112.jpg
Animation - 1720727469317 (1).gif

This opportunity to build and rethink the order fulfilment process for Ajio B2B and B2C VMS sellers sets some high expectations and I was fortunate enough to get to work on this project which is a very crucial flow for any

e-commerce to achieve and has the potential of impacting millions of sellers.

O V E R V I E W   📖 

As a UX Designer in the VMS team, I got the challenge to redesign the entire order fulfilment process for Ajio B2B & B2C.

 

The initial vision was all about empathising with the sellers. We wanted to understand the seller's perspective – the problems they faced – by talking to them and with the Reliance operations team (as they also handle and connect with the seller side of things more than anyone). This would pave the way for a more user-friendly system for all.

 

Let’s delve in!

As this was a large scale project which took a lot of time and effort to get implemented, I will only showcase selected parts from the project that will illustrate my thought process, design direction, and the nature of my work. This will provide a glimpse into the approach that led to a successful solution for our sellers.

Role

Product designer​

Projects

Order fulfilment
Drop ship bulk management
JIT B2B & B2C

3P Forward 
Returns - claim SPF

Goals 

User retention

Reduction in clicks
Usability
Duration of fulfilment
Seller growth & performance

Areas to focus

Order processing
Inventory management
Logistics
Returns
B2B and B2C Sellers
JIT and Dropship

Packing and printing

M Y   W O R K F L O W  🌟 

Design process.jpg

W H A T ' S   T H E   S C E N E   🔎 

Context

Reliance offers a Just-in-Time (JIT) fulfilment shipping model for sellers. Sellers receive orders, fulfil them in the warehouses, pack and forward them to Reliance, and manage inventory only upon order placement. Reliance then distributes these orders directly to customers from their CDCs, streamlining the process for sellers.

Frame 2608802.png

Now we begin discovering “More about JIT & the issues”⚠️

  • Secondary research (Competitive study and white paper research)

  • A lot of discussions with the Product and engineering teams.

  • Calls with the internal stakeholders to discuss their departments and issues they have been facing in dealing with the sellers.

  • User interviews and field visits (warehouses/offices) to empathise and understand the existing work flows.

  • Discovered current user flow to get more clarity on how things works across the systems. 

In this case study I will only be focusing on JIT model (B2B which is one type of fulfilment in the E- commerce industry)

Started understanding the current system first, how it functions - figured out the major insights for the JIT model.

  • JIT Delivery

    • Longer lead time due to warehouse QC.

    • Benefits:

      • New seller onboarding.

      • Maintain buyer-seller anonymity (for now).

  • Seller Capability:

    • JIT vs Dropship depends on seller's ability to ship individual orders.

  • Major difference in B2B and B2C Payment:

    • COD offered.

    • 10% upfront payment required to process order.

S E L L E R  I N T E R V I E W S 🧐

& Field research  

image 776.png
ece54dd3-bb5b-4559-8f39-f5226e2a50d1 1.png
image 777.png
image 775.png
8fa62650-d442-459a-8b29-d9880d405d2b 1.png
Interviews_data.png

Conducted interviews with sellers to gather qualitative data on their pain points and visited multiple warehouses to observe the order fulfilment process in real-time and identify bottlenecks.

123.jpg

To gain a holistic understanding of the seller experience, I also conducted research sessions with internal teams from various departments to learn about their workflows and the challenges they encounter when interacting with sellers.​

A comprehensive research report and internal newsletters were published to share key findings with the teams.

Untitled (2).png

M A P P I N G   &   I N S I G H T S  🧭

Through extensive user research, I gained a deep understanding of the challenges. Approaching these insights with a fresh perspective, I delved into each pain point to truly empathise with user needs.

To effectively synthesize a vast amount of research data, I explored various tools, including Dovetail. This platform is invaluable in helping me systematically analyze the information and extract actionable insights.

While I cannot share the full research synthesis due to confidentiality, this document provides a glimpse into various key findings I identified. Here are a few of the most significant issues we uncovered.

Problems.jpg
image 756.jpg

T O W A R D S   C L A R I T Y 🎬

Having sifted through a vast dataset, here are the critical problems we pinpointed and are tackling: 

PROBS.jpg
image 780.png
image 781.png
Pack station.png

This is the pack station where seller moves and packs his boxes. As mentioned above, a lot of problems lies in this particular section which leads to other delays and mismanagement. 

S E L L E R   L I F E C Y C L E 📈

Group 53.jpg

For a better understanding of a journey he follows end to end, this is the estimated map with touch points:

Through further analysis, now the problem statements are solidifying, providing a clear foundation for ideation. This journey map gave more clarity from an ideation point of view.

Frame 2608812.jpg
JIT B2B FLOW DETAILED.png

Here are the concise "PROBLEMS 🚨" in the most simplistic way possible.

Problems.jpg

L E T ' S   S O L V E   💡

Throughout the order fulfilment journey, sellers encounter various hurdles at different stages. We've focused on the most pressing issues that directly effect sellers lives to ensure maximum impact. These include upcoming, open, and packing shipments, which are the stages where sellers experience the most significant delays.

 

Let's delve deeper and explore potential solutions for open and packing order challenges.

Consolidated probs.png

Exploring all the possible use cases by breaking each element from the open and pack tabs separately

Initial concepts: 

Wireframe 2.png
Wireframe.png
  • Box detail in slider/ no separate screen

  • Upfront all packs info and collapsed version

  • Multiple boxes and their details in the open tab only

  • Article labels warning

  • Different ways to show packs and order details & quantity.

  • What if there is category wise listing?

  • In upcoming they can see product wise/style wise

Brainstormed a lot of concepts to figure out use cases and constraints:

IMG_9011.JPG
IMG_8956.JPG
IMG_9010.JPG

Specific use cases that need to be considered:

1. Seller & Buyer cancellations

  • Sellers may need to cancel orders if they lack sufficient stock or resources in the warehouse.
     

  • Currently, sellers can cancel an entire order by setting the quantity to zero (0).
     

  • Preventing Unnecessary Cancellations: Line items within an order that are not assigned to a box are automatically cancelled from the seller's side.
     

  • Seller sometimes don’t process orders which are latest to reduce the chances of buyer cancellations.

2. Filters

  • Order date> 30 days data to be shown, past data 30 days will have all orders expired or breached.

  • Filtering the categories is reflecting orders which are not even active.

  • "Fulfil By" Time: Prioritise Orders for Timely Delivery: This option emphasises how "Fulfil By" time can help sellers prioritise orders to ensure timely delivery.

  • Top selling category filter for the sellers having diverse catalogs. This will make the decision faster-what to go in which box.

  • Sellers are familiar with SKU IDs, allowing them to search for orders by SKU ID or Order ID is needed.

3. Moving and creating b0xes

(Basically, seller has to pack multiple shipments

in boxes and send them to the CDCs)

This is what we need:

  • Box serial number, Box configuration, Box weight, dimensions, heights etc., Open and close box

  • How can they edit a box and make changes

  • Adding a new box

  • Delete and save the box

  • Defaulted box

  • Box ID at the time of box creation

  • All packs belonging to one order ID have to move in boxes before generating the invoice for a particular shipment.

  • Partial processing is not allowed currently.

  • Packs can be split into separate boxes but not left behind.

4. Partial processing

  • At this time seller should be able to split his packs into multiple boxes before generating the invoices. If one order has 3-4 line items and all of them have different weight & sizes, So they need to go in separate boxes.

  • Selecting the quantity of order before moving to box and a warning of what is left behind to process asap.

5. Labels

  • Individual shipment labels for each pack (pack label)

  • Box labels: A label on each box before shipping

  • Article label only for B2B2C

  • Printer configuration (So that in s single click seller can print all the labels)

  • Labels are printed generally while packing but sometimes after packing tooDepends on seller preferences.


  • At which step the printing should be done for box labels and shipment labels. Before invoicing, while generating the invoices, while moving to boxes? (Open question)

6. Scanning

6. Orders & Packs

IdeationA.png
IdeationB.png

Critical decisions

  • There has been a lot of discussion back and forth with the PMs to brainstorm what is the better choice for the seller to move his orders to boxes (As this the main thing to solve)

  • Many concepts were discussed with the team.

  • After this one week long discussion with the product managers we were all convinced to have a separate overview screen for the box section and an upfront order list. (For ref check below the wireframe)

    Later moved on to considering and finding out more use cases on CDC's with the help of PMs and the existing flow:

The importance of CDC in this flow 

(CDC is the distribution centre where seller sends the packages)

CDC Flow.jpg

Proposed initial Solutions

Concepts after ideating for the open tab

WireframesA.jpg

In the above mentioned screens there is only one view box section which can accommodate only one shipment at a time so to create multiple at the same time basis on the CDC we need to do something else.

"Multiple shipments getting processed at the same time in different CDCs"?

image 447.png

Sub tabs under tabs, these CDCs are now like buckets each one have a separate view box section which means each cdc can have multiple shipment created.

Latest box: This overview section is what creating a lot of information clashes.
Now finding ways to remove it because the info displayed in this box is not that important.

Crucial decision making on "Orders X Box creation X CDC"

While initial discussions revealed mixed opinions on using tabs, we ultimately recognized it as the most effective solution for navigating the complexity of the CDC section.

Also, Implemented "All Orders" tab for comprehensive order visibility. This empowers sellers to view all orders, regardless of CDC, facilitating a complete picture of their order volume.

Resolving the CDC issue created a more intricate user experience for box management. Key functionalities for sellers now include: creating boxes, viewing box contents, editing box details, managing box state (open/closed), deleting boxes, closing all boxes, and tracking total boxes and items per box. This screen requires a comprehensive redesign to account for these expanded functionalities.


 

How can we ensure seamless integration between the CDC solution and box actions?

 

image 31.jpg
image 32.jpg
image 33.jpg
image 34.jpg

Multiple iterations later on each of these elements covering multiple use cases for the CDC X Box overview X Move

Seamless Integration with Carriers: Crucial for a smooth flow

  • One Shipment can have one carrier partner only and one CDC​​​​​

  • If a shipment is created, only one CDC orders can be added to it and one carrier can be assigned.

  • Orders from same carrier can only be added in one shipment. ​​​​​​​


Ideation on carrier:
 

  • After considering these points, I presented all ideas to our stakeholders, we discovered multiple scenarios related to the carrier partners.
     

  • One of our project PM suggested to have this option of having carrier as filter because we do not have many such cases at the moment where we need multiple carrier partners as 99% of the carrier partners is only 'one' carrier.
     

  • So, instead of having 'carrier' tabs which will confuse the user more its better to have it as an automated filter at the top.

Carrier.jpg

So yeah, just how I explained all the use cases and scenarios for the 'shipments moving to box'  along with CDC and carriers. This is how I solved other elements of this flow as well. ​

Like the cancellation flow, upcoming orders flow, modification, manifest, invoicing and so on​​​

Ready to see some final ideas? Let's dive into what emerged from our problem solving phase!

image 49.png
image 50.png
image 54.png

That's not all! We've got more to unpack.

 

We addressed the majority of identified issues, but there's always room for iterations. An adventurous UX challenge was waiting for me!


We received another set of business and product challenges which were needed to be solved before moving ahead but why now? What are these challenges? Why did we face them? ... it's yet another story to tell.

Early stakeholder engagement is crucial for effective mental model shifts. This collaborative approach ensures everyone is on the same page from the outset, maximizing design efficiency and output quality.


So now was the time for me to co-create with my developers/ engineering teams/product and business teams. Our initial idea and vision stayed the same but we had to tweak it a bit to accommodate new use cases. Let’s look at the feedbacks of stakeholders to understand deeply of what actually needs to be done next?

 

The Iteration phase starts now!


How we navigated our boat towards success in the middle of all the challenges that kept coming? 🚀

image 773.png
image 774.png

C O N S I D E R A T I O N S

For Design adaptations

Multi-user login confusion: 

  • If Agent 'A' processes BlueDart orders for CDC X and logs off, will Agent B see those open orders upon login? (and vice versa)

  • If both agents create boxes for the same Ship Rocket-CDC X combination, which open boxes will each see?

Mid-session logout

  • Unclear progress upon login. How will users see what was in progress, open, or processed before logging out?

  • Limited Multi-Order Selection: When processing orders, sellers can only select items with a valid OLSK. This restricts them from creating shipments that combine orders with and without OLSKs, even if they share the same carrier and CDC.

Limited data access:

  • Users lack clear visibility into which orders are currently being worked on within a shipment, leading to potential data conflicts.

Partial Order Shipment Confusion:

The system creates a shipment when any item from an order is moved to a box. This creates a problem:

  • The backend can't distinguish which remaining items (from partially scanned orders) are still in the open tab.

  • These unscanned items are already linked to the shipment, making it unclear which orders they belong to.
     

Challenge: Order Selection Clarity

  • Currently, the backend system struggles to identify which specific orders are included in a newly created shipment at the packing station. This lack of clarity leads to two issues:

  • If the seller doesn't scan all intended orders, the backend can't differentiate between completed and on hold orders.

  • Understanding of OLSKs

  • Multi-user Order Management

image 764.jpg

A problem well stated, is a problem half solved.

This problem-solving stage is what I truly enjoy, though we got a lot of new use cases to cover in this phase but brainstorming solutions and taking up these challenges head-on is always fun to me.

As I said This project had been through a rollercoaster ride of new ideas and solutions everyday. This time, it is with more deeper understanding in terms of development areas from backend logics to frontend constraints.

2904.jpg
Frame 2608809.png
image 593.png
image 594.png

Way to solve our open orders and packing the boxes

Open tab

Pack station

Shipment tab

  • Moving a single line item triggers two actions:

    • The entire order gets sent to the packing station.

    • The specific line item you moved gets placed in its designated box.

  • Any remaining line items from the original order stay in the same tab, but are now categorized as "partial."

R E F I N I N G  C O N C E P T S
One more time

After all the discussions I had with the developers up until now, I was onto developing/Re-iterating new concepts considering all the limitations in mind. 

Each of the elements in this case study had been through a lot of ideations and multiple rounds of iterations including the earlier problem that i mentioned like assigning orders, upcoming orders, invoicing and so on. Here for the process I am only focusing on open orders and packing station where movement of shipment is happening. 

 

Iterating my way towards success🌻
 

Frame 2608811.png

Only a few new use cases on cancellation indicated that we need potential friction with the cancel button and a need for bulk cancellation functionality was there. Through brainstorming with Crazy Eights, I developed a solution for the cancellation flow too that will be detailed out in the final designs.

Frame 2608810.png

U L T I M A T E   D E S I G N   D E L I V E R Y

animation_500_l41q0wk1.gif

 

  • Move to pack station: Orders can be moved from ‘open’ to ‘pack’ from here.

     

  • CDC will be used as sub tabs where seller can process orders independently in parallel.


  • Seller can search by Order ID or SKU ID

     

  • Category filter: To make seller’s decision faster basis on the category he can decide what to pack in which box.

     

  • Dispatch by: will be alarming for the seller to keep a track of time while shipping.

     

  • List of orders will only show the order ID and details of order ID can only be fetched when seller expands the list.

  • Clicking "Modify" opens a modal window, allowing seller to modify either the entire order or specific line items within the order.
     

  • The default view will show orders from the past 30 days. This acts as a global filter, automatically additional filters will be applied within that timeframe. To see all orders, simply remove the 30-day filter, and the list will reset.

     

  • When any category is selected, all the orders having those category items will reflect along with other line items.

Modify or cancel :

297.png
292.png

 

  • All items can be cancelled with 'cancel all' button. 

     

  • (-) minus button will be enabled by default i.e. he can only reduce the quantity. Once reduced, seller can use plus button until the update CTA has not been clicked. 

​​

  • Once updated the 'process quantity', rest all will be cancelled and a warning will appear to reconfirm.

     

  • A confirmation window will appear when the seller clicks "Update" to ensure they intended to cancel the order with the adjusted quantities.

Selection of orders:

  • Once the line items are selected, system will automatically filter same carrier and Olsk statuses basis on that selection.

     

  • Carrier logic: If 'Bluedart' is applied then the system reflects all Bluedart orders which then checks for the true state of OLSK.

     

  • Selecting these orders confirms acceptance and packing, triggering an acknowledgement to the backend.
     

  • Pick list can be generated by pdf or by excel to help the pickers.


Assigning & Re assigning:

Frame 2608754.png
Frame 2608731.png

  • Assigning orders: both Sellers and Managers can assign and re-assign tasks, Sellers can also select a Manager to oversee their work with a self assign option as well.
     

  • A long list of agents will be displayed in a manageable way with pagination. This allows seller to view 50 agents per page and easily navigate through the full list.

Packing station:

302.png
  • During packing, sellers can select specific quantities to move into boxes. Remaining items will be held in the pack station area until the invoice is generated.

     

  • Sellers can create a flexible number of boxes to meet their individual packing needs.

     

  • Line items which are not allocated to any box will be cancelled during the generation of invoice.

  • Global checkboxes for bulk selection.

     

  • If one whole order is selected using the bulk checkbox then other individual line items belonging to other order IDs can also be selected.
     

  • Any order ID can be removed from packing station, with all its line items to the open tab.

  • Shipment can be deleted: ALL items will be removed to the open tab.

Box management for shipments:

​​​Management of Boxes:

  • Default box is created with box type default- can be changed using the box type dropdown.
     

  • To create a new box, seller need to save the currently open box. Only one box can be actively edited at a time.
     

  • Box can be deleted and the content inside the box will be removed to open state again.
     

  • Optional weight input field for the seller to enter for logistics purposes.
     

  • He can select box types from the dropdown or if needed he can also create more box properties.

  • When all boxes are saved, seller can generate the invoice and move forward.
     

  • Clicking "Generate Invoice" will trigger a quick check to ensure all items are assigned to boxes. Any unassigned items will be highlighted, allowing seller to review and add them before finalising the invoice.

  • ‘Print all’ is for printing bulk article labels and box labels.
     

  • A red dot will appear on edited boxes, prompting sellers to double-check labels for accuracy before finalizing.

Automation for scanning: 

Frame 2608751.png
Frame 2608753.png
  • Click "Scan and Move." The scanner instantly activates, ready to capture item details. Sellers can scan items using either SKU codes or unique packaging Jio codes.
     

  • The scanner works for all the orders present in the current open shipment.
     

  • When he scans any product the total number of pcs will reflect and seller can select how many quantities he want to move to the box.
     

  • Rest all will go back to the open orders in pack station.

Log of open shipments - Pack tab: 

300.png
  • This pack tab is a log of all the shipments created from open tab, the status will remain open until the invoice is not generated.
     

  • This is for the seller to keep a track on all the shipments that has been created in a particular CDC.
     

  • By clicking on the hyperlink (shipment no.), seller can go to the pack station to see what all orders are there in this shipment and the boxes created respectively.

Upcoming orders:

The ultimate Handoff

This project aimed to establish a seamless design-to-development handoff process, minimizing back-and-forth communication and ensuring smooth implementation.
 

Here are my key strategies:

  • Early Developer Involvement (Post Ideation): Engineers were actively engaged from the initial stages of design iteration. This fostered a collaborative environment where limitations were discussed upfront, preventing future roadblocks.
     

  • Transparency and Communication: All design decisions and crucial considerations were documented and communicated transparently throughout the process. This kept developers informed and ensured alignment.
     

  • Comprehensive Documentation: Each screen was meticulously annotated, detailing use cases and potential scenarios for optimal understanding.
     

  • Interactive Prototype: A detailed prototype showcased the user interactions within the design, enabling developers to visualize the user experience.
     

  • Continuous Collaboration: To avoid surprises and maintain control, regular communication with developers was maintained throughout the development phase. This facilitated on-the-fly adjustments as needed.

Thank you ✨

It has been wonderful sharing my work with you, Thanks for your time.
Looking forward to connecting with you ⏳

~Shami Siddiqui

bottom of page