Workflow
The order that landed on the wrong day in your sheet
A seller swore an order was placed on the 10th. His sheet said the 9th. He thought the tool was broken.
The tool wasn't broken. The timezone was.
Here's the subtlety that catches almost everyone: eBay shows each marketplace in its own local time. A US store's orders are stamped in Pacific. A UK store's in London time. An Australian store's in Sydney time. The seller reads the date in that local frame, because that's what the Seller Hub shows them.
If your tracking pulls the raw timestamp and formats it in the wrong timezone, an order placed at 9pm Pacific can land on the next calendar day. It's not lost, it's not duplicated — it's just filed under a date the seller will never look for it on. And a report that quietly disagrees with the seller's own screen is a report they stop trusting.
Why it's so easy to miss
Because it only bites the orders near midnight, and only some of them. Most rows look perfect. The handful that shifted are the ones placed late in the local evening — enough to make the totals feel off without ever pointing at why.
Fetch Order Tracking dates each store in the timezone that store's marketplace actually uses, so the day in your sheet matches the day on eBay's screen. US stores get Pacific. Australian stores get Sydney. The boundary between one day and the next falls where the seller expects it to.
A tracking sheet only works if the seller trusts it, and trust dies the first time a date disagrees with what they saw with their own eyes.
Take a late-evening order and compare its date in your sheet against the eBay order page. Same day?
If not, every night-time order you have is one row off.