eCommerce Site

We arrive now at the first page the customer sees after leaving the credit card company. This salesorder.php page presents a summary of the approved order (or a "sorry" message on a disapproved order) that the customer can print for reference. Also, since the order has been finalized, a new order number is issued in case the customer wishes to continue shopping.

The main division of the page begins with the page heading and capture of the Approval query string passed from the ordercapture.php page. If the order approval is "True," then begins the process of displaying the order information.

<div style="position:absolute; top:75px; left:200px; width:550px">

<span class="head1">Sales Order</span><br>
<span class="head4">Date: </span><?php echo date('n/d/y') ?><br>
<span class="head4">Order No: </span><?php echo $_SESSION[OrderNo] ?><br>
<br>
<?php
$Approval = $_GET[Approval]

if ($Approval)
{

   $conn = odbc_connect('Driver={Microsoft Access Driver (*.mdb)};DBQ=c:\inetpub\wwwroot\PHPTutorial\Ecommerce\databases\ecommerce.mdb','','');

  $sql = "SELECT * FROM OrderHeader WHERE OrderNo='$_SESSION[OrderNo]'";
  $rsHeader = odbc_exec($conn,$sql);

    if (odbc_result($rsHeader,OrderNo) == "")
      {
      odbc_close($conn);
      ob_flush();
      header("Location:home.php")
    }

  $slqOrders = "SELECT * FROM OrderDetail WHERE OrderNo='$_SESSION[OrderNo]'";
  $rsOrder = odbc_exec($conn,$sqlOrders);

  ?>

A Connection Object is created for link to the eCommerce.mdb database and an SQL statement is used for retrieving information from the OrderHeader and OrderDetail tables. These sets of records are matched against the order number, which still remains in the $_SESSION[OrderNo] global variable. All information is available, then, for recreating the order, beginning with the billing information extracted from the OrderHeader table.

The small section of code following the opening of the OrderHeader table is noteworthy:

    if (odbc_result($rsHeader,OrderNo) == "")
      {
      odbc_close($conn);
      ob_flush();
      header("Location:home.php")
    }

This script checks for an EOF condition on the recordset, meaning that a match is not found for the OrderNo. How can this happen and why check? Well, it can happen if the customer uses the browser's "Back" button to return to the previous page (the confirmation page of the credit card company) and then clicks forward again.

When the present page is loaded the first time to present the sales order, the final section of script re-issues a new order number for the customer (see below). So, if the customer backs up a page and then comes forward again, the order number re-sent by the credit card company won't match the current order number and a script error will be generated. This section of code, then, avoids that problem by redirecting the customer to the home.asp page if no match is found. You can't keep people from using the browser's back button, but you can trap any problems that occur when they move forward.

The script then continues with producing the sales order by displaying the billing information and purchase details.

  <?php echo odbc_result($rsHeader,CustomerName) ?><br>
  <?php echo odbc_result($rsHeader,CustomerAddress) ?><br>
  <?php echo odbc_result($rsHeader,CustomerCity) ?>,
  <?php echo odbc_result($rsHeader,CustomerState) ?>
  <?php echo odbc_result($rsHeader,CustomerZip) ?><br>
  <br>
  <table border="0" cellpadding="3">
  <tr>
    <th>Item Number</th>
    <th>Title</th>
    <th>Quantity</th>
    <th>Price</th>
    <th>Amount</th>
  </tr>
  <?php
  $OrderTotal = 0
  while ($row = odbc_fetch_array($rsDetail) {
    $ItemNumber = $row[ItemNumber]
    $ItemTitle = $row[ItemTitle]
    $ItemPrice = $row[ItemPrice]
    $ItemQuantity = $row[ItemQuantity]
    $ItemAmount = $ItemPrice * $ItemQuantity
    $OrderTotal = $OrderTotal + $ItemAmount

echo "<tr>
      <td>$ItemNumber</td>
      <td><$ItemTitle</td>
      <td style=\"text-align:right\">$ItemQuantity</td>
      <td style=\"text-align:right\">$number_format($ItemPrice,2)</td>
      <td style=\"text-align:right\">$number_format($ItemAmount,2)</td>
    </tr>";

  }
  odbc_close($conn);
  $OrderShipping = number_format($OrderTotal * .02,2);
  $OrderTotal = number_format($OrderTotal + $OrderShipping,2);

echo "<tr>
    <td colspan=\"4\" style=\"text-align:right\">Shipping </td>
    <td style=\"text-align:right\">$OrderShipping</td>
  </tr>
  <tr>
    <th colspan=\"4\" style=\"text-align:right\">Order Total </th>
    <td style=\"border-style:solid\"><b>$OrderTotal</b></td>
  </tr>";
?>
  </table>
  <br>
  Thank you for your order. Please print this page and reference your order number
  on any inquiries. Your order will be shipped immediately.

<?php }
else
{

echo "We're sorry you could not complete your order. Once you have resolved the problem,
  please return to <span class=\"head4\">WebWarehouse.com</span> for your software
  purchases."

}
?>

The formatting of this sales order is similar to that used for the shopping cart display. The script loops through the records extracted from the OrderDetail table, producing a row for each record. As before, each $ItemAmount is calculated, the OrderTotal is accumulated, and the $OrderShipping is computed on the $OrderTotal.

(Again, here is a case where we might think about storing the shipping charge in the OrderHeader record rather than calculating it when the order is produced. At some later date when this order is recreated there will likely be a change in the percentage charge and the order total will be different from what it is today. We won't deal with that issue here.)

Now, an important part of the processing. This customer's order is finalized, over with, finished, kaput. Therefore, we need to reassign a new OrderNo value in case the customer wishes to continue shopping. It they did so without a new number, then we would end up with duplicate order numbers and create all kinds of havoc in trying to keep customer orders separate. The final processing step on this page, then, is to assign a new number using the same routine we did when the person first arrived at the site and was assigned a random number home.php file.

<?php
'-- Assign new OrderNo
$OrderNo = rand(1111111111,9999999999)
$_SESSION[OrderNo] =$OrderNo
?>

</div>

Everything has come full circle. At this point the former customer is a new customer and can begin the shopping experience from the start.

This pretty much ends discussion about the basic mechanisms for maintaining an on-line eCommerce site. There are, of course, many of features and functionalities that can be added. We'll look at one more--the automatic issuance of e-mail confirmations of orders--on the next page.