• Resolved Cristiano Luchini

    (@cristianoluchini)


    I have the following scenario with a client of mine.

    I developed a CSV generator to facilitate my client in converting Excel spreadsheets to CSV, allowing product importation to WooCommerce.

    To simplify the importation process, we divided the product importation by material type.

    In other words, my client generates a CSV for products made of Steel, another for General material, another for Aluminum, and so on.

    I’m using WordPress version 6.4.3, with the language set to PT-BR. It’s essential to note that if you’re using the EN language, automatic mapping of products for importation won’t occur, and manual mapping will be necessary. Additionally, I’m setting the “;” character as the CSV delimiter.

    Furthermore, I am using WooCommerce version 8.7.0 as the only installed plugin. There are no other plugins in use.

    The theme in use is Twenty Twenty-Four version 1.0.

    The first CSV used in the product importation works as expected. However, the second CSV imports the products without assigning the value of the material used in the product variation.

    Here are the two CSV files used for product importation.
    Note: The CSV files have been simplified to contain only 6 products. The actual files have over a thousand products each.

    toptolls-produtos-exaltt11-geral.csv

    toptolls-produto-exaltt11-aco.csv

    During the process, I began by importing the file toptolls-produtos-exaltt11-geral.csv and, as shown in the image from the link below, the import was completed successfully.

    toptolls-produto-exaltt11-geral.png

    When importing the second file, toptolls-product-exalt11-steel.csv, we noticed that the products are imported without the correct term linked to the variation regarding the alloy used. The image from the link below illustrates the product registered with the absence of the term related to the alloy variation.

    toptolls-produto-exaltt11-aco.png

    It is noticeable that starting from the second file to be imported, the new terms to be used in the variations are not registered, resulting in the product being imported without the correct link to the term.

Viewing 16 replies (of 16 total)
  • Plugin Support Feten L. a11n

    (@fetenlakhal)

    Hello Cristiano,

    Thank you for sharing your thoughts and concerns with us. We truly appreciate you taking the time to provide us with such detailed feedback.

    Regarding the issue with the CSV importer and the management of SKU attributes, it sounds like the situation is indeed complex with the high volume of variations you’re dealing with. I want to clarify that the default WooCommerce CSV importer is designed for standard use cases, which might not fully accommodate the specific needs of a setup with thousands of variations per attribute. We do see how a custom solution might seem necessary in such cases.

    Regarding the premium extension we recommended, our intention was to offer a solution capable of handling large-scale imports more seamlessly than the basic tools can provide. While we respect your decision to seek alternatives that do not involve additional costs, our experience suggests that the premium tools often yield the best results for complex scenarios like yours.

    Our support team strives to assist with issues within the core functionalities of WooCommerce, and while we aim to provide comprehensive support, complex custom setups sometimes require specialized developer intervention. We genuinely appreciate your understanding on this front.

    We’re here to support you and are committed to finding a workable solution. If you are open to exploring alternative strategies or revisiting the use of enhanced tools, we would be glad to assist in optimizing your setup.

Viewing 16 replies (of 16 total)
  • You must be logged in to reply to this topic.