Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Remove (or circumvent) location configured packages #1696

Closed
jhawthorn opened this issue Jan 31, 2017 · 1 comment
Closed

[RFC] Remove (or circumvent) location configured packages #1696

jhawthorn opened this issue Jan 31, 2017 · 1 comment

Comments

@jhawthorn
Copy link
Contributor

Location configured packages are a feature added in Solidus 1.0 which allows specifying an quantity and variant which must be sent from a specific location before shipments are created. This feature is only on the "cart" page of the admin (and available through the API). This is not the behaviour used on the shipments page.

The cart page forces the admin to specify which stock location they want to use inventory from. When building packages, the coordinator will build shipments specifically with inventory from these locations (in shipments separate from the automatically allocated inventory).

These are responsible for many bugs:

  • Creates split shipments where it's not desired (since location configured packages are always separate) #1366
  • Double-counts stock if both location configured and standard packages are built #1694
  • If you are adding to an existing line item, it doesn't work #1695

The UI is also extremely lacking ot misleading. These issues could also all be considered bugs

  • There is no indication in the admin that inventory has been reserved for a specific location.
  • There is no way not to configure the location when adding an item on the admin Cart page
  • In contrast to the above, there is no way to specify quantities when updating a line_items's amount

Action

We have three options for what action to take:

  • Make location configured packages optional. Require an additional mouseclick to use them from. This is probably the least controversial change.
  • Extract location configured packages to a separate gem, removing them from Solidus itself (my preference).
  • Leave it as is. Fix what issues can be fixed, others, like #1366 are a design flaw and can't be easily fixed.

Some relevant bits of code

@tvdeyen
Copy link
Member

tvdeyen commented Feb 10, 2017

In the last core team meeting we decided to go with option 2 (removing the feature).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants