Skip to product information
1 of 1

The importance of information design with fulfillment in mind

The importance of information design with fulfillment in mind

View full details

The other day, I had a meeting with the person in charge of fulfillment, and I learned a lot.

Although it is a rough summary, I will summarize what I learned and noticed.

https://twitter.com/Shin_EC_Web/status/1551807195079004161?s=20&t=8QQWs1SCJVMu1iLL4ZVkTg

How the meeting came about

When renewing our e-commerce business with Shopify, we held a meeting to confirm whether the order data from Shopify and the WMS we were currently using could be linked without any problems.

The point is to check if "When you pass Shopify order information to the warehouse, can it be read by the warehouse without any problems?"

When building Shopify, you tend to focus on the e-commerce site itself or the Shopify app, but you also have to forget about fulfillment and backend operations.

Things you need to be aware of when designing order information and customer information

The meeting helped me understand once again the importance of designing order information and customer information.

This is a specific case that I encountered, so I don't think it will be of much use as a reference, but it might help you realize that ``Is information design important for that reason?''

This time, we had to be aware of the following points when designing order information.

  • Be able to determine which delivery company to use
  • Be able to determine whether to gift wrap or not
  • I want to standardize the presence or absence of hyphens in phone numbers.

Be able to determine which delivery company to use

For example, let's say that there are cases where you use multiple delivery companies, such as ``Sagawa for regular delivery'' and ``Yamato for Nekopos''.

In that case, information that allows you to determine which delivery company to use is required in the order information.

This time, the "charge name" set in the Shopify delivery profile was reflected in the order information, so I made it possible to identify the delivery company based on the wording there.

Be able to determine whether to gift wrap or not

We use All in Gift to handle gifts, but we not only had to tell the warehouse whether or not the order was for a gift, but also whether or not this order required wrapping.

Therefore, if wrapping materials are also added to the cart, we decided to create a flow that can add the tag "wrapping" to the order information.

I want to standardize the presence or absence of hyphens in phone numbers.

Warehouses may also have problems if the format of phone numbers reflected in order information is inconsistent.

Therefore, the label of the phone number input field on the checkout screen has been changed from "Phone number" to "Telephone number (enter without hyphens)".

Changed the label of the phone number input field on the checkout screen from "Phone number" to "Telephone number (enter without hyphens)"

By the way, you can edit the wording in this part from "Theme" > "Actions" > "Edit Language"

Summary of this time

Builders should be aware that each warehouse with which they have a contract has rules that require order information to be in this format.

It would be great if we could design information with an eye to the future, such as, "Maybe we'll offer gifts in the future?" "Maybe we'll introduce an app like this?"