[ic] Large IC site and precise photo representation

Paul Jordan interchange-users@icdevgroup.org
Tue Oct 8 13:04:01 2002


> This is more directed to the larger IC sites, but basically, do you
> receive a lot of grief for not having a precise photographic
> representation for each of your products?  Asked differently, if you
> have tens of thousands of products, do you actually have a unique and
> specific photo for each of those and if not, how have you managed to
> avoid the flack of folks complaining about it not being 'precisely' the
> same?
>
> We sell electronic components and out of the dozen of extremely positive
> customer comments we have received, we had one person whine about the
> fact that the connectors on the picture didn't actually match the
> product specification.  Obviously the owner is reacting to the one
> single comment rather than the volume of positive ones, but
> realistically we cannot possibly photograph, photo-edit, and place
> images for 22,000 parts.
>
> Any thoughts or comments?
>
> Barry

Hi

we have a content site, with tens of thousands of images in pre-process
stage. In short, there are two answers. One, an obvious disclaimer on
flypage, basket, and mail_receipt.

However an actual picture is not out of the question. If your products don't
change (physically, asthetically) too often. A cheap digital camera with
macro lens attachment will easily take web-rez pics in a hurry. Photoshop 7
has a whole slew of automation to take advantage of using Actions,
javascript, Applescript, and Visual Basic.

We simply name our images the SKU of the item. So database editing/entry of
path/to/image is no longer needed.

we call it with <img src="__ITEM_DIR__/[item-code].jpg">

We set up "variables and directories" for all types of images (__LOGO_DIR__
__ELEMENT_DIR__ __THUMB_DIR__)


If the sales warrant the upgrade in customer satisfaction, and the products
don't change appearance but once in a while, then I don't think 22,000 is
that big of a problem. If they do change appearance, then go with the
disclaimer :)

HTH

Paul