openerp-india team mailing list archive

["Alexandre Fayolle @ camptocamp" <alexandre.fayolle@xxxxxxxxxxxxxx>]

Public bug reported:

If you setup you warehouse with the Output location manually chained to
the customer location, then returning goods is messed up.

A Sale Order will generate a move from Stock to Output, and the chained
location setup will generate a move from Output to Customer. When the
customer returns the good for any reason, the user will use the stock
return picking wizard from the OUT picking. This generates an incoming
move from Customer to Output, and the chained location setup generates
in turn an outgoing move from Output to Customer (and when the incoming
picking is processed, the outgoing move gets available...)

This is wrong, as it totally messes up the logistics of the company, and
it is a big problem for an e-commerce company handling over 100 SO per
day, with 5% return rate, as it requires a lot of manual processing. In
my opinion, there should never be an *incoming* move to the *Output*
location of the warehouse. This would solve the problem.

There should be a setting on the shop specifying which location is to be
used for returns, or the stock return picking wizard should provide a
way of specifying a location on a case by case basis.

** Affects: openobject-addons
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1075559

Title:
  [6.1] return product messed up when output location manually chained
  to customer location

Status in OpenERP Addons (modules):
  New

Bug description:
  If you setup you warehouse with the Output location manually chained
  to the customer location, then returning goods is messed up.

  A Sale Order will generate a move from Stock to Output, and the
  chained location setup will generate a move from Output to Customer.
  When the customer returns the good for any reason, the user will use
  the stock return picking wizard from the OUT picking. This generates
  an incoming move from Customer to Output, and the chained location
  setup generates in turn an outgoing move from Output to Customer (and
  when the incoming picking is processed, the outgoing move gets
  available...)

  This is wrong, as it totally messes up the logistics of the company,
  and it is a big problem for an e-commerce company handling over 100 SO
  per day, with 5% return rate, as it requires a lot of manual
  processing. In my opinion, there should never be an *incoming* move to
  the *Output* location of the warehouse. This would solve the problem.

  There should be a setting on the shop specifying which location is to
  be used for returns, or the stock return picking wizard should provide
  a way of specifying a location on a case by case basis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/1075559/+subscriptions