carbon ink

Offline order taking

Take NetSuite orders offline on Android.

Carbon Ink stores synced NetSuite customers, items, and pricing on the rep’s Android device. With valid offline access, reps can look up accounts, build orders, and submit delivery invoices without signal. Submission saves the work locally; reconnecting lets it synchronize and be processed into the configured NetSuite transaction.

Connor, Founder, Carbon InkUpdated 5 min read

Key takeaways

  • Customer, catalog, and pricing data is stored on the device after each sync.
  • Orders and invoices are saved locally the moment they’re submitted.
  • Queued work can synchronize on reconnect; processing must succeed before a NetSuite transaction is confirmed.
  • The rep can see local status; the office can review work after it reaches the service.

What you get

Customers and pricing on the device, work saved locally, and a safe sync to NetSuite on reconnect.

Works in dead zones

Browse customers, search items, and build orders with no connection at all.

Pricing on the device

Each customer’s price level is cached locally. If a price is missing, the app says so instead of guessing.

Saved on the device

Drafts and submitted work survive app restarts. Keep the device and app data intact until synchronization is confirmed.

Retries are recognized

Queued submissions retain their identity when retried. Check the resulting transaction after successful processing.

Freshness you can see

Balances and data show when they were last synced, so reps know exactly what they’re looking at.

Office visibility after sync

Admins can review submissions received by the service. Work still only on a disconnected device is not yet visible to the office.

How it works

Four steps from field to NetSuite.

  1. 1

    Sync before the route

    Reps open the app while connected. Customers, items, and prices refresh to the device.

  2. 2

    Sell offline

    Look up accounts, build orders, scan items, and submit, all without a signal.

  3. 3

    Saved on the device

    Each submission is stored locally and queued with a unique request ID.

  4. 4

    Reconnect and sync

    Carbon Ink sends queued work to NetSuite and updates its status for rep and office.

Why offline matters in distribution

Walk-in coolers, steel-framed warehouses, loading docks, and rural routes are where distribution actually happens, and they’re exactly where cell coverage disappears. An app that needs a connection to take an order forces the rep to write it on paper and enter it later.

Carbon Ink supports local order capture using data already on the device. Fetching new customers or prices, renewing access, and confirming a NetSuite transaction require connectivity.

How offline sync works

Synchronization stores a local copy of assigned customers, your catalog, and pricing. Price lookup checks the local customer price level and base price first; fetching missing data needs connectivity. Confirm the required data is available before starting an offline route.

When the rep submits, the work is written to the device first and queued with a stable request ID. On reconnect, Carbon Ink sends the work through the configured integration. That identity lets the service recognize retries if a response is lost. Check the final NetSuite record before treating the delivery as fully synchronized.

  • Submit offline: saved on the device and queued.
  • Reconnect: queued work can be sent for processing; check for errors that need attention.
  • Confirmed: successful processing creates the configured NetSuite transaction.

How pricing works offline

Prices come from the last sync: the customer’s assigned price level first, then the item’s base price. Price changes in NetSuite reach the device on the next refresh.

If an item has no synced price for that customer, Carbon Ink tells the rep instead of filling in a guess or a zero. Wrong prices on a printed invoice are worse than a short delay, so the app is strict about it.

  • Illustrative example: an item has a synced base price of $20 and a synced customer price-level price of $18. The customer price level supplies $18.
  • If no usable customer price-level price is available locally but the $20 base price is synced, the supported fallback is $20. Include this case in your pricing review.
  • If neither price is available while offline, reconnect and resolve the missing price before proceeding with that item.
  • A price changed in NetSuite during the route is not yet on the offline device. Refresh and verify pricing when connectivity returns.

What are the offline limits and recovery steps?

First sign-in and the initial customer, item, and pricing sync need a connection. In production, offline access lasts up to 24 hours from the last successful access renewal. Closing and reopening the app is different from rebooting the device: a production tablet that restarts needs to reconnect before offline work can continue.

Keep the device and its app data intact until the queued work has synchronized. Local storage cannot protect a submission if the device is lost, damaged, reset, or its app data is cleared before synchronization. The office cannot see a submission that has not left the device.

  • Before the route: renew access while connected and confirm the required accounts, items, and prices are available.
  • After a dead zone: reconnect, check submission status, and verify the resulting NetSuite transaction.
  • If processing fails: review the reported issue with the administrator and check for an existing transaction before creating a replacement submission.
  • Before changing devices or clearing app data: confirm that all outstanding submissions have synchronized.

How to test an offline order workflow

Use approved sandbox data and the Android device your reps will carry. Test capture without connectivity, then check recovery and the final record:

  • Sync a customer and a few of their items.
  • Turn on airplane mode and build an order.
  • Force-close the app and reopen it; the work should still be there.
  • Submit, then turn airplane mode off.
  • Open NetSuite and confirm exactly one transaction arrived.

Good to know

  • A rep’s first sign-in and initial data sync need a connection.
  • Offline prices reflect the last sync, so a quick refresh before the route keeps them current.

Common questions

Can reps really take orders with no internet?

Yes. After a sync, reps can look up customers, search the catalog, build orders, and submit them with no connection. Work syncs to NetSuite when the device reconnects.

What happens if the app closes before it syncs?

Drafts and submitted work are stored locally and survive an app restart while the device and app data remain intact. Reconnect and confirm synchronization before clearing data or replacing the device. A production device reboot also requires reconnection to renew offline access.

How does Carbon Ink handle a retry?

A submission retains a stable identity so the integration can recognize a retry after an interrupted connection. Verify the resulting NetSuite transaction and resolve any error before creating a new submission for the same delivery.

Are offline prices up to date?

They reflect the last sync from NetSuite. Reps can see when data was last refreshed, and syncing before a route keeps everything current.

How long can a rep stay offline?

In production, offline access lasts up to 24 hours from the last successful access renewal. Sign in and sync before the route. Closing and reopening the app is supported; rebooting the production device requires reconnection before offline work continues. Sandbox access rules can differ, so include production access recovery in rollout planning.

Can the office see an invoice submitted offline?

Not while it remains only on the disconnected device. The rep can see local status; the office can review the submission after it reaches the service. A confirmed NetSuite transaction requires successful processing.

Switch off the Wi-Fi and try it.

Set up your sandbox for free and run the airplane-mode test with your own customers and prices.