Skip to main content

Configure and run flows in the Orderful – NetSuite integration template

Stephen Brandt
  • Updated

Contents

Additional record mapping is required to integrate the template’s exports and imports with your Orderful and NetSuite apps.

Note that all of your flows are disabled when first installed. After configuring the flows, you may enable them in your Flows dashboard or in Flow Builder with the Off/On toggle button. then run or schedule each flow.

All flows in this template are configured for a single sample trading partner, “NORDSTROM,” That is, wherever you see record mapping in an import or source fields referenced in scripts, those fields are specific to Nordstrom records and you must modify them for another partner, such as Amazon, Best Buy, or CommerceHub, according to their field names as shown in the sample data exported for that partner. Similarly, if you add additional partners to a flow, add those fields to your scripts and mappings.

Orderful purchase orders (850) to NetSuite sales orders

On a scheduled basis, this flow retrieves new Purchase Order transactions (transaction type 850) from Orderful and creates Sales Orders in NetSuite.

Flow details

  • Export source: Orderful
  • Import destination: NetSuite
  • Built-in export: Get Orderful transactions by polling bucket ID (850 - purchase orders) – get all transactions from Orderful by polling bucket ID
  • Built-in lookup: Get Orderful transaction by transaction ID – get a transaction from Orderful by transaction ID 
    • postResponseMap hook: Processing orderful transactions(850).js – avoid loops from the nested arrays and store required elements in a single loop
  • Built-in import: Import NetSuite sales orders – add (or ignore) sales orders into NetSuite with purchaseordernumber as the lookup identifier
  • Built-in import: Import Orderful transaction status – update transaction status into Orderful with ID as the lookup identifier

Before you begin

  1. Customers should be present in both Orderful and NetSuite.
  2. Items should be the same in both Orderful and NetSuite.

Setup instructions

  1. Configure static mapping for Shipping Method (InternalId) for your NetSuite configuration in Import NetSuite sales orders.
  2. Configure hard-coded mapping for Items : Price Level (InternalId) and Items : Tax Code (InternalId) in Import NetSuite sales orders according to your business rules.
  3. Configure dynamic mapping for Items : Item (InternalId) and Customer (InternalId) according to your business rules in Import NetSuite sales orders.
  4. Configure hard-coded mapping for deliveryStatus in Import Orderful transaction status, according to your business rules.
  5. Add Subsidiary mapping according to your business rules in Import NetSuite sales orders.
  6. In the export Get Orderful transactions by polling bucket ID (850 - purchase orders), enter the ID for your Orderful poller in the Polling bucket ID setting.
Field mappings: Import NetSuite sales orders
Field mappings: Import Orderful transaction status

A bucket is a logical collection of transactions that have been processed by the Orderful platform and are ready for integrator.io to poll. Enable polling with the following steps:

  1. Sign into Orderful and navigate to the Communication channels page.

  1. From the Create channel menu, select Poller.

  1. Give your new poller communication channel a name and click Create.

You can now assign the new poller to any of your inbound relationships.

Once a transaction is available in a bucket, it can be retrieved by polling the API, as follows:

  1. Find the communication channel in your Communication channels page and click to open it.
  2. The resulting details include a Retrieval URL with a unique ID in the path. Copy the ID for your export’s Polling bucket ID value.

Orderful purchase order change requests (860) to NetSuite sales orders

On a scheduled basis, this flow retrieves Purchase Order Change Request transactions (type 860) from Orderful and updates existing Sales Orders in NetSuite that are in a pending approval/fulfillment status.

Flow details

  • Export source: Orderful
  • Import destination: NetSuite
  • Built-in export: Get Orderful transactions by polling bucket ID (860_PURCHASE_ORDER_CHANGE_REQUEST_BUYER_INITIATED) – get all transactions from Orderful by polling bucket ID
  • Built-in lookup: Get Orderful transaction by transaction ID – get a transaction from Orderful by transaction ID 
    • postResponseMap hook: Processing orderful purchase order change request (860).js – avoid loops from the nested arrays and store required elements in a single loop
  • Built-in lookup: Get NetSuite sales order by purchase order number – get a sales order from NetSuite by purchase order number
  • Built-in import: Import NetSuite sales orders – update sales orders into NetSuite with purchaseordernumber as the lookup identifier
  • Built-in import: Import Orderful transaction status – update transaction status into Orderful with id as the lookup identifier

Before you begin

  1. Purchase orders in Orderful and sales orders in NetSuite should be the same, already synced by running Orderful purchase orders (850) to NetSuite sales orders first.
  2. Orderful purchase order numbers should be stored as a PO# in NetSuite sales orders.
  3. Items should be the same in both Orderful and NetSuite.

Setup instructions

  1. Configure hard-coded mapping for Items : Price Level (InternalId) and Items : Tax Code (InternalId) in Import NetSuite sales orders according to your business rules.
  2. Configure dynamic mapping for Items : Item (InternalId) according to your business rules in Import NetSuite sales orders.
  3. Configure hard-coded mapping for deliveryStatus in Import Orderful transaction status.
  4. In the export Get Orderful transactions by polling bucket ID (860_PURCHASE_ORDER_CHANGE_REQUEST_BUYER_INITIATED), enter the ID for your Orderful poller in the Polling bucket ID setting.
Field mappings: Import NetSuite sales orders
Field mappings: Import Orderful transaction status

NetSuite item shipments to Orderful ship notices/manifests (856)

On a scheduled basis, this flow retrieves new item fulfillments from NetSuite and creates Ship Notice transactions (type EDI 856) in the Orderful platform.

