These modules record customer order status and interfaces with the Merchant
customer management functions. 

You can change the status of the order and even notify the purchaser of the
change with variable styles of update status emails.  The status change 
notice can also include the tracking number if applicable.

You can run a report for all dates, a range of dates, or a specific date 
displaying all records or just the records with a specific status, eg 
Backordered.

There is also a form which allows you to re-establish inventory levels if
you are using the Inventory Management module.  While the Inventory 
Management module will automatically deduct the ordered quantity, it will 
not replace the quantity if the order is cancelled.  Hence, this form was 
provided to do that.  It can also be used to set the inventory level even 
if not related to an order as it uses the product code to locate the record.

Procedures for Installation:

1. FTP the customer.mv file to your Merchant /modules/fulfill/ script 
directory on the server.  Be sure the file name is lower case customer.mv 

2. In Merchant admin, install the module to the mall with the following
path: modules/fulfill/customer.mv.  Then install it to the store as a 
fulfillment module.

3. FTP the ordstat.htm file to modules/ui/ordstat.htm If you want to use 
different abbreviations you can edit this file and the customer.mv file
that assigns a status when the order is processed.  Currently the default 
assignment is P for Pending.

4. If you are using the Open UI look and feel, skip to item 5 below.  If 
you are using the mmui you'll need to edit per notes in item 4.  In the 
mmui.mv file, locate the following functions:

A. <MvFUNCTION NAME = "UIModule_Dispatch" STANDARDOUTPUTLEVEL = "text, html, compresswhitespace">
Add the following into the area where the other screen types are called.

<MvCOMMENT>wcw account status</MvCOMMENT>
<MvIF EXPR = "{ g.Screen EQ 'ACCT'}">
		<MvIF EXPR = "{Customers.d.login}">
			<MvDO FILE = "{g.Module_Root$'modules/fulfill/customer.mv'}" NAME = "l.account" VALUE = "{Customer_Account_Status()}">
			</TD></TR>
			</TABLE>
			</BODY>
		</MvIF>
		<MvFUNCTIONRETURN VALUE = "{ MMUI_Close_Store() }">
</MvIF>
<MvCOMMENT>wcw end added code</MvCOMMENT>

Locate the screen for ACNT.  Insert the 3 lines related to login and MvDO 
as you see them here between the comment lines.  They go in the middle of 
the existing* MvIF for the ACNT screen.
*	<MvIF EXPR = "{ g.Screen EQ 'ACNT' }">
*		<MvASSIGN NAME = "l.ok" VALUE = "{ MMUI_CustomerAddEdit() }">
<MvCOMMENT>wcw added lines</MvCOMMENT>
<MvIF EXPR = "{Customers.d.login}">
	<MvDO FILE = "{g.Module_Root$'modules/fulfill/customer.mv'}" NAME = "l.account" VALUE = "{Customer_Account_Status()}">
</MvIF>
<MvCOMMENT>wcw end added code</MvCOMMENT>
*	</MvIF>

B. <MvFUNCTION NAME = "UIModule_Invoice" STANDARDOUTPUTLEVEL = "text, html, compresswhitespace">
Add the following just above the first TABLE tag.  Table tag shown here for 
demonstration, don't add the table, it is already there*.  This displays a 
message at the invoice screen.
	
<MvCOMMENT>wcw display customer login ID on invoice</MvCOMMENT>
	<MvIF EXPR = "{Customers.d.login AND Orders.d.cust_id}">
		<TABLE border="0">
		<TR><TD>Please remember or record your Customer ID: &nbsp;</TD>
		<TD><FONT size="+1"><MvEVAL EXPR = "{Customers.d.login}"></FONT></TD></TR>
		</TABLE>
		<BR>
	</MvIF>
<MvCOMMENT>wcw end added code</MvCOMMENT>

*		<TABLE BORDER = 0 CELLPADDING = 2 CELLSPACING = 0 WIDTH = "100%">

C. <MvFUNCTION NAME = "MMUI_Begin_Screen" PARAMETERS = "title, greymenu, category_id" STANDARDOUTPUTLEVEL = "text, html, compresswhitespace">
Add the following Javascript function and check status just above the /HEAD 
tag.  /HEAD tag shown here* for demonstration purposes only.  You may need 
the full URL rather than the virtual URL if you are using the cgi-bin URL 
for your Merchant script.

<MvCOMMENT>wcw help system added</MvCOMMENT>
	<SCRIPT language="JavaScript">
	<!--
	function PopupHelpCust(helpfile)
	{
	window.open( helpfile, 'Help', 'toolbar=no,location=no,directories=no,status=no,scrollbars=yes,resizable=yes,copyhistory=no,width=200,height=150' );
	}
	// -->
	</SCRIPT>
