Feature Request - Returned Items - Change where items are restocked

Chris
  • Edited

Hi Guys,

Current Process

  • Returns (processed in Shopify) are sync'ed into Cin7 
  • The items are returned back to the “bin location” that the item was picked from
  • It sounds good in theory, but in real life, it's not good at all.

Why this is not good

Going back to the original bin location it was picked from is bad for multiple reasons;

1. Products are constantly moving/changing Bin Locations 

  • We shift product into different bin locations quite a bit (generally if the item is a run-out) to make space for new incoming stock
  • This means, for example if we picked SKU001 from Bin A, a week later we could have moved SKU001 into Bin Z.
  • 2 months later, the customer returns the item and we process a refund and restock in Shopify.
  • Cin7 is electronically putting it back into Bin A, which now has a different/new SKU in it.
  • We accept returns up to 90 days, but I'm sure there are business' who have 180 and 360 day returns, so the likely of the SKU remaining in the original bin location that it was picked from is highly unlikely.

2. No Scan Data of where the item was physically placed

  • It might sound fine and dandy for the system to “electronically” complete the bin transfer back to the original bin location
  • But we have no scan data / history / record of the user who processed it and there is no verification that the warehouse member physically put the item back into the correct bin location.
  • For the above example, the return is processed in Shopify by the warehouse team member.
  • From there, they SHOULD HAVE placed the item back into Bin A, but they misread the SKU and put it into Bin B.
  • This is a real issue, when you have 2000+ and growing bin locations.
  • As there is NO SCAN DATA which verifies what bin location that the team member placed it into. Now becomes a nice game of hide and seek, trying to find where the item actually is in the warehouse.

3. Deprecated Bin Locations

  • With the current implementation, the system will still restock the item to the bin location it was picked from, even when the bin location has been deprecated / no longer exists.
  • This is not good at all, it makes no logical sense.

Suggested Solution

The fix is quite simply in theory.

  • Please have all returned item go back into the main warehouse it was sold from, and not the bin location it was picked from.
  • From there, the warehouse team would use the WMS > Receive > Bin Transfer
  • This is much better, because we would have a record of who and where the item was placed into, even if a mistake occurred where the user placed it into the wrong bin location. At least we know where it is!
  • It also solves the issue of products moving bin locations from when it was sold and returned, as you can simply choose at the time which bin to place it into
  • It also solves the issue of not going back into a deprecated bin location.

I sincercly hope this issue gets taken care of seriously with some sort of urgency, as returns is a critical / fundamental operation for any business operating a warehouse managing 1000s of bin locations and skus.

Related to

0

Comments

0 comments

Please sign in to leave a comment.