Registration ID
This is a plugin for pretix.
Adds an automatic, sequential registration ID (1, 2, 3, …) to orders. The ID is shown on the order page in the backend and to the customer.
Configure it under Settings → Registration ID in your event:
Select the products that should get a registration ID. Orders that contain none of them don’t get one.
Choose when the ID is assigned: when the order is placed, approved or paid. You can additionally have it assigned when an order is changed.
Nothing is assigned until at least one product and a moment to assign it are selected. Orders placed before the plugin was configured don’t get a registration ID retroactively.
REST API
Look up an order by its registration ID:
GET /api/v1/organizers/<organizer>/events/<event>/regid/<registration ID>/
The response is the same as pretix’s GET .../orders/<code>/ (including positions with their question answers), with an additional regid field. The include and exclude query parameters of the order endpoint work here too. It requires the “view orders” permission and works with team API tokens, OAuth and devices with full device access. Devices with a pretixSCAN security profile are not allowed to use it.
To install: pip3 install pretix-regid && python3 -m pretix migrate && python3 -m pretix rebuild && service pretix-web restart
Then just activate it in your event config.
Development setup
Make sure that you have a working pretix development setup.
Clone this repository.
Activate the virtual environment you use for pretix development.
Execute pip3 install -e . within this directory to register this application with pretix’s plugin registry.
Execute make within this directory to compile translations.
Restart your local pretix server. You can now use the plugin from this repository for your events by enabling it in the ‘plugins’ tab in the settings.
This plugin has CI set up to enforce a few code style rules. To check locally, you need these packages installed:
pip install flake8 isort black docformatter
To check your plugin for rule violations, run:
docformatter --check -r . black --check . isort -c . flake8 .
You can auto-fix some of these issues by running:
docformatter -r . isort . black .
To automatically check for these issues before you commit, you can run .install-hooks.
License
Copyright 2022 Christiaan de Die le Clercq (techwolf12)
Released under the terms of the Apache License 2.0
1 maintainer
Metadata
1 maintainer
Release files for pretix-regid 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pretix_regid-0.2.1.tar.gz | 14.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pretix_regid-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.8 kB
Release files / pretix_regid-0.2.1.tar.gz
| Download URL | pretix_regid-0.2.1.tar.gz |
|---|---|
| Size | 14.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ab24ecc1471a3feba7a86f84886eab97404e289bf62280f8dda63e9ed10ebc0
|
|
BLAKE2b-256 checksum How to use checksums |
ccf5cd260bea6a6f2c054cfb359e3d70976f6ed73690832f7ffd309704b4de7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logRelease files / pretix_regid-0.2.1-py3-none-any.whl
| Download URL | pretix_regid-0.2.1-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8ae78a606aea427f3bf0511d37efda2810f2e4e4436af124471653900eb672ba
|
|
BLAKE2b-256 checksum How to use checksums |
fd175ad935ca93bd2da579590b66bac4338e199118f6eeb52c81c6332f16a2af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logSecurity for pretix-regid 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pretix_regid-0.2.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
