We've enabled Multi-Factor Authentication (MFA) for all Orderful users authenticating with email and password login.

What's new

• MFA enforced for all non-SSO users – Any user authenticating with basic login (email + password) will be required to set up MFA upon their next login.
• Multiple factor options – Choose from TOTP (e.g., Google Authenticator), WebAuthn (fingerprint, Face ID, or security keys like YubiKey), Email, or Passkeys.
• 30-day "Remember this browser" – After completing MFA, users can opt to trust their current browser for 30 days, reducing repeated prompts.
• Recovery codes – During enrollment, users receive a one-time recovery code to regain access if their primary factor is unavailable.

What to expect

Upon next login, all non-SSO users will be prompted to enroll in MFA before accessing Orderful. SSO users are not affected — MFA for SSO connections is managed by your identity provider.

The Audit Log now tracks changes to Relationships and Rules, giving you a complete picture of configuration changes across your organization.

What's New

New Resources and Actions

How to Access

From anywhere

1. Click your avatar in the top right corner
2. Select Audit Log.

From the Relationships List View

1. Go to Transactions page from the navigation menu.
2. Click on the Audit Log icon.
   This opens a modal with the log pre-filtered to the Relationships resource. From there, you can click View Full Audit Log to open it in a new tab with this filter pre-applied and drill down further.

What's Next

Audit Log coverage will expand in the coming weeks. Coming soon:

• Audit log on EDI Jobs

Read More
Audit Log overview → Navigating the Audit Log →

When generating carton and pallet labels, Orderful now automatically sources Ship From and Ship To addresses so you don't have to re-enter them every time.

What's new:

Ship To: If no Ship To address is present on the 856, Orderful now falls back in this order:

1. If the 856 was created from a split, use the DC or store address from the receiver's org hierarchy
2. Pull the address from the linked 850 Purchase Order
3. If neither applies, you'll be prompted to select a saved Ship To party

Ship From: If no Ship From address is present on the 856, you can select or create a saved party — and Orderful will remember it for future label batches on the same relationship.

This update eliminates repetitive manual address entry and reduces the risk of errors when generating label batches.

You can now trade any file format through Orderful — not just EDI.

What's New?

• One place for all your trading activity — Any file exchanged between trading partners is a business document — and in Orderful, a transaction. Transactions all appear in the same Transaction List regardless of whether they are EDI transactions or Any file, with similar filtering, search, and action capabilities.
• Any file format supported — Trade CSV, XML, PDF, flat files, images, and more alongside your existing EDI transactions.
  New formats can be added on demand — contact Orderful support.
• Supported transaction types — A set of approved transaction types is available at launch: RAW_ORDER, RAW_INVOICE, RAW_ADVANCE_SHIP_NOTICE, RAW_PROOF_OF_DELIVERY, RAW_BILL_OF_LADING, RAW_SHIPMENT_STATUS, RAW_INVENTORY, RAW_ORDER_CHANGE, and more. New transaction types can be added on demand — contact Orderful support.
• Compatible with all communication channels supported in Orderful — API, AS2, FTP, SFTP, Poller, and HTTP.

How Does It Work?

When trading non-EDI files, Orderful applies MFT — Managed File Transfer — processing. Files are securely routed and passed through from sender to receiver as-is, with no EDI processing applied: no validation, no conversion, no transformation, no acknowledgment reconciliation, no workflow tracking.

Why Does It Matter?

Not all trading partners communicate through EDI.
Some enforce proprietary or legacy file formats your systems are expected to support.
Others are simply not EDI-capable and rely on CSV, XML, or flat files instead.
And some business workflows involve supporting documents — Proof of Delivery PDFs, Bills of Lading, labels — that have no EDI equivalent but are critical to the business process.

Until now, these files had to be managed outside of Orderful, fragmenting visibility across your trading activity. Any file over MFT lets you bring all of it into one place.

Read More:
EDI vs Any file? →
Available Any file Transaction Types →
Setting up an Any file over MFT partnership →
Inbound Communication Channels - Receive Any file →
Outbound Communication Channels - Create and Send Any file →

You can now see a complete, tamper-proof record of every action taken across your Orderful organization — who did what, and when.

What's New

Organization-level activity feed — a chronological log of all user and system actions with timestamps, actor details, the resource impacted, and context links

Powerful search & filters — filter by time range, actor, action type, resource type, and correlation ID to quickly find the events that matter

Immutable records — logs are append-only and tamper-proof, so you can rely on them during audits and incident investigations

Resources and actions available at launch

How to Access the Audit Log

Audit Log is available to all roles in Orderful.

From anywhere

1. Click your avatar in the top right corner
2. Select Audit Log.

From the Transaction List View

1. Go to Transactions page from the navigation menu.
2. Click on the Audit Log icon.
   This opens a modal with the log pre-filtered to the Transaction resource. From there, you can click View Full Audit Log to open it in a new tab with this filter pre-applied and drill down further.

From a specific transaction

1. Go to Transactions page from the navigation menu.
2. Open a specific transaction.
3. Click on the Audit Log icon.
   This opens a modal with the log pre-filtered to that transaction resource and context. From there, you can click View Full Audit Log to open it in a new tab with those filters pre-applied and drill down further.

