Add initial zones documentation for end users #2750
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
benjaminwil
force-pushed
the
user_guides/locations/initial
branch
from
66439c4
to
6ed2f57
Compare
gmacdougall
requested changes
May 29, 2018
| carriers you use for shipments. | ||
|
|
||
| For example, if you only want to allow UPS to ship packages domestically, you | ||
| could set its zone your home country only. You could be even more restrictive |
|
|
||
| This feature is useful in cases when you use multiple carriers that ship to | ||
| different regions. For example, if you use USPS to ship to the United States and | ||
| Canada, but you use FedEx to ship to the United States and Canada as well as to |
There was a problem hiding this comment.
I'd add an example here about offering different shipping services based upon ship time. For example, overnight shipping for $30 and ground shipping for $10.
There was a problem hiding this comment.
I'm not sure how this example would be applied to shipping in a zones context. But I do agree that this example should be added elsewhere.
The example here that I am providing is generic but clear.
benjaminwil
force-pushed
the
user_guides/locations/initial
branch
from
6ed2f57
to
f69ebbf
Compare
tvdeyen
requested changes
Jun 5, 2018
| specific geographical area. Zones are especially useful for helping you comply | ||
| with the tax variations in different regions. | ||
| Zones allow store administrators to set shipping rules and tax rates for | ||
| specific places. They also allow you group states or countries in a |
There was a problem hiding this comment.
They also allow you group states
Missing "to"
This commit makes some explanation of Solidus zones more clear. It also adds links to now-merged documentation about shipments and taxation.
Zones are mostly a Solidus concept, and the developer docs attempt to explain how this concept is used in practice. So, it is portable to the end user documentation as well. There are just a few changes because the end user documentation's audience is not developers.
benjaminwil
force-pushed
the
user_guides/locations/initial
branch
from
f69ebbf
to
11de74d
Compare
tvdeyen
approved these changes
Jun 7, 2018
gmacdougall
approved these changes
Jun 13, 2018
|
Looks like this needs a rebase. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds initial documentation about Solidus's zones settings for end users. The audience for this documentation is store administrators or anyone who has to touch the solidus_backend as a business person.