If all the labels are consistent in appearance and the only changes that will be needed is text on the label -- I'd use **PDF forms**. It is a simple matter to create a PDF form which allows any user to input form field data (text) in specific areas. Using a PDF form ensures a few things: - Editing is easy on the end user. They click and type, then save or print. - Artwork will not traditionally be modified by the end user. It *can be* but most won't bother. - Print production remains consistent. There's little chance an inexperienced user will improperly move or edit something they aren't supposed to. I tend to try and avoid providing InDesign files whenever possible. As others have mentioned there are several licensing factors which come into play with providing native files -- are all fonts properly licensed for redistribution (highly unlikely), is all artwork licensed for redistribution and repurposing. When you provide native files you are providing the *easy* ability to reuse anything in that file for *any* purpose. If you create icons for labels, and then provide the native InDesign file. It's a simple matter to pull the icons and use them for a web site, or app development, or anything. You can *clearly* do that with a PDF as well, but legally you'd have an easier time proving misuse if you never provided native icon files (in the form of an InDesign package). If you *must* provide InDesign files I try and make any links as difficult to edit as possible. For linked vector files I'll expand and flatten the artwork in Illustrator before copy/pasting them directly into InDesign (can make them a nightmare to alter buy they still reproduce well). And no matter what, I *never* provide fonts with native files. I only provide links to where fonts may be purchased. I have some fonts which cost thousands of dollars. The last thing I'll do is *give* them away just because I'm asked. PDF Forms just work so much better for stuff like labels and simple multi-line text changes where text reflowing isn't an issue.