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 Merchant inventory control system. While the inventory control system 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. Using the file upload under admin:modules:add module, add the customer.mv (customer.mvc if compiled) to the domain. 2. 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(c) 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. If using Merchant 4.14 or newer, change the edit from customer.mv to customer.mvc. You will also need to recompile using the mivascript compiler from Miva Corp. In the mmui.mv file, locate the following functions: A. Skip this edit if using compiled Merchant and you licensed this module after Nov 7, 2003. Add the following into the area where the other screen types are called. wcw account status wcw end added code B. This is a fairly long function. Scroll down to a few lines before the end of the function. You will see the line marked with the asterisk below. Place the added lines directly above that line but after the tag. wcw added lines wcw end added code * C. Add the following just above the second 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. wcw display customer login ID on invoice
Please remember or record your Customer ID:  

wcw end added code * Then further down in this same UIModule_Invoice function just before the line shown below with an asterisk, add in the lines of code you see here. wcw added lines wcw end added code * D. 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. wcw help system added end added code * E. 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. You can replace the line with   This will leave a blank space in the table cell. In order for a customer to be able to view their recent order (like an invoice) by linking to the store and loggin-in, you'll need to change the following. The existing lines are marked with an asterisk (*). Add the lines not marked to those that are marked. * * * * * 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: 6. If you've installed the customer.mv according to paragraph 2 above, you should have empty order history files. 7. Upload the custadm.mv file through admin:modules:add module. 8. Then install it to the store as a store utility module. 9. If using Merchant 4.13 or older, 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. I have included several versions in this example mailbody.mv file. 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. IMPORTANT: You MUST NOT use quote or apostrophe marks in the message unless you use the Miva escape method. 10. Merchant versions prior to 4.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 ** tag. This step is not necessary if using the openui look and feel mail modules. * wcw include Customer ID and order link in merchant/customer notification email wcw end inserted code ** 11. Merchant versions 4.10 and newer: If you want to include the Customer ID on the mail notifications you will need to add the code below. This edit is done in your merchant and customer notification emails. The standard Miva Corp files are meremail.mv and custeml.mv. This step is not necessary if using the openui look and feel mail modules. Locate the line: Immediately preceeding that line, add the following: wcw include Customer ID and order link in merchant/customer notification email wcw end inserted code 12. If you are upgrading from an earlier version (1.x or 2.x) of Customer and Product administration and were using the mmui.mv, you had made this edit in the UIModule_Dispatch function: * * wcw added lines wcw end added code * You had added the non-asterisk lines. You will need to remove that edit. Leave the lines corresponding to these lines above with the asterisk. Remove those in-between. If you are using the OpenUI, you can ignore this paragraph. 13. If you are upgrading from our earlier version of Inventory Management for Merchant prior to 4.x, you will need to uninstall from the store and domain the Fulfillment module, Inventory Management (im.mv), and the System Configuration module, CIM System Extension Module (cim_sys.mv). 14. The compiled version of this module licensed on or after November 7, 2003 has a new file called cim_new.mvc which you need to install. Install through admin as a system extension module.