Most resellers only discover a broken marketplace connection when something stops working. A listing fails to sync. A price update doesn't land. A sale doesn't route. By then, you've already missed window time, let a hot item sit unpriced, or worse, sold something you shouldn't have.
That ends today. ListForge now detects the moment your eBay connection drops a required permission and reaches out to you immediately — push notification, in-app alert, and a direct email with the reason and a one-click reconnect link.
What Was Happening Before
When eBay rejected a sync request because your OAuth token was missing required scopes, here's what happened:
- The sync silently failed
- ListForge flagged the account internally as "reconnect required"
- You'd see a warning banner next time you opened the app or visited settings
- If you weren't checking, you'd never know
The failure was there. The fix was easy. But nothing told you.
For resellers running lean operations — checking in a few times a day rather than watching a dashboard — that gap between "account flagged" and "reseller notified" could mean hours of stalled syncing or missed listing updates.
What Ships Now
Proactive notification on the first permission failure. The moment ListForge detects that eBay has rejected a request because your account is missing required OAuth scopes, it dispatches a MarketplaceReauthRequired notification across three channels simultaneously:
- In-app + push via the unified notification system, with a deep link that takes you directly to Marketplace Settings on both web and mobile
- Email to every org owner and admin, with the specific denial reason and a reconnect CTA
That last part matters. The email doesn't just say "something went wrong." It tells you why — what scope was missing, what eBay rejected — so you know whether this is a routine reauthorization or something worth a closer look.
How the Debounce Works
One thing we were careful about: if your account is already flagged and eBay keeps rejecting requests, you don't get spammed. The notification fires once on the transition into the reauth-required state. Subsequent rejections while you're already flagged are debounced.
This means:
| Scenario | Notification sent? |
|---|---|
| Account transitions from healthy to reauth-required | Yes — immediately |
| Account is already in reauth-required state, another rejection comes in | No — debounced |
| Account is reconnected, then drops permissions again later | Yes — new transition fires |
You get exactly the signal you need, when you need it, without inbox noise.
How to Use It
There's nothing to configure. The notifications are active for all org owners and admins automatically.
When your eBay account needs reconnection, here's what you'll see:
On mobile: A push notification appears with a summary of the issue. Tapping it takes you directly to the Marketplace Settings screen where you can reconnect.
In-app (web or mobile): The standard reconnect banners and status indicators you already know — ConnectedAccountRow, the item-detail marketplace cards, the NeedsAttention banner on mobile — continue to show the reauth state exactly as before. Nothing changes there.
In your inbox: An email lands for every owner and admin in your org, with the denial reason from eBay and a direct reconnect link. No digging through settings to figure out what's wrong.
To reconnect:
- Open the email or tap the push notification
- You land on Marketplace Settings
- Hit "Reconnect eBay" and complete the OAuth flow
- Syncing resumes automatically
The reconnect flow itself hasn't changed. What's new is that we're getting you there faster — before the problem compounds into something you have to untangle.
Why This Matters for Resellers
eBay OAuth tokens are not forever. Scopes can be revoked when you update your eBay account, change your business type, agree to new seller policies, or just hit a periodic token refresh that drops optional permissions. It's not unusual. It's also not something you should have to monitor manually.
For a reseller with 200 active listings and a weekly sourcing cadence, a 12-hour window where your connection is silently broken isn't just an inconvenience. It means:
- Prices that don't update when you're running a clearance push
- Sales that route but don't confirm, leading to manual reconciliation
- Listings that go dark without you knowing
Getting the notification the moment it happens — with enough context to fix it in under two minutes — is the difference between a minor interruption and a day of cleanup.
What Didn't Change
The existing in-app surfaces all still work exactly as before. If you're in the app when the flag is set, you'll see the warning where you already expect it. The new notifications are additive — they reach out to you so you don't have to be in the app to catch the problem.
The notification delivery is also designed to be fault-tolerant. If a push notification can't be sent, or an email fails to deliver, the system logs the failure and keeps going. The sync path that flagged the account in the first place is never blocked waiting for a notification to succeed.
What's Coming
Re-auth is just eBay for now. The notification architecture is built to extend to any marketplace ListForge supports. As we add new integrations, the same proactive alert pattern will apply — same schema, same delivery channels, same one-click reconnect flow.
The goal is a system where you never discover a broken marketplace connection from a failed listing. You find out from us, first, before anything stalls.
If you're a ListForge user and haven't connected your eBay account yet, get started at list-forge.ai. If you're already connected, you're covered — nothing to do on your end.