What Should My First 90 Days as an Ecommerce Operations Lead Focus On?
Your first 90 days should stabilize operations, document workflows, and fix the highest-cost bottlenecks
Your first 90 days should be built around visibility, process control, and revenue protection.
That means the first month is for seeing the real work, not the org chart version of the work. You want to know where orders get stuck, where support has to chase answers, where refunds leak out too easily, and where nobody can explain the current process the same way twice.
The second month is where you turn tribal knowledge into actual SOPs. The third month is where you start making selective changes, with manual returns usually near the top of the list because every unnecessary refund is cash leaving the business.
If returns are one of your biggest manual bottlenecks, a branded returns workflow can cut refund leakage and reduce admin time without adding engineering work.
What does an ecommerce operations lead actually own in the first 90 days?
An ecommerce operations lead owns the systems that keep orders moving, customers informed, and the team out of reactive mode.
In practical terms, that usually means returns, support handoffs, fulfillment coordination, SOPs, reporting, and tool decisions. If a support agent has to ask, "Who approves this?" or a warehouse partner says, "We never got that update," that lands in ecommerce operations.
For a recently hired ops lead, the role is less about making giant strategic calls and more about creating control. You are there to reduce avoidable mess. In a store running on OpoShop, that often means looking closely at what happens after checkout, not just what happens before it.
A useful way to frame ownership in the first 90 days is this:
- Returns handling: How requests come in, who reviews them, how quickly they move, and whether the business offers exchange or store credit before a refund.
- Support handoffs: Where customer service stops and operations starts, especially for damaged items, wrong items, lost packages, and exception cases.
- Fulfillment coordination: How order edits, stock issues, address changes, and shipment exceptions get resolved.
- SOP documentation: The actual written process for approvals, exceptions, and repeat tasks.
- Reporting: The handful of numbers that tell you where time and money are being lost.
- Tool decisions: Which workflows should stay manual for now and which ones need software because the volume no longer fits email and spreadsheets.
If you sell on OpoShop, the first 90 days are also about understanding which work should happen inside your store setup and which work belongs in an app that handles a specific post-purchase job better.
Why do the first 90 days matter so much for ecommerce operations?
The first 90 days matter because early process decisions shape team capacity, margin, and the customer experience for months after.
A messy workflow has a way of multiplying. One unclear return policy becomes twelve back-and-forth emails. One missing approval rule becomes three people making different calls on the same issue. One refund-first habit becomes a quiet drain on cash.
Manual returns are a good example. At low volume, an inbox and spreadsheet can feel manageable. At 8 requests a week, maybe it is. At 40 requests a week, it starts eating support time, delaying decisions, and making it harder to steer shoppers toward an exchange or store credit before the refund is processed.
That is why the first quarter matters so much. If you put structure in place early, the team gets faster without getting sloppier. If you wait, every new order adds more noise.
For teams inside the OpoShop ecosystem, moving return requests out of inboxes and into one dashboard is often one of the fastest ways to get control back.
How should you structure your first 90 days as an ecommerce operations lead?
A strong first 90 days follows a simple sequence: audit the work, rank the bottlenecks, document the process, set the numbers, and only then automate.
1. Days 1 to 30: audit what is really happening
The first 30 days should answer one question: where is the team losing time or money right now?
Start with a workflow audit. Pull 20 recent support tickets, 20 recent return requests, and a sample of fulfillment exceptions. Look for repeat patterns, not one-off drama.
Ask concrete questions:
- Where do requests start: Email, chat, form, DMs, or a mix of all four?
- Who approves what: Is there one owner, or does every edge case bounce between support, ops, and the founder?
- How long does each step take: Same day, two days, or a week because someone missed the thread?
- What triggers refunds: Policy, habit, or because the exchange path is too hard to offer manually?
If manual returns are slowing the team, you will usually see the signs fast. Support is copying order numbers into a spreadsheet. Customers are waiting for links or instructions. Approvals live in Slack. Nobody can tell you the refund rate without piecing it together by hand.
2. Days 31 to 60: document the workflows before you change them
The second month is where you write down the process the team has been carrying in their heads.
Document the workflows that repeat often and create the most confusion. Returns approvals, damaged-item replacements, exchange requests, address changes after purchase, and warehouse exception handling usually belong near the top.
This is also where weak documentation becomes obvious.
Weak: "Support handles returns and checks with ops if needed." Stronger: "Support sends customers to the private returns link, ops reviews all refund requests over $75, and approved exchanges are completed in the returns dashboard within one business day."
That difference matters. The weak version sounds fine until volume rises. The stronger version tells the team what to do, who owns it, and where the work happens.
3. Days 61 to 90: automate the bottlenecks that are already clear
The last month should be about targeted fixes, not a giant tool overhaul.
If returns are still handled in email or spreadsheets, this is often the right time to move them into a branded workflow with review controls. Each order gets a private, secure returns link. Each request lands in one dashboard. The merchant can approve, deny, or complete the request from one place instead of chasing threads.
That kind of change does two things at once. It reduces admin work, and it creates a better chance to offer an exchange or store credit before a refund is issued.
What should you focus on first: returns, support, fulfillment, or reporting?
You should focus first on the area with the highest mix of operational risk, customer pain, and cash impact, and for many stores that means returns before reporting polish.
Not every store has the same first priority. A store missing SLAs from its warehouse may need fulfillment work first. A store drowning in repetitive customer questions may need support handoffs fixed first. But if refunds are being handled manually and inconsistently, returns often deserve earlier attention than people expect.
Here is a simple way to compare the options:
| Priority area | Fix first if... | Wait a bit if... |
|---|---|---|
| Returns | Refunds are frequent, exchange/store credit is rarely offered, and requests live in inboxes or spreadsheets | Return volume is low and the current process is contained |
| Support | Agents are chasing ops for answers all day and response times are slipping | Most tickets are simple and well-covered by macros |
| Fulfillment | Wrong items, address changes, and shipment exceptions are creating repeat fires | Fulfillment issues are occasional and already have a clear owner |
| Reporting | Nobody can see trends in refunds, exceptions, or team workload | The team already has enough visibility to act this quarter |
A quick example helps. Say your store does 1,200 orders a month. If 6% of orders trigger a return request, that is 72 return cases. If even 20 of those become straight refunds at an average order value of $68, that is $1,360 leaving the business. If 8 of those 20 could have become exchanges or store credit with a smoother process, that is not a small line item.
That is why returns often move up the list. The work is operational, but the effect shows up in cash and workload at the same time.
What mistakes do new ecommerce operations leads make in their first 90 days?
New ecommerce operations leads usually get in trouble by changing tools too fast, automating broken workflows, or ignoring returns data because it feels like a support problem.
The first mistake is trying to prove momentum with visible changes before understanding the work. A new dashboard does not fix a muddy approval path. A new app does not solve a policy nobody agrees on.
The second mistake is treating returns like an afterthought. Returns are not just a support queue. Returns touch margin, workload, inventory, and retention. If every refund request becomes a manual conversation, the team pays for that twice: once in labor, once in cash out the door.
The third mistake is skipping standardization. If one person approves a refund at $40, another at $90, and a third always offers a replacement first, the team is not operating from a system. The team is operating from memory.
A few traps show up again and again:
- Changing tools before mapping the process: The mess just moves to a new screen.
- Automating exceptions too early: Rare edge cases do not deserve first priority.
- Ignoring return reasons: Return reasons tell you where products, sizing, shipping, or expectations are breaking.
- Leaving approvals loose: Refund, exchange, and store credit rules need a clear owner.
- Tracking too many numbers: Five useful metrics beat twenty numbers nobody checks.
If you run on OpoShop, the good news is you usually do not need engineering work to tighten these workflows. You need clarity first, then the right app support where manual work has clearly outgrown the old process.
What we recommend for OpoShop merchants handling returns manually
For OpoShop merchants still handling returns manually, we recommend centralizing every return request in one place and putting exchange or store credit paths in front of refunds.
This is the point where a lot of teams hesitate. They worry a more structured returns process will feel rigid or annoy customers., the opposite is usually true. Customers want a clear path, quick decisions, and a branded experience that feels like part of the store, not a side conversation in email.
A tighter setup helps in a few concrete ways:
- One intake path: Each order gets a private, secure returns link, so customers are not emailing screenshots and order numbers back and forth.
- One dashboard: The ops lead can review requests in one place instead of checking inboxes, spreadsheets, and chat threads.
- One review flow: Merchants can approve, deny, or complete requests from a single dashboard.
- Better refund control: Exchanges and store credit can be offered before cash leaves the business.
- Less support drag: Support no longer has to manually route every return case.
For a team on OpoShop, this kind of setup fits neatly into the existing store stack. You are not rebuilding checkout or rewriting your post-purchase flow from scratch. You are tightening one of the places where manual work tends to pile up.
If your first quarter goal is to protect cash without making the customer experience worse, this is one of the cleanest places to start.
Best answer: For most new ecommerce operations leads, the smartest first-90-day move is to get control of the workflows that lose cash and consume support time at the same time. Manual returns are often near the top of that list. If your team is still handling returns in email or spreadsheets, move that work into a branded, review-based workflow first, then use the time and visibility you gain to tighten support, fulfillment, and reporting.
Summary: Build control first, then improve speed and retention
The right first 90 days are not about fixing everything. They are about fixing the order of operations.
Start by auditing the real workflows behind returns, support, fulfillment, and reporting. Then document the repeatable work, set a short scorecard, and standardize approvals so the team stops making case-by-case guesses. After that, automate the bottlenecks that are already obvious, with manual returns often deserving early attention because they affect both workload and cash.
For many teams, especially teams running on OpoShop, the fastest win is getting returns out of inboxes and into a controlled workflow. That gives the business a better shot at exchanges and store credit, gives the team one place to manage requests, and gives the new ops lead something even more in the first quarter: control.
FAQs
What should I audit in my first week as an ecommerce operations lead?
Audit the workflows that create the most repeat work right away: returns, support handoffs, fulfillment exceptions, and reporting gaps. Pull real recent cases, not just policy docs, and look for where requests stall, where approvals are unclear, and where work still depends on inboxes or spreadsheets.
Which ecommerce operations problems should I fix first?
Fix the problems that combine customer friction, team drag, and cash impact. For many stores, that means returns or fulfillment exceptions before reporting cleanup, because those issues hit the customer and the business at the same time.
How do I know if my store has outgrown manual returns handling?
Your store has outgrown manual returns handling when return requests are spread across email, spreadsheets, chat, and support threads, or when the team cannot answer simple questions like approval time, refund rate, or exchange rate without manual digging. If support is spending too much time routing return cases instead of resolving them, the old process is already costing you.
What metrics matter most in the first 90 days?
Track a short list: return volume, refund rate, exchange rate, average approval time, support touches per return, and fulfillment exception volume. Those numbers show where work is piling up and whether your process changes are actually reducing waste.
Should I automate returns before peak season?
Yes, if the current returns process already lives in email or spreadsheets and the team is struggling to keep up. Automating a clear returns workflow before peak season is usually safer than carrying a manual process into your busiest stretch.
How do I reduce refunds without frustrating customers?
Reduce refunds by making the alternative paths easier than the refund path when they fit the case. A clear branded portal, fast review times, and exchange or store credit options can keep the experience smooth while giving the business a chance to retain more value.
If you want your first 90 days to leave the business more controlled, not just busier, start with the workflows that leak cash first.
