Pubeasy Release 3.17 (June 8, 2026)

This release is primarily dedicated to technical changes, but also includes a few retailer-visible improvements. The release is not expected to include any downtime when updated on Monday, June 8th, 2026. 

Maintenance messaging during registration downtime
When registration is unavailable due to maintenance, users now see clearer guidance instead of an ambiguous failure—reducing confusion and support requests.

Chat assistant available before logging in
You can now use the chat assistant if you have trouble logging into Pubeasy.com. Look for the icon on the bottom left of the screen.

Configurable exports for search results and order lists (XLS/CSV) added
You can tailor exports by selecting the columns you need (with a streamlined default), making it easier to produce clean spreadsheets for quotes, analysis, and workflows without extra cleanup. 

Search controls available above results
Added buttons above the search results list so you can adjust or reset searches without scrolling to the bottom—speeding up day-to-day browsing.

Order status UI cleanup at completion
The “reload” option no longer appears once an order reaches its final “Completed” state, reducing confusion and making the order status screen clearer.

Improved ONIX product contact handling
ONIX uploads now support product contact identifiers within the product contact structure, reducing rejected records and improving the quality and completeness of your product metadata.

More flexible ONIX requirements for product contacts
ONIX uploads no longer fail when the product contact email field is missing (where the standard allows it), making uploads more robust and reducing avoidable errors.

More reliable failure notifications for FTP exchanges
Improved notification behavior for failed OpenText FTP file exchanges so issues are surfaced more consistently and can be acted on faster. 

X12 5010 (850) purchase order processing support
Added support toward processing X12 5010 purchase orders so 5010 files can be ingested and reviewed in the interchange/transaction views, improving traceability and operational support.

Longer PO number support in frontend-generated X12 orders
Increased the PO number character limit (up to 22) for frontend-created X12 order files, aligning better with X12 constraints and reducing rejected/invalid orders.