Improvements for Shipments

Open
#9,671 9 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
django, python
Domain
backend

Research direction

The payload names no files or tests. Start by reading the linked discussion #9669 and the nine-comment thread here to see which of the four proposals maintainers accepted. Scope is still open: a global shipment entity, a shipment-method field, tracking links and barcode-driven plugins are separate design questions. Done means a maintainer-agreed design, not a patch, so ask before coding.

Written by the indexing model from the issue text.

Description

api enhancement migration order refactor User Interface
Discussed in https://github.com/inventree/InvenTree/discussions/9669

Originally posted by zsoden May 17, 2025
Hi all,

Firstly let me say just how impressive Inventree is. The developers have done a truly fantastic job thus far!

I own a small electronics manufacturing business and we're currently evaluating Inventree as an upgrade from our existing, limited, self-made system. Thus far it's really promising: we can customise Inventree to cover most requirements and will build a plugin or two for some additional functionality (most notable is the ability to take a photo of stock using a webcam during receipt of the stock).

A lot of the items on our list of limitations from the evaluation thus far has been related to the shipments functionality. If I've misunderstood any of the existing functionality please let me know!

  1. We find it typical that a shipment to a customer contains product from multiple customer POs (so multiple Sales Orders in Inventree). It seems that the shipments system has been designed as a subset of the sales orders but in my mind the shipments should be split out into a separate functionality (i.e. another page under the Sales menu). Each shipment would have a globally unique ID, instead of the ID that is unique within the Sales Order. So when a Sales Order line is shipped you have the option of using an existing shipment that could have been created in another Sales Order.
  2. A shipment needs to have a "shipment method" field, which is a list of items such as
  • Customer collect
  • Standard Post
  • Express Post
  • Fedex TNT
  1. Point 2 combined with the tracking number can be used to create a link to the tracking from the shipment page. We've found this immensely useful in our existing system.
  2. We've found that it's typically possible to determine the shipment method simply by scanning the corresponding barcode on the TNT address label or Express Post bag. So the ideal workflow is to simply scan the barcode and have the system automatically select the shipment method. It probably makes the most sense for this to be a plugin, since it's very custom behaviour.

Depending on how difficult it is I'd be happy to have one of my developers contribute to this functionality.

Edit: One other advantage of shipments handled separately that I forgot to add is that they could have Extra Line Items for those things that you would like to add to a shipment packing list but don't want to create a part for (i.e. we're sending the customer a sample of a non-stock item).

Dominant language
Python
Stars
7.7k
Forks
1.6k
Avg merge
21h 45m
Merged PRs (30d)
204

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from inventree/InvenTree

All issues in inventree/InvenTree

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.