The quick answer
Go to Customization > SuiteBundler > Search & Install Bundles, type the Bundle ID or the bundle's name in Keywords, and click Search. If two bundles share a name, pick the one whose Bundle ID and Company Name match the publisher's instructions. Open it, click Install, review the objects on Preview Bundle Install, and click Install Bundle. NetSuite takes you to Installed Bundles, where the new row starts as Pending. The list doesn't refresh on its own, so click Refresh until Status shows a check mark.
The screenshots show sample data. Person and operating-company names are fictional, and so is the bundle. Use your own bundle and values when you follow the steps.
Before you start
You need the Administrator role, or a role with the SuiteApp Marketplace permission. If the SuiteBundler menu isn't there, your role or account doesn't give you access to it. Get the Bundle ID from the publisher if you can. It's the most precise way to find the bundle, though you should still check the name, company and version before you install. Read the publisher's instructions too. Some bundles need a feature turned on, another bundle installed first, a license, or publisher approval before they'll install. If you have a sandbox, install there first.
Use SuiteBundler when the publisher gives you a Bundle ID or tells you to use Search & Install Bundles. That covers public, shared and private bundles. If the app is listed in the SuiteApp Marketplace, you can install it from Customization > SuiteCloud Development > SuiteApp Marketplace instead, which also shows compatibility, licensing and the install action available to your account.
In this example the bundle is Receiving Dock Calendar, Bundle ID 604218, from Tidewater SuiteApps (Publisher ID com.tidewaterapps).
01. Check what's installed
Go to Customization > SuiteBundler > Search & Install Bundles > List. Installed Bundles lists every bundle in the account with its Bundle ID, Version, Status, Owner, Installed By and Installed On. Here there are five (Total: 5), and Receiving Dock Calendar isn't one of them.
02. Search for the bundle
Click New. Search & Install Bundles opens on Basic search. In Keywords, type receiving dock calendar and click Search. A name search returns every bundle whose name or company matches, so expect more than one row. Here three come back, and two are named Receiving Dock Calendar.
If you have the Bundle ID, type it in Keywords instead. That narrows the results to that bundle, and you still check its company and version.
03. Pick the right bundle
Compare the two Receiving Dock Calendar rows before you click anything. The first has Bundle ID 604218, Version 2.3.1, Managed Yes, Company Name Tidewater SuiteApps - Receiving Dock Calendar, Publisher ID com.tidewaterapps, Availability Public and 18,406 installs. It matches the instructions.
The second has Bundle ID 588391, Company Name QA Sandbox 5519302 - Tidewater Mainline, no Publisher ID, Availability Shared and 9 installs. That looks like a copy sitting in someone's test account, but the low install count is a clue, not proof. What settles it is that the publisher gave you 604218.
Click the Receiving Dock Calendar name in the 604218 row.
04. Review Bundle Details and click Install
Bundle Details shows ID 604218, Version 2.3.1, Company Tidewater SuiteApps - Receiving Dock Calendar, Managed checked, No. Installs 18,406 and Availability Public. The Overview subtab says what the bundle does, and Admin Documentation links to the publisher's setup guide when the bundle has one. Opening this page doesn't install anything.
Click Install. Because this bundle is managed, a confirmation asks you to accept that the provider can install future updates to your account. Click OK.
05. Review the preview and install
Preview Bundle Install shows the name and version (Receiving Dock Calendar, 2.3.1) and every object the bundle will add, grouped by type: the Dock Appointment and Dock Door custom records, the Appointment Status list, a saved search, a portlet script, a Suitelet and their files. Each row has a Script ID, an Action, a Preference and a Lock on Install column.
Every Action here is Add, because none of these objects exists in the account yet. Check each row anyway. When an object with the same ID already exists, the row can offer other actions such as Add and Rename or Replace Existing Object, and replacing overwrites what's in your account. A lock icon means the publisher locked that object, so you won't be able to edit it after the install. This page is your last look before anything changes.
Click Install Bundle. One more confirmation says the bundle and all its objects will be installed into the account. Click OK.
06. Refresh until it finishes
NetSuite goes back to Installed Bundles. Receiving Dock Calendar is listed now with Bundle ID 604218, Installed By Alex Morgan, and the total is 6. Its Status says Pending. While it's pending, Version and the other bundle details can be blank.
The install keeps running after you leave the page, so you can come back to this list later. It just won't update by itself. Click Refresh. Here Status shows installation progress as a percentage, and the rest of the row fills in, including Version 2.3.1. A fast install can go straight from Pending to finished.
Give it a moment and click Refresh again. Status shows a check mark, the same as the other bundles, so the install is complete. Small bundles finish in seconds and big ones can take a while. If Status shows an error instead, the install failed. Find out why and fix the cause before you try again.
Check the result
- Installed Bundles shows Total: 6, up from 5.
- Receiving Dock Calendar is listed with Bundle ID 604218 and Version 2.3.1.
- Installed By shows the person who installed it.
- Status shows a check mark, not Pending or a percentage.
A check mark means NetSuite finished adding the bundle's objects. It doesn't mean the app is set up. Open the bundle's Admin Documentation for any configuration it needs, turn on anything it depends on, and give roles access to the new records and pages before people start using them.
Common questions
Should I use SuiteBundler or the SuiteApp Marketplace?
Use whichever the publisher's instructions name. SuiteBundler's Search & Install Bundles finds bundles by Bundle ID or name, including shared and private ones that aren't listed anywhere else. The SuiteApp Marketplace lists packaged SuiteApps and shows compatibility, licensing and the install action for your account. Some Marketplace apps are delivered as managed bundles, so the two routes overlap.
Two bundles have the same name. Which one do I install?
Compare Bundle ID, Company Name, Publisher ID, Availability and No. Installs, then match them against the publisher's instructions. In this example, 604218 is the bundle Tidewater SuiteApps gave out, with 18,406 installs. The other one, 588391, is a Shared copy in a QA sandbox account with no Publisher ID and 9 installs. When in doubt, ask the publisher for the Bundle ID.
What does Pending mean, and does leaving the page stop the install?
Pending means NetSuite accepted the install and hasn't finished processing it. Leaving the page doesn't stop it. Go back to Installed Bundles and click Refresh, because the list doesn't update by itself. You'll see progress as a percentage or go straight to a check mark, depending on how big the bundle is.
What is a managed bundle?
It's a bundle the provider can keep updating in your account after you install it. That's why NetSuite asks you to accept future updates before the install starts. The provider decides when those updates go out, so it's worth retesting after one lands.
What do Add, Add and Rename, and Replace Existing Object mean on the preview?
Add installs the object because nothing in your account conflicts with it. Add and Rename keeps your existing object and installs the bundle's copy under a different name or ID. Replace Existing Object overwrites your object with the bundle's version. Only pick that after you've confirmed nothing depends on what you're replacing.
What if the install fails, and should I test in a sandbox first?
If Status shows an error, write down the Bundle ID and the error, check the publisher's requirements, and contact the publisher or NetSuite support before you try again. Don't keep reinstalling until you know the cause. For anything important or unfamiliar, install it in a sandbox first and check permissions, dependencies and setup there before you touch production.