RMA Boundary
Current Salesforce boundary for returns and RMA-related context
Current Direction
Salesforce is not the primary operational RMA system. The dedicated external RMA app owns the full return workflow, including customer signing, photo analysis, inspection mode, and operational review.
Salesforce should keep only the thin correlation context needed for sales order history, finance, credits, and customer service. Any needed RMA data should relate through Sales Orders instead of rebuilding full RMA record-management screens inside Salesforce.
Boundary Map
Salesforce Dependencies
RMA-related metadata still exists in the repo and has dependencies in finance and sales-order mutability logic. Removing or changing it is not a UI-only cleanup.
Before changing RMA metadata, map impact across:
- Credit memo behavior.
- Sales Order mutability and downstream evidence.
- Existing RMA objects and lines.
- Emails and PDFs.
- External app correlation fields.
- Reporting or customer service references.
User Guidance
Users should not start a return workflow in Salesforce unless leadership has explicitly re-enabled that process. Start operational RMA work in the external app and use Salesforce Sales Orders as the customer/order history anchor.
Last updated on