THE COMPLETE GUIDE
Shopify supplier tracking automation without touching a spreadsheet.
Your supplier already emails you the tracking. The work is everything after that.
Getting a tracking number off a dispatch email and onto the right Shopify order is a small task you do dozens of times a day. This guide covers every way to automate it: what works, what breaks, and where each approach is the right call.
What supplier tracking automation means
Supplier tracking automation is one specific job done without you: taking the tracking number from a supplier’s dispatch confirmation and putting it on the matching Shopify order, then letting Shopify notify the customer, with no manual copy, paste, or lookup in between.
That’s it. It sounds trivial because each individual instance is trivial. A dispatch email arrives, you find the order it belongs to, you open the fulfillment dialog, you type or paste the tracking number, you pick the carrier, you hit fulfill. Thirty seconds, maybe a minute. The problem is that you do it dozens or hundreds of times a week, the emails never look the same twice, and the cost of getting one wrong is a confused customer and a support ticket.
The goal is to make that loop disappear: the dispatch email goes in one end, the customer gets a Shopify shipping notification out the other, and you never see it unless something needs a human decision.
Why it is harder than it sounds
If supplier emails were structured data, this would be a solved problem. They are not. Four things make it genuinely hard:
- Format chaos. One supplier puts the tracking number in plain text in the body. The next sends an HTML table. A third attaches a PDF shipping label and writes nothing useful in the email itself. A regex that works for one breaks on the other two.
- Courier variety.A YunExpress number looks nothing like a 4PX number, which looks nothing like a domestic carrier’s. You need to recognize the carrier to set the right tracking URL, and the carrier is often implied rather than stated.
- Order-matching ambiguity.The email rarely contains your Shopify order number. It might have the supplier’s own reference, a customer name, an address, a list of SKUs, or just some unreliable subset. You have to figure out which Shopify order this shipment belongs to from whatever the supplier happened to include.
- Most tools need the supplier to cooperate. The common workaround is to ask the supplier for a structured feed: a shared Google Sheet, a CSV export, an FTP drop. That moves the problem onto someone who has no incentive to help, and it quietly fails the moment they change a column header.
The approaches, compared
There is no single right answer here. It depends on your volume, your suppliers, and how much engineering time you want to spend. Here is an honest map of the options.
| Approach | How it gets the data | Supplier effort | Handles PDF / unstructured email | Best for |
|---|---|---|---|---|
| Manual or a VA | A person reads each email and types into Shopify | None | Yes (a human reads anything) | Low volume, or when you accept a 12-hour VA lag |
| Bulk CSV upload | You compile a spreadsheet and import it | None (but you do the compiling) | No. You extract by hand first | Periodic batches you are happy to assemble yourself |
| Structured feeds (Fulfilleo, syncX, AutoFulfill, EZ Fulfill) | Supplier provides a Google Sheet, CSV, or FTP/SFTP feed | High. The supplier must build and maintain it | No. It relies on the feed being clean | A few big suppliers who will commit to a feed format |
| DIY Zapier + Mailparser | You build parsing rules per supplier email template | None | Partial. Brittle, no PDF, breaks on layout changes | One or two stable suppliers and time to maintain rules |
| Email-parsing AI (Relayship) | It reads the dispatch email body, HTML, or PDF label directly | None | Yes. Built for exactly this | Many suppliers, messy formats, no feeds to negotiate |
One case deliberately falls outside this table: if you are leaving a marketplace entirely (AutoDS, Zendrop, CJ, DSers), the tracking comes back through the marketplace’s own sync, and switching off that marketplace is a different decision. We cover that trade-off in the AutoDS comparison. Relayship is for merchants whose suppliers live in their inbox, not behind a marketplace API.
The honest summary: if you have two stable suppliers who will maintain a clean feed, structured feeds are great and you may not need us. The moment you have ten suppliers, PDF labels, and emails that change shape without warning, parsing the email is the only approach that does not need everyone else to behave.
How email-to-Shopify automation works
Relayship is the email-parsing approach. The whole flow is four steps, and after the one-time setup you never touch the first three again.
- 1
Install and connect Shopify
Install from the Shopify App Store. OAuth grants only the minimum scopes needed to read orders and write fulfillments — nothing more.
- 2
Forward your supplier emails
Relayship mints a unique forwarding address. You add a Gmail or Outlook filter that auto-forwards supplier dispatch emails to it. Your supplier changes nothing.
- 3
Extract and match
Relayship pulls the tracking number, carrier, order reference, SKUs, and address out of the email body, HTML, or PDF label using Gemini, then runs a four-tier cascade to find the matching Shopify order.
- 4
Auto-fulfill or queue
Above your confidence threshold (default 0.9) it auto-fulfills via
fulfillmentCreateV2with the right line items and tracking, and Shopify notifies the customer. Below it, the shipment goes to a human confirmation queue. Typical end-to-end time is under about 60 seconds.
New installs default to review mode. Auto-fulfill is off until you confirm your first real matches. You watch it match your actual suppliers a handful of times, you build trust, and only then do you let it run on its own. Nobody’s first day ends with a wrongly-fulfilled order.
Matching: how the right order is found
Extraction is the easy half. The hard half is deciding which Shopify order a shipment belongs to when the email almost never names it. Relayship runs a four-tier cascade, stopping at the first tier that produces a confident answer:
- Order reference. If the email carries a usable order or PO reference that maps to a Shopify order, that is the strongest signal and it is used directly.
- Customer plus SKU. If there is no clean reference, it matches on the customer combined with the SKUs in the shipment. That is also how split shipments get attributed to the right line items.
- Name and address heuristics. When SKUs are ambiguous, it falls back to matching the recipient name and shipping address against open orders.
- Otherwise, queue it. If no tier clears your confidence threshold, the shipment goes to the human confirmation queue rather than guessing. A wrong fulfillment is worse than a thirty-second review.
Each tier contributes to a combined confidence score. Auto-fulfill only fires above your threshold; everything else waits for a human. That boundary is the whole safety model.
Per-supplier learning
The first few shipments from a new supplier are the least certain. Relayship has never seen their layout. So every correction you make in the queue becomes a few-shot example tied to that supplier’s sending domain. The next email from that supplier is parsed with your correction already in context.
In practice that means the match rate for any given supplier climbs over roughly the first ten shipments and then stays high. You are not training a generic model; you are teaching the system how your specific suppliers write their dispatch emails. A supplier who buries the tracking number in a PDF label gets handled better on shipment eleven than on shipment one.
What it costs
The pricing follows the value metric, and the value metric is deliberately narrow: successful tracking uploads to Shopify, not emails received. Failed extractions, duplicates, verification codes, and non-dispatch emails are all free. You pay when a tracking number actually lands on an order — nothing else.
Plans are Starter at 19 USD for 500 uploads, Growth at 39 USD for 2,000, and Scale at 79 USD for 10,000, with an Enterprise tier for custom volume. Every plan starts with a 14-day free trial. No credit card, no free-forever tier. If you go over your plan in a given month, overage is 0.02 USD per upload with no hard caps, so a busy month never stops fulfillments mid-stream. Full numbers are on the pricing page.
Set it up for your supplier
The setup is the same shape everywhere, but the details differ by where your suppliers come from. These walkthroughs go deeper for the most common cases:
- Alibaba tracking to Shopify: for suppliers sourced through Alibaba, including PDF-label-heavy dispatch emails.
- Private agent tracking to Shopify: for sourcing agents who batch many orders into a single email.
- How it works: the full pipeline, end to end, if you want the mechanics before you install.
FAQ
Does my supplier have to change anything?
No. Relayship reads the dispatch email your supplier already sends. There is no portal to set up, no spreadsheet to share, no feed to configure on their end. You forward; we parse.
What happens to emails that are not dispatch confirmations?
They cost nothing. Failed extractions, duplicates, verification codes, and non-dispatch emails are all free. You only pay for successful tracking uploads to Shopify.
Will it fulfill orders incorrectly?
New installs default to review mode, so nothing auto-fulfills until you confirm your first real matches. After that, only matches above your confidence threshold (default 0.9) auto-fulfill; everything below goes to a human queue rather than a guess.
Does it handle one email with several tracking numbers?
Yes. A batch email with N tracking numbers becomes N independently-matched shipments, and split shipments against a single order are handled line by line.
Is my data secure?
Shopify tokens are encrypted at rest with Google Cloud KMS, raw emails auto-delete after 30 days, and the GDPR compliance webhooks are wired. We keep the minimum we need to do the job and not a byte longer.