# How to build a mobile app for Oracle NetSuite > Source: https://netray.co/integrations/netsuite-mobile-app > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Integrations ## Short answer Oracle's NetSuite mobile app covers general ERP use, but shop floor and warehouse tasks usually need a scan-first app that calls RESTlets or SuiteTalk REST. Plan for network gaps, OAuth 2.0 sign-in, and a short list of tightly scoped transactions. ## System Oracle NetSuite ## Capability mobile-app ## Intro The standard NetSuite mobile app is good for approvals, dashboards, record viewing and quick entries by office staff. Receivers on a dock, pickers walking a warehouse, and operators at a work center need something else: big buttons, a scanner, and a screen that does one job without ten fields. That gap is why NetSuite manufacturers end up with handheld apps from warehouse management vendors, SuiteApps that add scanning, or custom Android and iOS apps built on the NetSuite APIs. A custom app is realistic if you limit it to a handful of transactions, design for flaky Wi-Fi, and accept that NetSuite is a cloud API, not a local database. Every scan is a network call unless you build a local queue. ## Use Cases ### PO receiving by scan **Description:** Scan the PO barcode and item labels, enter quantity and lot, and create an item receipt, with over-receipt tolerance enforced server-side. ### Bin transfers and cycle counts **Description:** Scan from-bin, item and to-bin to post inventory transfers, or capture counted quantities into an inventory count for review. ### Pick, pack and ship confirmation **Description:** Guide pickers through a pick list, record picks against a sales order and mark the item fulfillment packed with weight and carton data. ### Work order progress and labor **Description:** Operators clock in to a work order operation, report completed and scrap quantities, and post time, using the manufacturing records in the account. ### Field service and approvals **Description:** Technicians view assigned work, capture notes and photos against the case or sales order, and managers approve expense or purchase requests. ## System Surface - RESTlets written in SuiteScript 2.x, which give you purpose-built endpoints that return exactly the fields a screen needs and run validation in one call. - SuiteTalk REST Web Services and SuiteQL for generic record access and lookups, with record availability that depends on features enabled in the account. - OAuth 2.0 and token-based authentication for device sign-in; roles define what each user can do from the app. - Work Order, Work Order Issue, Work Order Completion and Assembly Build records for manufacturing reporting, depending on whether the account uses standard or advanced manufacturing features. - Inventory Transfer, Item Receipt, Item Fulfillment and Bin and Lot or Serial structures for warehouse tasks, where bin management and inventory detail rules must be respected. ## How It Works ### Decide what the standard app already covers **Detail:** Check the NetSuite mobile app and any WMS SuiteApp first. Build custom only for the tasks they do not do well, such as your specific receiving rules. ### Define a narrow transaction list **Detail:** Pick the five or six flows that cause the most keying: receive, move, count, pick, report production, approve. Each becomes one RESTlet endpoint. ### Design the RESTlets around screens **Detail:** One call returns the open PO lines for a scan, another posts the receipt. Put validation (units of measure, bins, lots, tolerance) in the server, not in the app. ### Choose the app type **Detail:** A progressive web app is fast to build; a native or cross-platform app is better for hardware scanners, camera barcode reading and background sync. Rugged handhelds usually run Android. ### Handle offline and retries **Detail:** Queue scans locally with a client-generated ID, post in order when connected, and make endpoints idempotent so a retry does not double-receive. ### Roll out by area **Detail:** Pilot at one dock or line, watch governance and concurrency in the Script Execution Log, and adjust before adding sites. ## Example Flows ### Dock receiving with lot capture **Trigger:** A truck arrives and the receiver scans the PO number. **Steps:** - App calls a RESTlet and shows open lines with expected quantity and lot-controlled flags. - Receiver scans the item, enters quantity, and scans or types the lot. - The RESTlet creates the item receipt with inventory detail and returns any tolerance warning. - Label printing is triggered for put-away. **Result:** Stock is available in NetSuite when the truck is empty, instead of after an office clerk keys the paperwork. ### Production completion at the work center **Trigger:** An operator finishes a batch. **Steps:** - Operator scans the work order traveler barcode. - App shows the operation, and the operator enters good and scrap quantity. - RESTlet posts the completion and labor, queued locally if Wi-Fi drops. - Supervisor dashboard in NetSuite reflects the status. **Result:** WIP and labor reflect the floor in near real time without double entry. ## On Prem NetSuite is not hosted on-prem, so a mobile app always reaches a cloud API. For plants with poor connectivity or restrictions on outside traffic, put a local gateway on the plant network that terminates device connections, queues transactions and forwards to NetSuite when allowed. If you add voice or AI features such as natural-language item lookup or defect photo classification, run those models on a local server so images and data stay on site, and send only the final transaction to NetSuite. Be clear with stakeholders that a full outage of the internet link means queued work, not live validation. ## Security - Use OAuth 2.0 per user or a managed device identity, with roles limited to the app's transactions, and never embed shared credentials in the app. - Use mobile device management for the handhelds: lock down installs, enable remote wipe and enforce screen locks. - Make every write endpoint idempotent and validate in the RESTlet, not in the client. - Keep photos and attachments scanned for size and type before they are attached to records. - Log device, user, endpoint and record ID so an adjustment can be traced to a scan event. ## Options ### NetSuite mobile app plus SuiteApp WMS **Fit:** Warehouse flows that match a packaged WMS and a licensed scanner app. **Effort:** Weeks including configuration, hardware and licenses. ### Custom PWA or native app on RESTlets **Fit:** Unique shop-floor flows, a team with SuiteScript and mobile skills, and a few transactions. **Effort:** Six to sixteen weeks depending on offline needs. ### Partner build with Netray **Fit:** You want the app plus private AI features such as natural-language lookups and photo capture, with a defined pilot. **Effort:** Scoped per flow; a single-site pilot is usually a couple of months. ## Pitfalls - Calling record APIs directly from the device for every field, creating slow screens and governance overruns. - No idempotency, so a retry after a timeout double-receives or double-issues stock. - Ignoring bin and inventory detail rules until the first receipt fails in production. - Underestimating concurrency when a shift starts and fifty devices call the same RESTlet. - Building a general ERP client instead of a few focused screens. ## Faq ### Does the standard NetSuite mobile app support barcode scanning? **Answer:** It has some mobile capabilities and device features, but warehouse-grade scan-driven receiving and picking usually comes from a WMS SuiteApp or a custom app. Check what your release and account features provide before deciding to build. ### Which API should a custom mobile app use? **Answer:** RESTlets are typical for transaction flows because they let you return screen-shaped data and validate in one call. SuiteTalk REST and SuiteQL suit generic lookups. Choose based on governance cost and how much logic the server must enforce. ### Can the app work offline? **Answer:** Partially. You can queue scans and post them later with client-generated IDs, but live validation such as available stock or open PO quantity needs a connection. Decide which tasks may be deferred and which must block. ### How are users authenticated? **Answer:** OAuth 2.0 or token-based authentication tied to a NetSuite role, ideally per person so transactions carry the right user. Shared device logins are tempting for shop floors but weaken traceability. ### Can AI be added to the app? **Answer:** Yes, for example natural-language item search, photo-based label reading or voice commands. Run the models on a local server if images or part data are sensitive, and keep the transaction itself going through the same validated RESTlet. ## Search terms netsuite mobile app, netsuite barcode scanning, netsuite shop floor app, netsuite warehouse mobile, custom mobile app for netsuite, netsuite receiving app, netsuite work order mobile, netsuite restlet mobile app, netsuite handheld scanner, netsuite offline mobile --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json