We have updated our 810 and 855 Print Views to be more complete and easier to read. The layout has been improved to make it more compact, thereby allowing more information to appear on every page. We have also made sure that every element of the X12 specification we map corresponds to a human-readable portion of the Print View.

810 Invoice Print View

810 Invoice Print View

855 Purchase Order Acknowledgment Print View

855 Purchase Order Acknowledgment Print View

📘

Rules and Print View

The Print View continues to show the latest revision of a Transaction. This means that the data you see has already had any relevant Rules applied to it. If one of these Rules changed the value of a property it is possible that our Print View will not be able to map it to a human-readable value to add to the Print View.

You can see the new Print View by going to your organization's Transactions page, clicking on an 810 or 855 Transaction, and selecting Print View under the Details tab.

We have updated our 850 Purchase Order Print View to be more complete and easier to read. The layout has been improved to make it more compact, thereby allowing more information to appear on every page. We have also made sure that every element of the X12 specification we map corresponds to a human-readable portion of the Print View.

📘

Rules and Print View

The Print View continues to show the latest revision of a Transaction. This means that the data you see has already had any relevant Rules applied to it. If one of these Rules changed the value of a property it is possible that our Print View will not be able to map it to a human-readable value to add to the Print View.

You can see the new Print View by going to your organization's Transactions page, clicking on an 850 Transaction, and selecting Print View under the Details tab.

We’re improving how we’re capturing delivery updates.

How it works

Orderful now has two new dedicated endpoints to approve or fail a specific Transaction delivery to an HTTP or Poller Communication Channel.

JSON transactions delivered to these Communication Channels will include additional links to new endpoints that get, approve or fail a Delivery:

When using Poller Communication Channels, approving or failing a Delivery with the new endpoints will also automatically remove the Transaction from the Polling Bucket.

Why we made this change

Previously, Transaction delivery would be confirmed for every Transaction. This could create confusion when a Transaction was sent multiple times. Deliveries are now their own dedicated objects in our API that can be individually marked as "Approved" or "Failed".

Although the links are only included for HTTP and Poller Communication Channels, this will improve the delivery audit trail on all Communication Channels by making the failure or approval of a delivery of each transaction a distinct event.

In the future, this improvement will allow Orderful to better detect Communication Channel outages.

If you are trading JSON data, you now have the ability to add one or more objects to any array within your JSON payload. You can then use our Rules Engine to populate the fields in these new objects.

How it works

If you are viewing a JSON transaction using our Rules Editor, you will now see the option to “Add {} to Array”:

For more information about how to use this feature, see Add data to a JSON transaction.

For examples of how to use this feature, see our documentation about how to use the Rules Engine:

Why we made this change

Your Trading Partner may require you to include data in your outbound transactions that are not stored in your backend. The Rules Engine now allows you to add objects to arrays to make sure you include all data that is expected by your Trading Partner, without having to update your API integration with Orderful.

We made some improvements to our default settings for Communication Channels.

You can now:

  • Configure the Auto-send flag as a default requirement on your EDI Accounts.
    Previously this was enabled on all new Relationships. You can now decide the default value of this setting for new Relationships.
  • Select “Keep In Orderful” as a default live or test Communication Channel on your EDI Accounts. That default setting is useful if you don’t integrate your transactions and manage them in Orderful.

Why we made this change

Orderful is working on enabling a new type of customer - non-integrated customers - that won’t build integrations for their partnerships and will instead create, send, receive and manage their EDI transactions entirely in Orderful.

We are adding these updates to our default requirements to enable automation of partnership setup for non-integrated customers.

Orderful has introduced a new UCC-128 Shipping Labels API that can generate ZPL (Zebra Programming Language) files needed for label printing. You can generate 250 UCC-128 labels per month for free as part of your Orderful subscription. To get started, see our new guide on how to Generate a UCC-128 Label.

How it works

You can send the data for the printing label to our new API endpoint, and we will return ZPL-formatted text that you can then send to your printer.

At launch, the following company’s shipping labels are supported:

  • The Home Depot
  • Macy’s
  • Nordstrom
  • Walmart (Case Domestic)

The shipping labels Orderful generates include barcodes in GS1-128 (formerly UCC / EAN-128) format, including SSCC-18 barcodes where required.

Why we made this change

We are adding this feature to simplify our customer’s workflows and save them money. Rather than integrate with a third-party service, you can now trade EDI documents and generate your UCC-128 labels using Orderful.

For more information see:

We have defined and released lists of Allowed Values for Guidelines defined in the Orderful JSON format. Going forward, when entering an Orderful JSON guideline, you will be able to select an element's "Allowed Values" from a predefined list.

We’re introducing a new tool on the Orderful website: the Real-time EDI Validator.

From the validator tool, you can:

  • Create, paste, and edit an X12 transaction payload
  • Validate this X12 payload against the default guideline of the receiver, the sender, or the X12 specification.

After validation, you can access a list showing any detected errors and convert your X12 transaction to Orderful JSON.

Orderful now supports transactions in the EDIFACT data format. If you do business outside the United States, your Trading Partners may require you to send and receive transactions in the EDIFACT data format. If that's the case, you can now onboard them using Orderful.

The EDIFACT onboarding process is similar to the onboarding process for your X12 partners. For more details, check out our documentation. To start onboarding today, you can send a Trade Request.

Once the partnership with your EDIFACT Trading Partner has been configured, Orderful will generate the schema for you in Integration Assistance.

We have made improvements to setting up a new Partnership as a Follower.

When you submit a Trade Request as a Follower, Orderful now allows you to look up your Leader within the Orderful network. Your Leader Trading Partner will be available for look up if they have default requirements configured in the Orderful network.

After creating the Trade Request, Orderful will guide you to the list of available default requirements that are digitized on the Orderful network for the partner you want to trade with:

  • EDI information
  • Guidelines
  • Communication Channels

You can then confirm whether you'd like to reuse the default requirements or not.

If you confirm you want to reuse all requirements, Orderful will automatically accept the Trade Request and redirect you to your new Relationships. The Relationships will be ready for you to configure and test.

If you choose to use different requirements or not all requirements are available on the Orderful network, Orderful will guide you to fill out the missing requirements on the onboarding form.
Once you submit the onboarding form, Orderful will auto-accept Trade Requests and auto-configure Relationships to the extent possible based on the information we have.