Help center
How to use DixonDesk
Setup, then a walkthrough of each tab in the app — the everyday workflow plus the parts that aren’t obvious from the screen.
Accounts
Where mailboxes and selling accounts get managed day to day, once connected. Enable/Disable turns syncing for an account on or off without deleting its history. Force re-download since… is the fix for a specific gap — re-pull everything from a chosen date forward, useful if something clearly didn’t sync correctly the first time. Reset this account… is the more drastic version, for starting that connection over from scratch.
A status column shows the real result of each account’s most recent sync attempt, including a clear “reconnect the account” message if a marketplace’s saved credentials have expired, rather than a sync that quietly stops working with no explanation.
Connecting your selling accounts
Step-by-step, one marketplace at a time.
DixonDesk connects directly to each marketplace’s own official API — never a browser extension, never scraping a page. That means each one needs real credentials from that marketplace’s own developer tools before DixonDesk can sync it. The tabs above walk through getting those credentials and entering them, one marketplace at a time.
Where this happens in DixonDesk, for eBay, Amazon, Walmart, and Temu: Tools → Add a selling account… One shared screen, with the fields relabeled to match whichever platform you pick from the dropdown. Wix has its own, separate screen — Tools → Wix → Connect Wix store…
What you’ll need: an App ID, a Cert ID, and a refresh token.
eBay is the only one of these four that requires a real, browser-based sign-in step — you have to actually log in as your seller account and click “Agree” to grant access. There’s no way around that; it’s how eBay’s OAuth works. The good news: DixonDesk has a built-in helper that walks through this exact step, so nothing needs a separate tool like Postman or curl.
Getting your App ID and Cert ID
A real gotcha worth knowing about: eBay sometimes shows a “Your keyset is currently disabled” message the first time. This means you still need to subscribe to (or explicitly opt out of) eBay’s marketplace account deletion/closure notifications — there’s a link right in that message that starts the process. It’s a compliance step eBay added, not something wrong with your setup.
Getting your refresh token, using DixonDesk’s built-in helper
If you don’t have an RuName yet: on the Application Keys page, click User Tokens next to your Cert ID, then look for “You have no Redirect URLs. Click here to add one.” Confirm your contact info, and eBay generates the RuName for you. You only need one, and can reuse it for this and any future keysets.
Worth knowing going forward: DixonDesk’s helper already requests exactly the permissions it needs (order fulfillment and finances data) — nothing to configure there. Refresh tokens don’t expire on a fixed schedule, but if eBay ever revokes it (say, after a password change), just run through the helper again.
What you’ll need: an LWA Client ID, Client Secret, and refresh token, plus your Marketplace ID (DixonDesk already fills in the US one: ATVPDKIKX0DER).
Amazon calls this a private seller application — self-authorized, meaning you grant your own app access to your own account, with no separate consent screen the way eBay needs.
Registering as a developer
Creating and authorizing your app
Copy that refresh token right away — Amazon only shows it once. If you lose it, you’ll need to click Authorize again to generate a new one (this doesn’t invalidate any refresh token you already have working elsewhere, so it’s safe to do if needed).
Worth knowing going forward: Amazon requires rotating your Client Secret every 180 days as a security policy — this isn’t optional, and an old, unrotated secret will eventually stop working. When you rotate it, you’ll need to update it in DixonDesk too (Tools → your Amazon account → Edit).
What you’ll need: just a Client ID and Client Secret. This is the simplest of the four — no separate app-authorization step, no refresh token to manage.
That’s the whole process — paste those two values into DixonDesk and you’re done. Leave the refresh token field blank for Walmart; it isn’t used at all, since Walmart’s own API works with just these two values directly, refreshed automatically behind the scenes every time DixonDesk syncs.
What you’ll need: an App Key, App Secret, and Access Token. Also pick the right region in DixonDesk (US, EU, or Global) — it should match where your Temu seller account is actually registered.
Creating your app
A real wait to expect: Temu may need to approve the application before it can actually be authorized. If Test Connection in DixonDesk fails right after creating the app, this is the most likely reason — give it some time and try again, rather than assuming something’s misconfigured.
Authorizing the app to get your Access Token
Paste the App Key, App Secret, and Access Token into DixonDesk, along with the correct region, and you’re set.
Wix works differently from the other four — it’s for tracking sales from your own Wix store’s product catalog, connected from its own screen: Tools → Wix → Connect Wix store…
What you’ll need: an API key and your Site ID. That’s it — no Client Secret, no refresh token, no OAuth consent screen at all.
Getting your API key
Finding your Site ID: look at your browser’s address bar while viewing your site’s dashboard — the Site ID is the string of characters right after /dashboard/ in that URL.
Worth knowing: unlike every other marketplace here, this key never expires and never needs re-authorizing later — one of the simpler, more durable setups of the five.
One honest note DixonDesk itself already shows here too: Wix support is newer than the others, built carefully from Wix’s own documentation — the first real connection is genuinely the first full test of every detail. If something looks off after connecting, DixonDesk’s own “Show raw data for one product” button is there specifically to help sort out exactly what Wix actually sent back.
Still stuck?
Ask in the Discord — edge cases and release notes live there too.