In case of Apache 2.0 as well as LGPL (if the code is only linking to your code without modification), you can distribute your product (for a charge) without having to open up your code of that product.
In this case, you have to make a list of libraries are included, and for each, the actual license files that your dependent libraries have provided in their source/object code. Credits to these libraries must be given.
As LGPL license puts it,
a) Give prominent notice with each copy of the object code that the
Library is used in it and that the Library and its use are covered by
b) Accompany the object code with a copy of the GNU GPL and this (the
LGPL) license document.
As Apache 2.0 puts it,
any Derivative Works that You distribute, all copyright, patent,
trademark, and attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of the
Also some of the other things you cannot use, is to use the Trademark, Logo of those libraries in part of your product. for example you should not:
use phrasing such as 'based on Apache', 'powered by Apache', or 'based
on Apache technology'
Further, if there is a warranty issue i.e. if the system doesn't function as intended because of software issue, the said libraries (under Apache) do not come with WARRANTY. Hence, you need to fix problems for the clients without pointing them to copy write owners of those libraries.
Refer to this: