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

Returns are not integrated with EasyPost out of the box #83

Open
aldesantis opened this issue Sep 23, 2020 · 1 comment
Open

Returns are not integrated with EasyPost out of the box #83

aldesantis opened this issue Sep 23, 2020 · 1 comment
Labels

Comments

@aldesantis
Copy link
Member

aldesantis commented Sep 23, 2020

Currently, this extension provides a thin layer on top of Spree::ReturnAuthorization that allows users to easily generate a return label.

However, unlike for shipments, there is no automated integration between Solidus' out-of-the-box RMA system and EasyPost:

  1. The EasyPost shipment ID related to the RMA is not persisted on the return authorization. Instead, a new EasyPost shipment is generated every time SolidusEasypost::ReturnAuthorization is instantiated.
  2. There is no way to buy a rate for the return authorization from the UI.

Unfortunately, this is because Solidus, by default, has no concept of shipping rates for return authorizations. We could hack a solution together, but this is probably better fixed in the core.

@aldesantis aldesantis changed the title EasyPost data not persisted to return authorizations Return authorizations are not automated Sep 23, 2020
@aldesantis aldesantis changed the title Return authorizations are not automated Returns are not integrated with EasyPost out of the box Sep 23, 2020
@stale
Copy link

stale bot commented Nov 22, 2020

This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant