Orderful

Audit a customer's per-relationship outbound transformation rules at /v2/rules and flag any whitelist that's narrower than the partner's published spec. Run this BEFORE writing JSONata for a new outbound document type — misconfigured rules silently strip required EDI segments at send time, surfacing as "missing field" validation errors that NS-stored messages and /v3/validate both contradict. Use when the user says "audit the rules", "check outbound rules", "the post-fact validations show missing X but the message has it", "before we write outbound JSONata", or any time you're starting outbound work for a customer / partner / doc type that hasn't been validated end-to-end yet.

Author and iterate JSONata expressions that fix outbound EDI message validation errors for a specific customer × document type. Combines NetSuite SuiteQL lookups, the Orderful SuiteApp's JSONata engine, and tight reprocess loops. Use when the user says "write JSONata for the X transaction", "fix this 856/810/855", "the partner is rejecting on validation", "help me iterate on advanced mapping", or "the SF segment is wrong on the outbound 856".

Review a GitHub PR or the current feature branch against the orderful-netsuite-skills rubric. Invoke explicitly; not auto-invoked.

Diagnose and propose fixes for ITEM_LOOKUP_MISSING errors on inbound 850 purchase orders. Combines NetSuite item search, Orderful transaction context, and customer-specific matching conventions to propose a single, scoped lookup record for the contractor to approve. Use when the user mentions a failing 850, a missing item lookup, ITEM_LOOKUP_MISSING, or asks to map a partner part number to a NetSuite item.

Build custom NetSuite SuiteScripts that extend the Orderful SuiteApp's

Fetch structured per-transaction validation errors from Orderful (`dataPath`, `message`, `allowedValues`) instead of screenshotting the UI. Use when iterating on a partner-spec JSONata fix and a transaction is showing INVALID on Orderful, or when the user says "fetch validations", "what's wrong with that transaction", "/fetch-validations", "give me the errors for <txId>", "why is this 856/810/855 invalid", or asks to debug a partner-spec rejection without manual screenshots.

Safely inject a test inbound EDI transaction (e.g., 850, 855, 856) to Orderful and verify it routes to a sandbox SuiteApp instance — never to production. Looks up the right test ISAs from the Orderful relationship, confirms NS sandbox customer wiring matches, posts the transaction, then watches the polling buckets and immediately calls confirm-retrieval if the transaction lands in a prod bucket. After a clean sandbox landing, monitors the target NS for ingest and reports the resulting record state. Use when the user says "inject a test 850", "send a test transaction to sandbox", "test the inbound JSONata change", "let's mock a 945 from the 3PL", or any other "send a synthetic EDI transaction into our system without it touching prod" scenario.

Read the Orderful SuiteApp's inbound diagnostic log (customrecord_orderful_diagnostic) to see the mapped Business Data Object (BDO) for an inbound transaction — what the SuiteApp parsed from the EDI and intended to write to NetSuite. Use when an inbound 850/860/etc. processed "Success" but the resulting Sales Order is missing data (ship-to address, location, item match, store/department), when the user says "check the inbound logs", "why is the SO missing X", "inspect the inbound diagnostics", "/inspect-inbound-diagnostics", or when inbound behavior is mysterious and you'd otherwise start guessing.

Draft a project plan for an Orderful customer onboarding — typically for a specific trading partner connection (e.g., Day Dream onboarding KeHE). Use when a user asks to 'build a project plan for [customer]', 'draft an onboarding plan for [customer] with [partner]', 'create a project plan for [customer] and [partner]', 'what's our plan for [customer]'s [partner] onboarding', or 'I need a plan and target dates for [customer]'. Produces an event-triggered three-phase plan (Pre-stage, Contract and Testing, Cutover) with explicit exit-criteria checklists per phase, an 'Already done' table that builds reader confidence, an 'In flight' table for active work, and a 'What we own this week' assignments table. Phases anchor to commercial gates (commercials close, contract sign, public launch) rather than fixed calendar dates. Internal and customer-facing variants are produced separately when both are needed — never combined.

