TIP: Click on subject to list as thread! ANSI
echo: home_office
to: BOB F HOWARD
from: RT POLLOCK
date: 1997-01-25 18:27:00
subject: @ sign

 BFH> I just had a mass confusion situation with this @ that caused some
 BFH> real problems. I read it as "at" in computer lingo, but as "each" in
 BFH> commercial use.
 BFH> It made a big problem for me on an order. What is the proper way to
 BFH> express it for commerical purposes?
I don't know about others, but when I generate a purchase order, I
_plainly_ specify the quantity I need. Example:
     QTY.               DESCRIPTION                  UNIT        EXT.
    1 pce           Model KSC keyboard              15.00       15.00
  500 pces          27K, 1.2W, carbon resistors       .07/pc    35.00
    3 pkgs          BNC, Male, cable, Mil-Spec      10.12/pkg   30.36
    1 reel          RG-8/U coax, Type "S", 1k ft.     .50/ft   500.00
                                 Sub-Total                     580.36
                                     S&H                       EXEMPT
                                     PST (8%)                  EXEMPT
                                     GST (7%)                   23.57
                                Grand Total                    603.93
In the event that I've pre-ordered by telephone (voice or fax), I'll
rubber-stamp the form as a "CONFIRMATION" so as to avoid order dups.
Plus, I'll reference the sales or CSR's name that I ordered from. If I'm
entitled to any discounts or I'm applying an order against specially-
advertised ("on sale") goods, I'll note this before any taxes and
shipping charges. I also always specify "no back-orders or substututes"
on my orders: if a supplier can't give me what I need, then I always have
my "secondary sources" to buy from or I can generate a new P.O. at any
time later, including the stuff that was missed. (Helps keeps the Books
straight here...)
By using common designators to indicate quantities, and further
providing backup with the use of the "UNIT" column, I ensure that what I
want is what I get the first time around. By doing this, I further
ensure that my purchase order is correct, and that any deviations on
errant suppliers's invoices become THEIR responsibilities to suffer the
cost(s) for corrective actions. Rarely do I use symbols _unless_ I hold
a firm understanding of what it is in English that they are meant to
replace (or supplant). I think that my policy is a good and sound one.
There have been a few times when I've had to order goods from overseas.
That can be tricky, as "over there" the lingo may not equate _exactly_
with what the practices may be here. Again, the use of good old English
terminology is precising in and of itself, and that's exactly what I use
! I leave it up to the overseas supplier to have my English sorted-out
rather than to second-guess them...
Semper Fi
RTP
~~~ PGPBLUE 3.0 
---
---------------
* Origin: Alpha City BBS, Oshawa, Ontario (905)579-6302 (1:229/420)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.