Oracle NetSuite and Orderful integration

What moves between them

Purchase orders and vendor bills flow from Oracle NetSuite to Orderful. ml-connector polls Oracle NetSuite every 15 minutes (or on a schedule you set) for new or changed purchase orders and vendor bills, translates them to EDI 850 (purchase order) and 810 (invoice) documents using the supplier's ISA identifiers stored in Oracle NetSuite vendor records, and POSTs them to Orderful. Incoming EDI 855 (purchase order acknowledgment) and 856 (ship notice) documents flow from Orderful back to Oracle NetSuite; ml-connector polls Orderful or receives webhooks, parses the EDI, and writes acknowledgments and receipt records into Oracle NetSuite as line-item acknowledges and goods receipt transactions. Reference data such as vendors, items, and departments flows both directions to keep ISA identifiers and line-level detail aligned.

How ml-connector handles it

ml-connector stores the Oracle NetSuite account ID and OAuth certificate encrypted and obtains a fresh bearer token before each API call (tokens expire after 60 minutes and have no refresh token). It accepts the static Orderful API Key encrypted and presents it in the orderful-api-key header on every request, checking for 429 rate limits and backing off with exponential jitter. Vendor records in Oracle NetSuite must contain the ISA sender and receiver identifiers for that vendor; ml-connector reads these fields, includes them in the Mosaic v4 create request to Orderful, and validates that ISA pairs exist before posting. Because Oracle NetSuite has no webhook signature, ml-connector uses an IP allowlist to secure the pull-only polling from Oracle NetSuite. Incoming EDI from Orderful arrives either as webhooks (if your endpoint is publicly reachable) or via polling; ml-connector handles both and writes back to Oracle NetSuite using a dedicated integration role with permission to create/edit purchase order line acknowledges and goods receipt transactions. Every record carries a full audit trail and can be replayed if a downstream write fails.

A real-world example

A mid-market discrete manufacturer sources components from twelve suppliers via EDI. The company runs Oracle NetSuite for procurement, inventory, and finance. Before the integration, the procurement team entered purchase orders in Oracle NetSuite, then manually exported them as CSV, translated them to EDI 850 using their legacy EDI software, and emailed or uploaded them to Orderful. When suppliers sent back acknowledgments (855) and ship notices (856) through Orderful, the EDI was translated to email, read by hand, and line items were entered into Oracle NetSuite receipts one by one. With Oracle NetSuite and Orderful connected, each new purchase order flows automatically to Orderful as an EDI 850, routed to the correct supplier by ISA identifier, and supplier responses (855 and 856) flow back into Oracle NetSuite as receipt records that close the purchase order lines. The procurement team now spends fifteen minutes per day reviewing the audit log instead of four hours re-keying EDI.

What you can do

• •Poll Oracle NetSuite for new and changed purchase orders, translate them to EDI 850 documents, and POST them to Orderful with the supplier's ISA identifiers.
• •Receive EDI 855 purchase order acknowledgments and 856 ship notices from Orderful (via webhook or polling) and write them into Oracle NetSuite as line-item acknowledges and goods receipt transactions.
• •Sync vendor ISA identifiers, items, and departments between Oracle NetSuite and Orderful so EDI documents are routed to the correct supplier and line details match across both systems.
• •Handle OAuth 2.0 certificate-based authentication for Oracle NetSuite (with 60-minute token refresh) and API Key authentication for Orderful, with encrypted credential storage.
• •Provide a full audit trail on every purchase order, invoice, acknowledgment, and receipt, with error replay and exponential backoff on rate limits.

Questions

Which direction does data move between Oracle NetSuite and Orderful?

Purchase orders and invoices flow from Oracle NetSuite to Orderful as EDI 850 and 810 documents. Acknowledgments, ship notices, and change orders flow from Orderful back into Oracle NetSuite as purchase order line acknowledges and goods receipt transactions. Vendor ISA identifiers and item reference data are synced bidirectionally to keep both systems aligned.

How does ml-connector handle the ISA identifier requirement in Orderful?

ISA sender and receiver identifiers must be stored in Oracle NetSuite vendor records. When ml-connector reads a purchase order, it looks up the vendor's ISA identifiers, includes them in the Mosaic v4 request to Orderful, and validates that both ISA pairs exist before posting. If ISA identifiers are missing or invalid, the transaction is logged as an error and can be replayed after the vendor record is corrected.

Does Oracle NetSuite webhook authentication work with Orderful, or does ml-connector use polling?

Oracle NetSuite Event Subscriptions do not include HMAC signatures, so webhooks alone are not secure enough for EDI. ml-connector uses polling on a schedule (every 15 minutes by default, configurable per customer) to read purchase orders and vendor bills from Oracle NetSuite. For incoming EDI from Orderful, ml-connector can receive webhooks if your endpoint is publicly reachable, or fall back to polling Orderful's polling-buckets API every 5-10 minutes.