Global Settings

These settings are available at the global level. Choosing the same setting on a Company level will override the global defaults.

In NetSuite: Navigate to Setup > Company > General Preferences > Custom Preferences

  • Company ISA ID The ISA ID for your main EDI Account in Orderful. Can be overridden at the Subsidiary or Customer level.
  • Test ISA ID The Test ISA ID for your main EDI Account in Orderful. Can be overridden at the Subsidiary or Customer level.
  • Polling Bucket ID The unique ID for the Poller communication channel to be used for importing transactions to NetSuite. See Adding Poller Information for how to find the ID.

Optional Default Settings

  • Company DUNS Number Used if providing remit to information is required by a trading partner.
  • AR Email Used to provide contact information on outbound transactions.
  • GS1 Prefix Used for generating SSCC18 carton IDs for the 856 when using the manual packing feature.
  • GS1 Pallet Extension Allows overriding the pallet extension digit for the SSCC18 generation. The default option is 1.
  • GS1 Carton Extension Allows overriding the carton extension digit for the SSCC18 generation. The default option is 0.
  • SKU Field Change if using a custom Item field instead of the NetSuite default itemid to identify your items with your trading partners.
  • Item UPC Code Change if using a custom item field instead of the NetSuite default upccode field for item UPCs.
  • Subsidiary by Item If using subsidiaries, choose how the subsidiary should be assigned for inbound orders.

Optional Settings Can Be Overridden At The Customer Level

  • Default Class Used to default the Class for inbound transactions like the Sales Order.
  • Default Location Used to set a default inventory location for Sales Orders. Can be overridden at the Subsidiary or Customer level.
  • Default Department Used to set a default department on inbound Sales Orders.
  • Shipping Partner If using a supported WMS provider, the 856 can be automatically generated from the WMS fulfillment data.
  • Allow Multiple Locations Per Order Allow Sales Orders to have multiple locations. Your system configuration must already allow this. If this is not selected and multiple locations are found for orders, the order will be split by inventory location.
  • Lookup Sub-customer Ship-to By Entity ID If a ship to is included in the 850, attempt to find the store location as a sub-customer using the ST identification code from the EDI. Each sub-customer must have the Ship To N1 Identification filled in with the Store ID. If a Store match is not found, the Sales Order will post to the parent account.
  • Split Orders by Store Location If active, create individual sales orders for each Mark For (SDQ) location found in the purchase order.
  • Split Orders by Ship To Address If active, create individual sales orders for each shipping destination found in the purchase order.
  • Use EDI Pricing If active, use the price provided by the partner from the EDI purchase order instead of the NetSuite price.