[IMP] Sales: Updated product variant import language#17830
[IMP] Sales: Updated product variant import language#17830theRealThagomizer wants to merge 1 commit into
Conversation
|
|
|
Hiya, @jero-odoo! Got a pretty quick review for you (I think). @cth-odoo drafted the initial copy, and I revised it for US guidelines and updated the doc while adding it in. Nothing too wild here. Thanks! |
jero-odoo
left a comment
jero-odoo
left a comment
There was a problem hiding this comment.
Looks good @theRealThagomizer ! A few notes, mostly wording changes. Let me know if you have any questions!
Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com>
theRealThagomizer
force-pushed
the
19.0-sales-product-variant-imports-thjud
branch
from
4a6a807 to
061ce0d
Compare
|
Thanks for the review, @jero-odoo! @Felicious, this is ready for your keen and discerning eye. |
Felicious
left a comment
Felicious
left a comment
There was a problem hiding this comment.
Good work with this complex doc, @theRealThagomizer !
@robodoo delegate+
| When modifying the product import template, keep in mind the following: | ||
|
|
||
| - Feel free to remove any columns that aren't deemed necessary. But, it is recommended that the | ||
| :guilabel:`Internal Reference` column remain. | ||
|
|
||
| While it is not mandatory, having a unique identifier (e.g., `FURN_001`) in the | ||
| :guilabel:`Internal Reference` column for each product can be helpful in many cases. This can even | ||
| be from previous software spreadsheets to ease the transition into Odoo. | ||
|
|
||
| For example, when updating imported products, the same file can be imported several times without | ||
| creating duplicates, thus enhancing the efficiency and simplicity of imported product management. | ||
| - Unnecessary columns may be removed. | ||
| - Keeping the :guilabel:`Internal Reference` column is recommended. | ||
| - Having a unique identifier (e.g., `FURN_001`) for each product in the :guilabel:`Internal | ||
| Reference` column can be helpful in many cases. This number can even be reused from previous | ||
| software spreadsheets to ease the transition into Odoo. For example, when updating imported | ||
| products, the same file can be imported several times without creating duplicates. | ||
| - Do **not** change the labels of columns that are meant to be imported. Otherwise, Odoo won't | ||
| recognize them, forcing the user to map them manually on the import screen. | ||
| - Feel free to add new columns to the template spreadsheet, if desired. However, to be added, those | ||
| fields **must** exist in Odoo. If Odoo can't match the column name with a field, it can be matched | ||
| recognize them, requiring them to be configured manually on the import screen. | ||
| - New columns may be added to the template spreadsheet, if desired. However, newly added columns | ||
| **must** exist in Odoo. If Odoo can't match a column's name with a field, it can be matched | ||
| manually during the import process. | ||
|
|
||
| During the import of the completed template, Odoo displays a page that shows all the elements of | ||
| the newly configured product template spreadsheet, separated by :guilabel:`File Column`, | ||
| :guilabel:`Odoo Field`, and :guilabel:`Comments`. | ||
|
|
||
| To manually match a column name with a field in Odoo, click the :guilabel:`Odoo Field` drop-down | ||
| menu next to the :guilabel:`File Column` that needs a manual adjustment, and select the | ||
| appropriate field. | ||
| When importing a completed template, Odoo displays a page showing all the elements of the newly | ||
| configured product template spreadsheet separated by :guilabel:`File Column`, :guilabel:`Odoo | ||
| Field`, and :guilabel:`Comments`. To manually match a column name with a field in Odoo, click the | ||
| :guilabel:`Odoo Field` drop-down menu next to the :guilabel:`File Column` that needs a manual | ||
| adjustment and select the appropriate field. |
There was a problem hiding this comment.
This section is helpful, especially the notes around Internal References and column matching! :D
One thing I’m wondering, though: did Cedric mention whether these are common issues users specifically run into when importing product variants? Right now, some of this guidance seems broad enough that it could potentially belong on the more general import/export documentation rather than being product-variant specific.
If these recommendations are based on common pitfalls during product imports (duplicate products, broken field mapping, update issues, etc.), I think it would help to frame them more explicitly as "common import considerations" or "frequent product variant import issues to avoid." That would make it clearer to the reader why this guidance appears in this article specifically.
Otherwise, it may be worth considering whether some of these points should instead be referenced from the generic import/export docs in the essentials
4 participants
This PR is part of a collaboration between myself and the Belgian writing team. The "Product variants" subsection is largely new and developed by the BE team, and I took the opportunity to refresh the language and images on the page while revising and adding the new subsection.
This 19.0 PR can be FWP to master.