The worst update so far

Ask the community
,
1

Hello Wix Support Team,

We run D’GARAJ, an e-commerce store on Wix with hundreds of products. The issues we have encountered following the recent product management update are directly disrupting our daily operations.

1. Additional information fields previously included in CSV exports are no longer exported.

Previously, we could export products’ technical specifications and other additional information sections, edit them, and upload them again. These fields are missing from the new export. While the main description is included, sections such as “Technical Information,” “Important Information,” and “Shipping and Delivery” are absent.

Our current file contains 734 products. Being forced to edit information individually when we could previously manage it in bulk is unacceptable.

We expect you to investigate whether this formatting difference is related to the update or data conversion. Furthermore, because the relevant fields have been removed from the CSV, we have also lost the ability to correct the issue in bulk.

Releasing an update that removes working features and disrupts established workflows is frankly amateurish. Wasting the time of paying businesses with active stores in this way is unacceptable for a platform of Wix’s scale. We should not have to manually edit hundreds of products to compensate for shortcomings in your platform.

We expect specific answers and solutions to the following:

  1. Why are additional information fields missing from the new CSV export?
  2. When will import and export support for these fields be available?
  3. How can the broken line spacing be corrected in bulk while preserving existing product content?
  4. Is there a temporary workaround that preserves our existing data until a permanent solution is available?

Please escalate this issue to your technical team, provide a support ticket number, and give us a clear timeline for resolution. Generic Help Center links or instructions to “edit products individually” do not constitute a solution.

2

Your data is not gone and all 734 products can be fixed in bulk. Just not through the CSV.

Taking your four questions in order, separating what is verifiable from what is not.

Why the fields are missing from the export. I cannot tell you Wix’s reason and I will not guess at their roadmap. But there is a likely structural cause worth understanding. In the current Stores catalog API, info sections are reusable entities that products are associated with, rather than free text stored on each product. A CSV column carries inline text easily. It cannot carry a reference to a shared entity without changing what the file means. If that is what happened, the export change is a downstream consequence of the catalog change rather than a feature someone deleted, and it also means a CSV-only fix may not return in the shape you had. Flagging plainly that this is my inference from the API structure, not something Wix has stated.

When import and export support returns. Only Wix can answer that, and this forum will not reach the team that decides it. Submit it at wix.com/updates, which is the route that actually reaches product, and open a support ticket separately for the regression itself. A forum thread gets you peers, not a ticket number.

Bulk correction while preserving content. This is the part that is solvable today. The Stores Products API exposes info sections and supports bulk operations across large catalogs. So the route is to read all 734 products with their info sections through the API, correct them programmatically, and write them back in bulk. Your content is fully readable and fully writable there. It is simply not in the CSV any more. That is a scripting job rather than a manual one, and it costs roughly the same effort whether you have 700 products or 7000.

A temporary workaround that preserves existing data. Before changing anything else, pull your full product data through the API and keep the dump. That gives you a restore point that does not depend on Wix’s CSV format, which is precisely the safety net you have just lost. Do that first, today, whatever else you decide.

On the line spacing, I would treat it as a separate problem from the export. If formatting shifted during a data conversion it needs its own diagnosis, and the same API route is how you would correct it at scale. But I would not assume the two share a cause without comparing before and after on a single product.

One honest note about where you have posted. Wix staff read this forum inconsistently. Posting here is still worth doing, because other merchants are hitting the same wall and it is how the scale of it becomes visible. But if you need a ticket number and a timeline, that has to go through support directly.

3

Dear webhil, First of all, thank you very much for your time and interest. Do you think it’s right to disable a system that’s already working? We might switch to Shopify just because this feature has been disabled. Disabling something like this on sites with high product volumes is an unbelievable idea. This has incredibly disrupted our operations. And I still haven’t been able to find an email address where I can directly contact the support team.

4

No, it is not right. Removing a working bulk path on a catalogue that size is a real operational cost and you are not wrong to be angry about it. I do not work for Wix, so treat that as a peer’s opinion rather than an answer from them.

Three things that are actually useful to you.

The support email does not exist. You cannot find it because Wix does not publish one. Customer Care is reached through the Help Center contact flow, which offers chat and a phone callback. Hours vary by language and region — English callback is listed as 24/7, chat is not — and email is only offered inside that flow when you are outside operating hours. So there is no address to write to. Start a chat or request the callback, and ask for the ticket number at the start of the conversation rather than the end. That is the only route that produces the reference you asked for.

The structural explanation in my earlier post is now confirmed rather than inferred. In the current Stores catalog an info section is a standalone entity with its own ID and uniqueName, and it carries a field called assignedProductsCount, described in the API reference as “Number of products this info section is assigned to.” So info sections are shared records that products are assigned to, not text stored on each product. That is why they cannot survive a CSV round trip — the column would have to carry a reference rather than a value. It also means the export change is a downstream consequence of the catalog redesign, not a feature someone chose to switch off.

That changes the size of your job, possibly by a lot. Before you script anything, read assignedProductsCount on your “Technical Information”, “Important Information” and “Shipping and Delivery” sections. If each of those is one shared section assigned to many products, you correct the text once and it lands everywhere it is assigned — you are not editing 734 products at all. If instead each product carries its own distinct section, it is a scripted pass across 734 records. Those are very different amounts of work, and one call tells you which one you are in. Do that before anything else.

On the dashboard, so you know its limits: you can add an info section to many products at once from Store Products, select the products, More Actions, Add info section. There is no bulk remove, and no documented bulk update of existing sections. The dashboard helps you apply, not repair.

On Shopify. I am not going to talk you out of it, and if the platform keeps breaking your operations that is a legitimate reason to move. But price it honestly against the alternative. Migrating 734 products with their specs, categories, images, URLs and redirects is a larger and riskier project than repairing the info sections through the API. Make that decision on where the platform is heading over the next year, not on this one regression.