Export overview

The full lifecycle from a committed order to a reconciled NetSuite transaction.

You want to move today's orders into NetSuite. The whole flow lives on Settings → Export, which is also reachable from the Export item in the sidebar if you have export permission.

The lifecycle

  1. 1Reps commit their orders. Only committed orders appear in the export list.
  2. 2Open the Export center. Select the orders you want, or filter to include already-exported orders if you are regenerating a file.
  3. 3Choose an export template. If you do not pick one, the default sales order template is used.
  4. 4Generate the file. NetOrderFlow creates an export job, writes the CSV, and flips each included order to Exported with an exported timestamp.
  5. 5If any order references a customer with no NetSuite Internal ID, a companion file ending in _new_customers.csv is written alongside the order file.
  6. 6Download the files and import them into NetSuite. Customers first if there is a companion file, then the orders.
  7. 7Return to Settings → Reconcile and mark the orders reconciled once you have confirmed they exist in NetSuite.

What gets validated before the file is written

  • Required segments. If Subsidiary, Location, Department, or Class is marked required in Settings → Defaults and neither the order nor the default supplies a value, the export is blocked.
  • Required template columns. A column marked required must resolve to a non-empty value.
  • Manual items. A line typed as free text has no item reference, so NetSuite has nothing to match. These are flagged before the file is generated.
  • A configured template. If no sales order export template exists, the export stops and tells you to create one.
Run a small file first

The first time you export after changing a template or a default, export one order and import it into a NetSuite sandbox or as a single-record test. It is much easier to diagnose one failing row than two hundred.

Export jobs and file history

Every generation creates an export job recording who ran it, when, how many orders were included, and the files produced. Use that history to re-download a file rather than regenerating it, so the file you keep matches the file you imported.

Regenerating is not the same as re-importing

Generating a new file for the same orders produces the same External IDs. If you import both files into NetSuite with Data Handling set to Add, you will get duplicate transactions. Use Add or Update when re-importing.

Step-by-step NetSuite import

NetOrderFlow does this for you. Start a 14-day free trial.

Questions about this guide?