Just one example...
# general
w
Just one example...
g
Ah, yes. In my case it's a rack that is being sold with say... 50 samples on it. Each customer may want different samples. They may return parts of it for replacement like discontinued samples so I still need that functionality
Not sure what option would fit the bill though. Assembly item?
w
I'm not familiar with assembly items, we don't have the manufacturing module
g
Ah, undertsood
Thank you
r
@Grant Horton as someone who has dabbled with kits and swapping out products, you cannot return just a part of a kit. When generating a item receipt, it returns all the items that were in the kit at the time of fulfillment. So you can "evolve" the kit in a way, but if not micromanaged a little, it can screw up inventory for discontinued items if you receive a kit with disco items. Also, NS will warn you of such when you try. I've done this whole process, but on a large scale, it would be untenable.
but the price doesn't have to be dependent on the components of the kit.
g
Hm, trying to find a way to have a "Shell" of sorts. Tells the customer service person that there are x number of samples and x number of blankets (or whatever item) that need to be selected before the order gets placed.
I suppose the trick is that it needs to stay the same price and.... we need to be able to return the samples that are discontinued later on and swap em out. Sounds like that'll be tricky. Might just need to end up being separate items like we do in our old ERP system.
w
Separate kit items seems like the way to go.
r
yeah, we were looking at a similar thing. we ended up using a coupon code to "normalize" the price of the kit, and had it also add a "pick-10 box" item, so that when the order was being processed, it would be understood that it needed to be packed as a "faux-kit" item. That kept the inventory control/flow at nominal.
put 10,000 inventory units into the "pick-10 box" inventory at 0 (zero) price so that it wouldn't run out for some time, and accounting would stay happy.