At 12:07 AM 4/16/2005 +0000, you wrote:
>I live in the USA, and am currently working on designing an electronic
>device for a client in Sweden.  I will soon have a prototype ready to
>ship to him, and I'm wondering what is the proper way to fill out the
>customs declaration form.  I assume "prototype electronic device" is
>sufficient for the description,

That assumption is probably true for one piece of a prototype, but
it would be better if you categorized it by explaining what it is
a part for/of and specify that it is "not for sale" or "unsuitable for
sale" to avoid other possible problems. Also mark it "made in USA".
The value and those two bits of information are what is needed to
fill the spaces in the entry form.
If you can specify the harmonized code (see the US government list
USITC Publication 3745) for the end product, all the better.
Especially if the value you use is high.

Shipments *to* the US can run into issues with FCC approvals unless
you provide a signed waiver to the courier (apparently they have
gotten bitten), and perhaps Europe is the same with CE or whatever.
Making it clear that it's a one-off for evaluation reduces the risk of
that, and running afoul of zillions of other regulations such as
"country of origin" markings, other safety standards, and so on.
I understand enforcement (and interpretation) is country-specific.

>but what do I use for the declared
>value?  The amount I'm charging him for development?  The cost of the
>parts for the prototype?  $1?
>         Jason Harper

Minimizing the price on the customs declaration (within reason)
minimizes the hassles. OTOH, if it disappears, it limits what the
insurance would pay. I usually go with some nominal amount that
would look reasonable to a customs guy/gal (not $1 but maybe $10, $20 or
$100). In a sense, the market value is really *less* than the parts that
went into it, since usually the prototype cannot/will not be sold and the
parts are "used". Using zero or $1 for the value can raise red flags, since
it obviously (to them) has *some* value.

You should not include development costs.

BTW, suggest you ask your client what to use, and do that unless it
strikes you as not truthful enough. For something like this, there is a
LOT of reasonable range.

>Best regards,

Spehro Pefhany --"it's the network..."            "The Journey is the reward"
RemoveMEspeffspamBeGonespaminterlog.com             Info for manufacturers: http://www.trexon.com
Embedded software/hardware/analog  Info for designers:  http://www.speff.com

month overview.

new search...