Nautilus acts as the warehouse execution system for NetSuite ERP. Scanning, putaway, picking, and counting happen in Nautilus on iOS and Android; the resulting transactions sync back to NetSuite's inventory and financial modules through SuiteTalk.
Inventory data, where you need it.
Three things the NetSuite integration does well, that you'd otherwise be doing by hand.
SuiteTalk integration
Direct REST connection to NetSuite via SuiteTalk. No third-party connectors, no SuiteApp marketplace charges. Native field mapping to inventory adjustments, transfer orders, and item receipts.
Bin-level inventory
Nautilus bin locations map directly to NetSuite Advanced Inventory Management bin records. Receipts, picks, and counts post against bins, not just locations, which keeps NetSuite's reporting accurate.
Transfer order execution
Warehouse staff execute NetSuite transfer orders by scanning. Nautilus splits multi-line transfer orders into pick tasks, validates source bins, and posts confirmations back to NetSuite as the transfer completes.
Bidirectional sync. No manual entry.
Data moves between Nautilus and NetSuite in both directions, near-real-time.
- Item receipts
- Inventory adjustments
- Transfer order completions
- Cycle count results
- Sales order picks
- Sales orders
- Transfer orders
- Item records
- Bin records
- Subsidiary structure
Four steps to live.
Under 10 minutes for most teams. The full health check takes longer but doesn't block sync.
Connect
Authenticate with one click. Nautilus uses OAuth — no API keys to copy, no credentials to store.
Map
Match your products, locations, and accounts. Nautilus auto-maps by SKU where possible.
Sync
Enable bidirectional sync. Changes in either system reflect in the other within 30 seconds.
Verify
Run the sync health check. Nautilus flags any mismatches before they become problems.
What the integration does, in numbers.
NetSuite questions, answered.
Does this require NetSuite WMS, or do we get warehouse features through Nautilus?
You get warehouse features through Nautilus. NetSuite WMS isn't required, and most of our NetSuite customers don't license it. Nautilus replaces the NetSuite WMS layer with a more modern mobile-first execution layer that posts the same transaction types back into NetSuite.
How are multi-subsidiary structures handled?
Each NetSuite subsidiary maps to one or more Nautilus warehouses. The mapping is configurable: a single subsidiary can have multiple physical warehouses, or one Nautilus warehouse can post to a specific subsidiary. Intercompany transfers are handled automatically.
What about NetSuite's per-API-call rate limits?
NetSuite limits SuiteTalk to roughly 25 concurrent connections per account. Nautilus batches non-time-critical transactions (cycle count results, batch transfers) and uses a small persistent connection pool for real-time events. We have not had a customer hit the rate limit in practice.
Can Nautilus and an existing SuiteApp coexist?
Yes, with one caveat. If you have a SuiteApp that posts to the same transaction types Nautilus posts to (another warehouse SuiteApp, for example), one of them needs to be the source of truth. Most customers turn off the other SuiteApp's posting and let Nautilus drive.
See Nautilus + NetSuite running on real data.
30-minute walkthrough with a Nautilus engineer. We'll connect a sandbox of your NetSuite account and show the sync live.