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

Enable Shipping Methods to be linked to an Order Cycle #8974

Closed
lin-d-hop opened this issue Mar 8, 2022 · 0 comments · Fixed by #9262
Closed

Enable Shipping Methods to be linked to an Order Cycle #8974

lin-d-hop opened this issue Mar 8, 2022 · 0 comments · Fixed by #9262
Assignees

Comments

@lin-d-hop
Copy link
Contributor

lin-d-hop commented Mar 8, 2022

Description

As an enterprise user I would like to be able to specify which shipping methods will be available in the shopfront on specific order cycles.

To select shipping methods we want an additional expandable panel in step 3 of edit order cycle:
Screenshot from 2022-03-08 13-30-27

When opened this panel should display any Shipping Methods that are available. Shipping methods that are available via the shopfront (eg not 'backoffice only' shipping methods) appear with a checkbox enabling them to be activated/deactivated for the order cycle (ticked means activated). 'Backoffice only' shipping methods should be 'greyed out' and unticked in this view.
Screenshot from 2022-03-08 13-30-59

By default all Shipping Methods should be selected for the user in the UI. All Shipping Methods will be available to shoppers in the shopfront.

If some Shipping Methods are then unchecked by the user, these Shipping Methods will no longer be available in the shopfront to choose. All Shipping Methods will continue to be available on Subscriptions and Backoffice Orders.

As this feature is using the complex OC set up, it will only be available to enterprises that are set up as hubs

Acceptance Criteria & Tests

Note to Devs - If any of these details prove complex in implementation please say so so we can rethink the spec if necessary.

  1. All existing order cycles should have all shipping methods available as now by default.
  2. When an order cycles is created all shipping methods are selected and available by default
  3. In the simple order cycle screen nothing changes
  4. In the edit order cycle screen for Hubs (complex) an additional expandable panel in step 3 of the Edit OC process specifies the number of selected and available shipping methods when closed (5/6). Shipping methods not available in the shopfront should be excluded from these numbers.
  5. When expanded this panel should display any Shipping Methods that are available. Shipping methods that are available via the shopfront (eg not 'backoffice only' shipping methods) appear with a checkbox enabling them to be activated/deactivated for the order cycle (ticked means activated). 'Backoffice only' shipping methods should be 'greyed out' and unticked in this view.
  6. When only a subset of shipping methods are selected, only selected shipping methods should be visible to choose on this order cycle in the shopfront. Unselected shipping methods will no longer be visible on checkout
  7. All shipping methods should remain available when creating subscriptions and backoffice orders
  8. This feature has a higher importance than tagging when deciding which OCs to display eg if a customer is tagged for a shipping method, the shipping method must be available in the OC for it to be displayed. If this acceptance criteria is confusing let me know, because the requirement is actually simple but hard to explain in writing.
  9. If no shipping methods are available the order cycle should not display. This also applies in the case of tagged shoppers, that might have a further reduced set of shipping methods and hence visible order cycles.
  10. The 'Ready For' field will move as per the image above to create more horizontal space for the additional expandable panel.
  11. The 'Customer Instructions' field will be moved to within the Shipping Methods expandable panel as per the image above.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants