Invoice No.

[bernie]

I was hoping the answer given to wploong would have done for me but sadly, no.

I need an invoice number each time an order is made.
My setup is that I am only using managecart and checkout.html as this info is handled by a secure server to where I go and read the order.

Is there somewhere in the checkout that a number generator can be called up each time it is sent to the form handler?

PS
or in the nopcart.js ?

[scott]

See my other threads in this forum. You can do the 'date trick' I used in Javascript as well. Just have it write your form element like that. BEFORE the call to checkoutcart within your script tag, add the line to write your hidden field. Read the other posts, and some JS boards -- you should be able to figure it out. If you are still really stuck, post as much as you figured out, and I'll try to help.

_Scott

[bernie]

Thank you both very much, I will give this a go.

[BadHabit]

This is excellent and thanks for the example code. The only item that might be missing is adding the invoice number to the CSV file for that order.

[winkphoto]

That can be done as well.

In the checkout.pl file, add this:

Code: Select all

print CSVF "\",\"";
   print CSVF "$this_Nbr";


Just place that wherever you want the order number to appear.

It can also be added to the Emails as well:

Code: Select all

 open (MAIL,"|$mailprogram");
   print MAIL "To: $youremail\n";
   print MAIL "From: $b_email\n";
   print MAIL "Subject: New Online Order\n";
   print MAIL "\n\n";
   print MAIL "A new order has been received.  A summary of this order appears below.\n";
   print MAIL "\n";
   print MAIL "Order Number: $this_Nbr, Dated: $months[$month] $day, $year $hour:$min:$sec\n";
   print MAIL " \n";


Regards,


Marc

[g]

Will this work with the checkout.php also?

[Michael]

I like the idea of automating invoice numbering; but I have another application for the same idea - creating membership numbers for sign-up pages.

However, I have my own slant on this and I wonder if anyone has any thoughts on whether it would work before I go ahead and make a fool of myself.



The idea is to have two or three separate membership sign-on pages, for basic, intermediate and agent members. Each will have its own modified checkout.pl cgi, but all will refer to a single member.dat file for the incrementing serial number. This way I can automatically give everyone a single unique sequential membership number but deal with them through separate database entries (modified e-mail responses and database scripts for different information on applications forms, etc.).

Obviously with three checkout.pl scripts using a single *.dat file there is every chance of a conflict. Is this likely to occur or would my web server, and the scripts, be able to handle the load and any conflicts?