Pos.cart.line-item-details.action.menu-item.render does appear when cart is in return view

Extensions
1

When i try to render pos.cart.line-item-details.action.menu-item.render during a return or exchange. It does not appear in the action menu and nothing in the documentation states this is a limitation it even lists the below as a use case.

Item modifications: Process returns, exchanges, or adjustments without affecting the entire cart.

2

Hey @Steve_Wilson - thanks for flagging this. You’re right that the current Cart details documentation specifically lists returns and exchanges as a use case, so it’s reasonable to expect this target to appear there: Cart details

From the available target coverage, pos.cart.line-item-details.action.menu-item.render is scoped to the standard active-cart line item menu. The return/exchange-specific targets are currently post-transaction targets, and I couldn’t find a documented target for line item actions during an in-progress return or exchange.

Could you share:

  • Your POS app version, device OS, and extension API version
  • Whether the menu item appears for the same product during a normal sale
  • Whether this affects both returns and exchanges

A short screen recording would also be helpful if possible. Once I have that, I can look into reproducing it on our end and loop back here. Hope to hear from you soon.

3

Hey @Alan_G ,

thanks for getting back to me.

in POS version: 11.11
Yes i got it working for a normal Cart
Yes it affects both returns and exchanges

(i have had it confirmed from other sources that this expected behaviour and is a known limitation, unless you can tell me otherwise :smiley: )

4

Hey again @Steve_Wilson thanks for this! I confirmed that the current target coverage doesn’t expose pos.cart.line-item-details.action.menu-item.render during an in-progress return or exchange, and there isn’t a separate line-item action target for those views at the moment.

Since it’s mentioned in the Cart details documentation that returns and exchanges are a solid use case, I’m flagging the documentation gap and confirming the intended target coverage on our end.

The closest available workaround is an order-details action before starting the return or exchange, though that won’t provide an item-level action inside the return cart itself. I’ll loop back if I receive a different confirmation on this on my end here.