Multi-store

Running eBay UK, US, and AU stores from one workspace

March 19, 2026 · 9 min read

Key takeaways

The goal is one operation serving three marketplaces, not three separate operations with their own logins and spreadsheets.
What genuinely differs per region is marketplace and currency, carriers, and fees and taxes; the tracking workflow itself is identical.
Different fee structures make guessed fees expensive across regions, so pull true net earnings from eBay's Finances API in each store's own currency.
A skip-list keeps delivered, cancelled, and refunded orders out of the working set so you never re-process finished rows across regions.
Fetch Order Tracking runs eBay UK, US, and AU from one workspace, batching about 25 orders per click into your Google Sheet.

Expanding from one eBay store to three across the UK, US, and Australia is the cleanest way to multiply revenue without finding new products — the same winners often sell in all three regions. But it is also the fastest way to triple your operational chaos if you run each store as its own island, with its own login, its own spreadsheet, and its own midnight tracking routine.

The goal is not three operations. It is one operation that happens to serve three marketplaces. Here is how to get there without losing your mind.

What actually differs between regions

Before you can unify, you need to be honest about what genuinely varies per region versus what you are needlessly duplicating. The real differences are smaller than they feel:

Marketplace and currency. eBay UK reports in GBP, US in USD, AU in AUD. Your profit math has to respect each store's currency rather than blending them.
Carriers and last-mile. UK orders land with Evri, Yodel, or Royal Mail; US and AU have their own carrier sets. The right courier still has to be resolved per order.
Fees and taxes. Marketplace fee structures and tax handling differ, which is exactly why you need true net earnings, not a guessed percentage.

Notice what is not on that list: the workflow itself. "Fetch tracking, detect refunds, write the row, keep finished orders out of the queue" is identical in every region. That sameness is what lets you collapse three operations into one.

The trap: one spreadsheet and login per store

The default path is to spin up a fresh sheet and a fresh routine for each new region. It feels organised on day one and becomes a tax forever:

You log in and out of three eBay accounts all day.
You run the same tracking chore three times, three windows, three chances to lose your place.
You cannot answer "how did the business do this week?" without manually stitching three sheets and three currencies together.
A process improvement has to be re-implemented three times.

If adding a third region triples your daily clicks, you have built three businesses. The win is to build one business with three storefronts.

The cost of unifying later is real, which is why it is worth designing for multiple stores from the start — a point we make in why setting up multi-store from day one saves you hours later.

Get currency-accurate earnings per region

Multi-region makes one mistake far more expensive: trusting gross prices. If your profit column subtracts a guessed fee, it is wrong in one market and very wrong across three with different fee structures. The fix is to pull true net earnings — what actually hit your payout after fees — for each store. eBay's Finances API gives you that real number, where the Order API only hands you gross. For the full argument see why eBay's Order API gives you the wrong earnings number.

One workspace, many stores: how it should work

The architecture that keeps you sane is a single workspace that holds every store, runs the identical sync against each, and keeps the data separated where it matters (region, currency, carrier) while unified where it helps (one place to look, one routine to run). That is exactly how Fetch Order Tracking is built.

From one workspace you can run eBay UK, US, and AU stores together. For every order, in every region, it:

Pulls the order from eBay and the source order from the AliExpress Dropshipping API.
Uses eBay's Finances API for true net earnings after fees, in the store's own currency.
Resolves the real carrier from the tracking-ID prefix — Evri, Yodel, Royal Mail, and the rest — instead of trusting AliExpress's unreliable carrier_name.
Writes the full row into the Google Sheet you already own: tracking ID, carrier, status, estimated delivery date, AE order amount, refund state, a delivery-proof link, and the AE order date.
Catches delivered-then-refunded orders by checking several fields together, not one.

It also handles order splitting by SKU across Amazon, AliExpress, and other sources, so a sale that needs more than one source order is matched correctly rather than silently dropped.

Batch once, clear everything

The part that makes multi-region genuinely painless is the batch runner. Instead of three separate tracking sessions, batch processing with auto-chaining clears your orders about 25 at a click with a small built-in delay, then chains into the next batch automatically — and a skip-list keeps delivered, cancelled, and refunded orders out of the working set so you never re-process yesterday's finished rows. Three regions' worth of orders get cleared in one sitting instead of three.

One routine instead of three.
One sheet you can read end to end, with region and currency intact per row.
One flat monthly plan with no per-order fees, so adding the AU store does not add a per-order tax.

Scale storefronts, not stress

Going multi-region should feel like turning up the volume on a system you already trust, not starting over twice. Keep the workflow identical, respect what truly differs (currency, carrier, fees), and run it all from a single workspace. Do that and a third store is a bigger number on the same dashboard — not a third midnight tracking session.

If you are about to open your second or third region, set it up unified from day one. Point Fetch Order Tracking at your sheet, connect each store once, and let one routine keep UK, US, and AU current together.

Frequently asked questions

Can I run eBay UK, US, and AU stores from a single workspace?

Yes. The workflow of fetch tracking, detect refunds, write the row, and keep finished orders out of the queue is identical in every region, which is what lets you collapse three operations into one. Fetch Order Tracking runs eBay UK, US, and AU together from one workspace, pulling each order from eBay and the source order from the AliExpress Dropshipping API. You get one routine to run and one sheet to read instead of three separate midnight sessions.

How do I keep profit accurate across three different currencies?

Respect each store's own currency rather than blending them, and never subtract a guessed fee, because fee structures differ by marketplace and a wrong guess is wrong in one region and very wrong across three. The fix is to pull true net earnings, what actually hit your payout after fees, from eBay's Finances API for each store. That gives you a real per-region number in GBP, USD, and AUD instead of a blended estimate.

Does adding a third region triple my workload or my costs?

It should not. The batch runner clears your orders about 25 at a click with auto-chaining, so three regions worth of orders get cleared in one sitting, and a skip-list keeps terminal orders out of the working set so you never re-process finished rows. The plan is one flat monthly fee with no per-order charges, so opening the AU store does not add a per-order tax on top.

Related guides

Try Fetch Order Tracking → More guides