magento attributes for ebay and amazon titles in m2epro

Which Way? Magento Attributes for eBay & Amazon Titles in M2EPro


If you consider Magento as a “Framework” to use and combine that with the flexibility of M2EPro for eBay & Amazon, you’ll end up with a curious question like Felix’s below.

Especially if you intend to sell internationally using Magento & M2EPro onto the different eBay & Amazon sites.

Note: Even if you don’t intend to sell on more than one eBay or Amazon site you should still have a read of this article as it’ll help you understand the two options you have available to you when the time comes.

So let’s take a look at question and we’ll then take a look at the options you have available to you.


I just looked at the Lesson concerning the definition of attributes for international listing on eBay. I was wondering why you need to define a title attribute for each ebay site you are listing on. Is it not possible to use one attribute “att_title” and save the translated Titles in the according storeviews? It would be much easier to handle. Otherwise i will need 5+ Ebay Titles and 5+ Amazon Titles.

Looking forward to your insight!

A Quick 101 on what is being discussed here

Magento Video TutorialsA few moments ago I mentioned that Magento can be considered as a framework, think of it as being a set of lego blocks that can be arranged differently to make different structures.

When it comes to Magento and product attributes, these come in different types, different lego blocks if you will.

They can be text boxes for a title or a bullet point, a price to hold a price (no surprise there eh?), a text area for a description and so on…

However these blocks can also be set up to have different scopes.

Scopes in Magento give you ultimate control, because that one lego block can now have a different value, say colour at different levels in Magento.

It’s this level of flexibility in Magento that can a little confusing to begin with and the thing is, there is no right or wrong of using them.

There are just different ways and that’s what we’re going to be discussing here in the rest of this article. How a Magento attribute can be used for the listing titles on eBay and Amazon.

Option 1 – The Simple Approach

As you may have already worked out, we like simple.

So the simple approach to handling different listing titles for different eBay and Amazon sites is to create a separate Magento attribute for each site and set the “scope” of the attribute to “Global”.

Note: The scope of “Global” basically means “Can be seen everywhere”

What this means is that you can see and edit the title on all storeviews of Magento and the title doesn’t change.

So if you go into a product record in Magento and you switch the Magento store view over, you still see the same title regardless.

magento m2epro attributes for listing titlesFor example a text entry box for:

  • eBay Listing Title

Or of you have lots of eBay sites:

  • eBay UK Listing Title
  • eBay US Listing Title
  • eBay DE Listing Title
  • eBay AU Listing Title

And stepping it up a gear:

  • eBay UK Listing Title
  • eBay US Listing Title
  • eBay DE Listing Title
  • eBay AU Listing Title
  • Amazon UK Title
  • Amazon US Title
  • Amazon DE Title

The last one might look a bit scary, one input box for each marketplace and you’d be right, it would take up a lot of space on the product edit page in the Magento admin.

This is the approach we suggest in the video tutorials for the setup of Magento & M2EPro and it has both positives and negatives.


  • Very simple to implement
  • Simple for internal and external staff to understand
  • Works great with Magmi because it’s a column per marketplace for the titles in the CSV file
  • Suggested for when you just have Magento and eBay or Amazon or eBay & Amazon


  • When you have lots of marketplace sites you will have lots of title fields on the product record
  • And if you have lots of marketplaces sites, the spreadsheet will become quite wide

And it’s this first negative that Felix is questioning here.

If you have lots of eBay and lots of Amazon sites, following the simple approach means that you could end up with 7 title attributes on the admin page for a product.

There could be so many of them they would warrant their own side group!

Matt’s Tip: Think of this approach as being a pack of cookies, each of the cookies is in one row in the packet.

So what is the alternative?

Option 2 – Store View Title Attributes

The alternative here is just as viable as the first option and it’s worth keeping in mind that both of these approaches will work.

You just need to think about which approach works for you and your business.

Ok, now for option 2.

Remember above I mentioned that our attributes (the lego) can also be have scopes?

What this means that instead of creating separate attributes for each marketplace, say one Magento attribute set as “Global” and we ended up with that list of 7 title attributes for covering the main eBay & Amazon sites.

magento storeview pickerOption 2 is different.

Instead of one attribute that is used for just one eBay or just one Amazon site, we re-use the attribute over.

What you would do here is create an attribute for the eBay title, say “eBay Listing Title” and this time set the attribute as having a scope as “store view”.

