Guide ✦ Ecommerce

What an online store
should delegate first

Support tickets are the loudest problem, so they get handed over first. They should be last. Start with product listings — the work is visible the same day and mistakes cost nothing.

Book my 30-minute call →
Seth Saavedra
Seth SaavedraAccount manager, Manila
Last reviewed August 2026
Looking for VA work yourself? Apply at staffingsolutions.ph — this guide is written for businesses hiring.

Almost everything an ecommerce owner does inside the admin every day is delegable. Building a product, sorting a collection, setting up a discount, checking an order exception, answering a where-is-my-order.

The decisions — what to stock, what to charge, what the brand sounds like — are yours and take a fraction of the time. Yet most owners spend the week on execution, because handing it over requires writing things down and there is never a moment.

The sequencing matters more here than in most industries, because one of these tasks reaches customers directly. Save that one for last.

Before you read on

Who this is for

✓Worth your time if

  • You are in your store admin most days doing repeatable work
  • Products are half-finished or missing attributes
  • Promotions go out late, or not at all
  • Support is answered in the evening, after everything else

✕Probably not if

  • You have almost no products and almost no orders yet
  • You need a developer — theme code is a different skill set
  • You want someone to own range and pricing strategy
  • You will not write down your policies or your voice
The work, in order

What comes off the owner, and when

Ordered by visibility and safety. Customer support is deliberately last.

Product listings

Products built end to end — copy from your brief, images sized and named, variants, tags, metafields and SEO fields populated rather than left blank.

Catalogue completion

The attribute and specification fields that drive filters and search, filled in across the existing catalogue. Unglamorous, and it changes what customers can find.

Merchandising

Collections curated and re-sorted, bestsellers surfaced, out-of-stock demoted, cross-sells configured.

Promotions

Discounts, bundles and campaign pages built, scheduled, checked live and taken down on time.

Store QA

Broken links, missing images, failing filters and checkout friction found by routine checking rather than by a customer.

Order exceptions

Held orders, address problems and payment flags caught and resolved before dispatch.

Email flows

Welcome, abandoned cart, post-purchase and win-back flows actually finished rather than half-built at launch.

Customer support

Last. Tickets, returns and review responses — to a macro library you build first, with the first week reviewed.

What stays with you

Execution travels. Commercial decisions and anything touching money or your payment stack do not.

  • Payment and payout settingsNever delegated. No access to gateways, bank details or payout configuration.
  • Pricing and marginThey enter your prices and build your discounts. What you charge is yours.
  • Range decisionsWhat to stock, drop or discontinue is commercial.
  • Ad spendBuilding a campaign is not authorising a budget.
  • App installationAnything that changes your stack or adds a subscription comes to you first.
ACCC — consumer guarantees ↗Shopify — staff permissions ↗
From the handovers we run

The first three months

Visible work first, customer-facing work last.

1

Weeks 1–2: twenty products, built end to end

Completely visible output, zero risk, and building twenty products teaches your catalogue, your voice and your conventions faster than any document. Review the first ten closely.

2

Weeks 3–4: catalogue completion and merchandising

Now across the existing catalogue. Filters start working properly, which shows up in search and conversion.

3

Month 2: promotions and store QA

They know products and collections by now, so campaign build is mechanical. Keep the offer decision; hand over the build and the checking.

4

Month 2: order exceptions

Needs enough context to know what is normal. Give them a written escalation rule for anything unusual.

5

Month 3: build the macro library, then hand over support

Write the answers first, together. Then they take tickets with your review for a week. This is the only task where a mistake reaches a customer, which is why it is last.

The mistake that costs a fortnight

Handing over support in week one

Support is the loudest pain, so it is the instinctive first handover, and it fails more often than anything else in ecommerce. In week one the person does not know your products, your policies, your shipping times or your tone — so every answer is either escalated or guessed, and guessed answers go to customers under your brand. The result shows up in reviews. Build the macro library first: your twenty most common questions with the exact answers, your returns policy in plain words, your refund thresholds, and a written rule for what gets escalated. That document takes an afternoon, makes the support handover safe, and is worth having even if you never hire anyone — because right now those answers only exist in your head and they are inconsistent.

Keep reading

Related guides

All guides →
Role

Store manager

Listings, merchandising and promotions.

Read it →
Guide

Shopify tasks to hand over

The task-level split, with permissions.

Read it →
Role

Customer service

Tickets, returns and reviews.

Read it →
Questions

Frequently asked

Can they write product descriptions in our voice?
With a template and three or four examples you like, yes — and for patterned categories the consistency is usually better than yours, because they are not bored on product forty. For brand-led products where the copy is the marketing, brief tightly or keep the copy and delegate the data.
What access do they need?
A staff account with the specific permissions the role requires — products, collections, discounts, orders — and no access to payment or payout settings. Never the owner login, which cannot be scoped and survives the person leaving.
Can one person handle multiple sales channels?
For a small-to-mid catalogue, yes — typically a main store plus one or two marketplaces. Large catalogues or heavy marketplace requirements usually need the catalogue work split out.
Is overnight support coverage actually useful?
Genuinely, yes — this is one of the clearest advantages. Manila covers your evening and early morning, which is when Australian consumers shop and complain, and a same-hour reply at 9pm is a competitive difference most stores do not have.
Is there a minimum term?
Three months, then month to month. It's the same runway you'd give a new local hire to learn your systems, your clients and your standards — and the team members who get a fair run are the ones who stay for years. There are no exit penalties at any point, and if the issue is the person rather than the role, the first-week refund and free replacement cover that separately.
How do you handle confidentiality?
The same way you'd treat any remote team member. Every placement signs an NDA and a confidentiality clause before day one, and they work inside your systems — your email, your CRM, your file storage — so you control what they can see and can revoke access instantly. No client data is stored on our side.