may not help but I remember something last year about setting the
inventory to Y and N making a difference.
about the time the drop shipper code was put in.
don't have time to go dig it out


madppiper sent the following on 6/9/2009 12:07 AM:
> Digging deeper into the logic, i got the following setup that perhaps helps
> to demonstrate the problem i got: 
> 
> I created a virtual product with
>       
> salesDiscWhenNotAvail ="Y"
> requireInventory="N"
> taxable="Y"
> chargeShipping="N"
> autoCreateKeywords="Y" 
> isVirtual="Y"
> isVariant="N"
> productTypeId="FINISHED_GOOD" 
>       
> and added a set of variant products to it, each differing in size and color. 
> 
> I now got a parent product (complete with productId) and differing physical
> products that are pointing towards this parent. Our warehouse reports to us
> the QOT of all the physical items, that way we have all of the physical
> items with an inventory > 0 and the virtual product (or parent item) with an
> inventory = 0. I am now trying to display only the virtual products to a
> customer where the inventory of their physical items in total is > 0. In
> addition, I want to allow the user to shop this very item, as long as there
> are variants available. However, on my ecommerce application I am receiving
> an error for such items, as long as I don't set "requireInventory" to "N"
> (which doesn't really make sense to me, as a virtual product should, by
> definition, never even have an inventory - at least thats how i understand
> the product page in the docs).
> 
> How can I solve this issue without a draining performance loss? (I know that
> I could use the getProductInventoryAvailableFromAssocProducts service, but
> that requires another delegator call previous to the service itself and
> seems rather slow at the whole) 
>                               
> 
> 
> madppiper wrote:
>> Heya,
>>
>> I noticed that I am receiving a "not available" message on the ecommerce
>> platform for a virtual product if it doesn't have a sufficient QOT.
>> However, any ProductAssoc associated with this product has a QOT > 0, so
>> there really shouldn't be a problem as the user buys one of the assocs not
>> the virtual product itself (just as with the Giant Widget - the user
>> should be able to purchase the giant-widget-b3 variant even if the
>> giant-widget has nothing on stock). 
>>
>> Is this a common problem or is there an easy fix to this?
>>
>> Cheers,
>> Paul
>>
> 

-- 
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.

Reply via email to