custom-process-transactions

Design and deploy NetSuite SuiteScripts for Orderful custom EDI transaction processing.

6|6|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill custom-process-transactions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: custom-process-transactions
Source: https://github.com/Orderful/orderful-netsuite-skills/tree/main/skills/custom-process-transactions
Command: npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill custom-process-transactions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you implement NetSuite SuiteScript extensions for Orderful’s “Process as Custom” flow when standard JSONata-based mapping can’t express your inbound or outbound EDI requirements.

Core Features & Use Cases

  • Inbound “Process as Custom” (SuiteScript MapReduce): stages inbound EDI JSON from customrecord_orderful_transaction, parses custrecord_ord_tran_message, creates/updates the correct NetSuite records, and sets a terminal success/error status.
  • Outbound “Process as Custom” (SuiteScript MapReduce or User Event / WorkflowAction): builds the outbound payload and stages it by writing a customrecord_orderful_transaction in “Ready To Send” for the SuiteApp to POST.
  • Maintainable deployment pattern: enforces the required sibling *_Orderful_lib.js pattern, consistent script-parameter naming, and safe status transitions so transactions don’t get stuck retrying forever.
  • Correct doc-series scoping (800 vs 900): guides you to configure the right entity (Customer vs Vendor/Location for 900-series) before writing code, including the 900-series lifecycle mapping to avoid incorrect source/target assumptions.

Quick Start

Ask Claude Code for a custom-process script plan for your specific doc type and direction, then request scaffolded steps that include the mandatory library file, the correct entity configuration, and the deployment parameter checklist.

Frequently Asked Questions about custom-process-transactions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle EDI transaction mappings in NetSuite when JSONata is not sufficient?

When JSONata is insufficient for EDI transaction mappings, you can implement NetSuite SuiteScripts using Orderful's Process as Custom flow to handle non-standard document types and custom source or target NetSuite record types.

What is the correct way to stage outbound EDI transactions in NetSuite for a separate sending job?

To stage outbound EDI transactions, your SuiteScript must build the payload and write a customrecord_orderful_transaction record in the Ready To Send status, allowing the separate sending job to POST it.

How do I filter inbound saved searches for custom EDI processing in NetSuite SuiteScript?

Inbound saved searches for custom EDI processing must filter records on the pending_cust_process status to correctly identify transactions awaiting your SuiteScript MapReduce script execution.

Does Orderful's custom EDI processing require a specific SuiteScript file structure?

Yes, custom EDI processing requires a sibling library-file pattern, using a consistent *_Orderful_lib.js file alongside your script, to ensure maintainability and safe status transitions.

How do I manage environment-dependent NetSuite record IDs in custom EDI SuiteScripts?

Environment-dependent NetSuite record IDs should be managed using script parameters, allowing your custom EDI SuiteScripts to safely reference the correct configuration across different NetSuite accounts.

Why do my custom NetSuite EDI transactions get stuck retrying forever?

Custom EDI transactions get stuck retrying forever if your SuiteScript does not enforce safe terminal status transitions, failing to set a success or error status after processing the customrecord_orderful_transaction.