Skip to content
DigiOS.
Log inBook a working session
Retailer EDI networks

Orderful with DigiOS.

Retailer orders arrive from Orderful as JSON, and acknowledgments, ship notices and invoices go back from the work the floor did.

Ask about Orderful

What moves each way

Orderful
  • Purchase orders (850): Into DigiOS
  • Delivery confirmation: Out of DigiOS
  • Acknowledgments (855): Out of DigiOS
  • Ship notices (856): Out of DigiOS
  • Invoices (810): Out of DigiOS
  • Functional acknowledgments (997): Into DigiOS
DigiOS
What moves between Orderful and DigiOS: what, which way, the documents and data, and when.
WhatDirectionDocuments and dataWhen
Purchase orders (850)InA retailer's order as a JSON transaction, with sender and receiver IDsWhen DigiOS polls the bucket
Delivery confirmationOutEach collected transaction approved, or failed with a noteWhen the transaction is stored
Acknowledgments (855)OutWhat will ship against each order lineWhen the order is accepted
Ship notices (856)OutWhat shipped and how it is packed, with carton and pallet labels by SSCCWhen the shipment closes on the floor
Invoices (810)OutAn invoice for the shipped goodsWhen the shipment closes, or when you release it
Functional acknowledgments (997)InA retailer's confirmation that a document arrivedWhen the document arrives

On your floor

ConnectionsSee each connected system, what moves each way, and when it last moved. When an exchange fails, the tile says why and who can fix it.

How DigiOS works with Orderful

DigiOS collects inbound transactions from an Orderful polling bucket, confirms each delivery as approved or failed, and creates outbound transactions through the Orderful API. Orderful turns your retailers' X12 and EDIFACT into JSON on the way in, and back to EDI on the way out. As the warehouse, DigiOS receives 940 and 943 and sends 945, 944, 947 and 846. When it relays a client's retailer documents, it passes on 850, 856 and 810.

Where it stands
1 Nov 2026
About Orderful
Orderful is an EDI network and API that exchanges X12 and EDIFACT documents between companies as JSON.
Your account
You keep your Orderful account and your retailer relationships.
If a document is rejected
A document that is rejected, late or missing goes to one queue with its reason, readable on screen and over the API. When the other side fixes its layout, run the document through again. A document sent twice never opens a second order.
Documents
As the warehouse, DigiOS receives 940 and 943 and sends 945, 944, 947 and 846, with 997 and 999 acknowledgments both ways. A client's retailer documents, the 850, 855, 856 and 810, are part of Client Link.
X12 version
Both X12 4010 and 5010, per trading partner. The version is set for each retailer in the mapping sheet.

Questions about Orderful

Why poll instead of waiting for a push?

A polling bucket holds a transaction until DigiOS confirms it, so a document sent while DigiOS is down is collected afterwards.

Does DigiOS work with EDIFACT through Orderful?

Yes. Orderful carries EDIFACT messages as JSON as well, and DigiOS maps ORDERS, DESADV and INVRPT.

Who tests with the retailer?

You and the retailer do, through Orderful's test stream. DigiOS runs the same documents through its own test channel first.

SPS CommerceRetailer purchase orders in. Acknowledgments, ship notices, invoices and inventory back.TrueCommerceRetailer orders in over SFTP, AS2 or API. Acknowledgments, ship notices, invoices and stock back.Direct AS2 and SFTPEDI files in and out with a retailer or a client, without an EDI provider in the middle.

Ask about Orderful.

Tell us what you run and what you want Orderful to do. A person answers in writing.

Ask about Orderful