There is no easy way to tell for sure, as there may be many lines of code in your live theme that came from other apps, and those are often difficult to distinguish.
Many apps automatically install one or more lines of code as a script to your theme when you first add them to your store.
Sometimes, app developers will insert customized code as a workaround to fix a problem between their app and your store while they work on a more permanent solution that they can deploy for everyone in their source code.
You may also have worked with a developer to intentionally customize the way an app works with your store - they typically use this type of customized code as well.
Unfortunately, all of this means that, although we - or, for that matter, any app developer - may be able to tell you that a particular line of code was added to your theme as part of a customization, it is impossible to always tell for sure who added it or why it was added. And it’s important to be sure, because editing or removing customized code can have unexpected consequences for how your store looks and functions.
This is even true for customizations added specifically just by (or for) BundleBuilder.
At BundleBuilder, we’ve been creating light customizations for our customers free of charge for over 2 years. The app is built to look good and work well for most businesses, but every store is different, and sometimes merchants have a specific vision, and we’re happy to work with them to achieve that vision.
We’ve tried to track that work carefully over the last couple of years, but because there are so many different reasons to add customized code, and because so many different people on our team may have added that code, it is impossible to always tell for sure that a section of customized code on your theme came from BundleBuilder.
However, there are some situations where we do know the code came from us, and we can usually figure out what it’s there for:
We have a technical ticket tied to the customization, including what was added and who added it.
The code was clearly written to interact with known specific elements within BundleBuilder’s source code.
The code was placed in a file within a theme where that file was specifically designated just for BundleBuilder.