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
2K members online now
2K members online now
For questions related to Google Shopping and Merchant Center. Learn to optimize your Shopping ads
Guide Me
star_border
Reply

Google Merchant Center Manual Feed

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

HI,

 

I was wondering if anyone had best practices for the manual feed. I know you have to re-upload every 30 days, and I did see suggestions that said don't delete the original feed you upload. I searched all over and i didn't see how you can upload a new feed without deleting the old feed manually. 

 

Could anyone please explain how this is done and any other best practices? 

 

 

Thanks,

Katie

1 Expert replyverified_user
1 ACCEPTED SOLUTION

Accepted Solutions
Marked as Best Answer.
Solution
Accepted by topic author Katie L
June

Re: Google Merchant Center Manual Feed

[ Edited ]
Top Contributor
# 2
Top Contributor

 

there is no need to ever delete a feed simply for a re-upload.

simply select fetch-now, or upload-input-file by clicking on the

three-dot-icon, under the feeds-processing-tab, by clicking on

the registered feed-name, under the products-feeds-tab:
https://merchants.google.com/mc/products/sources

as to best-practices --

- register only one, single, primary-feed -- only once;

the one feed can handle about 100,000 inventory items.

- never, ever, delete the feed, unless indicated to do so by a person at google.

- use the same feed for all updates -- including any
additions, deletes, changes, or simply a re-upload.

 

of course, multiple copies of the feed may

be saved to the local-machine, as backup.

- if there are no changes to the website or physical inventory,

re-upload the feed every 30-days -- yes, which is required --

a best-practice is to re-upload the feed at least 5-days *before*

the feed is scheduled to expire.

- immediately re-upload the feed, if any critical changes occur
on the website, or to any physical on-hand product inventory;

- long-term, consider using a scheduled-fetch, or ftp, to help automate re-uploads
and coordinate re-uploads with the website's e-commerce system and the business
physical product-inventory system -- rather than manual re-uploads.

- use a mix of both letters and numbers for id -- for example, abc123;

- never change an item's id, once assigned to a physical item.

 

View solution in original post

Marked as Best Answer.
Solution
Accepted by topic author Katie L
June

Re: Google Merchant Center Manual Feed

[ Edited ]
Top Contributor
# 2
Top Contributor

 

there is no need to ever delete a feed simply for a re-upload.

simply select fetch-now, or upload-input-file by clicking on the

three-dot-icon, under the feeds-processing-tab, by clicking on

the registered feed-name, under the products-feeds-tab:
https://merchants.google.com/mc/products/sources

as to best-practices --

- register only one, single, primary-feed -- only once;

the one feed can handle about 100,000 inventory items.

- never, ever, delete the feed, unless indicated to do so by a person at google.

- use the same feed for all updates -- including any
additions, deletes, changes, or simply a re-upload.

 

of course, multiple copies of the feed may

be saved to the local-machine, as backup.

- if there are no changes to the website or physical inventory,

re-upload the feed every 30-days -- yes, which is required --

a best-practice is to re-upload the feed at least 5-days *before*

the feed is scheduled to expire.

- immediately re-upload the feed, if any critical changes occur
on the website, or to any physical on-hand product inventory;

- long-term, consider using a scheduled-fetch, or ftp, to help automate re-uploads
and coordinate re-uploads with the website's e-commerce system and the business
physical product-inventory system -- rather than manual re-uploads.

- use a mix of both letters and numbers for id -- for example, abc123;

- never change an item's id, once assigned to a physical item.

 

Google Merchant Center Manual Feed

Visitor ✭ ✭ ✭
# 3
Visitor ✭ ✭ ✭

Thank you! 

 

I also have one more question for you. 

 

Do you know if for the manual feed…. I can make up product ids that don’t exist on the big commerce website?

 

Does the feed have to exactly reflect the website for product id?

 

I ask because of the t-shirts we sell. It seems google likes the ids to be different according to size and color. But on our big commerce retail site, it assigns the shirt one product id and not a product id for each shirt size.

 

right now say the product id is 148 but i would make it 148-S, 148-M  etc

 

Can i do that?

Re: Google Merchant Center Manual Feed

[ Edited ]
Top Contributor
# 4
Top Contributor

first, you're welcome.

 

as to the follow-up questions, the short answers are:
(a) yes;
(b) no;

 

id values must simply be unique per item-offer --

regardless of any variants -- id must never, ever,

change, once assigned to a physical inventory item.

 

id is essentially a merchant's stock-keeping-unit (sku) --
google tracks all products and history by an item's id.

 

a best-practice is to use a mix of both letters and numbers for id;

for example, abc123uk; especially if a spreadsheet is being used.

 

id submitted do not need to match any id on a website.

 

that said, a best-practice is to always change any inventory detail
at the source, within the website or e-commerce system, not later,
as a modification to the feed for example; the website/e-commerce
system should be updated, if needed, to properly handle variants.

 

the best likely course is to contact big-commerce support, so that

both the site and feed-data are coordinated and handle variants

properly, based on google's rules and policies for variants.

 

only physical items may be submitted --
a parent-item, or a virtual-item, that
represents multiple physical variants,
is not allowed and is a policy violation.

 

variants also require an item_group_id attribute, with
proper identical values, for all items in a variant-group.

 

variants also require at least one unique variant-attribute with one
unique value, for each item in a variant-group -- such as size.

 

variants also require a unique landing-page, per physical inventory item,
or each physical inventory item to be preselected, for the user, using url
parameters and server-side-scripts;
e.g.
http://www.example.com/uk-en/products/red-shirt123-size-m
or
http://www.example.com/products/shirt123?locale=uk-en&color=red&size=m

 

if the variants differ by color or pattern, a unique image_link
url value, for each item in a variant-group, is also required.

 

otherwise, submitting only one physical item --
such as the default on the landing-page -- may
be the only option, to stay within the policies.

 

for variants, simply changing id values is not enough --
and is otherwise a policy violation and grounds for a
disapproval or suspension from the program, at any time.

 

the best likely course is to contact big-commerce
support directly, before making any such changes.

 

see also
https://support.google.com/merchants/answer/6324507
https://www.bigcommerce.com/contact/