

Listings table with synced products and eBay status.
Your product data stays in your own WordPress database, not on a third-party cloud platform. LystoSync is a WooCommerce eBay integration that runs inside your WordPress admin. Publish products as eBay listings straight from the products list, keep prices and stock in sync, and end listings automatically when items sell out. Every setting is a plain option you can read and change.
Coming from WP-Lister Pro for eBay? LystoSync Pro migrates your listings, profiles, templates, and category mappings. See the FAQ below for what carries over.
Core features (free):
Pro features (LystoSync Pro):
How it works:
LystoSync handles eBay OAuth tokens server-side, so you never touch API credentials. You don’t need a LystoSync account, just your active eBay seller account.
This plugin transmits data to two external services:
LystoSync API
All eBay API requests go through ebay-api.lystosync.com. On account connection, your site URL and license key are sent to authenticate. Subsequent requests include product data, pricing, inventory levels, order details, and shipment information, depending on which features you use. No data is sent until you connect an eBay account.
Separately, the plugin can check for service notices (eBay API outages, critical fixes, and eBay changes that need action on your account). This is optional and off by default. You are asked once, at the end of setup, and can change the answer at any time under Settings, Advanced. While it is off, no request is made. While it is on, the check sends your plugin, WordPress, WooCommerce and PHP versions, your site language, and whether you want offers, and nothing else: no site address, email, eBay account, or customer or order data. A second, separate checkbox adds product news and offers to the same notices; it is also off by default and only works while service notices are on.
eBay
Product listings, pricing, inventory, and shipment data are submitted to eBay via the LystoSync middleware. eBay’s own privacy policy and user agreement govern how eBay handles that data.
The human-readable source files for all compiled assets ship with the plugin, in
resources/js/ and resources/css/, alongside the build script (build.js) and
the build dependencies (package.json). Every generated file in dist/ also
carries a header comment naming the source file it was built from.
Build tools required: Node.js, npm
To regenerate the compiled files in dist/:
npm install to install dependencies (esbuild, PostCSS, Autoprefixer).npm run build (or node build.js) to compile and minify all assets.The build uses esbuild for JavaScript bundling and minification, and PostCSS with Autoprefixer for CSS.
Compiled file => source file:
dist/admin.js => resources/js/app.jsdist/accounts.js => resources/js/accounts.jsdist/listings.js => resources/js/listings.jsdist/templates.js => resources/js/templates.jsdist/template-editor.js => resources/js/template-editor.jsdist/profiles.js => resources/js/profiles.jsdist/settings.js => resources/js/settings.jsdist/setup.js => resources/js/setup.jsdist/setup-license.js => resources/js/setup-license.jsdist/import.js => resources/js/import.jsdist/wple-migration.js => resources/js/wple-migration.jsdist/product-overrides.js => resources/js/product-overrides.jsdist/product-metabox.js => resources/js/product-metabox.jsdist/products-bulk-list.js => resources/js/products-bulk-list.jsdist/order-metabox.js => resources/js/order-metabox.jsdist/admin.css => resources/css/design-system.css + resources/css/admin.css + resources/css/category-picker.cssdist/product-overrides.css => resources/css/product-overrides.cssdist/product-metabox.css => resources/css/product-metabox.cssdist/order-metabox.css => resources/css/order-metabox.cssEach JavaScript entry point also pulls in shared modules from resources/js/lib/,
which are bundled into the output rather than shipped as separate files.
The SortableJS library (node_modules/sortablejs, bundled into dist/profiles.js and dist/settings.js) is available at https://github.com/SortableJS/Sortable under the MIT license.
Bundled fonts. The admin interface uses two self-hosted webfonts, copied from
resources/fonts/ to dist/fonts/ by the build. Nothing is loaded from a font
CDN or any other third-party host.
Both are licensed under the SIL Open Font License 1.1. The full license texts
ship as resources/fonts/OFL-DM-Sans.txt and resources/fonts/OFL-Syne.txt.