Integration setup and integration operations are usually treated as separate concerns. One screen stores credentials and mappings, while another job, log, or support request reveals whether the connection is actually working. That separation makes routine questions harder than they need to be: Is the job scheduled? How much work is waiting? Which run failed? Can the team replay it safely?
Integration setup and integration operations are usually treated as separate concerns. One screen stores credentials and mappings, while another job, log, or support request reveals whether the connection is actually working. That separation makes routine questions harder than they need to be: Is the job scheduled? How much work is waiting? Which run failed? Can the team replay it safely?
The August Company releases bring more of those answers into the same HotWax Commerce app that holds the connection.
Operate Shopify order and inventory flows
Batch Order Sync gives teams a guided way to configure order ingestion, monitor recent runs, and investigate the two processing stages behind an import. Supported jobs can be run, paused, resumed, or scheduled from the workspace, and eligible errors can be replayed without reconstructing the original request by hand.
Each failed run keeps its error details available, so teams can review the cause before deciding whether to retry.
Inventory Sync adds the other side of the Shopify connection. It shows waiting inventory events, batches, jobs, recent resets, and publishing history for each shop. Teams can also see whether the supporting data feed is in manual or real-time mode. Together, the order and inventory workspaces make backlog and processing state visible beside the connection they belong to.
The latest August release makes every participating inventory job visible. Company shows one publisher for each inventory channel, the system-message sender, the manual discard tool, and the retention purge that explains how long completed event history remains available. Administrators can edit the parameters a job accepts, while app-created jobs begin paused so their scope and schedule can be reviewed before activation.
Current development UI, captured October 3 with demo data. The existing inventory channel shows delivery activity and publishing and reset jobs; counts and schedules describe this demo connection. Select the image to enlarge it.
Configure carriers and Unigate together
Company now includes carrier catalog, creation, detail, and shipment-method setup. Administrators can maintain the carrier and its methods, map the values used by connected systems, and review a readiness checklist before the configuration is used in fulfillment.
For retailers using Unigate, the same area carries credentials, method mappings, billing details, and tenant connection information. This makes it easier to distinguish a missing business mapping from a missing connection value when a label or rate request does not behave as expected.
Monitor NetSuite order push
The NetSuite workspace shows the order-push backlog, recent runs, rule groups, rules, and schedules. Teams can run supported processing immediately or update its schedule while retaining the context of which order feed is being controlled.
The workspace also identifies rule conditions that the order feed does not yet evaluate. Teams can distinguish a saved configuration from a filter that is actually changing which orders are exported.
Keep app rollout controls close to administration
Company also adds application-version management for development, user acceptance testing, and production environments. Administrators can see which app build is intended for each stage and coordinate a controlled rollout without treating the latest available front end as the only option.
Company is becoming the operating home for integrations, not just a place to enter setup values. The practical shift is that configuration, backlog, schedule, recent execution, and recovery controls can be read as one operational story.
