🚧

Customization Compatibility

Orderful For Netsuite may not function as intended if your NetSuite environment includes extensive customizations, scripts, or third-party integrations that alter standard workflows.

Extensibility is a key design consideration of Orderful For Netsuite and custom compatibility remediation may require additional work.

This page provides a complete overview of the Orderful for NetSuite SuiteApp's capabilities. For installation and setup, see Quick Start.

Supported EDI Transaction Types

The SuiteApp supports the following EDI transaction types with full native processing. Each type can also be configured in Custom Process Mode on a per-customer basis for developer-handled workflows.

Order-to-Cash

850 Purchase Order & 875 Grocery Purchase Order

• Direction: Inbound to NetSuite
• Mapping Definition: 850, 875
• Creates: Sales Order
• Functionality:
  • Creates Sales Orders in NetSuite from inbound EDI purchase orders
  • Supports item lookups via multiple product qualifiers
  • Customer-specific item cross-references with custom lookup support
  • Kit/SLN item handling for grouped and component-level items
  • Automatic order splitting by ship-to address, store location, or SDQ segment
  • Can use either EDI pricing or NetSuite pricing (configurable per customer)
  • Supports ship-to cross-referencing for store locations and distribution centers
  • Location assignment and multi-subsidiary support
  • Discount & Allowance Handling: Supports SAC loop processing with dollar amounts and percentages, single and multiple header-level discounts, and line-level discounts. See Discounts & Allowances.

For details on processing inbound orders, see Importing Orders.

---

855 Purchase Order Acknowledgment

• Direction: Outbound from NetSuite
• Mapping Definition: 855
• Source Record: Sales Order
• Functionality:
  • Can automatically acknowledge orders when inventory is available
  • Allows for pending approval workflow
  • Supports customizable item ship date sources
  • Provides acknowledgment of accepted/rejected line items
  • Triggered after a Sales Order is processed in NetSuite

For workflow setup, see Acknowledging Orders.

---

856 Advance Ship Notice (ASN)

• Direction: Outbound from NetSuite
• Mapping Definition: 856
• Source Record: Item Fulfillment
• Functionality:
  • Three packing methods supported:
    • Manual Packing: User-controlled carton/pallet creation and item assignment via the built-in packing application
    • Auto Packing: Automatic carton generation based on "Units per Carton" settings
    • Custom Packing Source: Integration with external packaging data via NetSuite Analytics DataSets
  • Supports SSCC18 serial number generation for cartons and pallets
  • Supports hierarchical packaging data (pallets containing cartons containing items)
  • Can consolidate multiple Item Shipments into a single 856
  • Supports tracking numbers and package dimensions
  • Lot number and expiration date support
  • Shipping Labels with barcode generation

For workflow setup, see Fulfilling Orders.

---

810 Invoice & 880 Grocery Invoice

• Direction: Outbound from NetSuite
• Mapping Definition: 810, 880
• Source Record: Invoice
• Functionality:
  • Generated from NetSuite invoices
  • Maps NetSuite invoice data to standard EDI 810 or 880 format
  • Supports shipping data cross-references via Shipping Lookup
  • Supports allowances and charges via Authorized Discount mappings
  • Standalone invoice support (not linked to a sales order)
  • Automatic send on invoice creation (configurable)

For workflow setup, see Invoicing Orders.

---

860 Change Order (Buyer Initiated)

• Direction: Inbound to NetSuite
• Modifies: Existing Sales Order
• Functionality:
  • Applies buyer-requested modifications to existing Sales Orders
  • Matches change orders to existing sales orders via the original purchase order number
  • Configurable options:
    • Allow/deny quantity changes
    • Allow/deny pricing changes
    • Allow/deny requested ship date changes

---

864 Text Message

• Direction: Inbound to NetSuite
• Creates: Note record
• Functionality:
  • Receives EDI text messages and creates Note records attached to the associated customer or vendor entity in NetSuite

---

Warehouse & 3PL

For full setup instructions, see 3PLs and 900-Series Transactions.

940 Warehouse Shipping Order

• Direction: Outbound from NetSuite
• Source Record: Sales Order / Transfer Order
• Functionality:
  • Sends fulfillment instructions to 3PL warehouse partners
  • Generated from Sales Orders and Transfer Orders
  • Automatic send on order approval (configurable)
  • Custom workflow trigger option

---

945 Warehouse Shipping Advice

• Direction: Inbound to NetSuite
• Creates: Item Fulfillment
• Functionality:
  • Receives fulfillment confirmations from 3PL warehouses
  • Generates Item Fulfillments from Sales Orders and Transfer Orders
  • Line item quantity matching and carton data
  • Tracking number and shipping carrier assignment

---

943 Warehouse Stock Transfer Shipment Advice

• Direction: Outbound from NetSuite
• Source Record: Item Fulfillment (Transfer Order)
• Functionality:
  • Sends transfer order shipment details to 3PL warehouse partners

---

944 Warehouse Stock Transfer Receipt Advice

• Direction: Inbound to NetSuite
• Creates: Item Receipt
• Functionality:
  • Receives transfer order receipt confirmations from 3PL warehouses
  • Creates Item Receipt records in NetSuite from Transfer Orders

---

