We're excited to announce some big changes to our UI today, a reskin with a side-panel navigation!


If you would like to provide us with feedback, please send your comments on the new UI reskin to[email protected].

New Look

The new navigation features Orderful's deep blue, and has all core business objects located on a side-panel, vertical navigation.

The vertical navigation allows us to help drive more left-to-right flows in the application for core user behaviors: Testing, and Transaction Issue Resolution, for example.

Over the next few months, we will continue to add new features to the new navigation and you will see the app continue to change for the better! We are excited to ship these changes for you.

Old Look

Our old navigation was horizontal across the top of the page. It limited us quite a bit in terms of helping drive a flow in the application for users to process and do work from Left to Right.

Again, if you would like to provide us with feedback, please send your comments on the new UI reskin to[email protected].

We're excited to announce a new feature today – the ability to add your custom HTTP destinations to send transactions to.

Once you've created a custom HTTP destination, you can now assign it to your organization. If assigned, it will be the default setting for all of your relationships, unless, at the relationship level, a destination is set.

You can create custom destinations and their auth settings on the /settings/integrations page

If you would like to add a destination to a relationship, you can do so on the relationships page.

You can read more about destinations here

There are two types of statuses now: transaction status and validation status. New icons have been added as well to better distinguish between the two status types. This change also includes detailed filtering for the two status types.

For more information, please visit our guide for details.

Today we've improved our Guidelines feature to provide full support for X12 composite elements.

While our users have always had the ability to write guidelines on component elements – the simple data elements making up an X12 composite element – until now, the requirements of that parent composite element couldn't be specified.

As of today, you'll see a separate entry in the Guidelines builder for composite elements, allowing you to indicate whether or not a composite element is mandatory, as well as write syntax notes on that composite element indicating which of its component elements have relational conditions between them.

Formerly, if you marked a component element as 'mandatory', a transaction would always fail validation if that component element wasn't present. Now, that transaction will still fail validation, but only if the parent composite element is also mandatory, or other component elements are present. Said another way – if a composite element is optional, a missing mandatory component element will only cause a validation error if at least some portion of that composite element is being sent.

We've been careful to make this change in a way that ensures that your existing guidelines will still be evaluated in exactly the same way that they always have been. If you'd like to take advantage of the new functionality with your existing guidelines, you can do so simply by copying your published guideline to a new draft, making the needed changes, and then publishing the new version.

We're excited to announce a new feature today – the ability to track and visualize sequences of transactions that belong together in a business process.

Groups of related transactions are automatically created and maintained as transactions are processed by Orderful. As a first step, we've added the Retail Workflow, which groups transactions of the following types by their associated Purchase Order number:

• 850 Purchase Order
• 855 Purchase Order Acknowledgment
• 856 Shipment Notice Manifest
• 860 Purchase Order Change Request Buyer Initiated
• 865 Purchase Order Change Acknowledgement
• 810 Invoice

When you click on a transaction in the Retail Workflow, our updated Transaction Details page will now show you all of its related transactions from that workflow:

Filter settings on Transactions, Relationships, and Guidelines are now automatically persisted and restored locally. You can now use other Orderful features knowing that your filters will still be there when you're back.

We've improved the Turnaround rule writing experience. By pulling in your reference Transaction and displaying them side-by-side with your currently selected segments, you can now visually select the paths you want matched.

In order to provide you and your system with the most accurate data, we introduced a new optional validation step to our platform. Now, you’re able to add an “inbound guideline” to your account. This guideline is then used to validate all your incoming transactions of a certain transaction type, similar to how that’s already being done to transactions you’re sending to your trading partners.

If any transaction reaches your Orderful account and it doesn’t meet your guideline for that transaction type, the transaction will be marked “Invalid” and held in your account. You can then write rules to fix that transaction and new ones of that type going forward. Once the transaction becomes “Valid”, it will be automatically posted to your system.

If you’re looking to set up such an inbound guideline, please contact us and we’ll help you through the process.

We've got a really exciting new feature to announce – support for X12 relational conditions, i.e. Syntax Notes!

Under the X12 specification, whether or not a certain data element should be sent as part of a given segment often depends on whether other related data elements are sent alongside it. For example, if one data element contains a qualifier code specifying the type of data sent in another element, then it's often the case that you need to send either both of those elements together, or neither of them, otherwise your X12 message will be invalid.

With our new Syntax Notes feature, you're now able to specify those conditions when writing your guideline, and we'll take those conditions into account when validating transactions.

Here's an example of adding a Syntax Note to a segment:

We know it can be a lot of work adding all your trading partner's requirements when building a guideline, and our syntax notes feature just adds to that, so we've snuck in one more new feature with this release – improved pre-population of X12 default values!

What that means is that when you add a new segment to your guideline, the syntax notes & maximum use values specified by the X12 standard will be pre-filled for you, and any elements which are always mandatory in that segment, together with their data types & lengths, will be automatically added as well. We think you'll now find that once you've added all the needed loops & segments to your guideline, your work is very nearly complete.

We've got a new feature to announce today – the ability to upload a PDF of your guidelines, accessible by both your organization and your trading partners.

We've been working hard here at Orderful on our Guidelines feature, and we've made a lot of improvements over the past couple months to make guideline entry easier and faster than ever. That said, we understand that mistakes do happen when entering data, and we've heard the request that it'd be nice to have an easy way to reference the original PDF guideline to verify that the guideline was entered correctly and that transactions are being validated as expected.

That's now a possibility with our new PDF guideline upload feature, live in our app as of this morning. You'll have the opportunity to upload your PDF at the time of either creating a new guideline or viewing an existing one. Also, when your trading partners see that one of their transactions has failed validation, they'll also have the opportunity to click through to your guideline and download the original PDF.

See it in action:

As always, we'd love to hear your feedback, so reach out to us anytime and let us know how you like it!