---
schema_version: "1"
id: 242ee020c86987482c58539206b214fbcf22ed96e6f416db9fbae86fd438152e
title: Process Point of Sale Return Transactions for End Customer Returns
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/chrm-end-customer-returns.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.chrm-end-customer-returns.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: caf089e078d5a1028312d060a8347a528ef7caf83691c761b80f956a79308345
description: Process point of sale return transactions reported by partners when end customers return products. Use the Process Point of Sale Return Transactions for End Customer Returns data processing engine (DPE) to capture return documents, validate return data, identify eligible returns, and update partner unsold inventory and related ledger records.
products:
  - Partner Cloud
  - Cross Cloud
  - Manufacturing
release: "264"
---
# Process Point of Sale Return Transactions for End Customer Returns

Process point of sale return transactions reported by partners when end customers return products. Use the Process Point of Sale Return Transactions for End Customer Returns data processing engine (DPE) to capture return documents, validate return data, identify eligible returns, and update partner unsold inventory and related ledger records.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Professional</strong>, and <strong>Unlimited</strong> Editions with the Channel Revenue Management add on</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d26100e65">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d26100e65 ">To adjust channel inventory by using end-customer return data</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d26100e65 ">Channel Partner Inventory User</td>

          </tr>
        </tbody>
      </table>

Here are the high-level steps in the DPE template:

1. The DPE captures inventory returns from end customers to partners by processing Transaction Journals of type Point of Sale Return Document.
2. When a Return PoS references the original Point of Sale transaction, the DPE uses this link to credit the corresponding inventory.
3. If the Return PoS doesn’t reference the original PoS, the DPE uses matching criteria such as account, product, and price to associate the return with a Partner Unsold Inventory (PUI) record.
4. The DPE processes Return PoS entries with original references first, followed by those without a reference.
5. It calculates the creditable quantity at both the matching Point of Sale and Partner Unsold Inventory levels.
6. The DPE also identifies any unprocessed or partially processed quantities from valid transaction journals.
7. In reservation scenarios, the DPE handles returns that are initially on hold and later move to Approved or Rejected status based on further processing.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-channel_revenue_mgmt-264-0-0-production-enus/0afcbbd8-b325-4d62-baa1-63243d1c10aa/images/icon_example.png)

Example A partner submits a return transaction from an end customer with a quantity of 300. The Return PoS doesn't reference the original Point of Sale document. Based on matching criteria such as account, product, and price, the DPE identifies the corresponding Partner Unsold Inventory record. This inventory was originally created from a sale transaction of 1000 units, followed by PoS transactions totaling 600 units. As a result, the creditable quantity is 600.

The DPE credits 300 units to the inventory, updates the associated Partner Unsold Inventory record, and creates a corresponding ledger record. The return transaction journal is then marked as Processed. If the return quantity is not valid or no matching inventory is found, an error message is logged and the transaction journal status is updated accordingly.

When creating a Transaction Journal (TJ), if a related journal is specified, the DPE doesn't check for account, product, or price. To ensure these are checked, use validation rules on Transaction Journals.

#### See Also

- [Validation Rules](https://help.salesforce.com/s/articleView?id=platform.fields_about_field_validation.htm&language=en_US&type=5)