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.

Sign up for GitHub

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

Jump to bottom

Restrict shipping methods by stock location #391

Closed
jhawthorn opened this issue Sep 24, 2015 · 5 comments
Closed

Restrict shipping methods by stock location #391

jhawthorn opened this issue Sep 24, 2015 · 5 comments
Labels
type:enhancement Proposed or newly added feature
Milestone
1.3.0

Comments

@jhawthorn
Copy link
Contributor

This is a common need for any store with multiple stock locations. Shipping methods should be able to restrict which stock locations they can be used from.

This will likely require improvements or changes to Spree::Stock::Package
@jhawthorn jhawthorn added the type:enhancement Proposed or newly added feature label Sep 24, 2015
@hhff
Copy link

hhff commented Sep 24, 2015

👍 i was looking into this recently and was so surprised this doesn't exist

@alexstoick
Copy link
Contributor

👍 we have this in our app, and I'd be more than happy to port this over

@gmacdougall
Copy link
Member

@alexstoick That would be great. We would really appreciate any help in this area that you could offer.

@athal7
Copy link
Contributor

athal7 commented Oct 1, 2015

@alexstoick yes!

@alexstoick alexstoick mentioned this issue Oct 2, 2015
Merged
@jhawthorn
Copy link
Contributor Author

Resolved by #412! Thanks to @alexstoick for the hard work on this. 🎉

@jhawthorn jhawthorn added this to the 1.3.0 milestone Jan 21, 2016
@DanielePalombo DanielePalombo mentioned this issue Oct 25, 2019
Open
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type:enhancement Proposed or newly added feature
Projects
None yet
Milestone
1.3.0
Development

No branches or pull requests
5 participants
@jhawthorn @athal7 @gmacdougall @alexstoick @hhff