We have a requirement where a customer wants to have separate price
lists for each Account in their B2B Commerce Server application. I
believe that this is a pretty standard requirement for B2B, and was
wondering what would be the best architectural approach.

My initial thoughts would be to use Virtual Catalogue, as this customer
has around 100 accounts this could mean the management and maintenance
of 100 virtual catalogues.

Anybody out there done anything similar? How did you implement it?

What pitfalls have you found in your solution?

Thanks for your help in advance.

[ Post a follow-up to this message ]

It really depends upon your business requirements (products, pricing,
discount, etc.) and the complexity of your catalog schema. If every customer
will have the same basic products (or a subset /superset of those products)
with different pricing, then the virtual catalog works great. It really cuts
down on the maintence aspect. If every customer has different products, then
I prefer to create customer specific base catalogs. Again, it really depends
upon your business requirements.

--
Jeff Lynch
MVP Windows Server System - Commerce Server
http://codebetter.com/blogs/jeff.lynch


<gdarkin@gmail.com> wrote in message
news:1155746086.879705.313440@75g2000cwc.googlegroups.com...
> We have a requirement where a customer wants to have separate price
> lists for each Account in their B2B Commerce Server application. I
> believe that this is a pretty standard requirement for B2B, and was
> wondering what would be the best architectural approach.
>
> My initial thoughts would be to use Virtual Catalogue, as this customer
> has around 100 accounts this could mean the management and maintenance
> of 100 virtual catalogues.
>
> Anybody out there done anything similar? How did you implement it?
>
> What pitfalls have you found in your solution?
>
> Thanks for your help in advance.
>

[ Post a follow-up to this message ]