We have added support for Sprouts Farmers Market to our label printing API.
For more information about the Sprouts label see our Sprouts UCC-128 Label Requirements.
For information about generating UCC-128 Labels see Generate a UCC-128 (GS1-128) Label.
We’re expanding our email notification system for customers in the Retail industry.
You can now subscribe to email notifications to receive an email when:
You can manage your subscriptions to these notifications from the Notifications page inside your User Settings.
We improved the Order Fulfillment page with quick filters at the top of the page.
The quick filters help you visualize the order fulfillment steps and help you keep track of and manage your orders:
We’re introducing a new page for retail customers to follow the status of their orders. This new page is available for customers trading 850, 855, 856 or 810 transactions.
The Order Fulfillment page will display the list of retail Workflows and their status for a specific purchase order:
Order status will be automatically skipped if you don’t trade that document type.
You’ll be able to filter your orders based on the Workflow creation date, your or your partner’s EDI Accounts and purchase order numbers.
Workflows may become stuck in a particular status if you or your Trading Partner doesn’t acknowledge a transaction or if you or your partner don’t send a document even though you have a relationship for that transaction type. In this case you should just manually move to the next status or remove relationships you don’t intend to trade documents for.
By clicking on a specific order from the Order Fulfillment page, you’ll access a new Workflow Overview page where you’ll see the transactions assigned to each Workflow status.
Suppliers can manually skip a status or cancel an order from that page.
Coming soon: Suppliers will soon be able to manually create a transaction from the Workflow Overview page. These transactions will be auto-mapped with data from the original purchase order and suppliers will be able to manually review and enter missing information on the new transaction.
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
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.
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.
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.
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:
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:
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.
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 shipping labels Orderful generates include barcodes in GS1-128 (formerly UCC / EAN-128) format, including SSCC-18 barcodes where required.
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:
