Within Cinchio Back Office reporting, you may come across both Transaction Count and Customer Count . There is a distinction between the two:

• Transaction Count: This is the sum of all transaction types.
• Customer Count: This is the sum of all Sale transactions less the sum of all Refund transactions. This represents the number of customers that you have served.

For example: 

These are not to be confused with Covers Count, which is either declared at the POS or is based on the number of menu items sold within the transaction.

Within Cinchio Back Office, transactions and sale items are allocated against a type.

At transaction level, these types are:

• Sale: A standard transaction, comprised of sale items and payments with a net positive value.
• Refund: A standard transaction, comprised of sale items and payments with a net negative value.
• Zero Value Sale: A transaction either comprised of:
  • Sale items at zero value, therefore no payments. (e.g. A comp or 100% discounted transaction.)
  • No sale items, but payments that offset each other. (e.g. Gift card sale paid by cash.)
• Cancelled Sale: A transaction comprised of voided sale items only. There are no payments.
• No Sale: A record of a "No Sale" entered at the POS. There are no sale items or payments.
• Other Actions: A transaction comprised of no sales, payments or voided items. Typically a date stamp of an action on the POS. 

And within each transaction, at individual sale items level these types are: 

• Sale: A sale item with a positive quantity value.
• Refund: A sale item with a negative quantity and value.
• Zero Value Sale: A sale item with a positive quantity and zero value.
• Void: A sale item with zero quantity and zero value.

Multiple Transactions

Summary level information of multiple transactions can be exported to CSV in the following areas: 

• Transaction Search Feature
• Transaction Analysis Report

Individual Transactions

Any transaction can be exported as a full detailed receipt in PDF format. 

To download a transaction PDF:

1. Access the transaction within Cinchio Back Office.
2. At the bottom of the page, select [DOWNLOAD PDF].

This will download a PDF copy of the transaction as per your browser settings.

Note that the following elements can be configured to show against a PDF receipt: 

• The company logo can be configured to show as per the Company Configuration.
• The site contact details can be configured to show as per the Site Configuration.
• A custom message can be configured to show at the bottom of the page as per Transaction Footer Notes within the Company Configuration or Site Configuration.   

Against a transaction you may see reference to payloads or webhooks. These provide information related to communication with external systems for data related to this transaction coming in or going out of Cinchio Back Office.

Transaction Payloads

A transaction payload is the raw data that Cinchio Back Office receives from the transaction source. 

This raw data contains transaction data as provided by the source, which is then converted into a standardised transaction within Cinchio Back Office.

Should you need to view a transaction payload:

1. Access the transaction within Cinchio Back Office.
2. At the bottom of the page, select [VIEW TRANSACTION PAYLOAD].

The transaction payload will open in a new tab. This is only available for 14 days after the data was received, and after this the raw data is no longer available to view.

Transaction Webhooks

A transaction webhook is a method of passing transaction data to a third party as it occurs. For example, sending to a loyalty provider or an external sales analysis tool.

In cases where transaction data has been provided via a webhook, it is possible to view the transaction webhook information and status against the transaction:

Should you need to view a transactions webhook status:

1. Access the transaction within Cinchio Back Office.
2. At the bottom of the page, select [VIEW WEBHOOKS].

The webhook status and details for all webhooks related to the transaction will show. This is only available for 14 days after the webhook was actioned.

The webhook for the individual transaction can be resent if required, by selecting [RESEND]. 

Further information for all webhooks can be seen within the Webhooks section. 

KMS Payloads

If using the Logwood KMS solution, the KMS ticket generation details for any remote order transactions are available to view 

Should you need to view a KMS ticket payload:

1. Access the transaction within Cinchio Back Office.
2. At the bottom of the page, select [VIEW KMS TICKET PAYLOAD].

For each preparation area where the KMS ticket is sent, the time that the ticket is generated is shown. Selecting the plus icon on the left then displays the raw KMS ticket data. This is only available for 14 days after the ticket was created.

Within the transaction you'll see a [Refund] button if:

• The Transaction Source support refunds and is enabled to allow refunds. (Currently this is restricted to Cinchio Kiosk, Mobile and Retail sources only.) 
• You have Delete access against Transactions within your user role. (Click Here if you do not have access.)
• The Transaction is within a recent date range. (By default this is 7 days, but can be updated at Transaction Source level to between 1 and 30 days.) 
• The Transaction only contains payment types that are eligible for Back Office refunds.
• There is no Cash Up in Counted state or higher for the current and future dates.