NetSuite integration

• Data flow
• Sync frequency
• Turnaround time
• Your team's involvement
• Your responsibilities
• NuORDER team's involvement

• NuORDER's responsibilities
• Data transfer method
• Special considerations for NetSuite
• System requirement callouts
• Other integrations
• What's supported

• Creating and updating items: The NuOrder product integration will be able to identify the difference between new and existing items in our system. 
• Customized data mapping: Your Implementation Manager will work with you to map NetSuite data to NuOrder required, standard, and/or custom fields. 
• Pricing and Multiple currencies: Your NuOrder integration will sync default and wholesale prices for each currency. Additional NetSuite Price Levels can be supported through customer-level discounts or via a NetSuite Pricesheet integration. 
• Price-per-size is supported. 
• Removing Items: The NuOrder integration will be configured to archive or disable products in NuOrder based on custom fields from NuOrder's NetSuite bundle. 
• Custom Sync Parameters: You will work with your Implementation Manager to specify the rules the integration should use to identify which items should be synced to NuOrder (e.g. Item Status, Category, checkbox at the item level, etc.).
• Supported NetSuite Item Types
  • Inventory Items
  • Assembly Items

• UPC Codes: The Item NetSuite Internal ID is mapped to the NuOrder "UPC" field. If the actual UPCs are needed in NuOrder, they can be mapped to the "GTIN" or "UPC Code" fields. 
• Parent/Child Items: If color and size variations are not included in the NetSuite matrix items, work with your Implementation manager which NetSuite fields should be mapped to the NuOrder Style Number, Color, and Size fields. 
• Unsupported NetSuite Item Types
  • Groups 
  • Kits
  • Non-Inventory Items

• Two-way customer sync is not supported: Your customers must originate in NetSuite and be synced to NuOrder with all the necessary account codes. (This is how NetSuite will recognize the customer when the order is synced back in.) Bi-directional syncing for customers is on our product roadmap for future development.
• Creating and updating customers: The NuOrder company integration will be able to identify the difference between new and existing companies in our system. 
• Customized data mapping: Your Implementation Manager will work with you to map NetSuite data to NuOrder required, standard, and/or custom fields. 
• Multiple billing and shipping addresses for a single company are supported. 
• Custom sync parameters: You will specific the rules for which customers should be synced to NuOrder (e.g. Customer type, groups, checkbox at the customer level, etc.).

• Two-way customer sync is not supported: Your customers must originate in NetSuite and be synced to NuOrder with all the necessary account codes. (This is how NetSuite will recognize the customer when the order is synced back in.) Bi-directional syncing for customers is on our product roadmap for future development.

• Process for New Customers: When working with a new customer in NuOrder, you will need to save the order as a DRAFT. Your team will need to add the new customer record into NetSuite first. The customer will sync to NuOrder on the next run (within 30 minutes). Once the customer is visible in NuOrder, the sales rep can open their draft, select the customer, fill in the buyer's name and email address, and submit the official order.

• Create buyers in NuOrder by extracting buyer name and email from NetSuite contacts
• Delete buyers in NuOrder

• Warehouses: Multiple warehouses are supported. You will specify which warehouse locations should be synced to NuOrder.
• Immediate ATS (available-to-sell): The ATS extracts from the "quantity available" field in NetSuite. If different quantities should be visible in NuOrder, let your Implementation Manager know.
• WIP (work-in-progress): WIP quantities can be extracted from NetSuite Purchase Orders, Transfer Orders, and Inbound Shipments. 
• Prebook: For items that should have unlimited quantity available in NuOrder, the following custom fields will be utilized from the NuOrder-NetSuite bundle: 
  • Prebook (boolean)
  • Prebook Start Date (date) - optional 
  • Prebook End Date (date) - optional

• NetSuite Supply Allocation Tool: NuORDER's Inventory integration can work with NetSuite's free Supply Allocation Tool. If Supply Allocation is not configured within your NetSuite environment, please work with your NetSuite admin. The NuOrder Team cannot advise on how to properly configure the tool.

• Pricesheets will be used to support more granular pricing levels within a currency. For example, if a category of customers have product price points that differ from your other customers dealing in the same currency.
• A price sheet will include a list of all items and the associated price, and whether the item is active for that particular price price sheet.
• Pricesheets are often referred to as PriceLevels in NetSuite.

• Customers not assigned to a price sheet will receive the default wholesale and retail prices from the product data.

• Custom Sales Order Form: The Order Export will be configured to sync orders to NetSuite utilizing your existing NetSuite B2B sales order form.
• Custom Fields: Your Implementation Manager will work with you to set up any custom NuORDER fields that should be mapped back to NetSuite needed for your Sales Order. 
• Sync Parameters: NuOrder can export Pending, Approved, and/or Review orders. 
• Sync Frequency: Orders will be exported to NetSuite in near real time (~5minutes).
• Order Fulfillment Process: Orders will be exported to NetSuite with a "Pending Approval" or "Pending Fulfillment" status. Your team will then process the order per your normal approval/fulfillment process. 

• Importance of Internal IDs: When the integration exports an order to NetSuite, the NetSuite internal ID for the customer, address, and every item (to the size level) is sent to NetSuite. If any of the IDs are not valid in NetSuite (e.g. the record was deleted), the order will not be able to sync. If this happens, you will need to review the record that was not recognized and resolve the issue.
• Sync Errors: NuOrder will provide your team with a list of common order sync errors, and what action needs to be taken to resolve it. It will be your team’s responsibility to review these notifications, and address any errors that occur.
  • These errors can include things like:

    • Invalid or missing Customer ID (Company code)

    • Invalid or missing Item ID (UPC)

    • Customer is on credit hold in NetSuite

NuOrder's 2way integration is comprised of: 

• Order Creation will import orders created in NetSuite
• Order Edits will import changes to existing NuORDER orders like: 
  • Price changes
  • Adding/canceling line items
  • Canceling orders
  • Shipping Costs
• Order Shipments
  • Shipment & tracking information, including line items shipped 
  • Partial shipments are supported

• Required data to accept a 2way Order Integration for NetSuite: The customer record and all line items must exist in NuOrder to successfully update a NuOrder order.