Core platform
Tenancy, identity, facility and product model, inventory ledger, orders, tasks, workflows, twin, Brain, picking and packing, labelling, loading, returns, metering and the apps.
One core. Every warehouse. Every executor.
WarehouseAI is a multi-tenant platform licensed to warehouse owners and operators. Its core models space, containers, products, inventory, orders, tasks, evidence and decisions, with nothing specific to one segment. Add-ons and connectors fit it to your business and your equipment.
TwinP123 is confirmed in bin B08. Its inspection is still open.
KnowledgeMerchant A requires inspection before returned units can be sold.
BrainCreate inspection work and keep the unit unavailable.
ExecutionAn operator inspects the unit and reports the result.
One returned unit passing through the four layers. Illustrative.
Every unit has an address.
WarehouseAI keeps one location model with two forms of guidance: a canonical identity for systems and robots, and a readable address for people. Containers nest, so moving a tote moves everything in it.
FacilityWH-A
ZoneGRID-1
PositionB08
ToteT501
CompartmentT501-3
PackageP123
- Layouts are versioned and published. Changing the floor reconciles the jobs and stock it affects.
- Package, compartment, tote and position keep their identity through any reorganisation, and nothing is counted twice.
- Placement checks real geometry: usable capacity, fit, reachability and the cost of getting it back out.
- A robot’s pick target and its navigation target are separate, so the same address serves a scanner user and a fleet.
Stock that can’t be allocated twice.
Inventory lives in balanced quantity journals. Expected, received, eligible and reserved are different states, and neither a forecast nor an inbound notice creates stock on hand.
ExpectedCollectedReceivedAcceptedAvailableReservedPickedPackedHanded over
Dashed states are records only. Nothing is physically in the building yet.
- Reservations are atomic. Two orders cannot take the same unit.
- Adjustments are controlled, with a reason and an authority.
- Counts, holds and compartments are part of the ledger, not spreadsheets beside it.
- Lot trace and recall holds work across facilities, forwards and backwards.
- Shelf life and sale eligibility are checked again at each step, not once at receipt.
- Goods you hold for others and goods you own stay separate, all the way to the books.
Tasks that a person or a machine can claim.
Every physical step is defined by what it is for, what it needs and what evidence closes it, independent of who or what does it. Manual work stays a supported mode and the fallback for every automated path.
- Work is assigned by capability. A person, a forklift and a mobile robot are not interchangeable workers.
- Claims are exclusive. Two executors never work the same task.
- Hybrid jobs hand over explicitly between robots and people.
- Execution mode is set per facility, zone and task type, not one global switch.
- The mobile app shows the task first, guides the scan sequence, captures offline and makes exceptions explicit.
The cloud decides what to move. Equipment controllers decide how.
Certified adapters translate tasks into vendor protocols. Motion, trajectories, grasping and safety stay in controllers and certified skill packages, and a site edge gateway keeps already-delegated work moving through a cloud outage.
Core, add-ons and connectors.
Every tenant gets the core. Add-ons bring physical capabilities a segment needs. Connectors link outside systems. Each is an entitlement you turn on, and none can bypass the core’s invariants.
Contract logistics (3PL)
Client onboarding, acceptance profiles, ASNs, SLAs, client data APIs, value-added services and contracted capacity.
Quick commerce
Your own retail stock, available-to-promise, instant orders, minute-level promises, substitution and rider handoff.
Courier and parcel
Multi-leg journeys, parcel sortation, cut-offs, consolidation and high-rate induction.
Goods-to-person storage
Cube and grid, shuttle, mini-load and vertical-lift systems with bins, compartments, ports and decanting.
Conveyors and sortation
Conveyor paths, induction, tracking, diverters and conveyor-to-vehicle transfer.
Robotic handling
Robotic picking, packing, label application, unloading, vehicle loading and mobile robot fleets.
Special handling
Cold chain, dangerous goods, high-value and regulated items.
Connectors
TransportLogisAI or any other transport provider, or a recorded manual handover.
Parcel carriersParcel carriers and multi-carrier platforms.
CommerceCommerce platforms, marketplaces and ERPs.
BillAIInvoice your own clients from verified usage, through your own BillAI seller account.
AccountsAIAccounting documents, payments, cost measurements and statements.
Where your teams work.
A spatial workspace for running the floor and plain task screens for doing the work. The 3D view explains the warehouse, while 2D, list and scanner views cover the same core actions.
warehouseai-opsThe operations workspace: facility setup, 2D and 3D views, stock, workflows, cases, integrations and remote supervision.
Mobile appOne app for warehouse staff and drivers, with role-specific workspaces, scanning, offline capture and handover.
Stations and kiosksFocused views for ports, decant, pack and load stations.
Developer console and SDKAdapters, connectors and add-ons, built against emulators in isolated sandboxes.
What WarehouseAI deliberately does not do
No customer portalClients, merchants and manufacturers exchange JSON with WarehouseAI through their own systems or authorised agents.
No motion commands from the cloudWarehouseAI decides what to move, pick, pack or load. Equipment controllers and certified skill packages decide how.
No custody of goodsWarehouseAI Corporation provides software and support. Your goods stay yours.
Built to serve many operators.
Each tenant’s data, configuration, add-ons, credentials and integrations are isolated. One tenant can run several facilities, operating profiles and customer relationships.
- Per-facility time zone, business calendars, metric or imperial units, and label language, with at least English and French for Canadian sites.
- Privacy and retention profiles, and a data residency region you choose for primary storage and backups.
- Typed custom attributes, configurable workflow steps and rules that ship with their own test cases.
- Configuration packages promoted with a diff, an approval and a rollback.
- Sandboxes with equipment emulators, and signed, replayable event subscriptions.
Start at L1 on the floor you already have.
Design partners get the first operating profiles built and tested against their own floor, SKUs and order history. You start with directed manual work and climb from there.