I purchase from a manufacturer gift cards (not virtual ones, but real plastic ones), and keep it in my warehouse as serialized inventory, this base product is not salable.
i sell them as another products, that has additional virtual charachteristic (fixed one, that cant be configured by the customer). e.g. i can have 3 diferent products of: 100$, 200$ and 300$, and have the style of the base product in the warehouse. again,all defined as separate product in the catalogue.
I thought of modeling the inventory product as "configurable product" and the dependant product as "configurable product instance", and add the fixed configuration as features of the product. Is this the correct way? i see configurable product example, only when customer is defining configuration (the PC001 sample).
any other way? (maybe variant? though, my understanding it fits only when base product is virtual)
Thanks,
Amit
For gift cards, I prefer use variant products because that's the way that use OFBiz in the demo data and, above all, OFBiz has processes ready for this type of product-with-variants: load balance of the gift card, relate gift card with customer, etc. Check using Gift Card in OFBiz.
Just one consideration, if you sell the gift card as a product itself, not as a "payment method", then you can use both solutions: you can create the parent product as a virtual one and its "childs" as variants (like a shirt with different sizes), or create it as a configurable one (like a PC with several PC components). Just check the different processes that uses OFBiz to "sell" the product depending of this type (variant or configurable), and use the one that suits you. In this case I also prefer use a virtual product with variants, it's easier to manage it.
Related
we sell virtual gift and social experience like hot air balloon rides, tree house, horse riding, Ferrari car riding etc. These experience provides by different suppliers at different address. We are using nopcommerce as our development platform and as we thought our social experiences are products and supplier are manufactures but we still having problem in mapping addresses. The supplier has two kind of address. One the office address of the supplier and second address is where experience will take place. In other words, the products we sell will have many address and also has relationship with manufactures.
The relationship more or less will be
manufactures have many products and one product can be supplied by many manufactures.
manufactures has many address and they also provide experiences(products) at different addresses.
we need product information, supplier information and then address information for each experience(products). The entity relationship is
Is this diagram ok? Or what will be the way to map this information in nopcommerce?
You can use specification attributes in nopCommerce for the providing different addresses of the product.
I have been given the following scenario :
HyperAV is a retailer of home cinema equipment. They sell a variety of products including televisions, speakers, amplifiers, Blu-ray/DVD players and cables. The company has its head office in Stockport and 5 retail branches around the UK (in London, York, Cardiff, Manchester and Newcastle) and a large warehouse in Birmingham.
Due to the specialised nature of the products most sales are made in the shops which also have demonstration facilities allowing staff to show off the products to customers before they buy. However, the shops can also take orders over the telephone. The company deals with a number of suppliers who deliver items to both the shops and the warehouse. Limited space is available in the shops, so large numbers of items are stored at the warehouse and sent to the shops when their stock runs low.
The company’s buyer and stock controller are based in Stockport and work together to ensure that each branch has an adequate stock level of fast-selling items. If a shop takes an order for a product that it does not hold in stock, payment is taken and the item is sent to the shop from the warehouse. If the warehouse does not have a product in stock, it is ordered from the supplier by the buyer.
From this scenario I have been asked to draw a use case diagram.
I have received feedback but only to an extent where I have been told it is slightly incorrect. I would like to know if anyone can see what is wrong with it or how i can improve it in anyway?
I will not go and analyze what is right/wrong with your business case, but here are a few remarks:
Do not use Generalization with UCs. Each UC shall be a unique added value the system under consideration (SUC) delivers to the actor. If you have Generalization this means your UC is not unique. E.g. Deliver product: these are two absolutely separate UCs. They use a delivery service. But that's a UC for another SUC (namely the delivery service).
Avoid the use of <<include>>/<<extend>> as they indicate the use of functional analysis. UCs are about synthesis which is the opposite of that.
Use verb-substantive to name your UC. Order for example is not a UC.
Think about the "use" in UC. What is the added value it returns to its actor? If that is not of a real use, it's not UC. Process payment is an administrative task, not a UC. So what is the use behind this?
I know this seems silly but I'm having a really hard time with this structure.
My data model is for a computer store (strictly academical only), so I have a generate product table for things like, title (i7 4790) description, unit price and specifications. Then it links to suppler and Category.
Category will have all the parent Category's like motherboard, CPU, power supply etc.
But now I'm not sure if I should then go and have a table for each of, referring to the category table, so motherboard would have things like, chip set and socket, CPU could have a chip set as well, and maybe clock speed, power supply could have capacity.
But then I could have a sub category table That referring to itself, but I'm not fully sure how to structure that.
Please could you help me with the right design decision and why it's the best decision, also what are the pros and cons per solution.
EDIT
Here is a quick Model that i wiped up of my thinking so far. The product table will hold the general details of all products, such as Name of the product, Unit price, Description and Specifications and they will then link to the catagory table that will then link to the different tables, like motherboard, CPU, Memory etc.
The reason im thinking like this is because each catagory, Motherboard, CPU Case etc, is an entity on its own, an object on its own, so it deserves a table of its specific attributes.
Am i on the right track ?
I just answered a question along these lines. You can have a Product table with all the data that is common to all products (SKU, shipping weight, mfg, mfg order num, retail price, etc.) and then, using the Categories value, place category-specific data in separate tables, using the category value to enforce the integrity of the whole system.
I am using Ubercart for products on a Drupal site. I want to extend this product to show a wide range if different information on products. One of the bits of info I want to show, is "specifications".
Take this product as an example. It has various categories of specs, e.g:
Attachment and Capacities
General Specifications
Function and Size
But each of those categories, has actual values underneath them. E.g. Under "attachment and capacities" you have:
Citrus press:Yes
Dough tool:Yes
Mini bowl :Yes
Etc
When I create a new product, I want to be able to add infinite amounts of specifications, that fall under a group.
The best way I have found to do this is using Inline Entities. But this is very slow. Is there no better "field type" I could use to demonstrate this relationship? I.e. one where I can infinitely add categories of values to a specific node?
You can use Product Specification module to achieve the same.
This module allows you to attach product specification data to any
entity in Drupal 7. Mostly we can use this module to store product
specifications on product display page.
Assume I have an imaginary factory for building different kinds of vehicles: cars, buses, pickups, etc...
Each of these vehicles is built up of many different materials: doors, door openers, wheels, etc...
I have a template for each vehicle type: e.g. a car consists of 4 wheels (regardless of the wheel model, size, or brand).
A customer buys a vehicle of type car, and now I want to specify the brand of the tyre. How can I differentiate now between the template which builds a vehicle and the exact item codes of which this specific car is built of?
Update1:
My goals are to be able to:
make a (general) template for each vehicle
build a concrete vehicle (with all materials used)
Suppose a car needs 4 door handles. I mention in this in the template. However, I have e.g. 4 kinds of door handles: a, b, c, & d. I cannot mention this in the template bec. it depends on the customer choice later on.
After a while I build a car and I use handle kind b.
My question is how can I have the proper setup/relationships for templates, all materials, and real vehicles?
An individual car and tyre brand needs to be a 1:1 relationship. It ought to be a simple query.
Your database schema and the template that builds a specific car in memory are two separate issues. Which one are you really asking about?