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

Carriers and service levels for shipping methods #7

Merged

Conversation

Senjai
Copy link

@Senjai Senjai commented Jan 22, 2016

Bonobos implimentation for solidusio#730

When we're dealing with a shipping method, we have no formal way of
adding additional information that would be useful for fulfillment
purposes.

We can add an "internal" name to the shipping method, but that would
require pattern matching to get any useful information from. Often, in
most fulfillment scenarios, we have a desire to know _exactly_ what
carrier and service level a specific shipping method is representative
of.

Given a shipment I can then infer that it should be shipped with UPS one
day shipping by introspecting on the methods' carrier and service_level
columns as necessary.

This is optional as it stands, but validations can be added in stores as
required for complex fulfillment scenarios.
Allows users to set service levels and carriers for shipping methods on
the backend.
@Senjai Senjai changed the title Carriers Carriers and service levels for shipping methods Jan 22, 2016
@philbirt
Copy link

👍

Senjai added a commit that referenced this pull request Jan 25, 2016
Carriers and service levels for shipping methods
@Senjai Senjai merged commit 8ed2173 into bonobos:nov_9_with_gift_return_cherry_picks Jan 25, 2016
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

Successfully merging this pull request may close these issues.

2 participants