> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.navipartner.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.navipartner.com/_mcp/server.

# Configure products for Entria

> Set up memberships, subscriptions, vouchers, coupons, tickets, and Attraction Wallets for the Ecommerce flow.

Configure the product types you plan to sell through Entria. Each section below describes the required setup and checks for Ecommerce processing. Complete only the sections relevant to your business. For packages containing multiple product types, complete the setup for each included type.

## Memberships

Prepare the Member community, Membership Setup, and Membership Sales Setup so that the sales item is linked to the appropriate membership. For standard setup, follow [<ins>Membership Setup</ins>](/product/attraction/membership/reference/membership-setup2) and [<ins>Membership Sales Setup</ins>](/product/attraction/membership/reference/membership-sales-setup).

For the Ecommerce flow:

1. Verify that the item number from the order exists in Membership Sales Setup.
2. Verify required member information, the activation date, and the date of birth if age validation is used.
3. Configure **Configure Membership Processing Job Queue**.
4. On a test Ecommerce document, verify the Membership line subtype and the created membership through **Memberships**.

## Subscriptions

A subscription requires a membership, renewal rules, and a payment method that supports recurring payments. For the basic renewal rules, use [<ins>Set up auto-renewal process</ins>](/product/Attraction-membership-autorenewal); that reference covers memberships, while the following requirements are specific to the current Ecommerce flow.

1. Configure the membership and its renewal according to the business model.
2. Open **Subscription Payment Gateways**, configure the code, integration type, and status, then select **Show Setup Card**. For Adyen, the Subscriptions Payment Gateway Adyen Setup Card uses **Merchant Name**, **Environment**, **API URL Prefix**, and **API Key**, together with **Payment Account Type** and **Payment Account No.** For Pay by Link, also check **Pay By Link Exp. Duration** and **Recurring Processing Model**. Verify renewal jobs; the Ecommerce membership creation job does not replace jobs used for later renewals.
3. For monitoring, use **Subscription List**, **Subscription Request List**, and **Subscription Payment Request List**.

Missing email or the required payment data blocks further document processing. Enabling the Subscription field alone does not provide renewal capture.

## Vouchers

Prepare Retail Voucher Types according to [<ins>Voucher types</ins>](/product/retail-vouchers-voucher-types). Check issuance, validity, application method, and the appropriate posting setup.

Distinguish between two operations:

* **Selling a voucher**: On Ecommerce Setup, run **Configure Voucher Processing Job Queue** and verify the issued voucher through **Vouchers** on the Ecommerce document.
* **Paying with a voucher**: the payment line contains the existing voucher code in `data.voucher_code`. Verify that the voucher exists, has sufficient available balance, and uses PARTIAL as its Apply Payment Module. The reservation amount is maintained in local currency.

Set **Apply Payment Module** to `PARTIAL` for all voucher types sold or accepted as payment through Entria.

Use testing to verify issuance of a new voucher and, separately, payment with an existing voucher. For digital delivery, check the template and voucher exclusion from the manifest in [<ins>Digital Notifications</ins>](/product/ecommerce-entria-setup-guide-digital-notifications). The basic overview is available in [<ins>Retail voucher overview</ins>](/product/retail-vouchers-intro).

## Coupons

Create and enable the relevant coupon type and configure its issuance and discount rules according to [<ins>Discount coupon setup</ins>](/product/retail-coupons-discount-coupon-usecases).

Set **Issue Coupon Module** to one of the two supported values:

| Issue Coupon Module  | Use                                                                                                                                                              |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ON-ECOM-SALE         | For coupons issued through Ecommerce sales.                                                                                                                      |
| ON-ATTRACTION-WALLET | For coupons included in an Attraction Wallet package. Configure the wallet coupon issuance setup. These coupon lines must belong to an Attraction Wallet bundle. |

Other issuance modules are rejected by Ecommerce coupon processing.

* Check **Reference No. Pattern** on the coupon type.
* On Ecommerce Setup, run **Configure Coupon Processing Job Queue**.

On a test order, verify the Coupon subtype, payment status, and issued coupons through **Coupons**. Issuance requires the line to be paid and not already processed. Use digital notifications and the appropriate design to deliver the issued coupon.

## Tickets

Configure tickets, ticket types, availability, and reservations according to [<ins>Ticket Module overview</ins>](/product/Attraction-ticket-intro).

For the Ecommerce flow, verify that:

1. The item has the appropriate Ticket Type and ticket setup.
2. An order that uses a reservation carries the correct reservation token and reservation-line identifiers.
3. **Configure Ticket Processing Job Queue** has been configured.
4. The ticket design is linked according to [<ins>Use the NP Designer</ins>](/product/Attraction-ticket-ticket-designer).

If you already use a separate ticket email, align it with **Exclude Tickets From Manifest** in [<ins>Digital Notifications</ins>](/product/ecommerce-entria-setup-guide-digital-notifications) to avoid duplicate delivery.

## Attraction Wallets

Attraction Wallet groups the digital products in a package. For an item that creates a wallet:

1. On the item card, under **NP Attraction**, enable **Create Attraction Wallet**.
2. On the item card, link **Item AddOn No.** to the relevant record; the target opens as **Package Template Card**. Check **Enabled**, the Package Template flag, lines, quantities, and **Add To Wallet**.
3. Configure **Design Layout Label** for the digital representation if you use it.
4. Verify that the incoming order contains the correct parent and child package lines. The BC template by itself does not prove that the incoming order sent the correct package content.
5. Configure **Configure Wallet Processing Job Queue** and the jobs for every product type contained in the package.
6. Verify **Attraction Wallets**, package contents, and the digital representation on a test order.

When child lines carry the price, the parent line may have a zero amount. Check the total amount and verify that neither products nor payment are duplicated. For design, use [<ins>Use the NP Designer</ins>](/product/Attraction-ticket-ticket-designer).