Match Returns to Orders, Tickets, and SKUs

Resolve return relationships without guessing identities or creating duplicate records.

Before you begin

Capture the source order number, ticket number, SKU, organization, and return record. Use exact identifiers rather than customer names or product descriptions. Confirm that the required Orders, Communications, Products, and Returns modules are available to your role.

How it works

Return relationships connect operational context: Orders supplies the transaction and line items, Communications supplies the support ticket, and Products supplies shared SKU identity. The Returns grid uses these identifiers to open related views and support analytics. A missing relationship can indicate formatting, synchronization, organization scope, or identity problems.

Step-by-step

Open the return and copy the source order, ticket, and SKU identifiers exactly as shown.
Search Orders in the same organization and confirm the transaction and line item.
Search Products for the line-item SKU and inspect any parent or child relationship.
Open Communications and verify the ticket number when a support case exists.
Return to the Returns grid and select or enter the supported linked values.
Save the record and use the linked order or ticket control to test navigation.
If an identifier remains unmatched, check whitespace, prefixes, source formatting, and synchronization state.
Use Imports preview and matching results when the issue affects a workbook batch.
Document unresolved source discrepancies rather than substituting a similar record.

Check your result

The return opens the correct order and ticket, and its SKU resolves to the intended product or variation. Product-level returns analytics include the record in the expected grouping. No unrelated organization record was used to force a match.

Common problems

The order number looks correct but will not link: compare internal and external order identifiers and confirm the owning organization.

The ticket is unavailable: the Communications account may still be synchronizing, or the role may lack access.

The product name matches but the SKU does not: use SKU identity as the primary product relationship.

An import reports many unmatched rows: stop before committing the batch and correct mapping or source identifiers in preview.

Permissions and data notes

Linked modules enforce their own permissions. A Returns user may see a stored identifier without being allowed to open the related record. Do not copy private customer details into fields intended only for matching. Preserve original source identifiers for audit and troubleshooting.