Service Programs & Copy Source

I have a question related to the copy source associated with a service program I have for communicating with Amazon SP-API. I've had this service pgm for quite a while for managing merchant fulfilled orders.
I recently was asked to add the ability to get(buy) shipping labels. I debated whether to create a standalone program vs. creating a separate service program vs. adding a procedure or two to the existing service program.
Because the authentication and base URLs are the same (and the new procedure would be called from multiple programs), I decided to add it to the existing service program.

Now, I'm wondering about the /copy source. For better/worse it contains a lot of named constants, defined values (templates), and exported procedures that wouldn't be necessary (or relevant) in programs that call this new procedure.

So my question... do I just add the new prototypes to the existing service program /copy source, OR should I create a second /copy source containing JUST the prototypes necessary (two of them) for the other programs. Is that "OK" to do, or is it frowned upon? I'm thinking about complexity, conflict of named constants, procedure names (no prefix), etc.

Thoughts?
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>