Consider special wid (or other technique) for virtual terminal checkout page

[Brian Koblenz]

You guys are too good! Thanks.

[CnP.Support]

Since it was a respectful disagreement we will go ahead and add it to the road map for the next release.

Things we do for our clients

[Brian Koblenz]

I respectfully disagree that your workaround is "easy". I already have complex skus where the beginning, ending and other associated text is used. Changing SKUs for the same item purchased through different means makes all of my reporting more complex since I constantly need to be thinking about VT in my SKU.

Using something like wid=00000 for VT makes me only need to think about VT once during autoresponder vs with every operation that works on SKUs.


While I agree that many things can be worked around with SKUs that does not make that workaround a good long term solution.


The purpose of the wid is to know how something was procured. I think extending wid to VT is consistent with the wid usage, while adding VT to SKUs is not consistent sku usage which is basically for tracking items.


thanks

[CnP.Support]

Good day!

This may easily be achieved with SKU's.

Transactions from VT, for example, may have a prefix of "VT-"

& SKU may be set up for STARTS WITH VT-

why would we then need to add yet another condition?

VT allows for item campaign and item SKU, both of which triggers the autoresponder.

Please let us know conditions where the above 2 parameters are not enough.

[Brian Koblenz]

It would be nice if autoresponder emails could also be triggered by the virtual terminal page as well as specific checkout page wids.

Treating the autoresponder as wid=00000 would be fine with me or a checkbox saying virtual terminal as a condition for autoresponder.

-brian