-
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
Add shipping carrier integration #100
Comments
Hi, I'd like to help this awesome project. |
@JobaDiniz thanks! Anything you are interested in helping with is greatly appreciated. Region specific features are a great way to get involved. You can read more on how to get started as a contributor here: http://thoughts.reactioncommerce.com/how-to-get-involved-with-reaction-commerce/ Let us know if you have any questions, we're here to help. |
I already read it some time ago. I have a Windows PC, so that's one problem. I'd like to implement shipping cost and shipping tracking for Brazil, but as I see, the infrastructure for shipping was not implemented yet. Also, I'd like to implement Brazil invoices as I have experience in that area; there are a lot of things to implement in order to support Brazil invoices. |
@JobaDiniz we've implemented a shipping schema, and a flat rate example that can be used as a basic template for dynamic lookups. We'll be building dynamic methods soon, but most of the logic that you see for the flat rate lookup would similar for any implementation. We're getting ready to work on the order workflow again in the next week or so. I'm not sure the status of Windows support, I know there are several projects that allow you to run Meteor on Windows, although I'd probably use a linux VM with a shared folder (vagrant, for instance). |
Items remaining:
|
Add Shippo Package. See #421 |
…-pe-plugin Feat nnnnat pe plugin
…9953ce3136a12207c27ee4 [Snyk] Upgrade sharp from 0.23.4 to 0.28.3
…/tmpl-1.0.5 chore(deps): Bump tmpl from 1.0.4 to 1.0.5
Add support for US and Global shipping carriers.
The text was updated successfully, but these errors were encountered: