Skip to main content
Question

No‑Code Solution to Capture Customer Return Reasons for Reporting

  • May 20, 2026
  • 2 replies
  • 23 views

Forum|alt.badge.img+6

Following up on our credit memo reason‑tracking requirement, we also need to record reasons for customer‑returned goods in Acumatica.

Ideally, the return reason should be captured at the line level for each returned inventory item. If line‑level setup is too complex using native tools, we can accept document‑level reason selection as a fallback option.

Just like with credit memos, this field is only for reporting and statistical analysis and will not affect existing business processes. We need to analyze return quantities by reason using Generic Inquiry later.

Again, we prefer native no‑code functionality to avoid customization compatibility issues during the Classic‑to‑Modern‑UI transition.

Could you advise how to set this up with standard Acumatica features such as attributes or built‑in reason codes?

2 replies

Forum|alt.badge.img+9
  • Captain II
  • May 21, 2026

Shipment lines have a Reason Code field which you could create reason codes for common categories of returns, then potentially a more detailed explanation if needed in the notes section.

 

You could create a custom field through the screen/Modern UI editor which would be “no code”.

 

Also worth noting, simple field additions will not create compatibility issues during Classic to Modern UI migration.


Forum|alt.badge.img+6
  • Author
  • Captain II
  • May 22, 2026

@aiwan Thank you for your advice, I will try the reason code if I I could found the native fields.
Actually, I was stuck in the migration from classic UI to modern. like this case below:
Modern UI Migration 2026R1: Display SOShipment DAC Field in SOShipLineSplit Header Panel | Community