Why this issue exists
The order detail footer's action validator modelled a Reship action that had no handler, so it never rendered. It was removed in #534 so the code stops looking like a live feature. This issue keeps the decision so it can be picked up.
Product decision (2026-06-11, from the removed validator header)
- Reship is a remediation action for any order that is not
ORDER_CANCELLED, including after items complete.
- This was recorded as open assumption R1 together with Appeasement, and never confirmed with product.
Backend: missing
- The removed validator notes that the legacy OFBiz flow (
ReShipOrderItems.ftl) was dropped in the OFBiz → Moqui migration.
- There is no reship service or REST resource in
hotwax/oms service/oms.rest.xml today. A code search for "reship" only matches ProductStoreShipmentMeth.
- The Clone design (
docs/OrderCloneDesign.md) treats "re-ship as a new order" as a case Clone covers. Decide whether Reship is its own flow (a replacement ship group on the same order) or a Clone preset before building a backend.
Where the removed code lived
To do
Why this issue exists
The order detail footer's action validator modelled a Reship action that had no handler, so it never rendered. It was removed in #534 so the code stops looking like a live feature. This issue keeps the decision so it can be picked up.
Product decision (2026-06-11, from the removed validator header)
ORDER_CANCELLED, including after items complete.Backend: missing
ReShipOrderItems.ftl) was dropped in the OFBiz → Moqui migration.hotwax/omsservice/oms.rest.xmltoday. A code search for "reship" only matchesProductStoreShipmentMeth.docs/OrderCloneDesign.md) treats "re-ship as a new order" as a case Clone covers. Decide whether Reship is its own flow (a replacement ship group on the same order) or a Clone preset before building a backend.Where the removed code lived
RESHIPcase ofvalidateFooterActioninsrc/utils/OrderActionValidator.ts@ 8d5ab9aTo do