Elbuz connects to a Wix site with an API key, pulls products and orders into one catalog and sends prices and stock back. The site stays as is; only the source of the numbers changes.
When you need this:
- A second sales channel: the site's catalog sits in Elbuz next to your marketplaces.
- You calculate prices in Elbuz: the export writes them into the variants on Wix.
- Site and marketplace orders live apart: they come together in one document queue.
- You hid a product on the site: the next run disables its card.
Where to start: create an API key in your Wix account and copy your Site ID.
What the Wix connection can do
- Works with both catalog versions: V1 and V3 are detected automatically.
- Brings the product into the card: title, description, brand, SKU, sale price, stock, visibility, category and photos.
- Splits out variants: each color or size becomes a separate card in a family.
- Carries over visibility: a product hidden on the site is disabled in Elbuz.
- Pulls orders as “Customer order” documents with fulfillment and payment statuses.
- Sends prices and stock back to the site: only into your variants, leaving the rest of the product alone.
What you need from Wix: API key and Site ID
| Where | What to do |
|---|---|
| Wix account | Open manage.wix.com → “Account settings” → “API keys” |
| Same place | Create a key with Wix Stores and eCommerce permissions and copy it |
| Same place | Copy the Site ID: the string in the dashboard URL right after /dashboard/ |
| Elbuz | Import window → your “Wix.com” template → the “Connection” card → the “Wix API key” and “Site ID” fields |
Wix shows the API key only once: copy it right away and keep it somewhere safe. If you lose it, create a new one and revoke the old one. Without Wix Stores and eCommerce permissions, catalog or order requests are refused with an access error.
Step-by-step setup
- Create a template of type “Wix.com” and paste the key and Site ID into the “Connection” card.
- Click “Check connection”: the response shows your site's catalog version.
- Choose what to import: products, orders or both, and whether to fetch photos.
- Save the template and run the import manually.
- Compare a few cards (price, stock, category) and a few orders (items, total, customer) with the site; a mismatch is easier to spot on ten cards. Then put the template on a schedule.
Two catalog versions: V1 and V3
Wix has two generations of its catalog, the old one (V1) and the new one (V3), and a site runs on only one of them. Elbuz detects the version on every run, so there's nothing for you to choose.
There's one difference: sending prices and stock back to the site is built for V3. On V1, importing into Elbuz works fully, but the reverse update doesn't, and the log says so explicitly.
What goes into the card
| Wix data | Product field in Elbuz |
|---|---|
| product name | Name |
| description | Description |
| brand | Manufacturer |
| SKU | |
| price and discounted price | Price (selling) and old price |
| stock | Quantity |
| product visibility | Status |
| collection / category | Category |
| images | Photos (if the checkbox is on) |
| variant options (color, size…) | Product option attributes |
The price is taken as the customer sees it: if Wix has a discounted price, that becomes the selling price, and the full price goes into “Old price”. The struck-through price from the site is kept on your side too.
Product variants
If a product has variants, such as sizes or colors, Elbuz creates a separate card for each variant and groups them into a family under the main product's name; there's no separate card for the “main product”.
- The card name is the product name plus the option values after a dash: “T-shirt — Red / M”.
- The SKU comes from the variant itself, and the customer's choice (color, size) goes into the option attributes.
- You get more cards than there are products on the site; the log says as much: “products (including variants)”.
Categories
Elbuz first reads the site's list of collections (categories in V3) and only then places the products. If the list doesn't come (say, the key lacks permissions), products go into the service category “Products - wix”, which is disabled and excluded from exports; the log gets a separate line about it. How to handle service categories: import overview.
- Start or end
- Action or result
- Decision: the path depends on the answer
Whose price stays in the card
Three mechanisms write the price in turn, always in the same order:
- The Wix import sets the price from the site.
- Markup rules run only on cards created by this run, and only where the cost price is above zero. Wix doesn't send a cost price, so a new product keeps the site's price. If the cost price is filled in (by hand or from a supplier price list), the rule overrides the Wix price. “Fixed Price” and “Do not update” exempt a product from markup.
- Field formulas marked “Apply when importing the catalog from external sources” have the final say: they cover both new and long-standing products that meet their condition.
What a repeat run does with your edits
Every run overwrites these fields in an existing card: name, description, brand, SKU, price, old price, quantity and active status. If you corrected a name or description in Elbuz, the next run brings back the site's text without warning.
Left alone: photos (they're added only to new cards), option attributes, the product's place in your category tree, the page URL, the cost price and any fields Wix doesn't have.
The card is recognized not by SKU but by a fingerprint of the name the product first arrived with. Renaming it in Elbuz won't protect it from updates: the name comes back from the site. Renaming it on Wix creates a new card, because the run can no longer find the old one.
You can lock a card in the “Import protection” section: “Do not update” excludes it from the run entirely, while “Fixed Price” protects only the price and old price. More: how to lock your own value.
- Start or end
- Action or result
- Decision: the path depends on the answer
1
Do not update switch2
Fixed Price switch- Do not update — shields the whole card from the Wix import run.
- Fixed Price — shields only the price and the old price from the import run.
A product disappeared from the site or was hidden
| What happened on Wix | What happens to the card in Elbuz |
|---|---|
| The product was deleted | Stays as it was: with the last price and stock, active, with no line in the log. Remove it by hand |
| The product was hidden | The next run disables it; make it visible again and it becomes active again |
| One variant was removed | Its card stays in the family with the old numbers |
| A V3 site returned no variants for a product | The product is skipped, with a red line in the log showing its name (what to do) |
The Wix template has no “delete what's missing from the source” checkbox. So hiding a product on the site is safer than deleting it: a hidden product reaches Elbuz, a deleted one doesn't. The general rule: a product disappeared from the source.
Disable or delete the card
Disabling is reversible: the card stays in the catalog with all its data and only disappears from the Elbuz storefront. Two things to know:
- The export to Wix still picks up a disabled card: selection goes by the “Export to file (to website)” flag and an active category. If you don't want to send its price and stock, add a condition on active status to the export template's filter.
- The site controls active status: if you enable a card by hand while the product is hidden on Wix, the next run disables it again.
Deleting also removes the link to the product on Wix: the export no longer sees it, and the next import creates the card from scratch, with a new date added, a new page URL and none of your edits.
How to receive Wix orders
Elbuz reads orders from the unified eCommerce layer, so the catalog version doesn't matter here. The first run brings in the order history; after that, orders that have changed since the last run are pulled, and existing ones are updated, not duplicated.
The document gets:
- the number, creation and modification dates;
- the recipient's first name, last name and phone, the customer's email, and the delivery address with city, postal code and country;
- the currency, delivery method, total and line items with SKU, price and quantity;
- the fulfillment status and payment status, as separate fields with separate mappings in the “Related settings” card.
Each order arrives as an unposted “Customer order” document: stock isn't written off or reserved. Only posted documents hold a reservation, and only with inventory tracking turned on.
Statuses and repeat runs
The document status comes from the fulfillment status through a mapping (the “Order statuses” button); the payment status has its own mapping. An unmapped status becomes the first status in the list, that is, “New”.
A repeat run changes your processing status only when the status on Wix has actually changed since last time. Payment and delivery statuses and payment and delivery methods are taken from the site as is. A posted document is never touched by the run. The general mechanics: two statuses of one order.
- Start or end
- Action or result
- Decision: the path depends on the answer
The separate “order state” field that Wix uses to mark a cancellation isn't carried into the document. An order canceled in your Wix account stays in Elbuz with its previous status, so close it by hand. Refunds are visible from the payment status.
Wix sends instant order notifications only to apps from its App Market. With an API key, orders arrive on a schedule: the delay equals the interval between runs. For a busy store, schedule a dozen or more runs a day.
Re-fetch orders for a period
In the template card, expand the “Advanced” block: it has the “Import orders from date (YYYY-MM-DD)” and “Import orders starting from ID” fields.
- You set an earlier date: the next run pulls orders from that date and updates existing documents; there are no duplicates.
- You cleared both fields: the run goes through the whole history but doesn't update existing documents, only adds missing ones.
1
Order statuses button2
Import orders from date field3
Import orders starting from ID field- Order statuses — opens the mapping of Wix order statuses to Elbuz statuses.
- Import orders from date (YYYY-MM-DD) — orders created earlier than this date are skipped.
- Import orders starting from ID — orders with a lower ID are skipped.
How to update prices and stock on the site
The reverse direction is a separate export template of type “Wix.com” (export templates). Wix can't update a single variant on its own, so Elbuz reads the whole product, replaces prices and stock only in your variants and sends the product back in one call. Other variants and the product structure stay untouched.
- It doesn't create new products on the site: the site owns the product pages. Products not linked to the site are skipped, and their count shows in the log.
- It deletes nothing on the site: a product removed from export or deleted in Elbuz stays on Wix as it was; remove it in your Wix account.
- A V1 site doesn't accept the export (about versions).
- Start or end
- Action or result
- Decision: the path depends on the answer
Scheduled updates
Once you've checked the first run, put the template on a schedule. For orders, a schedule is the only way, so its frequency sets the delay.
How much one run handles
There's no cap on the number of products or orders.
- Data is fetched in pages of 100 items with a one-second pause between them; products are written to the catalog in batches of 500.
- The program waits up to 120 seconds for a single request and 30 for a connection.
- On “too many requests”, up to three retries with pauses of 3, 6 and 9 seconds; after that the run stops with the line “429: retry limit reached”.
- Reverse export: every ten products add a line to the log and a short pause.
You can close the template window: the log lives in the Operations Center. How long your catalog takes shows in the “Time spent” column and in the “Run history”.
Scenarios
The site owns the catalog, Elbuz combines it with other channels
What to turn on: in the “Wix.com” template, in the “Select data to import” card, the “Products” and “Photo” checkboxes, then a schedule.
What you get: each run brings name, description, brand, SKU, price, quantity and active status from the site. Photos go only to new cards. Take a product off sale by hiding it on the site; the run then disables the card.
Elbuz owns prices and stock, the site only displays them
What to turn on: import the catalog once with the “Products” checkbox so the cards get linked to the site. Then clear “Products” and leave “Orders”, or turn on “Fixed Price” in the cards. Prices go to the site through a “Wix.com” export template.
What you get: the export writes the price, old price and stock into the linked variants on Wix. If you leave “Products” on without a fixed price, the next import brings the site's prices back into the cards.
Site orders in one queue with your other channels
What to turn on: the “Orders” checkbox, a mapping via the “Order statuses” button in “Related settings”, and a schedule.
What you get: each order becomes an unposted “Customer order” document, with no duplicates. The run changes the manager's status only when the fulfillment status on Wix has changed.
Re-fetch orders for a period
What to turn on: in “Advanced”, set an earlier date in the “Import orders from date (YYYY-MM-DD)” field.
What you get: the next run pulls orders changed after that date and updates existing documents (re-fetch orders).
Protect individual cards from the site
What to turn on: in the product card, in the “Import protection” section: “Fixed Price” to keep only the price, “Do not update” to keep the whole card.
What you get: with “Fixed Price”, the other fields are still updated from the site. With “Do not update”, the run changes nothing, so you'll have to disable an item hidden on Wix by hand.
What to do when Wix won't import
| What you see | Why | What to do |
|---|---|---|
| “Wix: enter the API key and Site ID” | The template has no key | Paste the key and Site ID into the “Connection” card (where to get them) |
| “Wix: API error —” followed by the site's refusal text | The key is invalid, revoked or lacks Wix Stores and eCommerce permissions; less often, the site is temporarily unavailable | Click “Check connection”. If needed, create a new key with the right permissions in your Wix account |
| “Wix: failed to get the category list — products will go to the source category” | The collection list didn't arrive; most often the key lacks permissions | Move the products from the “Products - wix” category into your own tree, or fix the key's permissions and run again (categories) |
| “Wix: the site returned no variants for a product — product skipped, contact support” | The V3 site didn't return the variants of this particular product | The product didn't reach the catalog at all. Its name is in the same log line; pass it on to support |
| “Wix: the site runs the legacy catalog (V1) — export supports V3” | The reverse update is built for the new catalog (about versions) | Importing from the site still works fully; contact support about export for V1 |
| “Wix: skipped products not linked to the site” | These products have no link to a product on Wix: they weren't created from the site | First run a catalog import from Wix; that's where the link is set (updating the site) |
| “429: retry limit reached” | Wix keeps answering “too many requests” and didn't let up after three attempts | Run it later and make the schedule less frequent; after this line the run has stopped (run limits) |
If a run broke off
Products are written in batches of 500, so part of the catalog is already updated. Each page of orders (up to 100) is saved at once and the “import orders from date” value moves with it, so the next run resumes where it stopped. Run it again: no duplicates. General mechanics: if a run broke off.
The “Stop” button in the Operations Center finishes reading the current page, saves what it got and doesn't take the next one. For the catalog, markup rules still run after that, and the log shows the usual summary “Wix: catalog imported”.
If you imported the wrong thing
In “Products”, filter this template's products by “Source - name” and overwritten cards by “Date updated” (if you imported the wrong thing). Wix specifics: bulk-deleting cards also deletes their link to the site's products, so the export loses them and the next import recreates them as new cards. Orders are re-fetched with a date in “Advanced” (re-fetch orders).
FAQ
Why do Wix orders arrive with a delay?
Wix sends instant notifications only to apps from its App Market; a connection with an API key doesn't get them. Elbuz pulls orders on a schedule, and the delay equals the interval between runs. Set a more frequent schedule.
Why were more products imported than there are on the site?
Variants become separate cards: a product in three sizes gives three cards linked into a family. The log says as much: “products (including variants)” (variants).
Does Elbuz create new products on the Wix site?
No. The export updates prices and stock of existing products; the site owns the product pages. Products not linked to the site are skipped, and their count shows in the log.
What happens to a product I removed from the Wix site?
If you deleted it, the card stays with the last price and stock; remove it by hand. If you hid it, the next run disables the card, and making it visible again re-enables it (product disappeared).
An order was canceled on the site. Why isn't it canceled in Elbuz?
Wix's cancellation flag isn't carried into the document: Elbuz reads only the fulfillment and payment statuses. Close the document by hand; refunds are visible from the payment status.
Does an imported order change stock in the catalog?
No. The order arrives as an unposted “Customer order” document, and a reservation appears only after posting, and only with inventory tracking turned on.
Where to find it and who has access
- Menu
- Directories → Operations → Data import
- Template
- new template → type “Wix.com”; one template = one site
- Access right
- the “Import” window in “Group permissions”
- Prepare
- a Wix API key with Wix Stores and eCommerce permissions, and the site
1
Wix API key field2
Site ID field- Wix API key — paste the key created in your Wix account with Wix Stores and eCommerce permissions.
- Site ID — the site identifier taken from the dashboard URL in Wix.
How import templates work in general: data import overview.
Related topics
- To understand how an import template handles any source: Importing data into the catalog.
- To combine Wix orders with your other channels: Importing orders via API.
- To send prices and stock from Elbuz to the site: Export templates.
- If you're connecting marketplaces too: Importing a catalog via API.
