Returns, RMA, exchange, and refund lifecycle workspace

[dt2patel]

Business goal

Turn return visibility in order-manager into an action-oriented return/RMA/refund workspace for the AS Beauty demo.

Linked planning

• Jira: https://hotwax-team.atlassian.net/browse/PM-118
• Jira subtask: https://hotwax-team.atlassian.net/browse/PM-126
• RFP items: 1.1.6.2, 1.1.6.3, 2.3.14, 2.3.15

Scope

• Add RMA creation and return lifecycle action flow.
• Support label generation, receive return, exchange, refund method selection, split tender/store credit, and short-ship refund states where APIs allow.
• Show lifecycle status without repeating the whole order or return summary.

UX constraints

Use core Ionic components, keep all flows mobile compatible, and do not write CSS.

[dt2patel]

Jira link for AS Beauty tracking:

• PM-126: https://hotwax-team.atlassian.net/browse/PM-126

[dt2patel]

Triaged in the scheduled automation pass. I am not opening a broad frontend PR for this yet because the current app has return visibility, but the requested RMA/refund/exchange workspace depends on backend/API action contracts that are not exposed to Order Manager as structured REST flows today.

What I verified:

• Current Order Manager has read-side return coverage: ReturnDetail.vue loads oms/returns, customer detail has a Returns segment, order detail uses returnItems from the order master to show returned quantity, and PR Improve customer returns tab loading #224 already improved customer return loading.
• There is no top-level Returns search/workspace yet. The Figma alignment notes explicitly kept Returns/Shipments menu rows omitted because OrderService.ts has return/shipment normalizers and DataDocument identifiers, but no corresponding search actions, route records, or view components.
• ReturnDetail.vue is status/detail display only: RMA id, items, status, requested date, facility, order link, channel, reason/type. It has no create/receive/refund/exchange actions.
• OMS has legacy CSR return screens and services such as validateOrderToCreateReturn, createReturnForOrderAndAdjustment, autoAcceptAndReceiveReturn, completeReturnItems, processRefundReturn, replacement/exchange services, and return notifications. Those are wired through web-controller view/request flows or service definitions, not as a single Order Manager-safe REST contract with structured eligibility, action payloads, and result/audit state.
• I did not find REST-style oms/returns action routes for the full workflow requested here beyond the read path currently used by this app.

A safe frontend implementation needs a narrowed API/product contract for:

• return/RMA creation from an order with returnable item eligibility and reason/type options;
• label generation or label-state handoff;
• receive return / complete return actions with per-item received quantities;
• exchange/replacement order semantics;
• refund method selection, split tender/store credit, and short-ship refund states;
• lifecycle/action audit state and per-action failure results.

Until that exists, a frontend PR would only duplicate the current read-only return detail surface or pretend legacy screen services are a stable app contract. Recommended split: keep the existing visibility work as shipped, then define a backend-backed return workspace contract before building the Ionic action flow.

Auto-triaged by the GitHub issues automation loop.