Read More: Audit Log overview → , Navigating the Audit Log →

The Audit Log is not retroactive. Logs start being recorded from March 24th, 2026 onward. Events that occurred before this date are not captured.

What's Changing: Transaction Audit Trail

New transactions (created after this release) show a new "Audit Log" button on the transaction details page. Pre-release transactions retain the old "Audit Trail" button and the existing audit trail view.

What's Next

Audit Log coverage will expand in the coming weeks. Coming soon:

• Audit log on Relationships and Rules
• Audit log on EDI Jobs

Read More
Audit Log overview → Navigating the Audit Log →

We are excited to announce the launch of Orderful EU, a dedicated region built to bring the power of Orderful directly to European enterprises. By establishing localized infrastructure, we are providing the speed and performance you need to manage your supply chain with confidence, while ensuring your data stays within the region.

A Phased Approach

We are rolling out Orderful EU in two strategic stages to help you scale your operations:

• Phase 1 - Available Now: Local EU Trading New European customers can immediately begin onboarding and trading with their European partners. This phase focuses on optimizing your local supply chains with maximum efficiency.
• Phase 2 - Available Soon: Cross-Region Expansion Shortly after launch, we will enable Cross-Region Trading. This will allow you to seamlessly bridge your EU operations with partners in the US, managing global trade through one unified network.

The Same Orderful Experience, Localized

Orderful EU is built to work the exact same way as our US region. European and US customers enjoy the same interface, features, and workflows you’ve come to expect, simply optimized for the European market.

To help you identify and access your specific region, we have established dedicated URLs:

• Orderful UI: https://ui-eu.orderful.com
• Orderful API: https://api-eu.orderful.com
• Orderful AS2 server: https://as2-eu.orderful.com
• Orderful SFTP server: sftp://ftp-eu.orderful.com

Key Benefits

Regional Data Residency: Meet compliance and data residency requirements by hosting your data directly within the EU.

Reduced Latency: Experience faster processing and improved platform responsiveness by utilizing local European infrastructure.

Seamless Consistency: Whether you are in the US or EU region, the platform functionality remains identical, ensuring a zero-learning-curve experience.

Global Scalability: Bridge the gap between your European and American operations with ease as we enable cross-region support.

We've introduced a comprehensive partnership testing framework that enables you to validate end-to-end order-to-cash workflows before going live with your retail trading partners.

What's New

Standard Order to Cash Integration Testing

You can now add a partnership with a demo retail partner and execute automated scenario tests that validate the complete order-to-cash cycle:

1. 850 Purchase Order - Receive PO from the demo partner
2. 855 PO Acknowledgment - Send acknowledgment confirming order receipt
3. 856 Ship Notice/Manifest - Send an advance ship notice
4. 810 Invoice - Send invoice for shipped goods

The system automatically validates data consistency across all four transaction types, checking:

• Line item matching and carry-through
• Product ID consistency
• Quantity validation
• Unit of measure alignment
• Status codes and acknowledgment types
• Invoice accuracy against orders and shipments

Why this matters to you

If you work with retailers or dropship programs and are setting up your integration with Orderful, this feature gives you one place to test that everything is working. You can make sure your integration can send and receive valid transactions before going live. The demo partner provides a safe, end-to-end testing environment so you can be confident your integration is ready to handle real data with live trading partners.

Read more on how to use Integration Testing

We've updated our rules engine to make it safer to develop new rules without impacting your live transactions.

What's New? ✨

Users can now define separate rule expressions for liveand test transactions.

• Synced By default, rules will apply to both streams

• Users can split a rule and write different expressions for the different streams

• Bring them back in sync by duplicating one expression to the other stream

• Create Test Only rules to try out new rules without impacting live transactions

See more in this guide

We've updated the unprocessed transaction emails you receive to make troubleshooting faster and easier.

What's New? ✨

When you receive an email about a transaction that couldn't get created, we added a direct link "View EDI Job Details and Content" to the corresponding EDI Job in Orderful.

This direct link allows you to immediately:

• View Error Details: See the specific reason the transaction failed.
• Access full original payload: You can view and download the complete, original file that was sent.

We've updated the inbound relationship settings to provide clearer instructions on the acknowledgement behavior.
Note: The acknowledgment behavior is unchanged. This update is purely for clarity and ease of configuration.

What's Changing?

The previous single checkbox "I will send functional acknowledgements in response to inbound transactions" has been replaced by a dedicated section titled "Choose your acknowledgment policy" with two explicit radio options:

• Auto-accept: Transactions you receive are automatically accepted.
• Send acknowledgment: You control the acceptance or rejection of transactions you receive.
  Control is managed either by sending a functional acknowledgment (997/CONTRL), if you trade X12 or EDIFACT or by using the Orderful API, if you trade JSON.

Benefit

This change moves configuration from an ambiguous checkbox to clear policy options, ensuring you always know the exact operational flow for acknowledging transactions and sending acknowledgments back to your partners. Additionally, the new UI provides confirmation on whether your partner can receive the required 997 or CONTRL acknowledgment.