Connect Newegg: pull orders in, push fulfillment out
Find your Seller ID, API key and Secret key in Newegg Seller Portal under API Settings, paste them into Integration, test, map, activate — orders flow in and fulfillment, products and inventory flow back.
The Newegg connector pulls orders from your Newegg seller account into OMS, and pushes fulfillment back to Newegg. It can also push products and inventory to Newegg, so listings and stock stay in sync on both sides.
Prerequisites#
- A Newegg seller account with access to Newegg Seller Portal.
- Permission to open Settings → Data Feed Settings → API Settings in Seller Portal — that page holds your Seller ID, API key and Secret key.
- For the first connection, have at least one real order in the account if possible — the test preview needs one real document to check the mapping.
Get your credentials#
- In Newegg Seller Portal, go to Settings → Data Feed Settings → API Settings.
- Turn on the Enable API switch on that page first, then copy your Seller ID. It is 4 characters, for example A006.
- Copy the API key on the same page. It is sent as the Authorization header. If the API key is empty, click the REGISTER button to request one.
- Copy the Secret key on the same page. It is sent as the SecretKey header. Keep both keys somewhere safe — you will paste them into Integration in the next step.
Fill it into Integration#
- Open Integration → Connector Marketplace → Newegg → New connection.
- Seller ID: paste the 4-character Seller ID from API Settings, for example A006. Do not enter your store name — that is a different value and the connection will not match your seller account.
- API key (Authorization): paste the API key you copied from the same page. It is encrypted at rest and never echoed back.
- Secret key: paste the Secret key you copied from the same page. It is encrypted at rest and never echoed back.
Test the connection#
Test runs two levels: connectivity (Seller ID, API key and Secret key work together) and a document-level preview (pull one real order and show platform fields → standard order side by side). If the account has no orders yet, the connectivity check can still pass — see the FAQ for what to do when no order comes in.
Mapping / pick a template#
Pick the Newegg standard template. It maps order number, line SKUs, quantities, ship-to address and fulfillment status, and it covers the product and inventory fields that get pushed back to Newegg. Check the mapping preview with one real order before activating, especially if your SKUs on Newegg differ from your product SKUs in OMS.
Activate#
After activation, Integration pulls new orders on the schedule you set, pushes fulfillment with tracking numbers back to Newegg, and pushes product and inventory updates to Newegg. Watch the first few orders in Runs / Logs before trusting it unattended.
FAQ#
Test fails: API key or Secret key is rejected
The API key or Secret key you pasted does not match the values on the API Settings page. In plain terms, Newegg does not recognize the keys, so it refuses the connection — a missing character, an extra space, or API access that is not enabled yet will all cause this.
Go back to Newegg Seller Portal → Settings → Data Feed Settings → API Settings, turn on Enable API, and copy the API key and Secret key again without extra spaces. If the API key is empty, click REGISTER to request one first, then test again.
Seller ID is wrong: you entered the store name
The Seller ID field holds the store name instead of the 4-character Seller ID. The keys may be correct, but the connection points at the wrong seller identity, so orders do not match your account.
Open the same API Settings page, copy the 4-character Seller ID exactly as shown (for example A006), replace the value in Integration with it, and test again.
No orders are pulled in
The connection is fine — the Newegg account simply has no new orders to pull. Test and activation can succeed while the order list stays empty when nothing new has been sold.
Check in Seller Portal whether a new order exists. If there is one, run a manual pull in Integration. If there is none, wait for the next order — new orders will be pulled on the normal schedule after activation.