|
List Info
Thread: Buy Now Policies seem flawed...
|
|
| Buy Now Policies seem flawed... |
  United States |
2007-06-12 10:51:12 |
The following is to say, if you were to run a community
website for
which users must register to participate, you would likely
logically
have your registration on the front page, and according to
this
policy, you must then also be selling something on the front
page,
when typically, selling products is not the primary source
of a social
networking sites revenues. So forcing such a service, albeit
quite
valuable, is inherintely secondary in nature of some site
structures
and thus having a higher potential to damage the value of
the site,
unless placement options were more viable, of course, still
appropriately (e.g. no Buy Now buttons where there is
nothing to
buy)..
http://checkout.google.com/supp
ort/sell/bin/answer.py?answer=46051&topic=8669
"Place Buy Now buttons before any registration or
sign-in pages."
Other policies on this page are questionable, at least to
me, as well.
---
Just to touch on another policy real quick on the same page,
I can
suppose a number of reasons why Google would not want
sellers
collecting zipcodes, however, it seems the appropriate times
for
collecting zipcodes as defined by Google are quite strict.
What if I
wanted to check not to see if something were available
(i.e.), but for
example (e.g.), I wanted to check if someone lived in my
state, to see
if tax was necessary, or to make sure if they signed up for
a news
letter, they would not get deals for things not available in
their
area.
Note, "i.e." is pretty strict, and I assumed it
was meant to be so,
while "e.g." is much more flexible, though vague.
Having fun?! Take a breath of fresh air! Meditate! Relax...
: - ))))
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "API Integration Basics" group.
To post to this group, send email to
google-checkout-api-integration googlegroups.com
To unsubscribe from this group, send email to
google-checkout-api-integration-unsubscribe googlegroups.com
For more options, visit this group at http://groups.google.com/group/google-checko
ut-api-integration?hl=en
-~----------~----~----~----~------~----~------~--~---
|
|
| Re: Buy Now Policies seem flawed... |

|
2007-06-12 12:11:22 |
|
Hi, i can not give u the reasons about the first paragraph, but i can, at least, solve one of ur issues.
regading tax, u can define tax zones and filters, so tax areas can be differentiated. u can also use merchant calculation callback to calculate tax. In this callback u will be able to know not only the zip code, but the state, country, and other shipping address info
here is the link to the docs http://code.google.com/apis/checkout/developer/index.html#merchant_calculations_api
hope this helps
ropu
On 6/12/07, Chexed < chexed gmail.com">chexed gmail.com> wrote:
The following is to say, if you were to run a community website for which users must register to participate, you would likely logically have your registration on the front page, and according to this policy, you must then also be selling something on the front page,
when typically, selling products is not the primary source of a social networking sites revenues. So forcing such a service, albeit quite valuable, is inherintely secondary in nature of some site structures and thus having a higher potential to damage the value of the site,
unless placement options were more viable, of course, still appropriately (e.g. no Buy Now buttons where there is nothing to buy)..
http://checkout.google.com/support/sell/bin/answer.py?answer=46051&topic=8669 "Place Buy Now buttons before any registration or sign-in pages."
Other policies on this page are questionable, at least to me, as well.
--- Just to touch on another policy real quick on the same page, I can suppose a number of reasons why Google would not want sellers collecting zipcodes, however, it seems the appropriate times for collecting zipcodes as defined by Google are quite strict. What if I
wanted to check not to see if something were available (i.e.), but for example (e.g.), I wanted to check if someone lived in my state, to see if tax was necessary, or to make sure if they signed up for a news
letter, they would not get deals for things not available in their area.
Note, "i.e." is pretty strict, and I assumed it was meant to be so, while "e.g." is much more flexible, though vague.
Having fun?! Take a breath of fresh air! Meditate! Relax... : - ))))
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "API Integration Basics" group. To post to this group, send email to google-checkout-api-integration googlegroups.com To unsubscribe from this group, send email to google-checkout-api-integration-unsubscribe googlegroups.com For more options, visit this group at http://groups.google.com/group/google-checkout-api-integration?hl=en -~----------~----~----~----~------~----~------~--~---
|
[1-2]
|
|