Due to the point of Sales (POS) system limitations, the client purchases are sent every night to Loyalty Management as transactions. What are two…

Batch Management in Salesforce Loyalty Management is specifically designed to handle the asynchronous processing of large volumes of records. In the context of receiving nightly transaction data from a POS system, its primary benefit is the ability to efficiently process these high-volume transactions against loyalty rules (B). A crucial component of this feature is the operational oversight it provides; administrators can use the Batch Jobs page to track the status, progress, and health of each job, ensuring data is processed correctly and troubleshooting any failures (A).

C. Load large volumes of external data coming from external systems: Batch Management processes records that are already loaded into Salesforce objects (e.g., Transaction Journal), it does not perform the initial data loading or extraction from external systems.

D. Process zip files full of Loyalty Transactions coming from point-of-sales systems: The native Batch Management feature processes Salesforce records, not file formats like zip files. An external process would be required to handle file extraction before data can be processed.

1. Salesforce Help, Process Transaction Journals in Batches: "Use batch jobs to process a large number of transaction journals at a time... You can track the progress of batch jobs on the Batch Jobs page in Loyalty Management. The Batch Jobs page shows the status of each job part and the number of records that are processed, have failed, or are yet to be processed." (This supports options A and B).

2. Salesforce Help, Batch Management: "Batch Management helps you process large volumes of data by using batch jobs. You can monitor the health of your batch jobs and ensure that they run successfully." (This directly confirms options A and B as key benefits).

3. Salesforce Help, Considerations for Batch Management: This page details the record processing limits (e.g., "Batch jobs can process up to 250,000 records in 24 hours"), underscoring its purpose for handling large volumes (supporting option B). It does not mention file processing capabilities (disproving option D).