Flow details

  • Export source: NetSuite
  • Import destination: Orderful
  • Built-in export: Get NetSuite item shipments – get all item shipments from NetSuite that have been created since this flow last ran
    • preSavePage hook: Processing Orderful transactions (856).js – counts the number of items to add the numeric count sequentially for hierarchicalIDNumber in the items
  • Built-in import: Import Orderful ship notices/manifests (856) – add ship notices/manifests into Orderful
  • Built-in lookup: Get Orderful transaction errors by transaction id (856) – get a transaction error from Orderful by transaction ID
    • preSavePage hook: Processing orderful valid transactions (856).js – check whether the transaction is valid or invalid

Before you begin

  1. Purchase orders in Orderful and sales orders in NetSuite should be the same, already synced by running Orderful purchase orders (850) to NetSuite sales orders first.
  2. Orderful purchase order numbers should be stored as a PO# in NetSuite sales orders. 

Setup instructions

Configure hard-coded mapping for each of the following fields in Import Orderful ship notices/manifests (856), according to your business requirements:

  • sender:isaId
  • receiver:isaId
  • type:name
  • stream
  • N1_loop.partyIdentification.
    entityIdentifierCode
  • packagingCode
  • weightQualifier
  • weight
  • unitOrBasisForMeasurementCode
  • identificationCode
  • identificationCodeQualifier
  • transportationMethodTypeCode
  • dateTimeQualifier
  • hierarchicalIDNumber
  • hierarchicalLevelCode
  • referenceIdentificationQualifier
  • hierarchicalParentIDNumber
  • marksAndNumbersQualifier
  • numberOfUnitsShipped
  • unitOrBasisForMeasurementCode
  • productServiceIDQualifier
  • hashTotal
  • transactionSetPurposeCode

Customize the handlebars template

Follow the instructions below to modify the handlebars template for the Orderful HTTP request body:

  1. In Flow Builder, click to edit Import Orderful ship notices/manifests (856).
  2. In the Edit import panel, scroll down to the section How would you like the records imported.
  3. Under Build HTTP request body, click Launch.
  4. In the resulting editor, customize according to your requirements and preview the sample records.
HTTP request body: Import Orderful ship notices/manifests (856)

NetSuite invoices to Orderful invoices (810)

On a scheduled basis, this flow retrieves new invoices from NetSuite and creates Invoice transactions (type 810) in the Orderful platform. 

Flow details

  • Export source: NetSuite
  • Import destination: Orderful
  • Built-in export: Get NetSuite invoices – get all invoices from NetSuite that have been created since this flow last ran
  • Built-in import: Import Orderful transactions (810) – add transactions into Orderful
  • Built-in lookup: Get Orderful transaction errors by transaction ID (810) – get a transaction error from Orderful by transaction ID
    • preSavePage hook: Processing Orderful valid transactions (810).js – check whether the transaction is valid or invalid

Before you begin

  1. Purchase orders in Orderful and sales orders in NetSuite should be the same, already synced by running Orderful purchase orders (850) to NetSuite sales orders first.
  2. Orderful purchase order numbers should be stored as a PO# in NetSuite sales orders. 

Setup instructions

Configure hard-coded mapping for each of the following fields in Import Orderful transactions (810), according to your business requirements:

  • sender:isaId
  • receiver:isaId
  • type:name
  • stream
  • SAC_loop:servicePromotionAllowanceOrChargeInformation:
    servicePromotionAllowanceOrChargeCode
  • SAC_loop:servicePromotionAllowanceOrChargeInformation:
    allowanceOrChargeIndicatorCode
  • SAC_loop:servicePromotionAllowanceOrChargeInformation:
    unitOrBasisForMeasurementCode
  • PID_loop:productItemDescription:itemDescriptionTypeCode
  • baselineItemDataInvoice:unitOrBasisForMeasurementCode
  • baselineItemDataInvoice:productServiceIDQualifier
  • baselineItemDataInvoice:basisOfUnitPriceCode
  • N1_loop.partyIdentification.entityIdentifierCode
  • N1_loop:partyIdentification:entityIdentifierCode
  • N1_loop:partyIdentification:identificationCode
  • termsOfSaleDeferredTermsOfSale:percentOfInvoicePayable
  • termsOfSaleDeferredTermsOfSale:termsBasisDateCode
  • termsOfSaleDeferredTermsOfSale:deferredAmountDue
  • termsOfSaleDeferredTermsOfSale:termsTypeCode
  • referenceInformation:referenceIdentificationQualifier
  • transactionSetHeader:transactionSetIdentifierCode
  • carrierDetails:standardCarrierAlphaCode
  • dateTimeReference:dateTimeQualifier

Customize the handlebars template

Follow the instructions below to modify the handlebars template for the Orderful HTTP request body:

  1. In Flow Builder, click to edit Import Orderful transactions (810).
  2. In the Edit import panel, scroll down to the section How would you like the records imported.
  3. Under Build HTTP request body, click Launch.
  4. In the resulting editor, customize according to your requirements and preview the sample records.
HTTP request body: Import Orderful transactions (810)

 

Related articles

Comments

2 comments

Date Votes
  • Chris Mark

    thanks for this. please note that some of this is outdated, orderful has upgraded to v3 api and i've had to make some customizations to the templates. great starting point though!

    0
  • Stephen Brandt Documentation Manager Community moderator
    • Edited
    Engaged
    Great Answer
    Top Contributor
    Celigo University Level 3: Master

    Chris Mark, right you are, and I'm glad to hear that the template nonetheless served as a good basis for your integration. 

    UPDATE – 6/15/2021:
    The Orderful – NetSuite template has been re-released in the integrator.io Marketplace to include support for the Orderful v3 API. This article has also been revised to reflect the new flows. 

    1

Please sign in to leave a comment.