You are here:
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.
Required Editions
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.
Importing historical orders with the same Account or ContactId can result in duplicate Account/Contact creation or OrderCreationFailureSending orders with inaccurate or outdated data and 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.
| Entity | Deduplication Logic |
|---|---|
| Account, Person Account, Contact |
|
| Pricebook2 | Only Standard Price Book lookup is supported. If a Pricebook2 node is included in the request, the Standard Price Book ID is queried and used. |
| Product2 | Deduplication is based on ProductCode. If an existing Product2 with the same ProductCode is found, it’s used. |
| PricebookEntry |
|
| SalesChannel | Deduplication is based on the SalesChannelName field. |
| Promotion | Deduplication is based on the Name field. |
| WebStore | Deduplication is based on the ExternalReference field. |
| OrderDeliveryMethod | Deduplication is based on the ReferenceNumber field. |
