> For the complete documentation index, see [llms.txt](https://userguide.zappost.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/zapp/using-the-zapp/sending-zaps/processing.md).

# Processing

## ZAP Processing page

To navigate to the ZAP Processing page, click the ‘processing’ icon in the header of ZAP-POST.&#x20;

<figure><img src="/files/fAqxLFhWBDIP5O1fDOcc" alt=""><figcaption></figcaption></figure>

From the ZAP processing page, you may see important information relating to each submission:\
\
\&#xNAN;**- Date Submitted** - This is the date the original submission was uploaded to the campaign\
\&#xNAN;**- Submission ID** - A unique submission ID (for future use with ZAP-API)\
\&#xNAN;**- Count of Records** - The number of records on initial upload, prior to any data cleansing results and a link to download the original submission data. \
\- **Paper Stock** - The paper being used for the submission\
\&#xNAN;**- Campaign Name** - The name of the campaign the data has been submitted against\
\- **View/Edit Design** - You can use this to amend which design a submission uses\
\&#xNAN;**- Accepted Data** - The number of accepted records following the PAF and Cleanse process\
\&#xNAN;**- Failed Cleanse Records** - Details of all records that fail the PAF and Cleanse process\
\&#xNAN;**- Zaps Created** - The number of Zaps to be printed and posted\
\&#xNAN;**- Frequency Rejected** - Details of any records that have been rejected due to the accounts frequency settings\
\&#xNAN;**- Scheduled For** - The date Zaps are due to send\
\&#xNAN;**- Invoice** - Downloadable PDF invoice with cost breakdowns\
\&#xNAN;**- Download Returns** - Provides a list of records for any Zaps that have been returned to sender\
\- **QR Code Tracking** - A report highlighting which customers scanned a QR code and when

<figure><img src="/files/Gi4quUExmtlJ0nnU38al" alt=""><figcaption></figcaption></figure>

## Downloading Original Submission Data

Users can download their original submission data by clicking the download icon in the 'Count of Records' column on the processing page

<figure><img src="/files/GFz7iyhap3DJOJ88Wb2h" alt=""><figcaption><p>Count of records with download button available for original submission data</p></figcaption></figure>

## View or Edit Design

If you've already submitted data and realised you need to change your design. You can make changes to your design, save and publish your changes and select the new design from this screen.

Click on the View/Edit Design icon and select 'Change Design'

<figure><img src="/files/3Zf0zbpc9Qq54Frpy8c1" alt=""><figcaption></figcaption></figure>

You'll then be prompted to select a new front and back panel.

<figure><img src="/files/iSyHG0oRV3yStO7gEN4R" alt=""><figcaption></figcaption></figure>

Once you've selected your new design, you'll be able to specify which submission(s) you would like to update.

<figure><img src="/files/GN1rpgXK2g9ogqIbMKHf" alt=""><figcaption></figcaption></figure>

Once you've selected which submission is updated, click 'Save and Exit'


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://userguide.zappost.com/zap-post-web-app/zap-post-user-guide/zapp/using-the-zapp/sending-zaps/processing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
