> ## Documentation Index > Fetch the complete documentation index at: https://dokumentation.websale.de/llms.txt > Use this file to discover all available pages before exploring further. # New customer vouchers > Issue a voucher that only new customers can redeem for their first order, and define who counts as a new customer in the shop. A new customer voucher rewards the first order. Technically, it is a universal voucher that is given the restriction "new customers only" when it is created. The code can be distributed freely, but only someone who has not yet purchased in the shop can redeem it. The real work lies in a single question: who actually counts as a new customer in your shop? This determines whether the campaign works or whether it locks out exactly the people it is meant to reach. ## Who counts as a new customer The shop knows two definitions. You define which one applies in the configuration. | Definition | Criterion | When it fits | | - | - | - | | `NoCustomerNumber` (default) | The customer does not yet have a customer number | Shops without a connected merchandise management system, in which the customer number is only created with the first order | | `NoOrder` | There is no order for the customer yet | Shops with a merchandise management system that assigns customer numbers independently of orders | ### Why the default becomes a problem with a merchandise management system Some prospects register in the shop but do not order right away. If a merchandise management system is connected, it may already assign a customer number to the account without an order ever having taken place. With the default setting `NoCustomerNumber`, this is enough for the shop to classify the prospect as an existing customer. When they come back weeks later with their voucher, the voucher is rejected even though they have never bought anything. `NoOrder` solves exactly this case: the shop then does not check the customer number but whether an order already exists for the customer. If not, they remain a new customer and can redeem the voucher with their first order. > [!WARNING] > > Without a merchandise management system, `NoOrder` changes practically nothing; with a connected system, it is usually the only usable setting. Before starting a new customer campaign, check when the customer number is created in your setup. Once the campaign is running, only very few affected customers will get in touch. Most will abandon. > [!NOTE] > > For both definitions, the customer must be logged in. Without a login, the shop can check neither the customer number nor the order history and rejects the voucher with a notice that login is required. ## Prerequisites **The voucher generator must be activated.** If you want to use it, contact your WEBSALE representative. > [!NOTE] > > If the vouchers come from an external system and are therefore not in WEBSALE format, add the entry `ExternalVouchers-Allow = yes` in the `` section of the `shop.config`. **Voucher entry must be integrated in the shop.** If your shop does not offer vouchers yet, the input field on the basket page `ws_basket.htm` and the order overview page `ws_place_order.htm` is missing. Guide: Provide voucher entry ## Step 1: Defining the new customer definition ```ini theme={"theme":{"light":"github-light","dark":"github-dark"},"languages":{"custom":["/languages/websale.json"]}} NewCustomerDefinition = NoOrder ``` > [!NOTE] > > If the shop does not recognize the value, it uses `NoCustomerNumber`. A typo is therefore not noticed as an error but silently falls back to the default. Check the spelling. > [!WARNING] > > The setting applies to the entire shop, not per voucher or per batch. You cannot have one campaign checked by customer number and another by order history. Reference: Voucher-Txt section ## Step 2: Creating the voucher Create the voucher as a universal voucher in the voucher generator in the online service area and select the restriction to new customers there. Guide: Create or import vouchers ## Step 3: Providing the appropriate error messages A new customer voucher is rejected more often than an ordinary one, simply because the condition is narrower. Without stored texts, the customer sees an empty message and does not know why their code is not accepted. Four rejection reasons are relevant for new customer vouchers. | Reason | When it occurs | | - | - | | 9 | customer-specific voucher for new customers only, the customer is not a new customer | | 10 | customer-specific new customer voucher, the customer is not logged in | | 11 | voucher for new customers only, the customer is not a new customer | | 12 | voucher for new customers only, the customer is not logged in | > [!NOTE] > > Reasons 10 and 12 are the most important. They affect everyone who enters the code before logging in, which is the normal case in a promotional campaign. The text should therefore not just state the rejection but lead the customer to log in. Guide: Provide voucher entry, section "Placing messages" ## Related topics * Guide: Offering vouchers: Overview * Guide: Create or import vouchers * Guide: Provide voucher entry * Guide: Universal and promotional vouchers ## Related topics - [Newsletter vouchers](https://dokumentation.websale.de/en/v8s/gutscheine-anbieten/newsletter-gutscheine.md) - [Provide voucher entry](https://dokumentation.websale.de/en/v8s/gutscheine-anbieten/gutschein-eingabe-vorsehen.md) - [Prices, taxes, and currency](https://dokumentation.websale.de/en/v8s/referenz/konfigurationen/shopkonfiguration-shop-config/preise-steuern-und-waehrung.md) - [MSG- (Messages)](https://dokumentation.websale.de/en/v8s/referenz/tags/msg-meldungen.md) - [Excluding buyers with a customer discount from a voucher](https://dokumentation.websale.de/en/v8s/gutscheine-anbieten/gutschein-fuer-kaeufer-mit-kundenrabatt-ausschliessen.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.