Packaging is like creating a kit, then storing the created kit as stock, ie. create the package and Jim2 understands that the individual components have now been locked away, unavailable for another job. This means Jim2 knows packaged kits are on hand for sale. The pack type and the default content for the packaging is set up and maintained via the stock record. An example of a package would be a hamper containing different things that has actually been made up and is sitting in stock as such.
A second packaging process is run to indicate that the building process has taken place. Jim2 will then manage serialised identification on individual packages or batch numbers on batch packaging. The packaging process becomes part of the workflow, where each packaging session can be monitored through defined status milestones.
At the end of the packaging process, the quantity of packaged kits will be available as stock on hand.
•Packaging is a bundle.
•Packaging is kits in stock (no journal).
•Packaging is easier to break up by unpackaging (even if some has been sold).
•A component can be returned.
•Costings don’t include labour.
•Pricing rules are fixed, list or less than (cannot be Cost +).
Packaging involves:
a)The stock code that is to be packaged (assembled).
b)The stock codes to be used in the package.
c)A packaging session, which is where the stock codes in point b) are configured to produce the stock code in point a).
Once a package has been packaged, it appears in a stock list as stock on hand. It does not increase the inventory asset balance.

|
Stock codes used in packaging sessions cannot be sold individually – only within the finished package. When the package is sold, the customer sees the package stock code on their invoice, however Jim2 understands it is invoicing the individual components.
A package cannot be used in another package or kit. It cannot be purchased.
|
|