What an Ecommerce Manager Actually Does All Day
When people hear "Ecommerce Manager," they often imagine someone sitting inside Shopify all day.
Uploading products. Changing prices. Updating banners. Checking orders.
That is part of it, but it is a fairly small part of the job.
I've been working as an Ecommerce Manager at a small to medium-sized store for the past two years, and the job is much closer to keeping a small machine running than simply managing a website.
There is rarely a perfect morning where everything is working, the numbers look great, every order is moving through fulfillment, and you can calmly spend the afternoon planning next month's marketing.
Usually, something needs your attention.
So I start with operations.
Before worrying about campaigns or conversion rates, I want to know whether the basic business is actually functioning. Are orders coming through properly? Are there failed transactions sitting somewhere that nobody noticed? Are payments working? Is fulfillment moving? Are couriers collecting orders on time? Has anything gone wrong overnight?
Because there is not much point celebrating a great day in Google Ads if customers are placing orders and those orders aren't getting fulfilled.
This is one of the less glamorous parts of ecommerce, but it is also one of the easiest places for money to disappear.
A failed payment might look like a small technical problem until you realise the customer never came back.
A fulfillment problem might start with one delayed order and turn into a pile of unhappy customers.
A courier issue might have nothing to do with marketing at all, but the customer doesn't care. As far as they're concerned, they bought something from your store and the store didn't deliver it.
So if something is broken, that comes first.
Once the basic machinery is working, I move into performance marketing.
This is where the day gets more interesting.
I'm looking at Google Ads, including Search and Shopping, as well as paid social. Depending on what the store is doing, that can mean building campaigns, launching promotions, adjusting budgets, checking search terms, looking at which products are getting the spend and trying to figure out whether the money is actually producing anything useful.
The important part is that the budget shouldn't simply keep running because nobody remembered to touch it.
If one campaign is producing profitable sales and another is quietly eating money, there is a reason to look at the difference.
Sometimes the answer is obvious.
Sometimes it isn't.
A campaign can have a decent return while still selling the wrong products. Another campaign can look expensive until you realise it is bringing in customers who buy repeatedly. A product can get plenty of clicks and barely any orders.
This is why I don't like looking at advertising in isolation.
Eventually you have to leave the ad platform and look at what happened after the click.
That brings me to the numbers.
Revenue.
Average order value.
Conversion rate.
What is scaling?
What has slowed down?
Where is money being wasted?
Which products are carrying the business?
Which ones are getting attention without producing much in return?
The numbers are useful because they stop you from relying entirely on instinct. But they also have to be connected to what is happening on the site.
So while I'm looking at performance, I'm also looking at the website.
Heatmaps are useful here because analytics can tell you that something happened without always making it obvious why.
You might see that people are reaching a product page but not continuing.
You might find that an important section is being ignored.
You might discover that people are clicking something you didn't expect them to click.
Or you might simply find that the page makes much more sense on a desktop than it does on a phone.
These aren't always dramatic problems.
Sometimes the problem is a small piece of friction that appears at exactly the wrong moment.
The customer has questions about shipping and can't find the answer.
The product information is buried.
The checkout feels unnecessarily complicated.
A button isn't where someone expects it to be.
The page takes too long to load.
None of these things make for particularly exciting marketing meetings. But they can make a very real difference to whether someone buys.
And then, throughout the day, there are the marketplaces.
Amazon.
eBay.
Etsy.
Each one has its own little collection of things that need attention.
Listings need updating. Prices change. Products need monitoring. Performance needs checking. Sometimes something that works well on one marketplace doesn't work particularly well on another.
So the job becomes a constant movement between systems.
Shopify.
Google Ads.
Meta.
Analytics.
Heatmaps.
Merchant Center.
Amazon.
eBay.
Etsy.
Fulfillment.
Payments.
Customer behaviour.
Financial numbers.
It doesn't always feel like one job.
That's probably because it isn't.
An Ecommerce Manager sits in the middle of a lot of different parts of the business and has to understand how they affect one another.
A marketing problem can turn out to be a website problem.
A conversion problem can turn out to be a product problem.
An advertising problem can turn out to be a margin problem.
A revenue problem can turn out to be an operations problem.
And sometimes the thing that looks like a traffic problem isn't a traffic problem at all.
That's why I think the job is better understood as managing the entire customer journey rather than managing a Shopify store.
Someone sees an ad.
They click.
They land on the site.
They look at a product.
They add it to the cart.
They pay.
The order gets fulfilled.
The customer receives it.
Maybe they come back and buy again.
There are a lot of places for that journey to go wrong.
The Ecommerce Manager's job is to keep looking for those weak points.
Where are we losing people?
Where are we losing money?
What is working better than expected?
What deserves more budget?
What needs fixing?
What should we stop doing?
And perhaps most importantly, what is the next problem worth solving?
That last question matters because there is always something you could work on.
You could spend three hours changing product descriptions while a payment issue is preventing customers from completing checkout.
You could increase an ad budget while the landing page is leaking conversions.
You could celebrate a strong ROAS while most of the revenue is coming from products with terrible margins.
You could spend the morning improving a listing that accounts for almost none of the store's revenue.
There is no shortage of work in ecommerce.
The difficult part is deciding which work actually matters.
That is what I think separates managing a store from managing an ecommerce business.
The job isn't simply to keep Shopify updated and make sure the homepage looks nice.
It is to understand what is happening across the business, find the places where things are breaking or money is being wasted, fix them, and then keep looking.
Some days that means working on ads.
Some days it means fixing a checkout problem.
Some days it means staring at a heatmap wondering why everyone is clicking the same completely unexpected thing.
And some days it means going through orders and discovering that the problem has nothing to do with marketing at all.
That's ecommerce.
A lot of moving parts, very little room for assuming everything is fine.
The store is the centre of it, but the job is much bigger than the store.
Keep reading
What You Actually Need to Learn to Become a Shopify Developer
There is a particular kind of job post that makes Shopify development sound much harder than it is....
ShopifyAn Ecommerce Manager Should Be Looking at the Whole Business
There is a strange way some businesses define an Ecommerce Manager. They give someone access to Shopify, ask...