---
title: "Orderful Integration"
description: "Receive retail purchase orders (EDI 850) through Orderful and answer them with purchase order acknowledgments (EDI 855) in normalized JSON. Agents read each order line by line, check it against stock, and send the acknowledgment the trading partner plans against."
url: https://flowrunner.ai/integrations/orderful
date_modified: 2026-11-13T14:04:35-08:00
---

# Orderful

[E-commerce](https://flowrunner.ai/integrations/category/e-commerce)

Receive retail purchase orders (EDI 850) through Orderful and answer them with purchase order acknowledgments (EDI 855) in normalized JSON. Agents read each order line by line, check it against stock, and send the acknowledgment the trading partner plans against.

[Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 5 actions · API key · available

[Orderful website](https://www.orderful.com/) · [Platform Documentation](https://docs.orderful.com/) · Capability data verified 2026-11-13

1.  A retailer's 850 arrives with the full order
2.  Agent reads PO number, dates, ship-to and every line
3.  Get Item in NetSuite checks stock for each line
4.  Create Sales Order in NetSuite for the order
5.  Agent drafts the 855: accept, change or backorder each line
6.  Short or repriced lines posted to the order desk in Slack
7.  The order desk confirms the 855 before it is sent

## What This Integration Enables

Orderful exists so suppliers can trade EDI with retailers without living inside X12. This connector takes that one step further: an agent receives each retail purchase order as structured JSON and answers it the way the retailer's buyer reads it, line by line. The 850 trigger delivers the whole order in each event, so the flow can check stock and create the sales order without another call.

FlowRunner agents read transactions and their documents, list them by partner, type and status, and send the purchase order acknowledgment (855). Picking the PO an 855 answers fills in the partner IDs, stream and PO number. Orderful checks every 855 against the partner's rules and fails the step with its validation errors when it is refused. A separate receipt-level accept or reject serves partners trading JSON. The agent does the matching and the drafting. The 855 is a commitment the retailer plans around, so when it changes the order the agent stops and asks a person on Slack, email, WhatsApp or phone.

### Without FlowRunner

**POs rekeyed from a portal**: Retail purchase orders are read in an EDI portal and typed into the ERP by hand

**Acknowledgments sent blind**: The 855 says accept in full because checking every line against stock takes too long

**Big orders noticed late**: An unusually large PO is spotted when the warehouse cannot fill it

### With FlowRunner

**PO to sales order**: Each 850 becomes a sales order in the ERP with its lines intact

**Honest line by line answers**: The 855 reflects real stock: accepted, changed or backordered per line

**Unusual orders flagged**: A PO far outside a partner's normal pattern reaches a person before it is accepted

## Flows you can build with Orderful

### Retail PO to sales order to acknowledgment

A retailer sends a purchase order and On New Inbound Purchase Order (850) fires with the PO number, dates, parties and line items. The agent checks each line's stock with Get Item in [NetSuite](https://flowrunner.ai/integrations/netsuite) and creates the order with Create Sales Order. When every line can ship as ordered, it sends Send Purchase Order Acknowledgment (855) accepting the order. When a line is short, it drafts the 855 with the quantity it can ship now and a backorder for the rest, and sends it after the order desk confirms.

### Unusual orders flagged before acceptance

A PO arrives for ten times the quantity a partner usually orders. The agent compares it against the partner's recent orders with List Transactions, filtered by partner and document type. When the order falls far outside that pattern, it posts the PO to the order desk in [Slack](https://flowrunner.ai/integrations/slack) and logs it with Add Row in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). The desk decides whether it is a real order, a keying error on the retailer's side, or something to confirm with the buyer before acknowledging.

### Receipt acknowledgment and validation failures

For partners trading JSON with acknowledgments turned on, the agent answers each received document with Accept or Reject Received Transaction before processing it. A PO sent to the wrong supplier account is rejected at that point. When Orderful refuses an 855 against the partner's rules, the step fails with Orderful's validation errors. The agent reads them and corrects what it can, such as a missing date. Anything else becomes an [automation exception](https://flowrunner.ai/concepts/automation-exceptions) for the EDI owner, with Get Transaction showing the document's validation, delivery and acknowledgment status.

## Human-in-Loop Highlight

The gate is on Send Purchase Order Acknowledgment (855) whenever the answer is anything other than "accept as ordered." The 855 is the supplier's business answer: what will ship, when, and at what price. The retailer's replenishment planning runs on it. A backorder or a quantity cut sent by mistake is a promise broken in writing. So when stock falls short, the agent drafts the acknowledgment and posts it to the order desk: "PO 4500127731 from Northway Retail, 6 lines. Lines 1 to 4 ship in full on the 18th. Line 5 can ship 400 of 600, the remaining 200 on the 2nd. Line 6 is discontinued and would be rejected. Send this 855, or hold for the account manager?" The desk confirms or edits, and only then does the agent send it. This is [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) where a supplier's reputation with a retailer is actually decided.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

## Agent Capabilities

5 actions

### Transactions

3

-   **Get Transaction** Reads one Orderful transaction: its type, trading partners, test or live stream, document number such as the PO number, and its validation, delivery and acknowledgment status. Used to see where a document stands.
-   **Get Transaction Message** Downloads the document a transaction carries. For a PO traded as JSON this is the full order: PO number, dates, buyer and ship-to parties, and every line with item numbers, quantity and price. For partners trading raw EDI, the EDI text comes back instead.
-   **List Transactions** Lists transactions newest first, up to 100 per call, filtered by direction, document type, trading partner, document number, status and creation time. Used for partner history, reconciliation and catch-up.

### Acknowledgments

2

-   **Send Purchase Order Acknowledgment (855)** Sends the trading partner a purchase order acknowledgment: whether the supplier accepts, changes or rejects the order, and line by line what will ship, when and at what price. Orderful checks it against the partner's rules and fails the step with validation errors when it is refused.
-   **Accept or Reject Received Transaction** Tells the trading partner whether a document they sent, such as a PO, is accepted or rejected before it is processed. This is the receipt-level acknowledgment for partners trading JSON, not the 855. A transaction can be acknowledged once.

## Triggers

1 triggers

### Event Triggers

1

-   **On New Inbound Purchase Order (850)** Fires for each new purchase order a trading partner sends through Orderful, oldest first. Each event carries the transaction and the full order, so the flow can check stock or create the sales order straight away. It checks for new orders on a schedule, up to 25 per check.

## Frequently asked questions

### What can FlowRunner do with Orderful?

FlowRunner agents can run Get Transaction, Get Transaction Message, and List Transactions in Orderful, plus 2 more actions.

### Does connecting Orderful to FlowRunner require OAuth?

No. Orderful connects to FlowRunner with an API key, no OAuth flow required.

### Can Orderful trigger a FlowRunner workflow automatically?

Yes. Orderful supports 1 trigger that can start a FlowRunner workflow automatically.

**Work at Orderful?** This integration exposes Orderful to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current.

## Need a custom Orderful automation? Our team can build it for you.

Tell us the process. Our implementation team at Midnight Flow builds it around how you work, tests it on your real data, and keeps it running, in your own FlowRunner workspace.

[Have us build it](https://midnightflow.ai/packages/custom?utm_source=flowrunner.ai&utm_medium=referral&utm_campaign=general&utm_content=integrations.aside&utm_term=orderful)

---
Markdown version of https://flowrunner.ai/integrations/orderful. Site index: https://flowrunner.ai/llms.txt
