Quote Originally Posted by delia View Post
I certainly agree but we don't know why his situation is set up that way and it's really none of my business. I was hired to provide this to him and I way under estimated the time because he was not clear and I did not make sure my assumptions were correct. Just trying to complete a difficult job or else refund his money.

So Kobra, something constructive would be appreciated.

mc12345678, my first thought was to provide the ability to put the tax id in on the checkout page that now seems like the best way to proceed. Simple would be a change to the query that inserts the order. Perhaps in the class - order.php around line 614? I can add that field to the order and then would need an additional bit to insert it into the customer table somewhere? Does that sound doable?
Without digging in, the thing I would think about is possibly using a session variable for assignment once entered. The thought is this:
Arrive at page (could be stepping forward or cycling through the checkout process).
If the session variable is set use that, if not set then pull from the user's stored information, if not set there, then display the field to be entered.
The next consideration is if this number can be different for the same person or not for each order that they place. If so, then best solution is to provide a pick list of such values including the ability to add one. Otherwise, if not such a pick list then the field is always displayed possibly showing a list of previously used values to copy and paste and the field is always displayed but if previously entered in a loop then it should appear again.

As to capturing in the order, the order class would need to be modified to account for the additional field to be associated either with the user or the entire order (this last appears to be addressed by incorporating in the line section described.)

Then there is the need to pull the information back out on the admin side, which assumably is already addressed.

Ideally, and a little of this has been done here in this thread, need to identify how the data is to be used throughout the process, to what it is relevant, who needs to be able to see it etc... That planning will cut down on the coding and help identify what needs what and where...