AdWords is now Google Ads. Our new name reflects the full range of advertising options we offer across Search, Display, YouTube, and more. Learn more

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

Complicated Shipping - Can I exclude Shipping Attribute?

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

I have complicated shipping for my products (see http://www.displayme.com.au/view/delivery/17), so I would like to simply exclude the shipping attribute from my listings.  I have tried to do this by changing at an account-level but my feed still is asking for the attribute to be in my feed, which i thought was only meant to go in if you wanted to override the account-level settings.

 

Feeling frustrated.  Any suggestions?

1 Expert replyverified_user

Re: Complicated Shipping - Can I exclude Shipping Attribute?

[ Edited ]
Top Contributor
# 2
Top Contributor


(1) yes, if shipping is properly set within the account then,
shipping may be excluded from the submitted data (feed) --
any submitted shipping is considered a per-item override.

(2) assuming the account-shipping is set correctly, the settings
can sometimes take a few hours or so, before being propagated
through the system and the data (feed) can be re-submitted.

check the feed's last-upload date under the feeds-tab, against
when the account's shipping-method settings were last saved.

(3) if a shared-rate-table is used, be certain that a
corresponding shipping-method-rate-table is also set.

a shared-library entry cannot replace, or be used as, a shipping-method --
the library is simply a reuse repository and a used-in field should (must)
indicate at least one shipping-method;

an active shipping-method must still be specified.

e.g. by selecting: use existing rate-table from shared-library.

(4) be certain that the shipping-method and any shared-library setting are
created within the proper target-country that matches the registered-feed --
the default is sometimes inadvertently set to the united-states.

(5) shipping_weight is required to be submitted if any weight-based table is
active within the account -- shipping_length, shipping_width, shipping_height
are all required for corresponding carrier-calculated rates; but, currently, are
available and used only for a u.s. registered feed.

all the shipping-dimension attribute values should also include a
number, space, and google-supported unit and might be submitted
and processed for possible future use in other target-countries --
but will otherwise be ignored.

 

currently, account-level carrier-calculated-rates are only

available for a u.s. feed and will otherwise be ignored.

(6) be certain all submitted weights fall within configured ranges.

for example, be certain that the 'all-other' option is checked and all
submitted data contains a proper and accurate shipping_weight value

check the individual item for any (shipping) details --
by clicking on the item's title under the products-tab.

hand-inspect the submitted (feed) data for any missing,
invalid, or out-of-range, shipping_weight values.

(7) a valid shipping_weight includes a number, space, and google-supported unit
e.g.
123.45 kg

(8) importantly, to use a shipping-setting for a specific item, the
submitted shipping attribute value must be blank (entirely empty)
for a tab-delimited .txt feed -- and cannot exist, at all, as a tag
for a google-xml .xml feed, for that specific item.

blank values within an xml feed will generally not be processed properly.

the shipping attribute (column) may be deleted altogether
for a .txt tab-delimited or google-sheet feed if all items will
be using the account-level settings.

 

(9) shipping may be either exactly correct or an overestimate --

if proper, exact, shipping cannot be set or submitted then, an

overestimate is required (either set in the account or submitted).

otherwise, forum members cannot look into feeds or accounts --
the best likely course would be to contact a support specialist.