Product identifiers, Model/SKU is "mixed up"?

[oewean]

Hi!

Just started to test and learning osCV4 and in products there is different product identifiers.

I think Model/SKU is "mixed up"

My thoughts about this is:

SKU: Stock keeping Unit is different from business to business, linked to a MPN, EAN etc. A SKU is a seller-defined identifier.

As it's used now, it's more like a Model / MPN (Manufacturer part number), A MPN is a manufacturer-defined identifier.

Orders, invoices, packing list, import etc. should use SKU as primary identifier, as this is the normal for warehouses to use to identify products.

 

What do other users think about this?

 

Best regards

Ørjan

 

 

[CHD-UK]

Hi Ørjan,

Your reasoning is fine, do you have an example of where you think this is mixed up?

It is totally possible to change the text of the fields to read something which you consider more consistent, however if you believe that  the underlying field is used incorrectly throughout parts of the system this would need to be raised with the developers.  ( An example will help )

To change the screen label for the "Model (SKU)" in product identifiers shown here:

 

Go to ADMIN -> Design and CMS -> Translation

Search for MODEL and edit

to

 

Go back to the edit the product to see your changes

 

 

Further it is possible to assign different identifiers to each supplier. 

From the edit product screen, click the "Price and Cost Tab" then click the "EDIT DETAILS" link under your supplier.

 

 

 

 

[oewean]

Hi,

Thanks for the reply and sorry for the late answer.

 

I can rename this to SKU and use it as SKU, but it's good to be consistent.

The linked / structured data (application/ld+json) Report this as SKU, for example with use with Google.

Import / export use this as "Products Model"

But I think it's important to have MPN as well (for use with linked / structured data, shoppingfeed etc), so  it required to have MPN added as a product identifier.

 

[CHD-UK]

No worries,

I agree about the consistency.  I believe that the products_model field is from a previous version of OSC and, I guess, it would be a fair amount of effort to change and test this system wide. 

At the moment, the code for renaming the exported fields is not there.  There does appear to be provision for it in the database structure for the export (file_field)??, so currently, one option, if you want to change the "Product Model" in the export to read "SKU" is that you will need to modify one or more of the system files, depending on your needs,  as follows.   (** Note, future system updates may overwrite these changes, so keep a copy if you intend to use them.  Also I've only tested with export...)

So, for example, changing the "products model" in "products export" ::
In the Easy Populate, provider directory, locate the Products.php file and modify both occurences of the 'value' => ' Products Model',  to 'value' => 'SKU',  save and test the product export.

 

 

 

3 hours ago, oewean said:

But I think it's important to have MPN as well (for use with linked / structured data, shoppingfeed etc), so  it required to have MPN added as a product identifier.

As for the MPN as an product identifier,  probably best to create a new issue with a feature request for consideration on the github page here: https://github.com/osCommerce/osCommerce-V4/issues

 

However, as the system is customisable, you could add a new field or use an existing field in the products table to hold the information, then modify (as above) or create a new data provider to use this field and name it as required.   You could use the suppliers model field, then copy the "suppliers products provider" as new, rename the class and fields then add it to the list of providers in /lib/backend/models/EP/Providers.php  This would be your own totally customised flat file export.  All depends on what result you are trying to achieve.

 

 

Edited May 25, 2023 by CHD-UK

[oewean]

Thanks,

Have made a feature request on github.

[oewean]

Created an issue on github, but no response

Any thoughts about this?

https://github.com/osCommerce/osCommerce-V4/issues/42

 

PS! Keep up the good work with OSC V4 🙂

[pandrei]

On 5/25/2023 at 3:02 AM, CHD-UK said:

I believe that the products_model field is from a previous version of OSC and, I guess, it would be a fair amount of effort to change and test this system wide. 

You are absolutely right.

On 5/18/2023 at 4:13 PM, oewean said:

SKU: Stock keeping Unit is different from business to business, linked to a MPN, EAN etc. A SKU is a seller-defined identifier.

As it's used now, it's more like a Model / MPN (Manufacturer part number), A MPN is a manufacturer-defined identifier.

Orders, invoices, packing list, import etc. should use SKU as primary identifier, as this is the normal for warehouses to use to identify products.

SKU is different from business to business.
Model/SKU field is SKU for your business and you can rename it as you want.
If you also want to use MPN separately from SKU, you can:

1. rename one of unused fields: ASIN, EAN, UPC
2. use product property for MPN field
3. write extension and add new field