We had the following situation on a customer site:
1. User intended to add a "faked" email address. This adress is added to customers that do not want to receive an email for the invoice and do not need a printed invoice. (a hard copy of the invoice is delivered and when running duplicate invoice (after posting), it is not necessary to get a hard copy or an email). This is a valid process.
2. After adding the faked email econtct, user changed the email address to one of the real emails of this customers. This was a mistake.
3. As a result the email of step 2 above received all the emails that went to the faked email. There were many emails and the customer was able to see other customers' invoices which is always bad.

We changed the faked econtact details Name, Company, Address etc. to say DO NOT CHANGE THE E-MAIL !!! in order to prevent future mistake.

A warning " Are You sure you want to change the econtact email?, This can cause a problem " or similar message, could help as well.

There is no elegant way to print a duplicate invoice for an order that is not yet posted. Printers sometimes have issues or some other printing errors can occur while printing an invoice. Bad toner, bad printout, etc... If the invoice does not physically print there are only 2 options to get the invoice printed that I know of.

1. Print a duplicate invoice using Print Invoices. This can be done, but will also lock all users from printing invoices if the user does not complete the task quickly enough. This options is not good for users not skilled in Elliott enough to get it done quickly.

2. Void the invoice and reprint it using Print One Invoice. This works, but unnecessarily burns invoice numbers just to get an invoice to print.

If an order is not yet posted, allow the duplicate invoice to be printed in Print One Invoice if it meets all of the criteria to be printed.

When doing billing for a Lot item and the Lot doesn't have enough quantity Elliott prompts the user to add a new line for the remaining quantity. This is a good and necessary feature. But if the Lot entered has enough quantity, NOT all the quantity is coming from the same lot, the remaining quantity is put on back order and technically cannot be shipped on the same invoice. Currently this forces the user to ship everything on one lot and then doing an issue and receive transactions to adjust the lots. Obviously this is a bad practice but the user doesn't have any other choice.

If lot line item is not fully shipped and the lot has the quantity to ship, the system should ask the user if a new line has to be created so user can ship the remaining quantity on the new line with a different lot.

Elliott allows to use a variable on the Attach... field when sending a Post Office email. For example the variable InvNo will automatically attach a document with the invoice number as the file name. This is NICE. I suggest to allow multiple path in case the documents are in different folders and to allow wildcard. So instead of $InvNo$.pdf I can define $InvNo$*.*. For example if the invoice number is 123456, Elliott will attach 123456.DOC, 123456A.PDF etc. In addition user should be able to define different path so it can be something like M:\ELLIOTT8\DOC1\$InvNo$*.*, M:\ELLIOTT8\DOC2\$InvNo$*.*,M:\ELLIOTT8\DOC3\$InvNo$*.*. In this example, Elliott will attache any document that has the invoice number as the first characters in the file name. If the multiple path is complicated, I think that one path is acceptable.

Elliott currently supports Wish List items, which are items that customers would like to buy but cannot for some reason at the moment the item is added to the wish list. Its a great reminder system to build sales.

The support for favorite items should also be added. Favorite items are basically a list of items the dealers likes to order. The process to add an item to a dealer's favorite list could be handled in sales desk similar to the wish list items. Any active item could be added to a favorite list.

Users should be able to view and maintain favorite items from sales desk similar to wish list items. They could have an expiration date as well.

Favorites should be tracked by cusno / ship-to combination as different stores under the same account could have different favorites.

Duplicate entries for the same item for the same cusno/ship-to combination should not be allowed.

Possible table fields are:
Cusno (key)
Shipto (key)
ItemNo (key)
ProductCategory
UserDefinedCode
DateAdded
ExpirationDate (if needed)

To complement the favorites functionality, there should also be a utility process that removes Obsolete and expired items from all favorite lists.

There should also be a new associated web service to interact with the customer favorites. Basic add, remove and listing functionality should be included with all of the required validation of customers, ship-to's, items, etc... It would be helpful to return item information, quantity and current pricing information in the listing method as well, if it is requested, to avoid multiple web service calls to get complete data. The ability to get a smaller set of data with just the item info would be very helpful as well.

Optional paging by specifying a starting and ending record number would probably be a good idea as favorite lists could grow quite large if left unchecked.

Favorite data could also be incorporated into other Elliott functions as well, such as buyer's desk, eStore and other reporting.