Fix SCM Mobile Bundle Missing in NetSuite
You open Customization > SuiteBundler > Search & Install Bundles, search for SCM Mobile (590761) or NetSuite Ship Central (591665), and get zero results.
Ethan James MarshalSenior SuiteScript Architect & Lead NetSuite Engineer
On this page
You open Customization > SuiteBundler > Search & Install Bundles, search for SCM Mobile (590761) or NetSuite Ship Central (591665), and get zero results. The same IDs appear in Oracle's own installation guide, yet they refuse to surface in your account, sandbox or production, even on the Administrator role with SuiteBundler fully enabled. The bundles aren't hidden; they're gated behind license provisioning that the documentation buries in a footnote.
Why the Bundles Don't Appear
SCM Mobile is not a standalone SuiteApp. Oracle's help states it's "shared along with each SuiteApp required by its supported mobile apps: NetSuite WMS, Ship Central, Manufacturing Mobile, or Smart Count." If your account lacks the Warehouse Management System (WMS) license or the Inventory Management module, the bundle records simply don't exist in your SuiteBundler catalog. The same gate applies to Ship Central, it requires the Advanced Shipping or WMS license entitlement.
The bundle IDs you see in PDFs (590761 for SCM Mobile, 591665 for Ship Central) are real, but they're only provisioned into your SuiteBundler index after the parent license is active on the account.
Verify Your License Entitlements First
Before opening a support case, confirm what's actually licensed:
- Go to Setup > Company > Enable Features > Items & Inventory
- Check Warehouse Management System
- Check Advanced Shipping and Inventory Management on the same subtab
- If WMS is unchecked, the SCM Mobile and Ship Central bundles will never appear in search results
If WMS is enabled but bundles still don't show, the provisioning may not have propagated. NetSuite provisions bundle visibility asynchronously after license activation, sometimes up to 24 hours.
The Provisioning Path: What Actually Works
When the license is present but bundles remain invisible, the fix isn't a deeper search, it's a provisioning request. Follow this sequence:
- Identify your authorized NetSuite contact (Account Manager or designated technical lead on the account)
- Request explicit provisioning for:
- SCM Mobile (bundle ID
590761) - NetSuite Ship Central (bundle ID
591665) - Any dependent bundles: NetSuite WMS, Smart Count, Manufacturing Mobile
- Ask them to confirm the bundles are published to your account's SuiteBundler catalog, not just "enabled" at the feature level
Account Managers can trigger this from the partner/provisioning portal. Support reps often cannot.
Common Missteps That Waste Time
| Action | Result |
|---|---|
| Searching SuiteApp Marketplace | SCM Mobile and Ship Central are not listed there, they're bundle-only |
| Installing WMS bundle first | Required, but doesn't auto-publish SCM Mobile/Ship Central |
| Using sandbox to test | Sandbox inherits production's license state; if prod lacks WMS, sandbox won't have bundles either |
| Opening a standard Support case | Tier 1 often closes with "feature not licensed", escalate to Account Manager immediately |
After Provisioning: Install Order Matters
Once the bundles appear, install in this dependency order:
- NetSuite WMS (core engine)
- SCM Mobile (shared mobile framework, bundle ID
590761) - Ship Central (bundle ID
591665, or Smart Count / Manufacturing Mobile as needed)
Each install runs a background script that creates custom records, mobile device configurations, and role permissions. Run them one at a time and wait for the SuiteBundler > Installation Status page to show Complete before starting the next. Parallel installs frequently collide on custom record creation and leave partial configurations.
Mobile Device Setup, The Part Docs Skip
After bundle installation, the mobile app still won't function until you configure Mobile Device Records:
- Navigate to Lists > Supply Chain > Mobile Devices > New
- Set Device Type to SCM Mobile
- Assign a Warehouse Location (required, the app filters transactions by this location)
- Under Mobile Processes, enable only the processes your floor staff actually use:
- Ship Central: Pick / Pack / Ship
- WMS: Receive / Put Away / Pick / Pack
- Smart Count: Count
- Save, then generate the Device Activation Code, this is what the mobile app scans on first launch
If you skip the Warehouse Location assignment, the app launches but shows zero transactions. The filter is hard-coded to the device record.
Hardware & Browser Reality Check
The Oracle help article lists Chrome and Safari only, Firefox and Edge are unsupported for the mobile web client. Devices must run:
- iOS 15+ (Safari) or Android 11+ (Chrome)
- TLS 1.2 compliant browser
- Bluetooth enabled for scanner pairing
- Minimum 4 GB RAM for acceptable barcode scan latency
Test on one physical device before rolling out to the floor. Emulators don't replicate camera-based scanning behavior.
When to Escalate Beyond Account Manager
If your Account Manager says "those bundles don't exist" or "Ship Central is deprecated," they're working from outdated info. Ship Central was refined in 2023.2 with role-switching inside the app (WMS ↔ QMS ↔ Ship Central without re-login). Push for:
- Confirmation that your contract includes SCM Mobile App entitlement
- A provisioning ticket number you can reference
- Expected propagation timeline (usually 2–4 business hours post-approval)
What to Check Next
Bundles installed, devices configured, but floor staff report "No transactions found"? Verify the Mobile Device Record's Warehouse Location matches the Location on the sales orders or transfer orders they're trying to pick. The app filters strictly by that single location field, no multi-location support per device.
If you're still stuck after provisioning, the next article covers SCM Mobile role permissions: the three custom permissions every warehouse role needs but nobody documents.
