Integration, run by the team that builds the WMS.

Items, sales orders, purchase orders and inbound notices come in. Receipts, despatch confirmations with tracking, stock levels and returns go out. Every flow is per system, per client, and every event in the warehouse can push to the systems that need it.

Every connection targets one warehouse and one client, so each client in a shared building brings its own ERP or storefront, its own credentials, its own document formats and its own carrier accounts. A 3PL with a hundred clients has a hundred integrations that behave as one.

A new client on a system we already connect to is set up by configuration: connection, credentials, mappings, done. Guided setup for Shopify creates the order, shipment and stock connections together. New systems are scoped and built by the same engineers who run the hub. Supported today include NetSuite, SYSPRO, MYOB and MYOB Advanced, Cin7, Shopify, WooCommerce, Neto and Amazon.

APIs, webhooks, secure file transfer, email, message queues, cloud storage and direct database reads. EDI with retailers and trading partners mapped per partner. If a system can move data, the hub can connect it.

Failures raise an alert with the payload attached, land in the sync log inside .wms and can be replayed once the partner is back. Retries with back-off and rate-limited writes keep fragile ERPs stable. Your team sees every connection, its logs and a run-now action from inside the WMS.

A documented API for everything the hub moves, and Power BI connectors over the warehouse and billing data, so your analysts read .wms without an export.

Slimstock’s Slim4 forecasting connects to .wms and .tms, and dock appointment booking runs through a dock-scheduling integration.