If you were to go the marketing package route, the box of 10 would be the marketing package and the single piece would be the product that all inventory is stored against. The ProductAssoc (type "component" I think) between the box of 10 and the piece would have a quantity of 10. Whenever the box is ordered the system would automatically create a production run which will convert 10 pieces into 1 box.
So you have a standard finished good as your lowest UOM and then each higher UOM is a marketing package with the conversion factor stored in ProductAssoc.quantity. I can't remember exactly if it is the case, but I think marketing packages are capable of deriving the selling price from the components if a ProductPrice isn't defined for it, in that way you'd only need to maintain specific prices when you need to provide a lower cost for ordering in bulk. Regards Scott On 3/10/2010, at 6:02 PM, Hans Bakker wrote: > Hi Scott, this is sure an interesting idea, but then how does the system > know that they are for example 10 pieces in a box? I still what to have > the same inventory for boxes and pieces. > We should be able to store the conversion between the uom's for this > product somewhere? > > Thanks for you input! > > Regards, > Hans > > On Sun, 2010-10-03 at 17:39 +1300, Scott Gray wrote: >> Hi Hans, >> >> Sorry if this is a silly question, but why not just use different products >> for different UOMs? You could use virtual/variants if you wanted the UOM to >> be selectable on a single product page and also marketing packages to >> automatically produce inventory for the desired UOM from the base UOM. >> >> Regards >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com >> >> On 3/10/2010, at 3:54 PM, Hans Bakker wrote: >> >>> Thank you BJ, >>> >>> I had in mind to create and 'productUomAlternatives' table to the >>> product with a conversion for example from pieces to boxes with an >>> optional price adjustment percentage. >>> The system will have however only one uom where everything gets >>> converted to. >>> >>> Anybody else other solutions? >>> >>> Regards, >>> Hans. >>> >>> >>> On Sat, 2010-10-02 at 10:21 -0700, BJ Freeman wrote: >>>> Yes also like a Feed store will have boxes, Sacks, and loose feed. >>>> I used the multiple pricing model for the Uom Measure >>>> in the product screen made it allow multiple UOM. >>>> >>>> added to the code that converts from what is received in inventory to >>>> what is sold so it walks through the Uom. for instance a feed store >>>> Receives feed in Bulk and then sacks it as inventory is required. >>>> The Inventory levels have to be checked to see how many in a product >>>> run to generate to sack up the grain. This Triggers an Seca. >>>> >>>> >>>> I think a nice touch would be that the could generates the product data >>>> to show up in orders, based on the Uoms that were generated for the >>>> products. it would follow the same model for inventory levels on the >>>> orderentry and Ecommerce >>>> >>>> >>>> Hans Bakker sent the following on 10/2/2010 4:29 AM: >>>>> A question to the community: >>>>> >>>>> sometimes the same products are sold with different units of measure. >>>>> Example gold jewelry. >>>>> >>>>> Per piece, per box of 10, per box of 50 and per gram gold weight. >>>>> >>>>> Is here a preference how to implement that? >>>>> >>>>> Remember this has to show up in e-commerce, orders, shipments and >>>>> invoices... >>>>> >>>>> Regards, >>>>> Hans >>>>> >>>> >>> >>> -- >>> Ofbiz on twitter: http://twitter.com/apache_ofbiz >>> Myself on twitter: http://twitter.com/hansbak >>> Antwebsystems.com: Quality services for competitive rates. >>> >> > > -- > Ofbiz on twitter: http://twitter.com/apache_ofbiz > Myself on twitter: http://twitter.com/hansbak > Antwebsystems.com: Quality services for competitive rates. >
smime.p7s
Description: S/MIME cryptographic signature
