Size to Option? (And other ideas)

[Berin Iwlew]

Hi!

I think "Size" is too specific, because not all products have a
size.
How about changing the name to Option or ProductOption?

With that, I thought that perhaps these "Options" may have each have
an alternate price.
Are they in stock? In what order should we display them? Is there
more of a description to them?

With that, I ended up with the following table:

USE [SutekiShop]
GO

/****** Object: Table [dbo].[Option] Script Date: 05/03/2010
12:55:00 ******/
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

CREATE TABLE [dbo].[Option](
[OptionId] [int] IDENTITY(1,1) NOT NULL,
[ProductId] [int] NOT NULL,
[Name] [nvarchar](250) NOT NULL,
[Description] [text] NOT NULL,
[Price] [money] NOT NULL,
[IsInStock] [bit] NOT NULL,
[IsActive] [bit] NOT NULL,
[IsFeatured] [bit] NOT NULL,
[Position] [int] NOT NULL,
CONSTRAINT [PK_Option] PRIMARY KEY CLUSTERED
(
[OptionId] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY
= OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]

GO

ALTER TABLE [dbo].[Option] WITH CHECK ADD CONSTRAINT
[FK_Option_Product] FOREIGN KEY([ProductId])
REFERENCES [dbo].[Product] ([ProductId])
GO

ALTER TABLE [dbo].[Option] CHECK CONSTRAINT [FK_Option_Product]
GO



What do you think?

--
You received this message because you are subscribed to the Google Groups "sutekishop" group.
To post to this group, send email to sutek...@googlegroups.com.
To unsubscribe from this group, send email to sutekishop+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sutekishop?hl=en.

[Mike Hadlow]

When you start to think about it, a trully flexible eCommerce solution
should allow you to have a multi-dimentional matrix of options to
relate products to SKUs. Color and Size are the obvious ones, but
there are probably an infinite number.

You are right though, calling the one option available 'size' does
limit it's application. An alternative would not be to have product
options at all and simply have a one-to-one relationship between
product and SKU, so you would list Large-Red-Jacket, Small-Red-Jacket,
Large-Blue-Jacket, Small-blue-Jacket ... this also works well if you
want to have different prices for different sizes, a very common
scenario.

Suteki Shop was built for a particular set of requirements from an
online fashion retailer, so that's why it's 'size' rather than
'option', but I don't see any reason why it shouldn't change.

Mike

[Berin Iwlew]

I'm not sure about the alternative of listing every variation of the
product like that.
That would get awfully messy real fast. Can you imagine wading
through dozens of variations of the same tshirt just so that you could
find what you are looking for?

I'd rather have a user see "Hellow Kitty T-Shirt",have them click to
the details of it, and THEN select what size and color they may want
before clicking on the "Add to Basket" button.