adding admin arbitrary button code configured create data define doesn existing follow form format generate individual interface manually multiple names on0 on1 on3 option ordered os0 os1 os2 page price product product-config referring safe sku specifically stock tags tie tweak values variants variation variations weight wish

I have a product with multiple variations. It is actually easier for me to generate the code another way than having to enter each variation manually on the step called "DEFINE VARIATIONS WHICH TELL MORE ABOUT THE PRODUCT ORDERED". So my question is: Is that step just to create the form code to use with the button, or does it tie in with some back end stuff? If I just tweak the existing form code for my button by manually adding the <option> tags, am I safe?

If you are referring specifically to "Variations which tell more..." (and NOT "Variants having individual price/weight/stock/SKU"), then yes, the names and values you specify are completely arbitrary there; the actual button code in your page doesn't need to "match up" to any Variations data configured in Admin.

Our product-config interface for Variations is only used to generate the button code; you can follow that code format to make your on0/on1/on3 (names) and os0/os1/os2 (values) say whatever you wish in your page.