---
schema_version: "1"
id: 396e96ecdbe2c17c5d44e2ce05dba457afeb60c46e3e583e246b0b2f1f09155f
title: Transit Time
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/chrm_transit_time_parent.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.chrm_transit_time_parent.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3729e37d33681fe2ee8895058bf2280133be6047b5dc4fbd0b557aaf75f3bcc9
description: Define transit durations for partner inventory by specifying source, destination, usage type, and duration. Transit Time records set expected movement between locations. If no specific Transit Time exists, the Account Lead Time of type Transit is used as the default. Transit Time impacts price protection, inventory reconciliation, manual adjustments, and end-customer returns, ensuring accurate inventory tracking, claim calculations, and financial traceability. It builds on the existing Channel Inventory functionality to track partner inventory more effectively.
products:
  - Partner Cloud
  - Cross Cloud
  - Manufacturing
release: "264"
---
# Transit Time

Define transit durations for partner inventory by specifying source, destination, usage type, and duration. Transit Time records set expected movement between locations. If no specific Transit Time exists, the Account Lead Time of type Transit is used as the default. Transit Time impacts price protection, inventory reconciliation, manual adjustments, and end-customer returns, ensuring accurate inventory tracking, claim calculations, and financial traceability. It builds on the existing Channel Inventory functionality to track partner inventory more effectively.

### 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>

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

Note Transit Time is optional and can be configured to track partner inventory movement, either between locations or by partner account, with the option to include estimated timelines.

## Transit Time Applications

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d23151e69">Application Area</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d23151e72">In-Transit inventory Impact</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Application Area" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e69 ">Price Protection</td>

            <td data-label="In-Transit inventory Impact" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e72 ">
              <p>Enable Price Protection to include in-transit inventory by setting the In
                Transit Quantity Applicable checkbox in Rebate Type and Is Payable checkbox in Price
                Protection Term. The eligible quantity automatically reflects in-transit amounts,
                and if a price changes mid-transit, a new child bucket is created during claim
                generation to ensure financial accuracy. In-transit quantities are considered at all
                stages, from simulation to final claim generation.</p>
              <p style="margin-bottom:0;">Clone the
                Ready_to_Use_CalcClaimAmount expression set template, activate it, and attach it
                to the Program Rebate Type. After DPE execution, run the Update Product Pricing
                for Price Protection flow to calculate pricing differences and set the status to
                Ready for Claim. When the status is Ready for Claim, generate the rebate claim and
                the PPE status updates to Complete.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Application Area" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e69 ">Inventory Reconciliation</td>

            <td data-label="In-Transit inventory Impact" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e72 ">Inventory Reconciliation includes the Total In Transit Quantity field,
              calculated by DPEs using Transit Time and Account Lead Time definitions. Partner
              Inventory Item Reconciliation records can reference in-transit ledgers, enabling
              more accurate reporting. </td>

          </tr>
          <tr class="">
            <td data-label="Application Area" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e69 ">Manual Adjustments</td>

            <td data-label="In-Transit inventory Impact" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e72 ">Manual adjustments can move in-transit inventory between PUI records while
              retaining the original status of In Transit and the available date. Traceability
              records are updated automatically, ensuring accurate tracking of all manual
              inventory moves. To manually update a ledger from In-Transit to Approved, cancel the
              current ledger and create a new ledger using a manual adjustment. Set the correct
              available date in the new ledger.</td>

          </tr>
          <tr class="">
            <td data-label="Application Area" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e69 ">End-Customer Returns</td>

            <td data-label="In-Transit inventory Impact" class="slds-cell-wrap" style="vertical-align:top;" headers="d23151e72 ">Prevent incorrect credits against inventory still in transit. Validation
              subtracts in-transit inventory from total stock automatically to determine truly
              available inventory before allowing a return.</td>

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

![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 manufacturer sets a 3-day estimated transit time for smartphone shipments from a warehouse to a partner store. When 100 units ship on September 22, they are flagged as In-Transit with an availability date of September 25. The system reflects these units in reconciliation, applies price protection correctly if prices change mid-transit, allows manual adjustments without altering the original availability, and prevents returns until the inventory is approved. Transit time ensures accurate handling across reconciliation, price protection, manual adjustments, and returns from shipment to final availability.

## Order of Transit and Lead Time Application

When a transaction journal is processed, records are applied in the following priority:

- Transit Time: If both source and destination locations match, the corresponding Transit Time record applies.
- Account Lead Time: If no Transit Time record applies, an Account Lead Time record of type Transit is used based on the Account.
- Default: If neither exists, inventory is considered immediately available with the partner, and ledgers are created in an Approved state.

Transit Time and Account Lead Time determine whether ledgers are In-Transit or Approved, forming the basis for price protection, reconciliation, manual adjustments, and returns.

## Assumptions and Limitations

- Destination Locations on a transaction journal require an account that matches the TJ account. There’s no out-of-the-box validation, so mismatched accounts can cause processing issues.
- Accounts on source and destination Locations aren't validated.
- Account Lead Time matching considers only accounts where type is Transit.
- Inventory without matching Transit Time or Account Lead Time is immediately available and created in Approved state.
- For users without ship and debit permissions, [remove or update specific nodes](https://help.salesforce.com/s/articleView?id=xcloud.chrm_transit_time_nodes_update.htm&release=264.0.0&type=5 "For users without Ship and Debit permissions, remove or update the following DPE nodes to ensure accurate price protection processing.") in the DPE definition before running Price Protection.
- Transit and lead times can't be negative. Duplicate Transit Time or Account Lead Time records for the same source or destination or account aren't allowed.

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

Note To apply in-transit inventory in Price Protection, create related records in Rebate Program, Rebate Program Member, and Program Rebate Type. Ensure In Transit Quantity Applicable checkbox is selected in the Rebate Type record and the Is Payable checkbox is selected in the Price Protection Term record. Integration users need PSLs for Rebate Management, Channel Inventory, and Price Protection.

- **[Set Up Transit Time](https://help.salesforce.com/s/articleView?id=xcloud.chrm_transit_time_set_up.htm&release=264.0.0&type=5)**  
    Define expected transit durations for partner inventory between locations, link partner accounts to locations, and assign default lead times at the account level. The configuration enables accurate calculation of partner inventory availability, supports reconciliation, and provides visibility into claims processing.
- **[DPE Execution Sequence for In-Transit Inventory and Price Protection](https://help.salesforce.com/s/articleView?id=xcloud.chrm_transit_time_dpe_sequence.htm&release=264.0.0&type=5)**  
    Once Transit Time and Account Lead Time records are defined, execute the following DPEs in this order to ensure accurate handling of in-transit inventory, proper ledger status updates, and correct price protection calculations.
- **[DPE Node Updates for Users Without Ship and Debit Permissions](https://help.salesforce.com/s/articleView?id=xcloud.chrm_transit_time_nodes_update.htm&release=264.0.0&type=5)**  
    For users without Ship and Debit permissions, remove or update the following DPE nodes to ensure accurate price protection processing.