Sage 100

I have a customer on 2016.5. They are selling inventory kits (in BOM ) which consist of electronic items. There may be 5 items in a kit. Two of them serialized. As of today they just throw all the components into one big box to ship. That procedure isn't scaling well and for the future, they want to make that kit, put it into a pretty packaging box and put it into stock. That's pretty easy in Sage except I believe I lose the ability to trace the serial number once it goes into the finished good. Is my only/best option to use ACS for lot/serial traceability?

If you also serialized the finished good as well you could track it in the Production History report, but that's about it.

The finished good is not going to be anything except a small cardboard box where the components are placed. They will need to track down to those individual components. Example - Box will have Power supply , cable, circuit board (serialized), video board (serialized). They need to know where the serialized items were sold to at the component level.

I have a client with the same issue. I believe it will require ACS WMS base enabled to get Vendor Lot Traceability add-on to work. Client doesn't need MB, only VLT. At one time, ACS had talked about splitting it out. I haven't checked back with Ron C on it lately.

Looks as if DSD has VLT http://www.dsdinc.com/enhancement/imls-im-lot-serial-traceability/

Is IMLS from the SWK purchase? Also, note that it does NOT work with WO (only BM).

WO could be an issue but so far we are only using BOM for builds

The Bill of Materials Production History Report, run with component detail included, lists the component serial/lot numbers issued during production. The Inventory module's, Lot Serial Transaction History Report provides the transaction history (receipt, issue, disassembly, reissue, etc.) by date range or period.

@MoiraGoggin Does this type back to who the item was sold to? While we may look at this information for several reasons the biggest is that the end user (often a customer of a reseller) calls with the serial number and no idea who they bought it from. Now, it's simple. Just key in the SN and it shows exactly what Invoice it was shipped on. We would need the same ease of looking up by SN even when that SN was on a component that was built into a final product.

If a serial or lot # component Item is used in a sub-assembly for a Parent there is no traceability of the serial or lot to a SO invoice without an enhancement.

If multiple people will be looking stuff up at once use SQL rather than Access, or switch to Premium and have a query run from a script.

Bob is right. You could avoid a mod by changing the valuation method to serial and using the same serial number as the component.

Thanks for the info. This customer is selling a product very similar to how you might sell a cellular phone. Now they are selling all loose pieces picked from the shelf (these are BOM kits which explode components on SO and when picked they manually enter the SN): -Phone (serialized) -SIM Card (serialized) -Power cord -Power brick -Instruction manual Where they want to go is pre-assemble the items into a nice display box and seal up the box and scan just the display box when it's sold. I think the only difference here is instead of selling the BOM as a kit (and exploding components which are then picked and serial # assigned) they'd have to use production entry to create the item so it can ship from stock. In creating the item I believe we loose visibility of who bought what S/N.