Orders 7764 render create return page with context

[bc-vivekaggarwal]

What?

Massive refactoring for new return flow to use updated stencil page context(order details, reasons and resolutions) and use the new /create-return route

Requirements

• CHANGELOG.md entry added (required for code changes only)

Tickets / Documentation

Jira: ORDERS-7764

Screenshots (if appropriate)

All pages load fine:

###Orders listing page:

###Order details page:

###Add returns page:

When both flags(legacy returns_enabled and new returns_v2_enabled) off:

Orders list and Order details page don't show returns items and new_return route redirects to orders list page:

Existing add Return page (when only legacy returns_enabled):

Add return page when only new flag returns_v2_enabled enabled:

Redirects to orders list page. Currently BC app doesn't support redirection when legacy returns is disabled. We need to fix this as part of ORDERS-7825

Add Return page with new content(when returns_v2_enabled or both enabled):

New Design after consultation with JW and JH:

---

Note

Medium Risk
Changes which account routes load which return UI and how v2 is reached relative to feature flags; submission is not wired yet, but mis-routing could affect shoppers on the wrong template.

Overview
Moves the returns v2 UI off account/add-return onto a dedicated create-return route and page type, wired to stencil context (order, per-line returnableQuantity/price, and shared reasons/resolutions).

Routing & JS: app.js loads create-return.js for create_return and routes account_new_return back to the generic account bundle. add-return-new.js is removed in favor of CreateReturn, which validates submit from select controls (qty/resolution/reason), drops the quantity stepper, and exposes buildReturnInput() for the upcoming Storefront GQL submit (still a TODO).

Templates: add-return-new.html is deleted; add-return.html no longer branches on returns_v2_enabled and only renders the legacy POST return form (with small a11y/table copy tweaks). create-return.html implements the new layout: column headers on large screens, qty dropdowns capped by returnableQuantity, and dynamic reason/resolution options.

Styles & copy: .newReturn styles move from addReturn into a new createReturn SCSS component (header buttons, column alignment, select widths). en.json adds/updates strings for the new return request UX.

^{Reviewed by Cursor Bugbot for commit 4ee19ec. Bugbot is set up for automated code reviews on this repo. Configure here.}

[bc-vivekaggarwal]

cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit b838233. Configure here.}

[matt-evangelidis]

Add return page when only new flag returns_v2_enabled enabled:
Redirects to orders list page. Currently BC app doesn't support redirection when legacy returns is disabled. We need to fix this as part of ORDERS-7764

For context, what change do we need to make on the BCApp side to get redirection to work?

[bc-vivekaggarwal]

Add return page when only new flag returns_v2_enabled enabled:
Redirects to orders list page. Currently BC app doesn't support redirection when legacy returns is disabled. We need to fix this as part of ORDERS-7764

For context, what change do we need to make on the BCApp side to get redirection to work?

@matt-evangelidis Good catch, updated description. The redirection fix is dependant on: ORDERS-7825
Everything else is already there:

1. returns_v2_enabled already works now. But it comes in settings context which is currently behind STRF-13960.Settings_resource_migration. Either you turn it ON for your store or hack it in Storefront to bypass that FF.
2. Redirection: Currently all GraphQL order related APIs return only legacy URL in API response, we need to update that as part of ORDERS-7825 to the legacy/new URL based on which returns flow is enabled. Meanwhile, use hardcoded URL /create-return/{orderId} to land on the page