gnue
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUe] Re:Proposal for ITEM package


From: Reinhard Mueller
Subject: Re: [GNUe] Re:Proposal for ITEM package
Date: Tue, 23 Nov 2004 22:06:57 +0100

Am Die, den 23.11.2004 schrieb address@hidden um 22:02:
> > > >* commodity classification (nature, cargo type, code)
> > > >* hazardous item info
> > > >* tax category / categories?
> > > >* origin country
> > >  - This is a real pain to deal with but this should also be associated
> > >    with inventories
> > 
> > Here, I don't really see how this could be different within a specific
> > item.
> 
> sales distribution channel??. think small international company that has to 
> deal
> with different laws and/or different pricing scheme (based on
> region/country/whatever) (or i didn't understand the first comment. if so
> sorry.)

Point for you here. At least some of these points can vary by country.
However, then it still shouldn't be put in the inventory, IMHO.

> > > >* sales conditions
> > >  - I'm thinking a pricing module?
> > 
> > Yes. However, many small companies work with only a single price (or at
> > least a price that holds for the vast majority of cutomers), and they
> > would possibly prefer to have *that* price in the main item record.
> > 
> 
> yeah but even if you work with a single price, there are always cases where a
> sales representative has dealt something different,  based on qty or whatever
> one can come up with. so i think price determination module as standard is
> mandatory even in small business cases.

Although I agree that it would be used very often, I'd not say
"mandatory". "mandatory" is a word I'd generally try to avoid with gnue
:-)

Thanks,
-- 
Reinhard Mueller
GNU Enterprise project
http://www.gnue.org
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No army can stop an idea whose time has come.
        -- Victor Hugo, 1802-1885

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


reply via email to

[Prev in Thread] Current Thread [Next in Thread]