Instead of messing around with it, I would just have just one standard part number called PACKAGE or something, if you don’t care about distinguishing between what’s in said boxes - as far as ofbiz and the business is concerned, you’re taking in and reselling just one unique widget (a package).
Ofbiz tracks individual inventory items, but they need a master product to be associated with for the data model to work. In your eyes though maybe you would have different service/priority levels levels for the packages, and in that case you could have a catalog part number for each service level. You may also have part numbers for your auxiliary stuff, pallets, tape, wrap, assets (forklifts, trailers, etc for asset tracking purposes). --Paul ---------- Paul Mandeltort | Marco Specialties Inc +1-512-394-8119 | [email protected] On May 31, 2014, at 11:50 AM, Jim S <[email protected]> wrote: > Okay ... but we just receive the packages and don't pick and pack items of > our own. We only need to transfer the packages received from a client to > the customer. > > Even the shipping logistics like UPS when they ship a package to a customer > they only have information about the shipping party (client), ship to party > (customer), number of packages, type of package, weight, dimension of the > package. In turn UPS provide a unique shipping digest and tracking number > for the package so that client/customer can track the shipment. > > Certainly as a logistics we don't need to know the part number of the items > in the package and this information is only internal to the client. I think > the way ofbiz works is when you receive a package or inventory you must > have the product ID for the item in the system, right? so I guess the > process you described won't work. > > Thanks, > Jim
