High-Scale Orders and Deduplication

High-Scale Orders uses the Pending Order Summaries REST API to create summaries from order summary graphs. Entities included in the request parameter aren’t subject to deduplication rules.

If a request has entity details in the PurchaseSupportDetails section, the Pending Order Summaries REST API uses deduplication logic to determine whether to update an existing record or create a record. Duplicate entities within the request that aren’t in the database won’t be deduplicated.

Sending orders with inaccurate or outdated data can cause problems that are hard to fix later. Before sending orders to Salesforce Order Management, upload new information for Account, Contact, Product2, PricebookEntry, Promotion, WebStore, SalesChannel, and OrderDeliveryMethod.

This table lists the Pending Order Summaries REST API entities and their corresponding deduplication logic.

EntityDeduplication Logic
Account, Person Account, Contact
  • When you create Account, Person Account, and Contact Duplicate Rules and Matching Rules, the API calls these rules to find duplicates. For Contact, an AccountId is required to use duplication rules.
  • For Person Account, Person Accounts must be enabled.
Pricebook2Only Standard Price Book lookup is supported. If a Pricebook2 node is included in the request, the Standard Price Book ID is queried and used.
Product2Deduplication is based on ProductCode. If an existing Product2 with the same ProductCode is found, it’s used.
PricebookEntry
  • For a single currency Salesforce org, deduplication is based on Pricebook2Id and Product2Id.
  • For a multicurrency Salesforce org, deduplication is based on Pricebook2Id, Product2Id, and CurrencyIsoCode. If you don’t specify the CurrencyIsoCode, the default CurrencyIsoCode is used.
SalesChannelDeduplication is based on the SalesChannelName field.
PromotionDeduplication is based on the Name field.
WebStoreDeduplication is based on the ExternalReference field.
OrderDeliveryMethodDeduplication is based on the ReferenceNumber field.

See Also