What is your philosophy/approach in terms of provisioning custom fields in Netsuite? One approach is to reuse a 3rd party vendor's fields (ie created by Celigo or SPS Commerce etc...). The other approach is to create your organization's custom fields which gives you total control over them instead of relying on those 3rd party vendors who may use those fields for their own purposes.

If a bundle added a field and you don't know what its doing, then don't use it imo.

dont touch fields if you dont know their intended purpose

Thanks guys. I am in agreement with your recommendations. I was trying to find best practice since one of our consultants mentioned reusing a field that a 3rd party vendor already had.

I agree with @battk’s advice. If vendors like us (Celigo) or SPS define custom fields you should consider them part of a private “pseudo API”, and it’s best not to mess with them since they may have side effects you can’t anticipate.

Agree. Always make your own and set a naming standard for the field I’d (ie custbody_yourcompanyname_fieldpurpose) so that down the line if you have any development requirements it’s super clear which fields are yours vs bundles/3rd parties

but what if we clearly see that the field purpose is the same that we are going to use? Especially if we are talking about native Netsuite bundles, like EMEA localization, where by example we can find company code field which is a must in many countries of EMEA region.

in your specific case, that bundle is designed to add fields to use with payment templates and tax reporting