inject-test-transaction

Inject synthetic TEST-stream EDI transactions into Orderful and verify sandbox routing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires dotenv, and includes scripts (resource) components.

What problem does it solve?

It prevents accidental processing of TEST-stream EDI transactions in NetSuite production by forcing a synchronous routing verification against both Orderful polling buckets and then monitoring sandbox ingest.

Core Features & Use Cases

  • Sandbox-safe test injection with guardrails: Builds a TEST-stream transaction payload (rewriting PO/control numbers for grep-ability) and posts it to Orderful.
  • Two-bucket routing verification with an abort tripwire: Polls both the sandbox and production polling buckets; if the transaction appears in the production bucket, it immediately calls confirm-retrieval to evict it and escalates with evidence.
  • Sandbox ingest monitoring via SuiteQL: Watches the customer’s sandbox NetSuite for the Orderful transaction record state transitions and reports Sales Order creation (or validation failures), while defensively checking production for leakage during the watch window.

Quick Start

Ask the skill to inject a synthetic inbound EDI transaction into your Orderful-to-NetSuite customer sandbox and to verify it never touches production.

Frequently Asked Questions about inject-test-transaction

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

FAQPage Schema
How do I safely test inbound EDI transactions in a NetSuite sandbox without risking production?

The Orderful injection process works by building a TEST payload, posting it to the Orderful API, polling both sandbox and production polling buckets for routing verification, and monitoring sandbox ingest state via SuiteQL against custom NetSuite transaction records.

What happens if a test EDI transaction accidentally routes to the production polling bucket?

Yes, you can validate inbound 850, 855, 856, and 945 EDI behaviors by injecting synthetic transactions with rewritten PO and control numbers for grep-ability, allowing you to test mapping changes and reproduce failures using realistic fixtures.

How do I monitor an Orderful transaction state in NetSuite after a sandbox injection?

You need a configured Orderful environment with API access to POST /v3/transactions and GET /v3/polling-buckets/{id}, along with NetSuite sandbox access for SuiteQL monitoring, and the dotenv dependency to manage environment variables.

Why do I need to rewrite PO and control numbers when testing EDI integrations?

You need to rewrite PO and control numbers when testing EDI integrations to ensure uniqueness and grep-ability of synthetic test transactions, preventing duplicate document errors and making it easier to trace test data through the NetSuite sandbox ingest process.