Bringing a Wix Stores site across always raises the same practical question: how to pull in products, their variants and orders without retyping everything. This application reads the site's catalogue and brings it into yours, with a report of what was rejected.
Who the application is for
For merchants who run or have run a Wix Stores shop and want to bring their catalogue, contacts and orders into their own catalogue.
What the application does
- Reads categories, products, contacts and orders through Wix's current catalogue interface.
- Requests each product in detail to obtain its variants, which a plain listing does not return on this platform.
- Follows the next-page indicator returned by the store rather than counting itself, to stay reliable against its cursor-based pagination.
- Specifies the target site on every call, since a Wix API key is valid for a whole account rather than a single site.
- Never creates a duplicate if the import is rerun, and resumes where it left off.
Day to day
- Enter the Wix site identifier and the API key created by the account owner, with read scope on products.
- Check access before launching anything, to avoid a migration of several thousand products failing on the first page.
- Run a trial first, which changes nothing, and read the report to see what would be brought in and what would be rejected.
- Switch off trial mode and run the real import, accepting that the variants step takes longer than the products step.
- If the platform asks you to wait, let the import pause for a minute before resuming at the same point, rather than relaunching it by hand.
What the application does not do
- This is not a continuous sync, and it does not replace your sales system: it is a tooled catalogue import, run when you decide to.
- It writes nothing back to Wix.
- It could not be checked against a real Wix store, since access to this API requires an account, a site and a key that only the account owner can create.
- Anything beyond bringing in the catalogue, contacts and orders stays a case-by-case study.
Getting started
Have the Wix account owner create an API key with read scope on products, enter it along with the target site identifier, then start with a trial on a small scope before running the real import. Prefer the API key over an application token: the latter is only valid for four hours, while the key stays usable until revoked, which suits a migration spread over several days better.
Going further
To find out whether this application suits your business and how to activate it, compare the plans or write to us.