E-commerce VA.

Also posted as

Shopify assistant, Amazon VA, product data assistant, ecommerce ops assistant, listing specialist

Core loop

Product data → listings → orders and inventory → support → weekly numbers

Hours

20–40/wk. Support seats often need overlap with the store's peak hours.

Hardest part

Being responsible for an account you do not control the settings of

Easiest way in

Product data cleanup on a fixed price. Provable in a week, low risk for the client.

Progress is saved in this browser only. Nothing is sent anywhere.

1. 01

   How a store actually works

   You can explain the difference between a storefront and a marketplace, follow an order through its whole lifecycle, and never confuse a product with a variant or a SKU again.Time splitRatesRed/green flags24 min

   • A storefront is the merchant's own shop, like Shopify. A marketplace is someone else's shop that you sell inside, like Amazon. On a storefront you own the rules. On a marketplace you obey them or get suppressed.
   • A product is the thing. A variant is a version of it: size, colour, pack count. A SKU is your internal code for a specific variant. One product, five sizes, three colours is one product and fifteen SKUs.
   • The order lifecycle: placed, paid, fulfilled, delivered, and then possibly returned or refunded or charged back. Every one of those states has a different owner and a different clock.
   • Money is not one number. Revenue minus refunds minus fees minus cost of goods is what the owner actually keeps, and confusing revenue with profit in a report will lose you credibility fast.
   • FBA means Amazon stores and ships it. FBM means the merchant ships it. Which one applies changes who handles the return, who eats the shipping, and what you can promise a buyer.
   • You are staff, not the owner. You report numbers and flag risks. Pricing strategy, advertising budget and product decisions belong to the person whose money it is.

   Worked example — One product, written properly

   Before

   Waterproof jacket - blue/green/black, S M L XL, $89

   After

   Product: Tidewater Coastal Shell Jacket

   Variants: 3 colours x 4 sizes = 12 SKUs

   SKU pattern: TW-JKT-CST-{COLOUR}-{SIZE}, e.g. TW-JKT-CST-NVY-M

   Each SKU carries: barcode (GTIN), price, compare-at price, cost, weight, inventory quantity, location

   Shared at product level: title, description, vendor, product type, tags, images, SEO title, meta description

   Channel mapping: Shopify handle coastal-shell-jacket / Amazon parent ASIN with 12 children

   Everything downstream, imports, inventory, reporting, ads, breaks if the SKU structure is sloppy. Fix it at the start or fix it forever.

   Where the hours go

   Where an ecommerce VA's week goes

   40 hrs/week at a small DTC brand doing a few hundred orders a month across Shopify and Amazon.

   • Customer support: emails, returns, WISMO30%

     "Where is my order" is the single most common message in all of ecommerce.

   • Order and fulfilment ops20%

     Exceptions, stuck orders, address fixes, courier chasing.

   • Product data and listings18%

     Uploads, edits, variant fixes, image handling.

   • Inventory tracking and reordering14%

     Small slice, biggest financial consequence. A stockout on a hero product is brutal.

   • Reporting and admin10%

     Daily numbers, weekly summary, reconciling payouts.

   • Marketing support: email, ads, content8%

     Where you grow into the higher-paid work. Volunteer for this.

   Half the week is support and order problems. Get ruthlessly efficient at those two, and you free up the hours to learn the work that actually pays.

   What this pays

   What ecommerce VA work pays

   Ecommerce splits sharply. Uploading products is the cheapest work in the VA market; running ads or inventory forecasting is among the best paid. Same job title, triple the rate.

   Swipe the table sideways →

   Experience	Hourly (USD)	Monthly (USD)	What changes it
   Entry — listings and data entry	$3.50–5	$600–850	Product uploads, image renaming, basic edits. Highly replaceable.
   Junior — store ops + support	$5–7	$850–1,200	Orders, returns, customer emails, simple Shopify edits.
   Mid — listing optimisation + inventory	$7–11	$1,200–1,800	You write listings that convert and stop the store running out of stock.
   Senior — PPC / marketplace specialist	$10–17	$1,700–2,700	Amazon PPC, Klaviyo flows, marketplace strategy. Directly tied to revenue.
   Lead — ecommerce manager	$15–25	$2,500–4,000	You own the P&L levers: margin, ad spend, inventory, and other VAs.

   This table has 4 columns and scrolls horizontally on small screens.

   Same skill, different client

   • Verse's job board (median)$3.50

     Most live ecommerce posts are asking for the entry tier. Read the scope before the rate.

   • Amazon PPC specialist$10–17

     Highest-paid ecommerce niche for VAs, per 2026 agency rate cards. Worth specialising in.

   • US brand, direct$7–18

     Especially DTC brands doing $1M+. They understand that a good ops person pays for themselves.

   • Per-listing project work$8–25 per optimised listing

     Good side income and an easy first sale. Sell 20 listings, not 20 hours.

   Sources: Verse's live board (n=2,081), OnlineJobs.ph ecommerce tiers ($4.50–12), 2026 agency rate cards ($10–17 for Amazon PPC).

   Red flag / green flag

   Spot the difference

   Same situation, two ways it can go.

   The job post says

   Red flag

   "Ecommerce VA. Manage our Shopify, Amazon, eBay, Etsy and Walmart stores. Handle all customer service, run our Facebook and Google ads, do SEO, design graphics and manage inventory. $500/month."

   That's four specialist roles. At $500/month for 160 hours, you'd be earning $3.12/hr to be personally responsible for a business's entire revenue operation. When something breaks, and it will, it's your fault.

   Green flag

   "Shopify + Amazon VA for our skincare brand (~600 orders/mo). Daily: order exceptions, customer emails via Gorgias, inventory check. Weekly: listing updates, reorder report. $1,100/mo, 30 hrs/wk, 2 hrs PST overlap. Not your job: ads, design, or SEO."

   Two channels, an order volume so you can judge the workload, named tools, and an explicit 'not your job' list. That last line is the strongest green flag in any ecommerce post.

   You're given store access on day one

   Red flag

   Accepting the owner's own login and password over Slack, with full admin rights.

   Two problems. Sharing credentials breaks Shopify and Amazon's terms and can get the store flagged. And if anything goes wrong — a deleted product, a refund error, a breach — there's no audit trail separating you from them. That ambiguity always resolves against the VA.

   Green flag

   "Can you add me as a staff account with my own email? For Shopify: Orders, Products, Customers, and Reports — I don't need Settings or Finances to start. For Amazon: a User Permissions invite. That way everything I do is logged under me, and you can revoke it in one click if we ever part ways."

   You've asked for less access than offered, explained why, and made the audit trail point at yourself deliberately. Owners find this reassuring, and it protects you when something inevitably breaks.

   Do this

   Pick any real store with variants and reverse-engineer its structure by browsing the public site. Map its products, variants, collections and navigation.

   Hand in: A one-page structure map: how many products, the variant logic, the collection hierarchy, and three things you would restructure.≈ 40 min

   Check before you call it done

   • You distinguished products from SKUs with actual counts
   • You described the collection logic, not just the menu labels
   • You proposed a SKU naming pattern for their catalogue
   • Your three restructure suggestions each have a reason attached

   Mark module done
