Enterprise Drop Shipping, Part 9: How to Manage Returns

By: Jeremy Hanks

Drop shipping requires three major data integrations between the retailer and the supplier: product catalog, inventory, and orders. The order integration and workflow culminates with fulfillment and shipment from the supplier to the end customer.

To recap, managing product catalog data starts with the premise that drop shipping requires the seller-retailer to have a virtual representation — i.e., data — of a physical thing that they will never see, touch, or control. Product catalog is the collection of descriptive data — title, brand, category, attributes, images — of that physical thing.

Managing inventory visibility is the process that tells you where the item is, how many items there are, and what they cost you as the reseller.

Orders are when it all comes together. Managing orders occurs when a consumer has purchased a product that a retailer was selling virtually and the order and fulfillment information needs to be sent to the supplier who physically has the product so that they can ship to the consumer.

Assuming everything has gone well with the other three data integrations (catalog, inventory, and orders), managing fulfillment is as simple as the supplier — or a third party logistics provider — boxing up an item and shipping it to the consumer.

Once the consumer receives the purchased item, they are either happy with it (yay!) or for various reasons decide they want to return it. In this post I’ll take a look at the process for managing returns in drop shipping.

Returns Are Complicated

Some online products see return rates approaching 25 percent, so you will need to figure out a plan for handling drop-shipping returns because they’re going to happen. The process for handling such returns, however, is much more complicated compared with returns for physical retail stores. That’s why having a good policy and strategy that can be coordinated between retailers and suppliers is critical for ensuring the result that both parties are seeking: happy consumers.

Here’s a list of the data that could be coordinated between retailers and suppliers for returns:

  • po_number. The unique order identifier generated by the retailer’s system from the original order.
  • rma_number. The unique return identifier generated by the supplier.
  • order_return_reason. The reason the order is being returned. This could be, for example, “item delivered didn’t fit,” “customer decided product was not needed or wanted,” “item didn’t match the product description,” “company shipped the incorrect product or size,” or “product was damaged or defective.”
  • line_item_sku. The SKU being referenced by this update.
  • line_item_return_reason. The reason the line_item_sku is being returned.
  • line_item_quantity. The quantity that is expected to be shipped in this return.
  • line_item_condition. The condition of the line_item_sku. This could be, for example, “new,” “used,” or “damaged.”
  • line_item_expected_credit. The credit that the retailer expects to receive for the given SKU.
  • note. Optional note about this returned item.
  • needs_special_handling. Check if the person receiving this return should be aware of special handling needs prior to receiving.
  • return_attention. The name or title where the return is being shipped.
  • return_company. The company’s name where the return is being shipped.
  • return_address_1. Address 1 line where the return is being shipped.
  • return_address_2. Address 2 line where the return is being shipped.
  • return_city. City where the return is being shipped.
  • return_region. Region where the return is being shipped.
  • return_postal. Postal code where the return is being shipped.
  • return_country. Country where the return is being shipped, using the two-character ISO country code.
  • return_phone. Phone number where the return is being shipped.
  • return_email. Email address of customer service to whom the return is being shipped.
  • ship_carrier. The name of the carrier that is preferred to be used for this order. Options could include: FedEx, UPS, USPS.
  • ship_method. Shipping method requested. Only those options supported by the supplier will be supported.
  • return_tracking_number. The tracking number of the return, as assigned by the carrier.
  • return_ship_cost. The cost to ship the return.
  • return_ship_date. The date that the given return shipped.
  • return_ship_carrier. The carrier that is shipping the return.
  • return_ship_method. The actual shipping method for the return.
  • return_received_on_date. The date that the return was received by the supplier.

Considerations for the Trading Partnership

All of the factors around the returns process are based on the trading partner relationship between the retailer and supplier. These factors should be identified, discussed, and coordinated at the start of the relationship, rather than when a return actually occurs. Some of the things to consider and make a part of the supplier onboarding process are as follows:

  • Return to location: retailer-controlled location. There are pros and cons to any one method of handling returns. If you have infrastructure and processes in place to accept returns to your facilities and then send to suppliers, this can be used. It provides a single address for your customer service team to communicate with your consumers.
  • Return to location: supplier. Most retailers supporting returns tell the customer to send the item directly back to a supplier. Expectations and coordination are key with this plan.
  • Restocking fees. It’s important to understand if all, or some, of a supplier’s products will require a restocking fee. Many suppliers still use these fees because a high percentage of their business is B2B. Many other suppliers, however, are removing these fees as they engage more in direct-to-consumer selling.
  • Reverse logistics. Retailers who inventory and ship their own products can include prepaid return labels with the shipments. That strategy is very difficult, if not impossible, when working with suppliers. The best plan is to handle RMAs and return labels with the consumer through a process involving a customer service team. Packing slips — if you can provide them to the suppliers — should provide instructions to the customer as to how to handle a return.
  • Product category. It is helpful to understand the product category(s) you are selling. For example, return rates for apparel are multiples higher than for electronics. Research, and then plan accordingly.
  • Return policy. It is best for the return policy to be consistent across all products from all suppliers and for the instructions to be simple and clear for the customer. This includes restocking fees. Try to average things out so that you don’t need to provide what becomes an item-level return policy.

These points should provide a basis for an important part of the initial on-boarding and partnership discussions.

Ensuring Success

Retailers and suppliers that have the most success in dealing with drop-shipped returns are those that work diligently around the other data workflows and processes — especially product catalog and inventory visibility — as these processes lay the foundation for the best returns strategy: prevention.

Customers return products when they are disappointed with their purchase. In my experience, two of the top reasons for returns are “The customer ordered incorrect product or size” and “The product did not match the description on the website or in the catalog.”

Shoppers want to understand what they are considering to purchase. Having proper photographs and informative product descriptions that are as detailed as possible will greatly reduce the number of returns. I addressed this in “How to Manage Product Catalog Data” — the key is to use a heavy curation and standardization process. It’s critical that retailers and suppliers work together to get the best, most complete, and accurate virtual representation of these physical products as possible.

Returns are going to happen. However, communicating closely with your trading partners for product catalog, orders, and fulfillment will help make returns the exception and not the rule.

 

Jeremy Hanks

Jeremy Hanks

Jeremy Hanks is the Founder & CEO of Dsco (www.dsco.io), a distributed inventory network & supply chain intelligence platform. Previously, in 2002 he founded Doba (www.doba.com), an ecommerce drop shipping virtual distributor; and in 1998 GearTrade (www.geartrade.com), a marketplace for used, closeout and distressed inventory. In their own way, each company was centered on the sharing of data between retailers and brands so that they can more effectively match supply to demand and reduce inventory distortion. Based on his entrepreneurial arc over 20 years and across 3 companies, Jeremy has a unique perspective on the need to adapt and evolve the supply chain. He grew up on a Southern Idaho dairy farm, came to Utah 25 yrs ago for college, and stayed to live Life Elevated.