Skip to content
jtWMS Docs

Platform overview

jtWMS is a warehouse platform offered as multi-tenant software as a service. It is designed to run a warehouse from one system across three layers that are often bought as separate products:

  • Management: the master data and layout of the warehouse. Today that is facilities, the storage layout from areas and aisles down to individual positions, zones, and the product catalog with units of measure and barcodes.
  • Execution: the work people do on the warehouse floor. Today that is the worker app, a phone-sized app where floor staff sign in and choose the facility they work in.
  • Control: the automated equipment that moves stock. Today that is the equipment model: the conveyors, diverts, scanners and other equipment in each facility, how product flows between them, and the controller address of each device.

API-first

Section titled “API-first”

Every feature is built as a REST API first, and the jtWMS apps are built on that same API. Anything a person can do in the apps can be done through the API, with the same permissions and the same rules. Changes are also announced as events, which your systems can receive as signed webhooks. See Integration model.

Multi-tenant

Section titled “Multi-tenant”

Each customer organisation is a tenant. All tenants are served by the same deployment, and every request is held to the data of the tenant its credentials belong to. Each tenant has its own users, roles, API keys, plan and data. See Multi-tenancy and data isolation.

How the parts fit together

Section titled “How the parts fit together”
jtWMS architecture The jtWMS apps and your systems call a single gateway. The gateway authenticates each request and forwards it to one of four services: identity and access, warehouse configuration, catalog, and webhooks. Each service has its own database. Warehouse configuration and the catalog publish events to an event bus, and the webhooks service delivers them to your systems as signed webhooks. jtWMS apps admin app and worker app Your systems ERP, e-commerce, reporting Gateway authentication, tenant context, rate limits Identity and access Warehouse configuration Catalog Webhooks database database database database Event bus signed webhooks
Requests enter through the gateway. Each service owns its own database, and warehouse configuration and catalog changes travel on as events.
  • Clients are the jtWMS apps and your own systems. They all use the same public API.
  • The gateway is the only entry point to the API. It authenticates every request, works out the tenant and permissions from the credentials, applies the tenant’s rate limits and plan features, and forwards the request to the service that owns the route.
  • Services each own one business area and keep its data in their own database. No service reads another service’s database. See Service domains.
  • The event bus carries the events that warehouse configuration and the catalog publish after their changes. The webhooks service consumes them and delivers the ones you subscribe to.

Next

Section titled “Next”