Django Vendor
Django App Toolkit for selling digital and physical goods online.
The philosophy is "Cart to Receipt". What you put in the cart and what you do after the purchase is up to you. The app is opinionated within scope.
Goals of the project:
- Drop in to existing Django Sites without requiring changes to how Django works (flow, not fight)
- Handle everything from the point of starting a purchase, until payment is complete.
- BYOPM, Bring Your Own Product Model. Subclass your Product Model off of our base model and add whatever you want. You are responsible for things like Catalogs and Presenting products to the user, we handle the purchasing of the products and generate a receipt you can look for.
Docs
The docs can be found here: Documentation
For Developers
NOTE: It is reconmended that you first setup a virtual environment.
To install the project, all you need to do is check out the project and run the following to install all the dependencies:
pip install -e .
For developers, you'll need to also include a couple of dependencies that are only used in develop mode. Run this from the root level of the project.
pip install -e .'[dev]'
If you are working with Authirize.net you will need to run this:
pip install -e .'[authorizenet]'
If you are working with Stripe you will need to install this.
pip install -e .'[stripe]'
To run the project, go into the 'develop' folder:
To setup the models:
./manage.py migrate
Create the Super user
./manage.py createsuperuser
Then load the developer fixture if you want to pre-populate the cart & catalog
./manage.py loaddata developer
To run the project:
./manage.py runserver
to dump unit test data
./manage.py dumpdata --indent 4 auth.group --natural-foreign --natural-primary > fixtures/group.json
./manage.py dumpdata --indent 4 auth.user --natural-foreign > fixtures/user.json
./manage.py dumpdata --indent 4 -e contenttypes -e auth.permission -e sessions -e admin.logentry -e account.emailaddress -e auth.group -e auth.user > fixtures/unit_test.json
The install process
- Add the app to your project
- Create your Product model that inherits from the ProductModelBase base class.
- Change the settings.py value for VENDOR_PRODUCT_MODEL to point to your model
- Make migrations
- Migrate
1 maintainer
Release files for django-vendor 0.8.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 | |
|---|---|---|---|
| django_vendor-0.8.1.tar.gz | 125.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_vendor-0.8.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 293.7 kB
Release files / django_vendor-0.8.1.tar.gz
| Download URL | django_vendor-0.8.1.tar.gz |
|---|---|
| Size | 125.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
271ced4ed9d5430e7a2bedf2dce5e3b056caed345bc902c80b9f7ecbb007a0a9
|
|
BLAKE2b-256 checksum How to use checksums |
3e80baf9e5f40b1262b0501bf6632fbd9275bfc3187ef421ed6723dec08e3ffd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 28, 2026.
Transparency logRelease files / django_vendor-0.8.1-py3-none-any.whl
| Download URL | django_vendor-0.8.1-py3-none-any.whl |
|---|---|
| Size | 168.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e67a282a0f134557afe47f98e03ef7630656ed5d5aab410873aead1c1c5cf0f
|
|
BLAKE2b-256 checksum How to use checksums |
89027e87fd23007a5ce17db486cc7c10edba77d97d78ba8a42a4bd16e18dde61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Apr 28, 2026.
Transparency log