947 Warehouse Inventory Adjustment Advice

• Direction: Inbound to NetSuite
• Creates: Inventory Adjustment
• Functionality:
  • Receives inventory adjustment notifications from 3PL warehouses
  • Configurable adjustment reason codes
  • Default account assignment for adjustments
  • Positive and negative adjustment support

---

Inventory

846 Inventory Advice

• Direction: Outbound from NetSuite
• Functionality:
  • Provides inventory availability reporting to trading partners
  • Can be configured using either NetSuite Saved Searches or Datasets
  • Supports location-specific inventory reporting
  • Allows mapping of NetSuite locations to partner-assigned location IDs
  • Per-customer sending configuration
  • JSONata support for custom data shaping

For setup, see Inventory Advice.

---

Simplified Formats

For trading partners that don't use X12, the SuiteApp supports simplified (non-X12) versions of core order-to-cash transactions:

Simplified formats use the same processing pipelines as their X12 counterparts but accept/produce a streamlined JSON payload structure.

---

Key Capabilities

Mapping

The SuiteApp supports both Orderful JSON and Mosaic data formats for supported transactions, and includes a JSONata mapping engine for customizing how EDI data maps to and from NetSuite fields.

• Standard mapping: The SuiteApp ships with default mappings for all supported transaction types. Most customers use these as-is.
• Mapping by exception: Per-customer JSONata expressions can override specific fields without replacing the entire mapping.
• Inbound mapping: Customize how inbound EDI fields populate NetSuite records.
• Outbound mapping: Customize how NetSuite fields populate outbound EDI documents.

For advanced mapping, see the Developer Extensibility Guide.

Packing

The SuiteApp includes a built-in packing application for creating ASN (856) packaging data:

• Manual packing: Interactive carton and pallet creation with item assignment
• Auto packing: Automatic carton generation based on the "Units per Carton" configuration on each item
• Custom packing source: Pull packaging data from external sources via NetSuite Analytics

Packing features include:

• SSCC18 serial number generation (configurable GS1 prefix)
• Hierarchical packaging: shipment > order > tare (pallet) > pack (carton) > item
• Package dimensions and weight
• Tracking number assignment

Shipping Labels

Generate and print SSCC18 shipping labels with GS1 barcodes directly from NetSuite. Labels can be configured per customer and printed for cartons and pallets during the fulfillment process.

For setup, see Shipping Labels.

Handling Preferences

Each outbound transaction type has configurable handling preferences that control when EDI documents are generated and sent:

When set to Custom Workflow, the SuiteApp stages the data but does not automatically send. Outbound transactions can then be triggered manually via the "Generate & Send" button or via custom SuiteScript workflow actions.

For details, see Outbound Transaction Handling Preferences.

Custom Process Mode

Any transaction type can be configured to "process as custom" on a per-customer, per-transaction-type basis. When enabled:

• Inbound: The SuiteApp stages the EDI data as an Orderful Transaction record with status "Pending Custom Process" but does not create NetSuite records (Sales Orders, Fulfillments, etc.). A developer can build SuiteScript to process these records.
• Outbound: The native "Generate & Send" buttons are disabled. A developer must build custom outbound generation logic.

This is useful for:

• Transaction types with non-standard business logic for a specific customer
• Edge cases that the native processing doesn't cover
• Organizations that want to receive EDI data but handle processing in their own workflows

See the Developer Extensibility Guide for implementation details, including Custom Process Inbound Transactions.

---

Configuration

Item Configuration

• Product identifier qualifiers: Look up items by UPC, Vendor Part Number, Buyer Part Number, GTIN, and more
• Custom item lookups: Per-customer item cross-reference tables for trading partners with non-standard identifiers. See Custom Item Lookups.
• Kit/SLN handling: Group and component-level item resolution for kits and SLN segments. See Kit/SLN Item Handling.

For setup, see Items.

Customer Configuration

• EDI enablement: Per-customer activation of specific transaction types with individual settings. See Enabling Customers for EDI.
• Customer-level settings: Each customer can have unique handling preferences, mapping rules, and item cross-references
• ISA ID assignment: Company-level or customer-specific ISA identifiers

Transaction Control

• Auto-acknowledgment: Automatically generate 855s when sales orders are approved
• Order splitting: Split inbound POs by ship-to address, store location, or SDQ segment
• Pricing source: Use EDI prices or NetSuite prices (configurable per customer)
• Consolidation: Combine multiple fulfillments or invoices into a single EDI transaction

Identifiers & Credentials

• Company ISA ID: Primary interchange sender/receiver identifier
• Test ISA ID: Separate identifier for sandbox/testing
• Subsidiary ISA IDs: Override ISA IDs at the subsidiary level for multi-entity organizations
• GS1 Company Prefix: For SSCC18 serial number generation
• DUNS Number: Trading partner identification for remittance information

For setup, see Global Settings.

Integration

• Scheduled polling: Inbound transactions sync every 15 minutes via Poller Communication Channel
• Manual send: Send individual outbound transactions on demand
• Workflow actions: SuiteScript workflow action support for generating and sending transactions programmatically
• Test and production mode: Separate ISA IDs and configuration for sandbox testing
• Mapping custom fields via JSONata: Self-service field customization per customer