Understand the Orderful – NetSuite Quickstart integration template

Stephen Brandt

Updated October 17, 2024 10:49

Orderful is a software-as-a-service (SaaS) platform that modernizes traditional B2B data syncing by delivering EDI over a standard REST API in JSON format. The Orderful API has an underlying canonical model that allows for a one-to-many integration architecture in which you can connect your ERP, such as NetSuite, to Orderful and then trade with any number of partners. This approach offers advantages over building custom EDI flows in integrator.io, which are useful only for a 1:1 integration with each trading partner.

The Orderful – NetSuite template contains integration flows to automate processes for Orderful customers who are syncing purchase orders, sales orders, and shipments with NetSuite. After installing and configuring the Orderful – NetSuite template, you can enable only those flows needed for your business requirements.

Features & benefits

Turn B2B into A2A – that is, you can now transform business-to-business one-off data syncing into true application-to-application integrations, without the need for in-house EDI expertise
Self-service user experience – when you customize the Celigo integrator.io template you gain control over the user interface in your company’s integrations
Orderful offers a unique and differentiated pricing model, priced by the number of trading partners and transactions, instead of the charge per document type that can quickly become expensive at scale
An established and growing network of Orderful trading partners – including private value-added network (VAN-only) partners – gives you a headstart for common vendors and customers
Cloud integrations accessible to anyone – whether you are an application admin, business analyst, advanced end user, or IT developer
Integrate effortlessly with a purpose-built, out-of-the-box integration
Save time and minimize errors by eliminating manual data entry

Supported integration flows

The Celigo quickstart bundle contains workflows that you can easily configure and deploy without coding or IT support. The following built-in flows sync from the specified source data to the corresponding destination.

Orderful to NetSuite

Flow	What’s not supported
Orderful purchase orders (850) to NetSuite sales orders	Update, delete, cancel, refund Sales Orders Create, update, delete Customer Records Create SKUs/items Discounts and taxes Multi-currencies Variances Kit, Lot Numbered, Serialized, Bin, and Matrix items
Orderful purchase order change requests (860) to NetSuite sales orders	Create, delete, cancel, refund Sales Orders Create, update, delete Customer Records Create SKUs/items

NetSuite to Orderful

Flow	What’s not supported
NetSuite item shipments to Orderful ship notices/manifests (856)	Update, delete Fulfillments Kit, Lot Numbered, Serialized, Bin, and Matrix items
NetSuite invoices to Orderful invoices (810)	Update, delete Invoices Kit, Lot Numbered, Serialized, Bin, and Matrix items
NetSuite items to Orderful inventory inquiries/advices (846)	Update, delete Items Kit items

Orderful integration concepts and guidelines

If you’re unfamiliar with Orderful terminology, the three main components that you will be working with in your integration are as follows:

Relationships – Roughly the equivalent of an integration flow in integrator.io. Each relationship consists of a...
- Source, the sending organization
- Destination, the receiving organization
- Transaction type, such as EDI 850 or 810
- Transactions exchanged with the source
The destination organization and transaction type belong to the same relationship. For example, if Walmart and Amazon are buying your products, you must create four relationships within Orderful.
Transactions – Analogous to EDI transaction records in an ERP like purchase orders or invoices.
Guidelines – The Orderful counterpart to an integrator.io EDI file definition rule. A guideline can effectively be used to validate and normalize the data that is passed through it. Your organization should set up one guideline per transaction type traded. For example, if you trade a purchase order and an invoice, then create one purchase order guideline and one invoice guideline.

Common tasks in the Orderful environment necessary for syncing data in this template include...

Create Orderful purchase orders and purchase order change requests
Generate sample Orderful records for an EDI document

Create Orderful purchase orders and purchase order change requests

Navigate to the Transactions page.

From the Create transaction menu, choose Upload transaction.

Select a .json, .x12, or .txt file from your computer. (The file must contain either JSON- or X12-formatted data.)

Make sure to provide required fields like name, billing address, shipping address, payment method, shipment method, and whether it’s for single or multiple items. It’s important that these fields are not empty when you import the PO into NetSuite.

Note: The Orderful purchase order number should, of course, be the same for the original PO and the change request.

Generate sample Orderful records for an EDI document

Orderful offers a tool to help you determine the correct fields in your system of record to map to the Orderful API.

Navigate to the Integration assistance page.

Select the settings for your flow type, for example:
- Transaction type: 810 invoice
- Direction: Out (for an export)
- Format: JSON
- Trading partner ISA IDs: Amazonia-ofd

Integration assistance automatically provides sample data with the required fields. Use this sample data to configure your Orderful import.

Error handling

Most integrator.io error messages will clearly explain the error and suggest troubleshooting methods. If you are unsure of what the error means, contact Celigo support.

For errors passed through from NetSuite or Orderful, see the respective endpoint documentation.