OPINION
A VA uploading tracking looks cheap. The line item isn’t the cost.
The $300 is the part you can see. It’s the cheapest part.
Forwarding tracking emails to a VA feels like the obvious move. It’s a tiny monthly number, and the work disappears off your plate. The trouble is everything that number doesn’t include: the lag, the support tickets, the errors, and the fact that none of it ever gets faster.
Here’s a setup almost every dropshipper recognizes. A merchant on a public forum described theirs like this:
I have a VA that I forward all the tracking emails to and he uploads the tracking numbers to the order. The issue is (1) I have to pay him, and (2) because he is in a different time zone there is often a 12+ hour delay between the tracking arriving in our inbox and the customer getting it.
That’s the honest version. The $300/mo is real, and it’s the line item everyone budgets for. But it’s the smallest cost in the list. The expensive ones don’t show up on an invoice. They show up in your support inbox and your repeat-purchase rate.
Cost 1: the timezone lag
The tracking number arrives in your inbox the moment the supplier ships. It then sits there. It sits through the night, through your VA’s off-hours, until their shift starts and they work the queue. By the time it lands on the Shopify order and the customer gets notified, 12+ hours have often passed, sometimes a full day on weekends.
This is worse than slow shipping, and it’s worth being precise about why. Slow shipping is a real-world constraint: the package genuinely hasn’t moved yet. This is different. The information already exists. The customer could be reassured right now. The only thing standing between them and that reassurance is that a human in another timezone hasn’t copied a number into a box yet. You’re sitting on good news and not delivering it.
Cost 2: WISMO tickets
Every hour of lag manufactures “where is my order” tickets. A customer who paid two days ago, sees no movement, and gets no tracking email does the obvious thing: they email you. That ticket exists only because the tracking that would have answered their question was sitting unposted in your inbox.
And you pay for it twice:
- Once for the VA who’s eventually going to upload the tracking.
- Again for the support time (yours or another VA’s) spent answering a question the system should have answered automatically.
The cruel part is the order of operations. The support ticket often arrives beforethe tracking gets posted, so your team is manually telling customers “it’s on the way” while the actual tracking number sits ten lines down in the same inbox.
Cost 3: the error rate
Copy-paste at volume is copy-paste with mistakes. When a human is moving tracking numbers from emails into orders all day, some percentage go wrong:
- Tracking number pasted onto the wrong order. Now two customers are confused.
- Wrong carrier tagged, so the tracking link 404s or points at the wrong courier’s site (YunExpress tracking dropped into a 4PX field, or vice versa).
- A split shipment where only one of two tracking numbers gets entered.
Each of these is a support fire, and each one is a small hit to trust. A customer who clicks their tracking link and lands on someone else’s parcel (or a dead page) doesn’t think “data entry error.” They think “is this store even real?” That doubt is far more expensive than the $300.
Cost 4: it doesn’t compound
This is the one that actually matters long term. A VA at 100 orders a day is doing 100 orders of manual work. Tomorrow at 100 orders, it’s 100 orders of manual work again. The thousandth upload takes exactly as long as the first.
Nothing is learned. Nothing is reusable. When a new supplier starts sending dispatch emails in a weird format, your VA figures it out. That knowledge then lives in one person’s head and evaporates the day they take a holiday or quit. You’re renting throughput. The work never compounds. Every order you grow into is another order of the same cost, forever.
What the job actually is
Strip it down and the task is deterministic:
- 1
Read an email
Pull the tracking number, carrier, order reference, and SKUs out of the body, the HTML, or a PDF shipping label.
- 2
Find the order
Match it to the right Shopify order by reference, then customer and SKU.
- 3
Write the tracking
Fulfill the right line items with the right tracking so Shopify notifies the customer.
That’s a rules-and-pattern job. It’s the kind of work software is genuinely good at and humans are genuinely bad at: repetitive, time-sensitive, and unforgiving of small slips. It does not need judgment. It needs to happen instantly, every time, at any hour.
That’s the gap Relayship fills. You forward supplier dispatch emails to one address; it extracts the tracking, runs a match cascade against your Shopify orders, and (above your confidence threshold) auto-fulfills the right line items with the right tracking via Shopify’s fulfillmentCreateV2. Dispatch email to customer notification typically lands in under ~60 seconds, day or night, no shift to wait for. It learns each supplier’s format over the first handful of shipments, so the thousandth upload is easier than the first. And it only bills you when tracking actually lands on an order. Failed extractions, duplicates, and non-dispatch emails are free.
An illustrative monthly comparison
Rough numbers to make the point: illustrative only, not a quote or a measured benchmark. Your mix of suppliers and order volume will move these around.
| What you’re paying for | VA approach | Automated approach |
|---|---|---|
| The visible line item | ~$300/mo | From $19/mo (500 uploads) |
| Time from dispatch to customer | Often 12+ hours | Typically under ~60 seconds |
| WISMO tickets from the lag | Manufactured by every hour of delay | Removed at the source |
| Copy-paste errors | Inevitable at volume | Deterministic match, no retyping |
| Does it get faster over time? | No — linear forever | Yes — learns each supplier |
None of this means “fire your VA.” It means stop spending a human on the one part of their job that’s pure mechanical transcription. Keep them on the work that actually needs a person — supplier disputes, refunds, the judgment calls, the messy edge cases a rule can’t cover. Hand the deterministic part to something that does it in seconds and never sleeps.
The honest caveat
If your volume is genuinely tiny (a handful of orders a week), a VA or even doing it yourself is fine, and you don’t need any of this. The math tips when the lag starts generating real ticket volume and the manual hours stop being trivial. If you’re there, it’s worth a closer look at exactly what a person is doing that a deterministic pipeline could do instead.
Start 14-day trial VA vs. Relayship, compared
More on the mechanics and trade-offs over on the blog.