Set up a recurring background watcher for an Orderful onboarding customer that polls Slack, Gmail, the Orderful org, and Salesforce on a cadence and posts a concise digest back to the current chat whenever new activity is found. Use this whenever a user wants to stay on top of a specific customer's onboarding project without having to ask for updates — triggers include 'watch [customer] for updates', 'set up a watcher for [customer]', 'poll [customer] every hour', 'keep an eye on [customer]', 'background monitor for [customer]', 'don't let me miss anything on [customer]', or 'alert me when something changes on [customer]'. The skill resolves the customer's identifiers across systems, gathers the project stakeholder list, composes a self-contained polling prompt, and schedules it via the scheduled-tasks MCP. Designed for proactive project management — silent on quiet hours, vocal when there's signal.

Generate sample EDI transactions (850 POs, 856 ASNs, 810 invoices, 855 acks, 860 PO changes, 812 credit/debit adjustments) and inject them into Orderful as test-stream transactions, so a customer's connector and integration can be tested before their partnership is live. Uses real production transactions from comparable customers as the structural baseline and substitutes the target customer's product/SKU data. Triggers: 'generate sample 850s for [customer]', 'pre-stage test transactions for [customer] with [partner]', 'manufacture test PO for [customer]', 'inject sample [doc] for [customer]', 'create a test 850 from [partner] to [customer]'. Handles both phases — synthetic when product catalog is unknown (pre-NetSuite-access), real once the customer's catalog is pulled from their ERP. Always uses test stream, never live. Always uses real wire structure from existing partnerships.

This skill should be used when an Orderful customer is approaching their cutover date and the Implementation team needs to verify they're actually ready to flip to LIVE. Triggers on: "go-live readiness for [customer]", "pre-cutover check for [customer]", "is [customer] ready to go live", "run the cutover checklist", "what's blocking [customer] go-live", "ready to cutover [customer]". Produces a structured readiness report with a checklist of pre-cutover requirements, a risk assessment, and a cutover sequence plan.

This skill should be used when an Orderful customer has just closed and the Implementation team needs to absorb the AE handoff. Triggers on: "intake new customer", "process the handoff for [customer]", "AE handoff for [customer]", "start onboarding for [customer]", "new customer just landed", "absorb the handoff doc", "kick off implementation for [customer]". Pulls the AE handoff document, Salesforce account context, any Slack handoff thread, and pre-sales call transcripts from the shared Drive folder, then produces a structured onboarding profile that downstream onboarding skills (kickoff-prep, partner-list-intake, migration-plan) consume.

This skill should be used when the Implementation team is preparing for the customer kickoff call — the first formal Implementation-led meeting after a customer signs. Triggers on: "kickoff prep for [customer]", "prep me for the [customer] kickoff", "build kickoff prep doc", "I have a kickoff call with [customer] tomorrow", "pre-call prep for [customer] kickoff", "AM prep for [customer]". Produces a structured pre-call .docx covering agenda, decisions to lock during the call, expected Q&A, exit criteria, and post-call action items. Reads from the onboarding profile produced by handoff-intake, the Customer Kick-Off SOP, and the shared pre-sales call-transcripts folder.

This skill should be used after partner-list-intake has produced a classified partner list and the Implementation team needs an actionable execution plan. Triggers on: "build the migration plan for [customer]", "execution plan for [customer]", "what should we do first for [customer]'s partners", "stack rank [customer]'s onboarding", "sequence the partner migration", "how do we run [customer]'s migration". Produces an Excel workbook with the execution plan stack-ranked by actionability, an outreach queue grouped by vendor, and a raw data sheet with per-partnership status and gap codes.

Draft an outreach email to an Orderful onboarding customer — welcome notes, pre-kickoff prep, access requests, re-engagement, follow-ups. Use whenever the user asks to write, draft, or send an email to a customer who's in onboarding — pre-kickoff emails asking for system access, welcome / kickoff-prep messages, NetSuite / ERP access requests, requests for partner lists or EDI system credentials, re-engagement notes for stalled customers, or any outbound message to the customer-side stakeholders during onboarding. Also trigger on phrases like 'draft an email to [customer]', 'welcome email for [customer]', 'ask [customer] for NetSuite access', 'send the access request to [customer]', 'pre-kickoff outreach', 're-engage [customer]'. The skill verifies names and emails from Salesforce and Slack before drafting (never invents addresses), structures the email so the lede isn't buried, and saves the result as a Gmail draft with HTML formatting so bold renders properly.