2. 02

   Shopify admin without breaking anything

   You can build out a store in a development environment: products, collections, navigation, pages, shipping and the legal pages, and you know what you must never touch on a live store.WorkflowTools1 template40 min

   • Get a Shopify development store or a trial and build in there. Nobody will hand a stranger their live admin, and a screenshot of your own store is the credential.
   • Never edit a live theme directly. Duplicate it, edit the duplicate, preview, then publish. This one habit separates people who get kept from people who get quietly removed.
   • Collections come in two flavours. Manual collections you curate by hand, automated collections build themselves from conditions on tags, type or price. Automated ones scale, so build the tags to support them.
   • Navigation is not the collection list. Menus are their own structure and can point anywhere, so a tidy collection list with a chaotic menu is still a bad store.
   • Shipping settings are where real money leaks. Zones, rates, weight brackets and free-shipping thresholds all interact, and a wrong weight on one variant can quietly under-charge every order.
   • The legal pages, refund, privacy, terms and shipping policy, must exist and must match what support actually does. If the policy says 30 days and you tell buyers 14, that is now the owner's problem.
   • Apps are not free. Every one adds monthly cost and often page weight. Do not install anything on a client store without written approval.

   Worked example — The pre-change checklist you run every time

   1. What exactly changes, in one sentence, and which SKUs or pages it touches.

   2. Do I have written approval from the owner for prices, discounts or policy text?

   3. Backup: theme duplicated, or products exported to CSV with a dated filename.

   4. Make the change on a small sample first. Two products, not two hundred.

   5. Verify on the live storefront, not just the admin. Check mobile.

   6. Log it: what, when, who approved, and how to reverse it.

   Six steps, about four minutes. It is the difference between one bad afternoon and a catalogue you cannot un-break.

   Workflow

   Making a change on a live store without breaking it

   Any edit to a live, revenue-generating store. Treat every one as potentially destructive.

   1. 1

      Ask what the change is FOR before you make it

      "Change the product title" usually means "we're not ranking" or "customers are confused". Knowing which changes what you do.

   2. 2

      Duplicate the theme before touching anything visual

      Shopify: Online Store → Themes → Duplicate. Ten seconds, and it's the difference between a mistake and a disaster.

   3. 3

      Screenshot the before state

      Every time. When someone says "it used to say something different", you'll want the receipt.

   4. 4

      Change one thing, then check the storefront

      Not five things then check. When something breaks, you want to know exactly which change did it.

   5. 5

      Test the full path: product → cart → checkout

      Especially after touching variants, inventory or shipping. A broken checkout is silent and it costs money every minute.

   6. 6

      Log it

      Date, what changed, why, who asked, before/after. Five seconds now, saves an hour of forensics later.

   Where this breaks: Bulk-editing during peak hours. Do bulk operations when the store is quiet — usually 2–6am in the store's main market, which for a PH-based VA is conveniently the middle of your shift.

   Tool comparison

   The ecommerce stack

   Learn Shopify admin and one helpdesk properly. Everything else you can pick up on the job — but nobody will let you near a store if you can't navigate the admin confidently.

   Swipe the table sideways →

   Tool	Best for	Learning curve	Cost	Verdict
   Shopify adminLearn first	The platform behind most small DTC brands.	Easy — a week on a free dev store	Free to practise (dev store)	Start here today. Create a free development store, build a fake shop, break it. This costs nothing and is the fastest route to hireable.
   Amazon Seller Central	Marketplace selling. Utterly different mental model to Shopify.	Hard — the UI is hostile by design	Client's account	Painful but valuable. Amazon skills pay the most in ecommerce precisely because most people give up learning it.
   GorgiasLearn first	Ecommerce-specific helpdesk. Pulls order data into the ticket.	Easy — 2 days	$10+/mo (client pays)	The one most named in ecommerce job posts. Macros and rules are what make you fast — learn those, not the interface.
   Zendesk / Freshdesk	Bigger operations, multi-channel support.	Medium	Client's	Same concepts as Gorgias, more enterprise. Learn one helpdesk and the rest transfer in a day.
   Klaviyo	Email and SMS flows. Where a surprising share of DTC revenue comes from.	Medium — a couple of weeks	Free to 250 contacts	The highest-leverage skill on this list. An abandoned cart flow you build can be traced directly to revenue, which is the best possible argument at rate review time.
   Google Sheets	Inventory, reorder points, reconciliation, every report.	Easy to start, deep to master	Free	Genuinely more important than any app here. VLOOKUP, pivot tables and conditional formatting will do more for your rate than a fifth platform.

   This table has 5 columns and scrolls horizontally on small screens.

   Copy-paste

   Steal this

   Swap the bracketed bits and send.

   Store change log

   One sheet, every change, forever. The first thing you show when someone asks what happened.

   Copy template to clipboard

   Date	Time	What changed	Where	Why / who asked	Before	After	Tested	Reverted?
   Mar 4	03:15	Product title	SKU TW-114	Owner — not ranking for "reef safe"	"Sunscreen SPF50"	"Reef-Safe Mineral Sunscreen SPF 50"	✅ PDP + search	—
   Mar 4	03:40	Price	SKU TW-220	Owner Slack 3/3	$24.00	$21.60	✅ cart + checkout	—
   Mar 5	02:10	Inventory sync off	App: StockSync	Was overwriting manual counts	On	Off	✅	—

   RULES
   • Log BEFORE you make the change, not after. If you get interrupted, the record still exists.
   • "Why" must name a person and a date. "Owner asked" with no date is worthless in a dispute.
   • Anything you can't revert in under 5 minutes needs written approval first.
   
   ⚠ NEVER WITHOUT WRITTEN APPROVAL
   • Deleting products (archive instead — deletion loses order history)
   • Changing prices on live products
   • Editing anything in Settings: shipping, taxes, payments, checkout
   • Installing or uninstalling apps
   • Bulk operations over 50 records
   • Anything touching customer data or refunds

   Do this

   Build Tidewater Supply Co in a Shopify development store. Ten products with variants, three collections including one automated, a working nav, an About and a Contact page, one shipping zone with two rates, and all four legal pages.

   Hand in: Screenshots of the admin and the live preview, plus your change log for the build.≈ 110 min

   Check before you call it done

   • At least one automated collection driven by tags
   • Every variant has a SKU following your naming pattern, plus weight
   • Shipping rates make sense against the product weights
   • The refund policy states a specific number of days
   • The theme you edited is a duplicate, and you can say which
   • The change log has a reversal note for each entry

   Mark module done
