We originally looked at sales kits as a great time saver - not having to create jobs and report against them. Looking back, kanban receipts would probably have been a better fit.
A couple of other things we ran into (maybe fixed in more current versions of Kinetic?):
- Multi-site, alternate methods needed to pull the components if order entry changes sites
- No components loaded, order entry wasn’t hitting save on the last order line - must save the line to bring in the components
- Confusion in matching up customer facing document “Lines” since each kit component is its own line. We ended up modifying all customer facing documents to use the DisplaySeq instead of Line. Although customer shipment entry uses native line so had to really train on packing slip versus “shipment order line”
- Sales kits and credit card processing within earlier versions was buggy, especially if cancelling a shipment (might be fixed now)
- Our work around for the kit being returned on an RMA was to not reference the original order in the RMA line, just added “-Kit” to the end of the part number and manually put in amounts, salesperson etc. We then had to disposition RMA to scrap using a “Kit Salvage” control and write on the components using the same “Kit Salvage” control to net out transactions
- Forecasting kit components is buggy - there is an Epicor idea out there for improvements
Despite all of the above, I still work with many customers who are successfully using kits. Even ones that use component pricing and don’t have any issues with them.
Always recommend to test in a test environment and have your business use cases defined… Get accounting involved to validate the GL transactions too.
Good luck!
Jenn