Overview
The Next Gen Receipt Scanning (NGRS) feature supports Multi-Template client configurations. As receipts and orders enter the system with a Multi-Template configuration, the system tracks the multi-template ID and routes the data to the appropriate instance for processing.
NGRS Database Tables
The following database tables include a multi-template_id column to allow the NGRS feature to manage receipts under multi-template.
- s15_v3_receipt_submission_settings
- s15_v3_receipt_upload_widget_settings
- s15_v3_receipt_product_master
- s15_v3_receipt_submission_product_association
- s15_v3_receipt_store_master
- s15_v3_receipt_submission
- s15_v3_receipt_submission_data
- s15_v3_receipt_audit_trail
- s15_v3_receipt_product_details
Reporting
When a site has the Multi-Template toggle set to ON, the Multi-Template ID column appears in Loyalty reports. (The examples below are not a complete list.)
iFrame
In a Multi-Template instance, iFrame URLs use the multi_template_id value to display the appropriate values for the member.
Order API
In a multi-template instance, the Order API request can include the multi_template_id in the request header. Here are examples of this from Postman.
