May 2026 Release Notes
May 1, 2026
This update covers integration and service changes across five operating areas: AfterShip and native Shopify returns, PO-backed pre-order data, Shopify order and product synchronization, carrier labels and email communication, and app migration services. These changes target specific failure modes: stale PO ATP after quantity edits, new Shopify orders waiting behind update jobs, duplicate MDM writes when an order has not changed, carrier label errors hidden in carrier-specific code paths, and audit screens missing actor or log context.
Returns integration overhaul and supported flows
The release includes a new AfterShip returns integration and broader native Shopify return handling. AfterShip and Shopify return records can now enter OMS before final settlement, remain identified as in-progress or completed returns, and keep the channel, customer, reason, restock, destination facility, refund, and agreement context service teams need to understand the request.
Return and refund reconciliation also became more precise. HotWax now distinguishes in-progress returns, completed returns, appeasements, exchanges, replacement orders, multi-currency refund amounts, and NetSuite return sync steps instead of flattening them into one generic post-refund record. Read the full returns update.
Pre-order
Purchase order management in the Preorder app
Purchase order management moved out of the legacy purchase order screens and into the Preorder app, where users already manage pre-order availability. The app can now load purchase order lists, open purchase order details, show estimated delivery dates, and review receipts tied back to purchase order items.
That puts inbound supply next to the app's existing demand tools: grouped product and order search, variant-level release decisions, warehouse allocation, cancellations, and promise-date edits. PO ATP recalculates after quantity edits, and imported pre-order sales orders index after splitting and promise-date assignment. Read the full Preorder update.
Shopify
Order create/update queue separation
Shopify order creation now runs separately from order updates, so new orders do not wait behind a backlog of update jobs. Update-only queues can skip brand-new orders and leave creation to the create queue, while existing orders still receive fulfillment, refund, transaction, risk, and payment updates.
Before writing an order to MDM, the bridge now checks whether the order actually changed, including hash-backed comparisons for fields like customer, payment terms, outstanding amount, fulfillment, refunds, and risk. That reduces unnecessary mega-query and MDM work while keeping updates available when a real diff exists. Read the full Shopify order sync update.
The order sync path also picked up targeted fixes:
- Resolve shop context once and pass it downstream.
- Carry product store ID through the order sync flow.
- Skip duplicate shipping contact-mech creation during updates.
- Preserve pre-selected facilities on mixed POS and Shipsi carts instead of replacing them with defaults.
Product sync history and bulk operations
Product sync work focused on making existing Shopify catalog updates visible and operational in OMS. Product update history is now exposed through REST for sync dashboards, and Shopify product indexing runs after the sync transaction commits so search reflects committed product changes.
The product sync path also picked up targeted fixes:
- Fixed an issue where sometimes the wrong shop Id was saved in the product update history.
- Fixed a product sync failure where category and attribute writes could run
