Most businesses that come to us already run on something: an eBay store with thousands of listings, an inventory or ERP system the warehouse lives in, a payment account. A new website should plug into those, not ask you to type everything twice. Integrations are the work that makes the site and those systems agree.
eBay inventory integration
For sellers who keep eBay running beside their own store, the integration reads your listings through eBay’s official API and keeps the website in step:
- New listings appear on the site with every photo, the title, condition and the seller’s condition note, item specifics, shipping details and price.
- Price changes carry over without touching anything else on the product.
- Ended or sold listings are hidden on the site once eBay confirms they have ended, and shown again if a listing comes back.
- Vehicle fitment, for car and truck parts linked to eBay’s parts catalog, comes from eBay’s own compatibility data.
- Matching keeps one website product per eBay listing, so nothing is duplicated.
How often. The target for a full sync is every hour, which is 24 scheduled updates a day. What is reachable depends on eBay’s API rate limits (the Browse API’s default is 5,000 calls a day), your account’s permissions and the size of the catalog. We size the schedule to the limits before we promise a number, and the sync is scheduled, not instant, so availability can change between runs.
eBay’s rules. eBay’s API License Agreement restricts using eBay content to build a site that competes with eBay without eBay’s written consent. We raise this before the build and plan for it: either eBay’s written OK, or Wix’s own eBay connection. The details are in our guide to selling on your own website and eBay.
Inventory and ERP feeds
When stock lives in an inventory or ERP system, the website needs that system’s quantities, prices and new items. We start by reviewing the feed or API specification and access permissions, because those set what is possible: which fields can sync, how often, and whether website orders can flow back.
Before any feed goes live we agree the rules with you in writing:
- Which system owns each piece of data (price, quantity, description).
- How duplicates are handled.
- What happens when the two systems disagree on stock.
- Which order and stock updates flow in which direction.
Payment gateway setup
Checkout needs a payment provider. You connect it (Wix Payments, PayPal or another supported provider) in your business’s own legal name, so the money and the merchant account are yours from the first sale. We configure the secure checkout, shipping and tax rules, test the full path, and keep the connection working afterwards. Merchant transaction fees and provider charges are set by the provider, not by us.
Every sync is checked, every run is logged
An integration you cannot see is one you cannot trust. Each run writes a log: how many items were read, created, updated and hidden, and any errors with the reason. A daily check reads those logs and alerts us only when something is actually wrong. After the first big import we compare the counts with the source and check a random sample of 20 items field by field.
The numbers in any report have to be true. If a run fails halfway, the report says how many items actually landed, not how many were attempted.
What we need from you
- Access to the systems involved, granted the safe way (a developer key, a delegate login or a user account for us), never your own password sent by email.
- Your rules for stock and duplicates, written down once.
- A contact on your side who knows the data, for the questions that only the business can answer.
Where it fits
Integrations usually come with an online store build and continue under managed hosting, since a feed needs someone watching it. If your business sells through eBay, our page for eBay and surplus parts sellers shows how the pieces fit together.
