Skip to main content

pypi python mit

InvenTree Lectronz

This InvenTree plugin integrates the Lectronz marketplace into InvenTree.

Features

  • Automatic order synchronization
    For each new Lectronz order the plugin will automatically create a InvenTree Sales Order.
  • Automatic order fulfillment
    Lectronz orders will be automatically fulfilled if you complete a Sales Order Shipment.
  • Automatic stock synchronization
    Not possible yet, see lektronz-marketplace#33.

Installation

Available via pypi: inventree-lectronz

  1. Install the plugin according to the Plugin Installation Instructions.
  2. The plugin requires Schedule, Event, URL, Navigation and App integrations to function correctly. Enable all these integrations under Settings -> Plugins.

Usage

Initial Setup

Navigate to the plugin settings under Settings -> Marketplace Integration - Lectronz and enter your Lectronz API Token. Also set the Lectronz Company to the company which acts as the customer for all Lectronz orders.

Linking Products

For proper stock tracking you will have to link a Salable InvenTree Part to each of your Lectronz Products.

  1. Go to the Part page in Inventree.
    (There should be a new Lectronz Product Panel (this will only show up if the Part is marked Salable.)
  2. Select the Lectronz Product (and any product options) you want to link the Part to.

Example:

Example of the Lectronz Product Panel

Note: Unlinked products will still appear in your Sales Orders, but you won't be able to allocate Stock to them. You can link a product later and update the Sales Order though.

Fulfilling Orders

Lectronz Orders will be automatically fulfilled once you complete a Shipment for a Sales Order.

Note: If the order requires a tracking number you have to provide it in the Shipment information. (You can optionally also include a tracking link).

Example:

Example of a Shipment which will automatically fulfill an order

Credits

  • InvenTree (@SchrodingersGat and @matmair)
    This project wouldn't exist without their brilliant work on creating the awesome open-source inventory management solution.

  • Lectronz (@omzlo)
    The marketplace for makers and open-source hardware.

License

  • This project is licensed under the MIT license.

Metadata

Release files for inventree-lectronz 1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for inventree-lectronz 1.1
File Size Uploaded Provenance Actions
inventree_lectronz-1.1.tar.gz 210.2 kB With provenance Details for inventree_lectronz-1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for inventree-lectronz 1.1
File Interpreter ABI Platform Actions
inventree_lectronz-1.1-py3-none-any.whl Python 3 none any Details for inventree_lectronz-1.1-py3-none-any.whl

Total release size: 226.1 kB

Release files / inventree_lectronz-1.1.tar.gz

Download URL inventree_lectronz-1.1.tar.gz
Size 210.2 kB
Tags Source
SHA-256 checksum
How to use checksums
ebe25a14b36fb9d628473f4e25e11585d6a54ba3d5868f3e28fb54ce7552e6f6
BLAKE2b-256 checksum
How to use checksums
a275e8dfd85b8ef5fb5bd9a225a2e59901a8a9ba4e4c531ec97026e76ef5e745
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

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 Dec 23, 2024.

Transparency log

Release files / inventree_lectronz-1.1-py3-none-any.whl

Download URL inventree_lectronz-1.1-py3-none-any.whl
Size 15.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ff7e90b86e46a64275acbccf5071ed9a52f8979e766dcdfc808444b3ab66393a
BLAKE2b-256 checksum
How to use checksums
1410468e9fdc615910c95bc390d054a902401063dfa96273bb046dcfa058d49b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.0.1 CPython/3.12.8

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 Dec 23, 2024.

Transparency log

Security for inventree-lectronz 1.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

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for inventree_lectronz-1.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 Dec 23, 2024.

Transparency log

A 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.1 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page