2 replies to this topic

[Wolfie]

Maybe this is already possible and I just haven't figured out how to do it yet but here's a thought.

I'm using the word 'points' as a unit a measure. I'm sure another word would be better but instead of trying to come up with the right word, I'll just use 'points'.

Anyway, the idea is to let someone purchase an item and then with that item they can add on sub-items up to a certain number of points. The sub-items would require the first primary product but the client wouldn't be able to add on so many that it exceeds a certain points value. Okay I know that sounded confusing, so I'll give an example.

Let's say that I want to sell a five ring notebook that can hold up to 500 pages. When the client purchases the notebook, it allows them to add in up to 500 'points' worth of pages. I then have different options for what can be put into the notebook where the number of pages is how many points it will use up. I have over 1000 worth of points that the client can choose from. Some groups are 50 points (pages) while others are 40 or 45 or 55, etc. As the client is picking stuff to add into the notebook, the available points update to reflect how much more they have to spend. Of course if I wanted to, I could always charge more points than there are pages (but that would be set up per 'package'), I was just using the #ofPages = #ofPoints as an example.

Should also be able to charge per points being used too. Using the notebook example, it could be the notebook by itself, but with the option of adding in content for an additional fee. Let's say I'm selling the notebook for $1, then to add in content to fill it, it's coming out to about 1¢/page. So if someone fills the book, they would end up paying $6. However if they only fill it half way, then they would be spending $3.50.

So in a way, it would be like setting up a package as normal, but specifying how many points are available (in this case, how much 'space' is available) and then the filler contents would be like packages that require a primary product (as is possible now) but would require the product to be in the cart and the combined filler items (subitems/etc) couldn't exceed the points allotted by the primary package.

Of course, should be able to limit how many times the same subitem can be added to the primary product. Using my notebook example, perhaps there is a filler package that I don't want someone to be able to add twice, but other content they can have multiple copies of.


To use another example that might make sense. Say I'm selling custom built computers where it follows a pre-designed structure. I offer to let the client have up to 5gb worth of software preinstalled.


Oh and another option along with the points should be how many different qualifying items can use those points. Using the notebook example, I might want to limit them to 10 filler items, so even if they are only using (say) 400 of the 500 points and there is still other content that qualifies to fill it, they couldn't add it because of the count limit vs the points.


I hope that makes sense.

[GIANT_CRAB]

Hello,

Most people:



On-topic:

I can't decipher what you are trying to say.

So its like a bundle purchase discount system just that it uses points, right?

Firstly, points sounds very unprofessional.

Secondly, please summarise your point here, its too long and confusing.

Yours truly,
GIANT_CRAB

[Wolfie]

Firstly, points sounds very unprofessional.

Secondly, please summarise your point here, its too long and confusing.

Firstly, if you had read it, you'd see I said, "I'm using the word 'points' as a unit a measure. I'm sure another word would be better but instead of trying to come up with the right word, I'll just use 'points'." So I was saying that it should be called 'points', I was just using that word in place of thinking of another word that would actually be used. In other words, if it's added to Nexus, the developer (Mark) will most likely use another word that is more suitable.

Secondly, it's not a discount system. It's more of way to limit how much can be added to the main product. Imagine you are loading up a portable MP3 player with music and it can hold 4gb of files. You have 20gb of mp3's on your computer. You have to pick and choose up to 4gb of mp3's from what you have. Basically like that, where the main package has a finite amount of room that is either available or being offered and there are a bunch of subpackages that take up a certain amount of space. I also mentioned being able to limit the quantity of items, even if there is still room left for something else.

So there would be two optional limiting factors - capacity and quantity. Using the mp3 player as an example again, you might choose to copy over only 100 mp3's even though that might take up less than 1gb of the player. Using my notebook example (first post), let's say I'm selling magazines that I've collected over the years and know how much will fit in the notebook. I could limit the person by capacity and could also set a limit on the number of magazines added.


Again, the use of the word 'points' is just an example. I'm sure Mark can think of better words to use to describe it. Heck, he might have the back-end calling it 'capacity' with a spot to fill in what it's called on the front end (points, space, mb, gb, chapters, pages, etc) per package.