One-click install
npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill enable-customer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: enable-customer
Source: https://github.com/Orderful/orderful-netsuite-skills/tree/main/skills/enable-customer
Command: npx skills add https://github.com/Orderful/orderful-netsuite-skills --skill enable-customer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill configures a NetSuite parent customer (and its subcustomers) so Orderful-side EDI transactions line up with the right NetSuite enabled transaction records and ship-to identifiers, preventing mismatches that cause missing or stuck EDI flows.

Core Features & Use Cases

  • Audits NetSuite EDI readiness: checks the parent customer ISA ID, subcustomer representation, ship-to N1 ID fields, and existing Orderful Enabled Transaction records for the parent.
  • Cross-references with Orderful partner setup: validates which inbound/outbound document types the Orderful partner relationship enables for that partner.
  • Guided, safe remediation: prompts you to confirm intended changes, supports create/update of enabled transaction records and controlled updates to ship-to N1 IDs, and verifies by re-reading the same state after writes.
  • Guardrails and out-of-scope protection: does not create/delete customers or subcustomers and avoids touching advanced mappings and outbound handling preferences.

Quick Start

Enable customer EDI by running the skill for your target NetSuite parent and answering the prompts to approve the audited gaps and the final plan.

Frequently Asked Questions about enable-customer

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

FAQPage Schema
How do I enable EDI transactions for a NetSuite customer?

NetSuite EDI enablement audits the parent customer's ISA ID, subcustomers, and ship-to N1 identifiers, then reconciles them against Orderful partner relationships to create or update enabled transaction records and prevent missing or stuck EDI flows.

Why are my Orderful EDI flows getting stuck or missing in NetSuite?

EDI flows get stuck or go missing when NetSuite enabled transaction records and ship-to N1 identifiers mismatch the Orderful partner relationship setup. Auditing the parent customer's ISA join data and correcting mismatched enabled transaction records resolves the issue.

What is the process for mapping ship-to N1 identifiers in NetSuite EDI?

Ship-to N1 mapping involves auditing existing NetSuite subcustomer ship-to ID fields, cross-referencing them with Orderful partner setup, and performing controlled updates to confirmed mappings only, then verifying the results by re-reading the state after writes.

Does NetSuite EDI enablement support creating new trading partners?

Yes, NetSuite EDI enablement applies to new trading partners needing the NetSuite side wired for inbound and outbound EDI flows. It configures the parent customer and subcustomers by auditing existing records and creating missing enabled transaction records.

Can I create or delete NetSuite subcustomers during EDI setup?

No, you cannot create or delete NetSuite customers or subcustomers during EDI setup. The process is limited to creating and updating enabled transaction records and confirmed ship-to N1 identifiers, leaving advanced mappings and outbound handling preferences untouched.