Skip to content
TixFin

Trade fairs & exhibitions

Every badge printed before doors open

Batch-print the badges, give each entrance its own rules, put your exhibitors on the artefact, and hand finance an invoice they can post.

In short

How does TixFin work for trade fairs?

An exhibition is an access-control problem wearing a marketing budget. TixFin covers the access side with several active check-in lists per event — each with its own allowed pass types, extra capture fields and CSV export — so visitor, exhibitor, press and set-up passes never validate under the same rules. It covers the artefact with a badge mode in the ticket designer: A4, A5 and 10×10 cm layouts carrying name, company, ticket type, event, date, QR code and logo, exported as one complete PDF batch. Exhibitor and partner logos come from the project sponsor pool, and every order produces a ZUGFeRD invoice with a DATEV-oriented CSV export.

  • Badge batch export in A4, A5 and 10×10 cm
  • A check-in list per entrance and pass type
  • Exhibitor logos placed on the badge itself

Capabilities

What you get for an exhibition

  • 01

    Badge designer

    A badge mode in the ticket designer covering A4, A5 and 10×10 cm, with attendee name, company, ticket type, event name, date, QR code and logo on a real canvas.

  • 02

    Batch PDF export

    For an event-bound ticket type, a complete badge PDF is generated from all issued tickets — one export instead of hundreds of files.

  • 03

    Per-entrance lists

    Several active check-in lists per event, each with its own ordering, description, allowed ticket types, scan statistics and CSV export.

  • 04

    Data collected at registration

    Buyer questions per ticket type — text, textarea, select, checkbox and file — validated at purchase and stored per individual badge holder.

  • 05

    Exhibitor logos

    Sponsors are maintained in a project-wide pool and placeable in the ticket design, so a partner appears on the badge, the wallet pass and the PDF.

  • 06

    Invoices finance accepts

    ZUGFeRD 2.x XML per invoice, DATEV-oriented CSV export and reverse charge under § 13b UStG for cross-border exhibitors.

At the hall entrance

The right pass, at the right door

The scanner sends the check-in list identifier and the backend validates event assignment, active state and permitted ticket types before accepting the scan. A visitor pass at the exhibitor entrance is rejected at the door, not sorted out afterwards.

The TixFin web scanner checking a badge in at a trade fair entrance
The TixFin web scanner checking a badge in at a trade fair entrance

Challenges

What exhibitions run into

  • Badges are made the night before

    Hundreds of them, produced one at a time, from a registration list that changed twice that afternoon.

  • Not everyone enters the same way

    Exhibitors arrive during set-up, press needs its own desk, and a visitor pass must not open the exhibitor entrance.

  • Partners paid for visibility

    A sponsor logo on a web page is easy to promise. On every badge in the hall it is a placement you can actually charge for.

Key facts

Key facts for exhibitions

Badge formats
A4, A5 and 10 × 10 cm with complete batch PDF export
Badge content
Name, company, ticket type, event, date, QR code, logo, sponsor logo
Entrances
Multiple active check-in lists per event, validated server-side
Registration data
Buyer questions as TEXT, TEXTAREA, SELECT, CHECKBOX, FILE
Invoicing
ZUGFeRD 2.x plus DATEV CSV, with reverse charge under § 13b UStG

Workflow

Preparing an exhibition

  1. 01

    Define the pass types

    Create visitor, exhibitor, press and set-up types, and attach the buyer questions each one has to collect.

  2. 02

    Design the badge

    Lay out the badge in the designer, drop in the exhibitor logos from your sponsor pool and pick the format.

  3. 03

    Set up the entrances

    Give each door its own check-in list with the pass types it accepts and any field it has to record.

  4. 04

    Print and open

    Export the complete badge PDF batch, then scan visitors in and export the per-list CSV afterwards.

Features

The features behind it

FAQ

Questions from organisers

  • Yes. For an event-bound ticket type, a complete badge PDF can be exported from all issued tickets, in A4, A5 or 10 × 10 cm, with the layout you built in the badge designer.
  • Yes. Each entrance gets its own check-in list with its own allowed ticket types. The scanner sends the list identifier and the backend validates event assignment, active state and permitted types before the scan is accepted.
  • Sponsors are maintained centrally in a project-wide pool and are selectable as an element in the ticket designer, so the placement carries through to the badge, the wallet pass and the PDF.
  • Every invoice produces ZUGFeRD 2.x compliant XML, and a project-wide reverse-charge flag sets VAT to 0 %, adds the § 13b UStG note, uses CategoryCode E with an exemption reason in the XML and tags the row [RC] in the DATEV export.

Get your hall ready

Design the badge, set up the entrances and export the batch before doors open.