carbon ink

Implementation guide

A clear plan for your first route.

A field-sales rollout brings together your NetSuite administrator, operations team, and reps. Use this guide to agree on the workflow, prepare the data and devices, and test an invoice end to end before switching to production.

Open the checklist

Connor, Founder, Carbon InkUpdated 3 min read

Key takeaways

  • Name an operations owner and involve your NetSuite administrator early.
  • Agree on transaction types, pricing rules, and device requirements.
  • Verify a controlled sandbox invoice, including offline and recovery checks.
  • Treat production connection, team approval, and activation as explicit rollout steps.

Prepare with your team

Make the next step a clear one.

Your rollout readiness checklist

0 of 16 reviewed · Kept in this page session

Download checklist ↓

The download is a blank, editable text checklist for your team. It does not include the selections below.

People and workflow
Sandbox and devices
End-to-end verification
Production decision

Review the results with your team. These checks do not change your Carbon Ink account.

Ready to configure the connection? Open the current in-app NetSuite setup guide.

What to prepare

Know what to prepare, who needs to help, and what a successful pilot should prove.

People and ownership

Bring together the NetSuite admin, operations owner, pilot rep, and office reviewer.

Scoped access

Use the in-app setup guide to configure a dedicated integration and appropriate permissions.

Representative data

Pick customers and items that exercise the pricing rules your reps need.

Device readiness

Confirm Android hardware and any scanners or printers before the pilot.

A controlled pilot

Test in sandbox and account for scripts, email, inventory, and downstream integrations.

An explicit rollout

Review results, approve the team, and plan the first production route.

How it works

Prepare. Connect. Test. Roll out.

  1. 1

    Define the workflow

    Agree on the customer visit, prices, and destination transaction.

  2. 2

    Connect sandbox

    Follow the current in-app guide with your NetSuite administrator.

  3. 3

    Verify the pilot

    Check the Android workflow and the resulting NetSuite record.

  4. 4

    Approve production

    Confirm access, billing, team readiness, and the planned cutover.

Who should be involved before setup starts?

Name the person responsible for operations and the NetSuite administrator who can configure the integration. Include a rep who knows the route and an office user who understands the resulting invoices. Those people can catch different kinds of mismatch before rollout.

The current in-app NetSuite setup guide is the source of truth for features, permissions, and connection steps. Complete credential and certificate setup inside the application and NetSuite. Do not send integration secrets through email or chat.

Which data and business rules need review?

Choose a representative customer roster and catalog. Verify customer assignments, item availability, price levels, and the transaction type that should result from a visit. Include a customer with a pricing exception if that is part of your normal workflow.

Standard price-level behavior is only one part of a NetSuite account. Quantity breaks, multiple currencies, units of measure, custom forms, and transaction scripts need explicit review. A successful connection proves access; it does not prove that every invoice will meet your business rules.

  • Document the Invoice, Cash Sale, or assisted custom workflow.
  • List required subsidiary, location, tax, and transaction fields.
  • Review pricing exceptions and any downstream automations.
  • Identify who resolves a rejected or incomplete submission.

What should the sandbox pilot cover?

Test on the intended Android hardware. If the visit includes barcode scanning or invoice printing, verify the actual scanner and printer combination. DEX requirements need a separate discussion and validation for the retailers you serve.

Use approved test data and review potential effects on scripts, email, accounting, and inventory before submitting. Run a normal invoice, an offline submission followed by reconnect, and a recovery scenario. Have the office compare the results in NetSuite rather than relying only on a success message on the device.

When is the team ready for production?

Move forward when the pilot confirms the intended transaction, expected pricing, device behavior, and an exception-handling process. Agree on the first route, the support contact, and who will review that day’s transactions.

Production uses its own connection and explicit approval steps. Review current seat pricing and billing in the application, approve the team, and switch the source only when the guided flow permits it. The checklist helps organize the rollout; it does not activate production or certify an account.

Good to know

  • The in-app setup guide contains the current NetSuite configuration steps. This planning checklist does not replace it.
  • The checklist stays in this page session. Download a copy if you want to keep notes or share it with your team.

Common questions

Do we need a NetSuite administrator?

Yes. Someone with appropriate NetSuite administrative access needs to configure the integration and review permissions, data, and transaction behavior.

Does connecting NetSuite mean we can go live immediately?

No. Connection verification is followed by catalog checks, workflow configuration, and a controlled transaction test. Production approval and activation are separate steps.

Can we test before paying for production?

Carbon Ink offers free sandbox setup and testing. Review the current production seat pricing and billing terms before activating the live team.

Does completing this checklist change our account?

No. The checklist is a planning aid in your browser. It does not save account settings, send data, or activate production.

Make your first route a prepared one.

Bring your workflow and pilot requirements. We’ll help you plan the path from sandbox to production.