AdWords
2.7K members online now
2.7K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Your billing terms and conditions cannot just be provided via a link.

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

I'm confused by this policy:

 

  • Your billing terms and conditions cannot just be provided via a link.

 

Does this mean that billing terms and conditions must be on every product page? Not via a link to a single policy page?

 

I have looked at several Google Trusted Stores and they all provide their terms and conditions via a link, usually in the footer.

1 Expert replyverified_user

Re: Your billing terms and conditions cannot just be provided via a li

[ Edited ]
Top Contributor
# 2
Top Contributor


the clear-billing policy forbidding links, means that the
exact price and pricing-model used, how the user will be
billed, for exactly what, must be clear and conspicuous
on the link landing-page and during checkout -- no links
that clarify a purchase with added terms or conditions.

the price and description of what is being purchased must be
clearly and conspicuously indicated directly on the landing-page
and must be identical during the entire checkout-flow, on all pages --
including and exactly what the user will actually pay (finally billed) --
and exactly what is shipped to, and received by, the customer.

the price and item must be prominent on the landing page.

typically, this means one, single, item, with one, single, price
on the landing-page with an exact, clear, and obvious description
of what is being purchased, both directly on the landing-page and
during the entire checkout processes.

any deviation must be clear and conspicuous -- stated
directly on the landing-page -- usually, directly below
the single price of the item and on all checkout pages.

generally, this means any restrictions, any post-billing, any
unclear bulk-purchases, or any difference between the price
or the exact item being purchased -- on the landing-page or
at any point during checkout, on any secure-gateway pages,
on the user's credit-card, or what the user actually pays and
receives -- is not allowed.

for example, a single price on the landing-page of 29.95 for a single bottle
of shampoo, with a link to a page indicating that the user is billed per month
with cancellation-restrictions, and after checkout the user is billed 29.95
per-month, for the bottle delivered monthly -- would not be allowed.

for example, multiple or unclear prices on the landing-page.

for example, unclear product-bundling -- a link or fine-print that
indicates the product is sold as a box-of-10 would not be allowed;
a box of 10 shampoo bottles must be both clear and conspicuous
on the landing-page; e.g. a box of 10 bottles of shampoo directly
below the price of 89.50; not, 8.95 with a link; or, not 89.50
without clearly indicating the exact number of bottles -- the
89.50 for a box of 10 shampoo bottles would need to be clearly
indicated on the page and during the entire checkout-flow.

for example, an image of a vinyl-album when an mp3 is being purchased --
or the words vinyl-album at checkout or on the bill, when 2 mp3's are sold.

for example, two prices on a page -- one for a single item
and another for the actual price of a required bundled-offer.

links or fine-print cannot be used to clarify a purchase.

in addition, any bundling would need to be indicated in the feed --
for example, the price for the entire bundle or minimum purchase;
in addition, the is_bundle or multipack attributes, with exact values,
may be required, depending on the details.

also, the price being paid must be the most prominent price on the page --
prominent usually means the largest font and highest-contrast color for
the price being billed and paid; or simply only one price on the page.

related, all user data collection, during the entire checkout-process
must be ssl/https secure -- for example, some user-data collected on
an unsecured page on the site and some user-data collected on a secure
(payment-gateway-service) page, is not allowed -- either such user
data-collection would need to be removed -- or ssl/https must be
added to those specific pages with user-data-collection; otherwise,
the secure-gateway would need to collect all user-data.

importantly, google is the final arbiter
of clear, conspicuous, and prominent.

Re: Your billing terms and conditions cannot just be provided via a li

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭
OK, thanks. That describes a situation I would not have thought of. I just have a normal shopping cart with an item, description, photo, price, add to cart button. I'm using Woocommerce with PayPal checkout. Will this normally be compliant?

Re: Your billing terms and conditions cannot just be provided via a li

[ Edited ]
Top Contributor
# 4
Top Contributor


first, you're welcome

on the surface, those details and the
technical solutions seem satisfactory
and would meet the requirements.

however, the unclear-billing polices relate more
to exactly what is shown on the landing-page and
during checkout -- and what the user will actually
be billed and receive for their payment; these all
must be clearly and conspicuously presented.

one technique is to imagine the customer has never seen the product --
the product must be described over-the-phone to a potential customer,
without any image of the product, and the final price mentioned only once;
when the product is shipped, received, and a bill is seen, each is exactly
what the customer expected based on that phone-call; the landing-page
and what is seen during checkout, should clearly reflect that information,

without anything else being added or necessary.

 

recurrent, negative-option, billing is also not allowed.

 

subscriptions of any kind are also generally not allowed --

and should not be mentioned anyplace on the landing-page

or anyplace on any checkout pages during the checkout-flow.


also, be certain all user-data collection on the website --
such as name, address, and email -- is https/ssl secure;

otherwise, paypal would need to collect all user-data.

 

Re: Your billing terms and conditions cannot just be provided via a li

Visitor ✭ ✭ ✭
# 5
Visitor ✭ ✭ ✭
Thanks again. I may have to wait until I can afford an SSL, in that case, before I can submit a Google shopping feed. I don't collect payment info, but I do ask for a shipping address, email, and name.

Re: Your billing terms and conditions cannot just be provided via a li

[ Edited ]
Top Contributor
# 6
Top Contributor

 

first, you're welcome.


asking for most any shipping details such as an
address is generally not allowed unless secure;
in this case, simply allowing paypal to collect all

user-data is likely the best, easiest, solution.

that said, a single disapproval or a suspension
can be for multiple issues; unclear billing and
unsecured data-collection are separate policies.

generally, always contact a support-specialist
at google before making significant changes.