A repeatable test
Use a sandbox customer and a small set of approved items, with expected prices recorded first.
Invoice walkthrough
What happens after a rep submits with no signal? Follow one example through capture, local submission, reconnect, and the NetSuite result. Then use the same checks to test your own configured workflow in sandbox.
Explore the interactive exampleConnor, Founder, Carbon InkUpdated 3 min read
Example submission · DEMO-1042
Sample Market
$360.00 subtotal
Android
Synchronized
2 lines submitted
NetSuite
INV-DEMO-1042
Accepted
Final taxes and adjustments are checked in NetSuite.
Follow the submission
Interactive illustration · Fictional data
Explore the sequence below. This is a simplified example, not a product recording or a live NetSuite connection.
Step 1 of 4
The customer and prices were synced before the route. The rep adds the delivered items while the device has no connection.
Android · Delivery invoice
OfflineSample Market
Fictional customer · Wholesale pricing
Draft on device
NetSuite · Example destination
No transaction received
The invoice is still on the device. NetSuite cannot receive it until connectivity returns and synchronization succeeds.
Example reference: DEMO-1042
What to check
Use a sandbox customer and a small set of approved items, with expected prices recorded first.
Check that customers, items, and pricing are available before disabling the connection.
Switch off Wi-Fi and mobile data on the test device before capturing the invoice.
Confirm local submission separately from the later connected processing step.
Compare the final NetSuite record with the intended customer, items, and quantities.
Identify how your team finds and resolves submissions that need attention.
Choose an approved sandbox customer, two items with known prices, and a device your reps actually use. Confirm the destination transaction type before the test. Check that your sandbox scripts, emails, and integrations will handle test transactions appropriately.
Sign in while connected and complete the data sync. Open the customer and verify the needed items and prices. A device cannot fetch missing pricing or a new customer while offline.
Disable Wi-Fi and mobile data, then build the invoice. Confirm the customer, quantities, and prices before submitting. Carbon Ink saves submitted work locally for synchronization.
At this stage, NetSuite has not received that offline submission. Keep the device and app data intact until synchronization is confirmed. Closing and reopening the app can be part of the saved-work test; restarting the tablet is a separate access-recovery scenario.
Restore connectivity and check synchronization status. Processing time depends on the connection, integration, and NetSuite account. Do not use a fixed stopwatch target as a substitute for verifying the actual result.
Open the resulting NetSuite transaction and compare it with the submitted work. Check the customer, item quantities, pricing, transaction type, and any taxes or adjustments. Carbon Ink uses a stable submission identity to recognize retries; include an interrupted reconnect in your sandbox evaluation.
Repeat the exercise with missing pricing and an interrupted connection. Missing data should prompt a useful next step, rather than a guessed price or an assumption that the transaction reached NetSuite.
A NetSuite validation error may need an administrator to correct configuration before processing can succeed. Agree on who reviews exceptions, how the rep sees the current state, and when it is safe to continue. The interactive example illustrates the sequence; your sandbox test establishes whether your account is ready.
No. It is a self-contained illustration using fictional data. It makes no invoice submissions and does not connect to an account. Use the written steps to run a controlled test in your own sandbox.
No. Work held only on a disconnected device is not yet available to the office. Synchronization must occur before remote systems can receive it.
Treat it as an exception to investigate. Check the validation or configuration issue with your administrator and confirm successful processing before considering the transaction complete.
Yes. Connect your sandbox, synchronize approved test data, and review the configured transaction workflow before performing the test on Android.
Start in sandbox, or walk through the offline and reconnect checks with the Carbon Ink team.
Offline order taking
Customers and pricing on the device, work saved locally, and a safe sync to NetSuite on reconnect.
Read the guideNetSuite mobile invoicing
From delivered quantities to a NetSuite transaction, without office re-entry.
Read the guideImplementation guide
Know what to prepare, who needs to help, and what a successful pilot should prove.
Read the guide