@Dave224,

Good questions and thank you for much of the information provided. The key to the single vs. multiple customid aspect is how are the variants setup? From what has been provided both in the "configuration" and the results appears to indicate that every option value is listed on its own. Meaning that there is not a grouping such as option name 1's option value 1 with option name 2's option value 3 (really the first option value of option name 2, but calling it 3 for clarity).

I say this, because, 1) the same customid is not duplicated (x, x) and that there are two customid's provided (one for each option value selected which is two based on two option names with the product.)

Now why are there two array values? Well, each attribute of the product is stored in its own record. There are two attributes to the product, so two records. Further, the customid associated with the purchase, if I remember correctly, is stored with each attribute. Now I thought I stored each uniquely but then based on the previous determination output the customid as combined and did it this way so that the display could be modified if so desired (combine into one long customid if desired, separate out into individual, etc...), but unfortunately at the moment I'd have to review the code again more to accurately report that aspect. That review also depends on the answer to my previous posed question about the variant arrangement.