Price by Item Characteristic
Hello,
I've been trying to figure out how to set an item price based on the characteristics of that item.
I am purchasing t-shirts and distributing them, however I'm having a very big problem and I cannot find the solution anywhere.
I'm trying to enter some t-shirts where the price of the item increases when a certain sized shirt is purchased or sold.
When I select the item type in the "NEW ITEM" setup the only one that gives me the option to set prices by characteristics is "REFERENCE". If I select that however, none of my items show up when I do a purchase order in XTUPLE/Postbooks.
I sell shirts in different colors and sizes and the price of each shirt is different based on color, size and type.
Is there a way I can get this information into Postbooks without having to manually adjust every line item in postbooks?
Thats a tedious process.
Thanks in advance for your replies....
RJ
I am not making the shirts. The shirts are purchased and prices are basically based on sizes and colors. These items must be tracked in Inventory since I will be purchasing these shirts and distributing them.
I have looked at the Assemble-to-Order-Configurator and I HAVE TO assign a "Manufactured" item class to the shirts get the characteristics pricing per item to show up.
So what you are saying is neither Postbooks nor any of the xTuple products can be used in this type of Distribution environment?
MJ
What I'm saying is that you will have to create a distinct item record for each type, size, color combination.
WOW!!!!
That defeats the whole purpose and is exactly what I'm trying to get away what I'm trying to get away from. I will be distributing over 30 different items. One of these items has over 40 colors and 7 different sizes. Thats 280 item entries for a single product. Based on my estimates of all the items I will have in inventory That means I would have to set up 2500 items in the database.....and thats just for t-shirts and polo shirts.
WOW!!!!
MJ
MJ,
While you can wish it were different, its not. John is exactly correct. If you want data at the size/color/style level then you have to a have a unique record at that level.
I find it interesting that you will be selling products at different prices based on at least size and color, but appear to have no concern for the cost, sales history or inventory balance at that level. Not to mention how you produce purchase orders that define the requirements to your vendor or the shipping documents/invoices to your customer.
My suggestion is that you flow chart your business processes and the decision matrix for establishing list prices. You will find that both of these will point you to a requirement to have data at the style/size/color level.
Mitch Rushing
www.opensurgegroup.com
Mitch
I'm sorry if I'm being misunderstood, and I perfectly understand what John is saying, but it would be extremely time consuming to enter...even at a minimum of say 10 colors per size for 7 different sizes of shirts.
ALSO I never said I am not concerned about the cost of the products.
These products will be sold at a markup of the original cost either by percentage or a flat markup. All these products will be purchased at different prices and sold as such...with inventory and sales history tracking.
I have used another package in the past that these features were fully integrated in. All I had to do was add the attributes and amount/percent markup while adding a product/item, and all items/products are tracked in inventory with sales history and everything.......however that package does not run on Linux.
Additionally there are features in xTuple that fit my needs perfectly and thats why I chose xTuple.
Thanks for your responses though gents...and I hope you will look into adding that option to xTuple in the very near future.
MJ
What you are trying to do with pricing really only makes sense in the context of the Assemble To Order configurator:
http://www.xtuple.org/AssembleToOrderConfigurator
Characteristic pricing is specifically for "Configured" items. The deal with configured items is that each item you ship, or service you perform, is potentially unique. You can not effectively track inventory of configured items.
I have used xTuple in an apparel environment in a past life and can tell you that if you are passing these shirts through inventory using the configured option is not going to work unless you are making the shirts to order. You'll need to create an item number for each style/size/color combination. What we did was just used the class code as the corollary to "style" for reporting purposes.
Folks in the apparel industry instinctively cringe at this notion because it leads to an explosion in the number of item numbers you have to manage. Before choosing xTuple I investigated "apparel based" systems that purport to allow you to manage items by style, but what you end up with is a segmented item number that is really just a classification layer system. At the end of the day, the description, barcode, price and other other information still has to be manageable to each style/size/color combination. For certain, if you want to know how many shirts of style POLO, color RED size LARGE are in inventory, that combination must somehow be represented as a unique record in the database.
John