3. 03

   Product data and the CSV import that eats catalogues

   You can build a product master sheet and run a bulk import without overwriting live data, with a QA pass that catches errors before customers do.Workflow2 templates42 min

   • The master sheet is the source of truth: SKU, parent, title, vendor, type, category, price, compare-at, cost, barcode, inventory, variant options, weight, dimensions, tags, SEO title, meta description, image filenames, status.
   • One row per SKU. Not one row per product with sizes crammed into a cell. Every tool you will ever use expects one row per sellable unit.
   • The dangerous part of a CSV import is blank columns. In many importers a blank cell does not mean leave it alone, it means set it to blank. Export the current data, edit that file, and only include the columns you intend to change.
   • Test on two products first. Always. Import a two-row file, check the result in the admin and on the storefront, then run the rest.
   • Title conventions matter more than clever copy. Pick a formula, apply it everywhere: Brand + Product + Key Attribute + Size or Pack. Consistency is what makes a catalogue searchable and filterable.
   • Image filenames are data too. sku-01.jpg, sku-02.jpg beats IMG_4471.jpg, and it makes matching images to rows in a bulk upload possible at all.
   • Build the QA pass as a checklist someone else could run: duplicate SKUs, missing barcodes, prices below cost, zero weights, titles over the character limit, orphan variants, broken image links.

   Worked example — Product data, before and after

   Before

   SKU: (blank) | Title: coastal shell JACKET blue large | Price: 89 | Weight: 0 | Tags: jacket,waterproof,blue,large,new,sale,Blue,Waterproof

   SKU: (blank) | Title: Coastal Shell Jacket - Blue - L | Price: 89.00 | Weight: 0 | Tags: jackets

   Image: IMG_4471.jpg

   After

   SKU: TW-JKT-CST-BLU-L | Title: Tidewater Coastal Shell Jacket - Waterproof, Blue, Large | Price: 89.00 | Compare-at: 109.00 | Cost: 41.20 | Weight: 620g

   Barcode: 0850041234567 | Inventory: 14 | Option1: Colour/Blue | Option2: Size/Large

   Tags (controlled list): jacket, waterproof, mens, outerwear-ss26

   SEO title: Coastal Shell Jacket, Waterproof - Tidewater Supply Co

   Images: tw-jkt-cst-blu-01.jpg, tw-jkt-cst-blu-02.jpg, tw-jkt-cst-blu-03.jpg

   Duplicate row merged. Net: 340 SKUs became 331 real SKUs, 9 duplicates removed.

   The before rows are two records for the same physical jacket. That is how a store ends up overselling something it does not have.

   Workflow

   A CSV import that doesn't eat the catalogue

   Any bulk product upload or update. This is the single most destructive routine task in ecommerce.

   1. 1

      Export the current catalogue first. Always.

      This is your rollback. Save it somewhere dated and named. Skipping this step is how people lose 800 products at 3am.

   2. 2

      Export a template rather than building a CSV from scratch

      Export 2–3 existing products and use those exact columns. Handmade CSVs fail on column names and ordering you can't see.

   3. 3

      Test with 3 products before the full run

      Non-negotiable. Import three, check them on the storefront, then do the rest. Three broken products is a fix; 800 is an incident.

   4. 4

      Watch the handle and SKU columns like a hawk

      In Shopify the Handle is the unique key. A wrong handle doesn't create a new product — it OVERWRITES an existing one. Silently.

   5. 5

      Check the variant rows

      Variants are child rows with a blank title and a repeated handle. Sort or filter a CSV wrong and you'll orphan every variant in the file.

   6. 6

      Verify on the storefront, not just in admin

      Check a parent product, a variant, a price, an image and the inventory count. Admin can look correct while the storefront is broken.

   Where this breaks: Opening the CSV in Excel. Excel silently mangles data — it strips leading zeros from SKUs, converts long numbers to scientific notation, and reformats dates. Use Google Sheets, and set every column to plain text on import.

   Copy-paste

   Steal these

   Swap the bracketed bits and send.

   CSV import pre-flight

   Run this every time. The one you skip is the one that costs a weekend.

   Copy template to clipboard

   IMPORT: [what] | Store: [name] | Rows: [n] | Date: [date]
   
   BEFORE
   [ ] Full catalogue exported and saved as [date]-backup-products.csv
   [ ] Backup file OPENED and confirmed not empty (a 0kb backup is not a backup)
   [ ] Template exported from the live store, not built by hand
   [ ] File opened in Google Sheets, NOT Excel
   [ ] All ID/SKU columns formatted as plain text
   [ ] Owner approved the change in writing
   
   DATA CHECK
   [ ] Handles unique — no accidental duplicates (Data → Remove duplicates to check, then undo)
   [ ] Handles match existing products EXACTLY where updating
   [ ] No trailing spaces (TRIM every text column)
   [ ] Prices are numbers, no currency symbols, no commas
   [ ] Inventory quantities are whole numbers
   [ ] Image URLs are public and load (spot-check 5 in a browser)
   [ ] Variant rows have the parent handle repeated and title blank
   [ ] Required fields present on every row
   [ ] Special characters and accents render correctly (encoding is UTF-8)
   
   TEST RUN
   [ ] Cut 3 rows into a separate test file
   [ ] Import the 3
   [ ] Check each on the STOREFRONT: title, price, images, variants, stock, add-to-cart
   [ ] Only then run the full file
   
   AFTER
   [ ] Product count before: [n] → after: [n]. Does the difference match expectations?
   [ ] Spot-check 5 random products
   [ ] Check one variant-heavy product specifically
   [ ] Test a real add-to-cart and reach checkout
   [ ] Logged in the change log
   [ ] Backup file kept for 30 days
   
   IF IT GOES WRONG
   1. Stop. Don't run a second import to "fix" the first.
   2. Tell the owner immediately. Immediately.
   3. Re-import the backup file.
   4. Verify the count matches the pre-import number.

   Product data standards

   Agree once with the owner, then apply mechanically. Consistency is most of what makes a catalogue look professional.

   Copy template to clipboard

   [BRAND] PRODUCT DATA STANDARDS
   
   TITLE FORMAT
   [Brand] [Product name] — [key attribute], [size/count]
   e.g. "Tidewater Reef-Safe Mineral Sunscreen — SPF 50, 100ml"
   • Under 70 characters where possible
   • No ALL CAPS, no "!!!", no emoji
   • Attributes in a fixed order: type → key feature → size
   
   SKU FORMAT
   [BRAND2]-[CATEGORY2]-[VARIANT]-[SIZE]
   e.g. TW-SC-MIN-100
   • Uppercase, hyphens only, no spaces
   • Never reuse a retired SKU
   • SKU never changes once live — the whole system depends on it
   
   DESCRIPTION STRUCTURE
   1. One sentence: what it is and who it's for
   2. 3–5 bullets: benefits, not features ("won't sting your eyes", not "pH 7.2")
   3. Specs block: size, ingredients/materials, weight, care
   4. Shipping and returns line
   
   IMAGES
   • Main: product on white, square, minimum 2000×2000
   • 2–4 lifestyle shots
   • 1 scale/size reference shot
   • 1 back-of-pack or ingredients shot
   • Filenames: brand-product-variant-01.jpg (never IMG_4471.jpg)
   • Alt text on every image — accessibility AND search
   
   INVENTORY
   • Track quantity: ON for everything physical
   • Continue selling when out of stock: OFF unless it's pre-order
   • Low-stock alert at [reorder point]
   
   NEVER
   • Copy a competitor's description (copyright, and it's obvious)
   • Claim health, medical or safety outcomes without approved wording
   • Use "best", "#1" or "guaranteed" without something to back it
   • Leave a variant with no image — it looks broken and it kills conversion

   Do this

   Build a 40-SKU product master sheet for Tidewater from invented data, deliberately including six errors of different types. Then write and run the QA checklist that catches all six.

   Hand in: Master sheet, an import-ready CSV, a QA checklist, and a QA log showing the six errors found and fixed.≈ 90 min

   Check before you call it done

   • One row per SKU, no size lists inside cells
   • A documented SKU naming convention
   • A controlled tag list, no casing duplicates
   • The QA checklist covers duplicates, pricing, weights, character limits and images
   • Your notes state which columns you would exclude from an update import and why

   Mark module done