-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
PDP UX for Shipping, Taxes #1699
Comments
@lcampanis your feedback on additional fields for customs here would be great. |
Hi aaronjudd The Shippo fields required for any type of label (Shipping & Customs) to be generated are:
Height, length, width and weight of parcel (shippingParcel schema) are the ones needed in the UI. For international orders requiring a customs declaration, the minimum required fields are :
These are just the required ones,in my opinion. More fields are available here: |
@prosf great, thanks. we're discussing the best way to present these in the product detail page, and should begin implementing this week (along with some additional stuff for taxes,etc) |
I think we should probably add a "Tax Description" field that's optional but when filled in is passed along to the tax provider rather than the stock title/description. |
See the parcel object for shipping: https://goshippo.com/docs/reference#parcels We'll need all that dimensional data. |
Here's a mock w/ measurements added. And a dropdown for tax codes. For the measurements I added a selector to change your unit of measurement. Check out: #1647 for some more detailed notes related to this and the overall PDP UI. |
Disregard references to Customs on this ticket. This has now been moved to #1862. Should just be dimensions plus Tax Code. |
@rymorgan this is what the PDP will look like once I'm done with this ticket |
@rymorgan noted. |
For implementation of #1618, we need UX for designed for the following information on product details page:
Dimensions [Width (x) Length, Depth]
Customs Category (select from list)
Tax Code Category (select from list)
@rymorgan this is likely some additional fields, in the same area vein as the existing inventory, pricing.
The text was updated successfully, but these errors were encountered: