NetSuite setup checklist
What must exist and be configured in NetSuite before your first CSV import.
Most first-import failures are NetSuite configuration, not CSV problems. Work through this before you generate a real file.
Access
- Your NetSuite role has the CSV Imports permission and can create Sales Orders.
- You can reach Setup → Import/Export → Import CSV Records and Setup → Import/Export → View CSV Import Status.
- You can run and export saved searches, since that is how reference data comes into NetOrderFlow.
Records that must already exist
| Record | Requirement |
|---|---|
| Customers | Exist in NetSuite, active, and available to the subsidiary the orders will use. |
| Items | Exist, active, and available to that subsidiary. Note the Internal IDs. |
| Sales reps | Employee records flagged as sales reps. |
| Terms and shipping methods | Set up with the names or Internal IDs you will export. |
| Tax codes | Available on the relevant nexus if you export a tax code column. |
| Units of measure | The units you export belong to each item's UOM set. |
| Segments | Subsidiary, location, department, and class values exist for the combinations orders will use. |
| Discount items | A discount item exists if you export line or order discounts, with the GL account you expect. |
Bring the IDs back here
- 1Build a saved search per record type with Internal ID as an explicit result column.
- 2Export each to CSV.
- 3Import them at Settings → NetSuite sync → Import and save a profile for each so refreshes are quick.
- 4Fill Internal IDs on list values at Settings → Data model → NetSuite lists.
Agree the formats
- Date format: pick one and set it identically on Settings → Defaults here and in Advanced Options on the NetSuite import.
- Discount sign: match the way your NetSuite discount items expect rates to be written.
- Subsidiary: on OneWorld, decide the default and require it so no order can export without one.
- External ID prefixes: choose values that cannot collide with keys other systems create.
Do a dry run
- 1Enter one order for a real customer with two real items.
- 2Commit and export it.
- 3Import it in NetSuite with Data Handling set to Add.
- 4Open the resulting Sales Order and check the date, customer, both lines, rates, segments, and terms.
- 5Delete the test transaction, then reconcile or reset as needed before going live.
Save the mapping on the successful run
The dry run is the moment to save your NetSuite import mapping. Every later batch then takes a couple of clicks.
NetOrderFlow does this for you. Start a 14-day free trial.
Questions about this guide?