<MvCOMMENT>end added code</MvCOMMENT>
*		</HEAD>

D.  In the MMUI_CustomerLogin function, right after the Invalid Password 
line, you can add the following ONLY IF YOU WERE USING CUSTOMER MANAGEMENT IN 
THE MERCHANT VERSION 1.x USING CIM TOOL KIT II.  The explanation of why it is
needed is included in the comments of custconv.mv (see paragraph 5 below).  

<BR><I>
We've changed our customer management software and your previous password
may be invalid.  Try entering your "bill to" zip code as your temporary 
password.  If your login is successful you should change the password in
your account.  If you are unsuccessful, request your password be emailed to
you by clicking on the Send Password.
</I>

E.  Also in the MMUI_CustomerLogin function, you can eliminate the option for
customers to order without creating an account.  This is advisable since the
purpose of using this module is so that you can update customers on their 
status or they can look up their orders.  This can't be done if they don't 
create an account.  In order to remove it, look for the following line.
<A HREF = "&[ g.secure_sessionurl ]Screen=OINF&Store_Code=&[ Stores.d.code:attribute ]"><MvEVAL EXPR = "{ l.link }"></A>
You can replace the line with &nbsp;  
This will leave a blank space in the table cell.

5.  If you are using the MMUI look and feel, skip to item 6 below.  This 
module eliminates the option for customers to order without creating an 
an account.  This is advisable since the purpose of using this module is so 
that you can update customers on their status or they can look up their 
orders.  This can't be done if they don't create an account.  If you want to
give customers the option of ordering without an account, you can change the
default module behavior by editing the oui_extension2 function in the 
customer.mv file.  Locate the section in that function identified as 
Customer Login.  Remove the line:
<MvASSIGN NAME = "g.OUIX_text" VALUE = "">

6. If you've installed the customer.mv according to paragraph 2 above, you
should have empty customer and order history files.  If you were using the
CIM customer management in Merchant version 1, you should now convert your
version 1 customer and history files to version 2.  Read the comments in 
custconv.mv for instructions on how to convert the files.  After the 
conversion you can return to this custread.txt and continue with the next 
step.

7. FTP the custadm.mv file to your Merchant modules/util/ script directory 
on the server.  If you don't already have a util directory under modules,
create one.  Be sure the file name is lower case custadm.mv 

8. In Merchant admin, install the module to the mall with the following
path: modules/util/custadm.mv.  Then install it to the store as a store
utility module.

9. FTP the mailbody.mv to modules/fulfill/mailbody.mv  This is not a module.
Do not install it as a module; edit, then FTP.  This file is used by 
the custadm.mv to add a body to Update Status emails to customers.  If you 
want different versions of the mail, you can have several.  Just edit the
mailbody.mv, creating a mvif...new message..../mvif for each type of email
you might want to send and give it a keyword in the mvif.  In the custadm.mv 
you can hardcode the parameter so it wouldn't have to be typed in each time 
or you can leave it blank.  The example is set to software2.  You'll 
obviously change that.  Do a search of custadm.mv for the word softare and 
replace it with your keyword which you will use for most of your status 
emails.  Essentially, mailbody creates a variable which is then imported 
into the mail message as it is sent.  You CANNOT use quote or apostrophe 
marks in the message unless you use the Miva escape method.

10. If you want to include the Customer ID on the mail notifications you will
need to add the code seen here between the mvcomment segments.  This edit is
done in your merchant and customer notification emails.  The standard Miva
Corp files are meremail.mv and custeml.mv.  In some cases you may be using 
other 3rd party email notification files.  Locate this existing first line*, 
which pertains to the total in the email.  It may look slightly different in
other 3rd party email files.  Add the new code between it and the closing 
</MvSMTP>** tag.  This step is not necessary if using the openui look and feel.

*<MvEVAL EXPR = "{ padl( 'Total:', 77, ' ' ) $ ' ' $ padl( l.formatted_total, 13, ' ' ) }">

<MvCOMMENT>wcw include Customer ID in merchant/customer notification email</MvCOMMENT>
<MvIF EXPR = "{Customers.d.login AND Orders.d.cust_id}">
	<MvEVAL EXPR = "{ asciichar( 10 ) $ 'Please use this Customer ID on future visits: '}"><MvEVAL EXPR = "{Customers.d.login}">
</MvIF>
<MvCOMMENT>wcw end inserted code</MvCOMMENT>

**		</MvSMTP>

11. I've added a special pack routine in the custadm module.  Normally, when 
you pack your store, your Order History files will be packed automatically.  
However, there may be times when you only want to pack the Order History 
files.  This routine will do it.