James H. Zisch - Computer Services

Solutions : Ecommerce : Order Tracking

 

Order Tracking

PRICE:  $149.99 (subject to change without notice)

Description
Requirements
Usage
FAQs

Description

Order Tracking provides online customer order shipment tracking for carriers including UPS and FEDEX. It interfaces with the JHZ-CS Shopping Cart product in combination with a back-end administrative tracking number entry system supporting Comma Separated Values (CSV) files automated data entry as well as manual data entry.

Automatic customer notifications of tracking numbers are e-mailed when order tracking information is entered thru the back-end administrative facility. The customer front-end allows customers to easily check their order status online.

Supports both flat file and SQL RDBMS data sources for customer information management.

Web Server Requirements:

  • Operating Systems Supported: Unix, Linux, Macintosh OS X® and Windows®
  • HTTP 1.x with CGI (Common Gateway Interface) PERL 5.x (check with your ISP or Server Administrator; this requirement is typically supported on most systems)
  • SENDMAIL (supported on most all Unix/Linux platforms), or PERL NET:SMTP (available from CPAN) (commonly used on Windows® server platforms) with an SMTP system pre-installed and configured
  • SSL (Secured Sockets Layer) optional, but strongly recommended.
  • Optional: For configurations using an RDBMS (Relational Database Management System) data source requires a supported RDBMS, the PERL DBI module and the RDBMS specific DBD module to be previously installed and configured

Order Tracking
Installation and Usage

FILENAME: ot.html

DEPENDENCIES:

ec.pl - Ecommerce configuration and common logic modules (see: ec.html)
jhzcs.pl - JHZ-CS configuration and common logic modules (see: jhzcs.html)
IID (Item Information Dataset)

REQUIREMENTS:

Logic Modules

ot.pl - common configuration and logic module
track.cgi - front-end logic module
trkupd.cgi - back-end automated update and customer notification
trkupdmanu.cgi - back-end update w/o customer notification with manual selection

Page Templates

no_tracking.htm -
tracking_results2.htm -

Optional:

Support for Text Search and Banner Rotator System requires those components to be installed and configured according to their specifications. Inclusion of Special Template markup supporting those components must also be included within the templates supported by this product.

PACKING (PARTS) LIST

PACKING LIST
PRODUCT ID: OT
COMPONENT TYPE SIZE AUTH*
cgi-bin/ec/ec.pl TEXT 2293 750
cgi-bin/ec/ot/ot.incl TEXT 11386 700
cgi-bin/ec/ot/ot.pl TEXT 6333 750
cgi-bin/ec/ot/track.cgi TEXT 8161 750
cgi-bin/ec/ot/trkupd.cgi TEXT 18684 750
cgi-bin/ec/ot/trkupdmanu.cgi TEXT 11432 750
cgi-bin/ec/unacc_edomains.pl TEXT 38196 750
cgi-bin/ec/unacc_edomains.txt TEXT 14534 750
cgi-bin/geog.pl TEXT 11750 750
cgi-bin/jhzcs.pl TEXT 47225 750
cgi-bin/license.incl TEXT 7565 700
cust/cust.idx TEXT 0 770
data/tracking/tracking.dat TEXT 142 700
images/JHZCS.gif BINARY 745 750
logs/errorlog.txt TEXT 91 750
tmpls/ec/ot/no_tracking.htm TEXT 472 750
tmpls/ec/ot/tracking_results2.htm TEXT 2831 750
*AUTH - Authorization/permissions octal equilvalents where:
7=RWX, 6=RW, 5=RX, 4=R (R=Read W=Write X=Executable)
1 char indicates Octal number
2 char Owner
3 char Group
4 char All Others

INSTALLATION:

It is strongly recommended that you read the entire installation process steps prior to performing any installations. Each solution has specific instruction that must be followed precisely.

The Installation Process

The installation process follows this order:

  1. Download solution to PC development platform and expand installation package (use any standard archive application such as WinZip®, StuffIt Expander® or TAR command)
  2. Modify configuration settings
  3. Upload to server
  4. Set access authorization permissions
  5. Test
  6. Customize Templates
  7. Test

Authorize non-Logic Components

Authorize non-logic components as follows:

  • authorized all images for read and execute access; see NOTE FOR NON-LOGIC COMPONENTS below
  • authorized all static HTML ".html" documents for read access; see NOTE FOR NON-LOGIC COMPONENTS below
  • authorized all HTML Templates ".htm" documents for read access at the logic level; see NOTE FOR LOGIC COMPONENTS below
  • authorized all images for read and execute access; see NOTE FOR NON-LOGIC COMPONENTS below.

NOTE FOR NON-LOGIC COMPONENTS: Use the minimum required permissions to achieve most secure configuration; permission requirements for non-logic modules are dependent on the server configuration whether authorization is required for group only or for both group and other.

Modify Logic Components

Modify all logic components "*.cgi" and "*.pl" logic modules as follows:

  • first line of code (#!) correctly points to the PERL executable on the server (use command "which perl" or consult your server administrator)
  • all "requires" statements contained in all "*.cgi" and "*.pl" logic modules must use absolute directory paths (beginning with a forward slash "/")

Authorize Logic Components

Authorize logic components and dependent components (HTML and Email templates, and others) as follows:

  • authorized as all "*.pl" logic modules for read access; see NOTE FOR LOGIC COMPONENTS below.
  • authorized as all "*.cgi" logic modules for read and execute access; see NOTE FOR LOGIC COMPONENTS below.
  • authorized all HTML and Email Templates documents for read access at the logic level; see NOTE FOR LOGIC COMPONENTS below

NOTE FOR LOGIC COMPONENTS: Use the minimum required permissions to achieve most secure configuration; permission requirements for logic modules are dependent on the server configuration whether authorization is required for owner only (i.e., Apache with SUExec active), or for both owner and group.

Set Configuration in sc.pl; see embedded instructions for:

  • Use Database (for SQL RDBMS IID)

TEMPLATES:

Customize templates for content and appearance as desired:

no_tracking.htm
tracking_results2.htm

Special Mark-up Directives within Order Tracking Template "tracking_results2.htm" indicate repeating item groups with nesting.

		
<!-- Repeat Start -->
	<!-- Repeat UPS Start -->
	<!-- Repeat UPS End -->
	<!-- Repeat FEDEX Start -->
	<!-- Repeat FEDEX End -->
<!-- Repeat End -->

Uploading to Web Server

All dependent and required components must be installed and successfully configured. All components, with the excpetion of images, must be FTP uploaded as TEXT. Images must be FTP uploaded as BINARY.

TEST:

Test installation and configuration by invoking the various Order Tracking functions from a web browser.

USAGE:

Add "Order Tracking" links to pages and templates as desired.

Following successful installation and verification modify templates as desired for function and display aspects to meet the requirements of the website.

FAQs

Can my customers track their orders online?

Yes, Order Tracking links to FED-EX and UPS using the tracking numbers you enter into the system.

Can more than one order per customer be tracked?

Yes.

Do I upload the tracking data file using Text or Binary mode?

Upload the file as Text.

JHZ-CS Solutions are distributed exclusively under terms and conditions of the JHZ-CS Software License Agreement.