Complicated Tax Rules - split Nexus
We are submitting a data feed to google via a Magento extension.
We recently received a suspension email that indicated that the tax value in our landing pages do not match the value in the datafeed.
Apparently google is now auditing the feed against using our actual e-commerce site and simulating a checkout.
We have a fairly set of tax rules. We have nexus in Washington State, so we charge state tax for most of the products we sell. We also have a set of products that attract a Federal Tax called the Universal Service Fund, or USF. This tax applies to telecommunications subscriptions.
The problem is that for these products we charge both Washington State tax and the USF. For other billing addresses, we only charge USF.
The taxation calculation is handled within our website using our ERP taxation module, which handles all of this complexity.
There doesn't seem to be a way to configure our google merchant account to reflect our tax situation.
E.g. I need a way to categorize some products as as attracting Federal and State tax (but only if the customer is in Washington), Federal only, and State only.
The only thing I can think of is to have a category that I apply to the USF products, and manually set the value in each tax (with Washington's value reflecting both the state and USF tax rate).
All other products get a different tax category.
Has anyone else had issues with federal tax and google shopping?
Does anyone know why google is doing this auditing? They don't seem to display the tax values anywhere?
Re: Complicated Tax Rules - split Nexus[ Edited ]
2w - last edited 2w
yes, the tax_category attribute may be submitted to allow
account-level tax-settings, of different tax rates, for
specific item-offers, or specific groups of item-offers.
the tax attribute may also be submitted to
override all tax settings, for specific items.
if accurate tax cannot be submitted, or set within the account,
then google requires a reasonable tax overestimate -- submitted
or set, that users will actually be charged; otherwise, such items
cannot be submitted, at all, without risking a disapproval, or a
more permanent suspension from the program, at any time.
generally, always verify the tax settings and related data being submitted,
by carefully inspecting the final-attributes area and tax-rate-calculator
for individual items, by clicking on the item's title, under the products
list tab, in the merchant-center-account, against the tax displayed on
the landing-page and the actual tax paid, during e-commerce checkout.
for details on how to submit a tax_category attribute, or tax attribute
override, for specific items, the best likely course is to contact the
developer or support-group of the current magento-extension being used --
or possibly consider a secondary-feed/feed-rule, to augment the data.
the tax requirements have been in place for quite some time;
however, google does not check for all policy violations for all
items, within submitted data, or on the website, all the time --
google may flag a policy issue at any time.
a best-practice is to keep up-to-date with all policies and ensure that
all physical inventory, all items submitted, all submitted data, all
website landing-pages, all site pages, and the entire e-commerce
checkout-flow, meet all google's rules and policies, at all times --
regardless of google flagging, or not flagging, a potential issue.
importantly perhaps, google has many other strict policies
for recurring-billing based offers, related to subscriptions --
some items are simply not a good match for shopping-ads
and other campaign-types may be a better fit for advertising.