We have a in-house automated CRM/sales system that runs our
website.
As such, it handles checkout, return requests, tracking of
serial
numbers, etc, and lets the end customer do it all from the
website.
Enter google checkout. We signed up hoping to offer the
option; but
how does one use that information? It looks like we have to
create new
"customers" in our system for every order, which
contain fake contact
information, no login support so they can't log in to setup
support
tickets, return requests, view serial numbers, download
protected
files, etc....... because their login on an account they
generate on
their own, cannot be tied to a Google checkout account.
Why is this? Microsoft used to let 3rd party developers tie
into
Passport. If you had an account with a vendor, and an
account with
Passport, you could link them together, use the passport
account to
login, and hand it back to the 3rd party to manage their
session.
I don't see how the largest benifactors of Google
Checkout's only
advantage, the free processing credits, can benefit from
such a system.
We spend $30,000 a month with Google....and we'd love to
participate,
if not for the free credits, then for the fact it gives our
smaller
competition an advantage with the Google Checkout logo next
to their
ads.
It just doesn't make sense, we spend all this money with
google, but
google makes our ads less visible AND takes away the entire
system
we've developed to make our customer's experience what it
is.
Why can't we have a passport style or merchant gateway
style interface?
Am i missing the concept of how to integrate? Because it
looks like
anyway we integrate our customers lose all of the support
services and
come with purchasing from us.
|