August 2026 apps release notes
August 1, 2026
August connects more of the retail operating day across HotWax Commerce's order management system (OMS). Retailers can reconcile Shopify fulfillment locations, publish inventory from a recorded event history, manage integrations from Company, create transfer orders from Receiving, and follow the decisions behind Cycle Count inventory changes.
Shopify order and fulfillment synchronization
Keep Shopify fulfillment locations and OMS allocations aligned
HotWax Commerce now reconciles fulfillment-location changes in both directions. When Shopify assigns a fulfillment order to a different location, the OMS can move the related allocation. When the OMS reallocates fulfillment, a scheduled outbound process can move the Shopify fulfillment order to the matching location.
The reconciliation flow detects location-only changes and keeps an older Shopify notification from reversing a newer allocation. Unresolved moves stay in an exception task for investigation, and missed fulfillment records can be replayed through the same process.
Inventory corrections account for moves between physical and aggregate Shopify locations. This keeps the aggregate inventory pool consistent while the next absolute inventory publication remains available as a self-healing backstop. Read the full fulfillment-location reconciliation update.
Preserve more Shopify order lifecycle details
The August Shopify connector releases improve native Buy Online Pick-Up In Store (BOPIS) imports, return and exchange handling, estimated ship-date mapping, and custom order searches. Exchange lines and canceled returns retain their lifecycle state as changes move between Shopify and the OMS.
Inventory publishing
Publish Shopify inventory from a durable event ledger
Inventory changes can now enter a ledger before they are batched for Shopify. Each row identifies the business event, inventory channel, Shopify inventory item, quantity change, and reason. Replay-safe keys prevent the same event from being counted twice, and zero-change events can close without creating an unnecessary outbound message.
The controller recomputes aggregate available-to-promise inventory from committed OMS state and fans the change across the configured inventory channels. A batch publisher then groups pending changes into Shopify messages while retaining the reason for the change and isolating failures to a smaller scope.
Company adds an Inventory Sync workspace for monitoring waiting events, batches, jobs, recent resets, and feed mode. Absolute resets can supersede obsolete pending changes, giving the system a clear path back to authoritative inventory when a delta stream needs correction. Read the full event-driven inventory publishing update.
Current development UI, captured October 3 with demo data. Counts and schedules describe the existing demo connection. Select any screenshot to enlarge it.
Company
Run integrations from a shared control center
Company now brings Shopify inventory monitoring, batch order sync, app-version controls, carrier setup, Unigate configuration, and NetSuite order-push monitoring into one administration app.
Teams can inspect backlogs and recent runs, schedule or run supported jobs, pause and resume processing, and replay eligible errors from the same surface that holds the connection configuration. The Inventory Sync workspace now shows every job involved in publishing, including one publisher per inventory channel, the system-message sender, the manual discard tool, and the retention purge. Administrators can edit supported job parameters while app-created jobs remain paused u
