Separate SKU/Model field

Project:Ubercart Contributions
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:active
Description
Project: 
Ubercart

SKU (http://en.wikipedia.org/wiki/Stock-keeping_unit) and product model are two completely separate things. basically SKU is an internal number or code assigned by warehouse or retailer to a product; on the other hand product model is a number or code assigned by the manufacturer to the product.
SKU is a unique code within the warehouse/retailer but product model can easily have duplicates as it's unique within manufacturer. e.g. Samsung can choose T30023 as product model for a notebook and HP can choose the same code for a cartridge.

combining them into one field is as wrong as combining LastName/Birthday fields! having them in one field already caused lots of confusion between uc users as i noticed within forums.

we need to patch the uc core to separate SKU/Model field into SKU and Model fields; and we need to do it carefully as right know uc requires SKU/Model field to be unique (requirement for SKU, 2 products can have the same model) but the machine readable field name is "model"

Version: 
Ubercart 1.3
Ryan's picture
Offline
Joined: 08/07/2007
Juice: 15438
Re: Separate SKU/Model field

Actually, we unfortunately intermixed terminology so that both Model and SKU in the Ubercart backend ought to be referring to SKU. One of my goals for D6 development is to standardize that to SKU and standardize "delivery" to "shipping" for addresses. If there are other similar inconsistencies, I'd love to fix those, too.

What you're describing as Model I suppose I'd relegate to a CCK field if someone wanted it.