Universal Container have a points-based Loyalty Program and a B2C commerce website built with a Commerce built with a Commerce Cloud solution; the…

The Transaction Journal object is the primary object in Loyalty Management for recording every loyalty activity, including point accruals from purchases. To provide traceability back to the source transaction, this object includes a standard lookup field to the Order object. By populating this standard Order lookup field on the Transaction Journal record, an administrator ensures a direct, reportable link between the loyalty points awarded and the specific B2C Commerce order that generated them, fulfilling the business requirement without custom development.

A. Use standard Order Lookup on the Loyalty Ledger object: The Loyalty Ledger object tracks a member's aggregate balance for a specific currency. It does not record individual transactions and is therefore unsuitable for tracing back to a specific order.

B. Create a custom text field in Transaction Journal object to save the order purchased by the client: Using a text field is poor design. It prevents a true relational link, complicates reporting, and risks data integrity issues. A lookup field is the correct data type.

D. Create a custom Lookup field in Transaction Journal object to save the order purchased by the Loyalty member: Creating a custom field is unnecessary and not a best practice because a standard lookup field to the Order object already exists on the Transaction Journal for this exact purpose.

1. Salesforce Object Reference Guide for TransactionJournal: The official documentation lists the standard fields for the TransactionJournal object. It includes the OrderId field, which is a standard Lookup(Order) field. This confirms the existence and intended use of the standard lookup. (See TransactionJournal fields in the Salesforce Object Reference Guide).

2. Salesforce Help - Loyalty Management Data Model: The Loyalty Management data model overview illustrates the relationship between key objects. It shows that the Transaction Journal is the central transactional record and is designed to link to source records like Order to provide a complete view of a member's activity. (See "Understand the Loyalty Management Data Model" in Salesforce Help).

3. Salesforce Loyalty Management Developer Guide - Transaction Journal: This guide describes the purpose of the TransactionJournal object as "a journal of all transactions that result in a change in a member's point balance." It further details that it can be linked to source records, with the Order object being a primary example for accrual transactions. (See "Loyalty Management Objects" section).