This then means when you set up multiple store views for handling the different eBay & Amazon marketplaces in Magento, when you use the store view switcher in the Magento admin, you can override the title for each store view level.

Note: If I’m losing you here with the mention of storeviews, don’t worry they’re childs-play and we explain them in the step-by-step eBay Cross Border Trade course.

So one Magento attribute, being used multiple times.

So not 7 attributes, just one.

Note: Think of this approach as being an onion. Onions have layers and each layer you switch to is a different store view (an eBay or Amazon site) and different title.

As you guessed it, there are some positives and and some negatives to this approach:


  • Just one attribute to use, thus a tidier product admin page
  • Works in Magento with no extensions being needed, it’s standard functionality of Magento
  • And also works with M2EPro because M2EPro can use Magento store views

Note: M2EPro is extremely well integrated into Magento, this is a prime example!


  • You have to remember to to choose the right store view to change the titles
  • And then press save when making a change (not very junior staff friendly)
  • Only one column for Magmi
  • For each version or translation of the product title you need to add a new row in the CSV, rather than a column

Pausing to Consider the Importing of Product Data Implications

The mention of Magmi previously needs some further explanation.

In option 1 you would have a spreadsheet like this:

123,admin,"The UK title here","The US title here","The DE title here","The AU title here"

And then one row in the sheet for each product. Nice & simple, cookies in a row.

However in Option 2, you would have a shorter column count, but when loading products you would have to have each title set on a new row

123,ebay_uk,"The UK title here"
123,ebay_us,"The US title here"
123,ebay_de,"The DE title here"
123,ebay_au,"The AU title here"

So option 2 has layers of an onion.

In Summary

As we’ve just discovered, there are two ways of handling the listing title attribute in Magento.

Option 1 – The Simple way

Option 2 –  The neater, but more complicated way

Now it’s time to think about you and your business.

So which way is better?

Well that depends on a couple of factors.

If you only intend to sell on one eBay and/or Amazon site, then going with Option 1 is the best way for you.

It’s the way we teach you in the setup course here because it’s simple.

It also keeps the use of Magmi for importing products a lot simpler as well. You have just one row per product and change the titles over using columns in the Excel/CSV file.

However if you intend to sell on multiple eBay sites and multiple Amazon sites, then Option 2, could be better for you.

Notice my wording here, “could be“.

It’ll make the administration pages in Magento simpler to use, you won’t have say 7 Magento attributes for titles on the page. But on the flip side this causes complexities that you could struggle with.

Specifically that to change a title for one of the other eBay or Amazon sites, you’ll need to switch store view to that view, then change the title. And when it comes to Magmi you don’t just have one product row to import anymore, you have to import the same product in potentially 7 times in the example just to set the title on one product.

Which way would you choose Matt?

I would personally go with option 1.


Because I like simple.

Yes we would have multiple attributes on the product page and yes it would make it longer. However practically speaking, it would make it a lot easier for staff to use and a hell of a lot easier for me to use in the spreadsheets for creating and updating products using Magmi.

Think about that columns shown in option 1 back up this article.

This is dead easy to work with in excel. One row is one product.

For option 2, well thats 7 rows for 1 product and that’s not nice to work with and to even code against.

And with that said…

BOTH options are viable and I hope I’ve helped you understand the options you have when it comes to the layout of product attributes in Magento for use on the marketeplaces.

Oh and of course, great question Felix! I sincerely hope this article helps you make a decision,

Co-Founder of
Image source: here

2 replies
  1. GadgetBoy
    GadgetBoy says:

    I am setting this up now and whilst I agree option 1 is much simpler, how can I use this option to suit my multi store magenta setup? I am setting magneto up with a different store view for different domain names. Each domain will be for a different country and language (ie., .de, .fr, .es), so each store view needs the magneto title in a different language. As far as I can see you can only take the single product title attribute (English) to use in magento. Am I wrong? Or will I need to opt for option 2?

  2. Dale Holden
    Dale Holden says:

    Hi Matt
    I did Option 1 and yes it is simple. The only issue i have is keeping all the SKU’s at the correct price based on foreign currency fluctuation on everyday currency market.
    I know most sellers should have a buffer built in but you can get caught out. It would be great to see a vldeo on how you could process a daily price currency check or 4 times a day and update and if this could be done automatically via a cron job.



Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *