Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Return authorization subcase

Updated on January 27, 2021

The Return authorization case is a Parts return request subcase. It consists of the following actions between the dealer and the manufacturer:

  • A dealer creates a Return authorization subcase for each part number that needs to be returned per request.
  • The subcase provides the dealer with shipping instructions, part tags, and shipping labels that are pre-populated with the shipping address and carrier.
  • The service level agreement (SLA) is used by the dealer to ensure that the parts are returned to the manufacturer within stipulated time.
  • When the manufacturer receives a part at the parts return center, the return authorization status is updated to indicate that the part has been received, relieving the dealer of liability.

Upon receipt of the container, the shipping and receiving team at the manufacturer’s site verifies whether the material has been returned in good condition. The return authorization is resolved after the shipping and receiving team assigns a BIN number (storage space or slot) to the material and submits the subcase.

To notify the PartsRequestor party of any created single or multiple repair orders, configure the PartsRequestorMail correspondence rule. For more information, see Correspondence rules.

The Return authorization subcase helps you to choose the parts to return and then ship them. The subcase processes the return mode, carrier, and shipping information. After submitting a Return authorization subcase, the system notifies you that the part has been already shipped to the destination and is waiting to be received.

The complete Return authorization process flow is detailed in the following image:

Figure: Return authorization process

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us