> For the complete documentation index, see [llms.txt](https://kylin-inc.gitbook.io/spider-browser/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kylin-inc.gitbook.io/spider-browser/other-modules/configure-pre-sale-code.md).

# Configure Pre-sale Code

Configure pre-sale Code General Guide

## Priority Purchase Release

In the sales of some websites, the same sale will have advance priority purchase sales. It is necessary to fill in different information such as special code/account number/email/credit card to obtain the qualifications for priority purchase. Such sales need to be configured in advance. code.

## How To Configure Pre-sale Code General Guide

Under the wallet page, click "+" on the upper right to add a pre-sale code group, as shown in the figure:

<figure><img src="https://3214566683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBZkiP2ldvswDru47aqM%2Fuploads%2FkaVJHpqSsLbCSnriGKQ9%2Fimage.png?alt=media&amp;token=4c45926f-7360-4a9f-8f24-4d48cb53b08b" alt=""><figcaption></figcaption></figure>

After the creation is completed, under this group, click "+" at the bottom, and within this group, add the specific pre-sale code, as shown in the figure:

<figure><img src="https://3214566683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBZkiP2ldvswDru47aqM%2Fuploads%2F9khUiubXkKQxjtccTZyk%2Fimage.png?alt=media&amp;token=c1a5075b-842f-46cb-93d9-f70cd6890f47" alt=""><figcaption></figcaption></figure>

Then add the pre-sale code. The general format for adding pre-sale codes is code:email, one per line. The first field is in the front, and the second field is in the back. Different websites have different pre-sale codes, and they need to be configured according to actual needs. as the picture shows:

<figure><img src="https://3214566683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBZkiP2ldvswDru47aqM%2Fuploads%2F2liTLKQFVW3tm69BXJi8%2Fimage.png?alt=media&amp;token=ada62dc6-b6c4-4f6a-8134-d311eb33c609" alt=""><figcaption></figcaption></figure>

Click Save, the code is saved successfully, and then manually edit to change the status of the code to "GOOD".

<figure><img src="https://3214566683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBZkiP2ldvswDru47aqM%2Fuploads%2F0u6STcgLzTOmDnzNECZg%2Fimage.png?alt=media&amp;token=83e7dde0-62c2-452c-a062-baf2276846b5" alt=""><figcaption></figcaption></figure>

When creating the corresponding website task, if it is a release purchased first, you need to configure the corresponding pre-sale code in the pre-sale code group in the creation task, as shown in the figure.

<figure><img src="https://3214566683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDBZkiP2ldvswDru47aqM%2Fuploads%2FmHqk9dro8ozodAoewtJZ%2Fimage.png?alt=media&amp;token=beeb47e5-4e37-4f41-a837-30c22e151ea4" alt=""><figcaption></figcaption></figure>

## Pre-sale Code Description

Different websites have different forms of pre-sale codes. The configuration format of the pre-sale codes is: First field: Second field

code:email&#x20;

The email part is in the second field, and other account names or card numbers are configured in the first field.

* Account name: Configure the account name, for example: ABC123:
* Email: configure the email name, for example: <12345abc@gmail.com>
* First 6 digits of credit card number: directly configure the first 6 digits of credit card number, for example: 465742
* &#x20;Code and email: Configuration code: Email, for example: ABC123:<12345abc@gmail.com>
* Random code + number: direct configuration, for example: abc12345

## Tips

* Different releases have different pre-sale code forms. You need to confirm the pre-sale code content of the specific release before configuring it correctly.
* After saving the pre-sale code, you need to manually change the status to GOOD before it can be used normally.