Stock packages and pallet


We are doing some tests on shipment_out with stock_package modules (stock_package, stock_package_shipping, stock_shipment_measurements).

When doing shipment_out, we are using pallets to put our packages on it.

Is pallet considered as a package ? Is there a specific module for pallet (custom) ?
Packages in Tryton are considered as containers then pallet is not really a package but we need to use it for shipment_out with details about it (number, dimensions, …) like for packages.

Because if pallet is considered as a package in Tryton (which would be a good thing), then we need to give some extra details (length, width, height) for shipment. PackageType has such details but you never know dimensions of the packages on the pallet (it depends the way they are putted on it).

What do you think of adding fields such length, height and width on Package model ? By default those fields will have values from PackageType, but in case of package like pallet they should be updated manually when order is packed on the pallet and user measure correct dimensions.

Thanks for suggestions!

1 Like

There is the stock_location_move module which should be used as a pallet that can be moved inside of the warehouse. The idea is that once you receive a pallet, you create a new location and put all the received produts on it. Then you can move the location (aka pallet) and all the products of this location will be moved to the location. If you remove products from the pallet you use the movable location (aka pallet) as source of the move. If you add just use it as destination.

But this is only usefull if you want to manage the movement of pallets inside the warehouse.
If you want to track the pallets that are sent to the customer (or carrier) then you should consider using packages by creating a type of carrier.

Do you think it can computed someway? Or it should be always defined manually?

Maybe we can add a “variable” checkbox on the package type which allows to define a measure on the package. Does this it make sense for you?

We are in the case to track pallets sent to the customer. We are taking a pallet, putting products from different locations in packages and then putting them on the pallet.

Each pallet is different (different packages, the number of packages, the way they are positioned,…), so for me is should be always defined manually (maybe we could consider the width and the length by default).

Could be a solution :slight_smile:

But we should have some constraints on it. For example if we have a package of 50cm height on a pallet it should not be possible to set the pallet height to less that 50cm.

And also we should define somewhere which mesaures are required to be entered by the user to be able to sent the package. Otherwise we can end up with packages without measures

Indeed, but once again it depends on how the package is placed on the palet (i mean your package could have an height of 50cm, a length of 80cm… if the user put the package vertically on the pallet, the height is now 80cm…)

I think all measures should be required. And by default, package will have measures of package_type. Or you define on package_type, which measure is required by type…

So indeed for a pallet only the height is unknown (there are probably a maximum).
I think the best would be to add dimensions on the package type and leave empty those that are “dynamic”. In case a package has a type with dynamic dimension, it shows a field to enter it.
There maybe some configuration to make a dimension required or not per type.

1 Like

1 Like