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.
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 until they are reviewed and activated.
Carrier setup includes methods, mappings, billing details, and a readiness checklist so configuration and operating status remain visible together. Read the full integration control center update.
Manage company structure and NetSuite subsidiary mappings
Company can now manage internal organizations as a hierarchy, including create, rename, and reparent actions with cycle protection. Facility assignments make it easier to see which operating locations belong to each organization.
For NetSuite exports configured to use the facility's owning company, administrators can maintain the subsidiary ID in that company's External ID field. The mapping stays beside the company and its locations. Read the full multi-company update.
Transfers and receiving
Create and receive transfer orders through one connected workflow
Receiving now includes a transfer-order creation flow for selecting the source, destination, products, and quantities. When a warehouse transfer order is approved, the OMS can move its items to the valid state and reserve inventory from the source warehouse.
The flow connects Receiving with Transfers and Fulfillment. NetSuite transfer lifecycle imports now use master data management, so fulfillment, cancellation, and receipt activity completed outside the OMS can update the same transfer records. With event-based Shopify publishing enabled, warehouse commitments reduce the inventory offered for sale close to real time. Read the full transfer-order update.
Receiving also corrects force-scan behavior, transfer-detail redirects, and purchase-order sorting. Products without an inventory record at the receiving facility now show zero on hand without repeatedly requesting the same quantity.
Existing demo replenishment transfers with item counts and package tracking. Current development UI, captured October 3, 2026.
Cycle Count
Create counts and trace variance decisions
Cycle Count adds a creation page for both administrator and store views. Teams can define the count at the point of work instead of preparing every request in a separate administration surface.
The Pending Review search now accepts a count name or work effort ID. A new variance-decision view connects each decision to its count, facility, product, reason, outcome, and the person who made it. Other inventory views can use that record to explain a stock change. Read the full Cycle Count update.
An unsaved count plan using the demo's existing Brooklyn facility and catalog. Current development UI, captured October 3, 2026; no count was submitted or inventory changed.
Store fulfillment apps
Make daily queues more dependable
BOPIS improves loading behavior on Ready for Pickup and Completed, validates pickup-notification responses before showing success, and preserves the selected locale. Order details show when canceled orders will next synchronize. Fulfillment improves picker search, order counts, transfer-shipment permissions, carrier updates, and locale persistence.
Receiving, BOPIS, Fulfillment, Cycle Count, and Transfers continue the move to centralized application permissions and installable progressive web app support where included in their August releases.
OMS and integration services
Carry better operational context through the core platform
OMS updates add customer and order context to assigned tasks, expand order audit history, improve task transitions, and correct negative reservation cases. Inventory details retain more movement reasons, including point-of-sale issuance corrections, while fulfillment records can carry estimated ship and delivery dates.
NetSuite connector and OMS updates add transfer-order receipt imports, pending order-push counts, more detailed inventory movement reasons, and estimated ship and delivery dates. NetSuite configuration also uses the current RESTlet URL, and product identification reuses the resolved HotWax product ID throughout the export flow. These changes keep integration status and operating context visible at each boundary.
