← Tobala Software Pilot enquiries
Warehouse management · In pilot

A warehouse system that knows
how warehouses work.

Receiving, putaway, wave picking, pack and ship — the depth that used to require an enterprise contract, sized for one building, one team, and orders measured in hundreds. Run it for your own brand, or run it as a 3PL for a dozen client brands. Same system, either way.

Tahona WMS dashboard showing orders today, open, picked and shipped counts alongside a recent activity feed
The floor at a glance. What came in today, what is still open, what is picked, what has gone out — and an activity feed that names the person behind every action.
01 · Who this is for

Two operations, one system.

Most warehouse software makes you pick a side. Merchant tools assume every order is yours. 3PL platforms assume you never ship your own. Tahona was built for both from the start, because the same building often does both — and because brands that outgrow their own floor tend to become someone else’s client, not someone else’s migration project.

Path one

You ship your own orders.

A brand fulfilling from its own warehouse. Orders land from Shopify and Amazon, get allocated against real stock, group into waves, get picked, packed, and labelled — and the tracking number goes back to the channel without anyone copying it anywhere.

Path two

You ship for other brands.

A small 3PL fulfilling for client brands. Each client owns its own inventory, orders, receipts, and sales channels. Stock is segregated per warehouse, client, and SKU — and a per-client usage report gives you the numbers you invoice from.

02 · What makes it different

Six decisions that aren’t the default.

Every WMS claims the same feature list. These are the choices underneath it — the ones that are hard to retrofit and easy to check.

01

A database per customer.

Your data lives in its own database — not in a shared table behind a tenant_id column. Real isolation, not a WHERE clause. It also means your data can be handed to you, or moved, as a unit.

02

Merchant and 3PL from one product.

One brand shipping its own orders, or a 3PL fulfilling for many client brands, out of the same install. Turning on client mode is a setting, not a different product and not a migration.

03

Enterprise depth at small-operation scale.

Wave picking, putaway with suggested locations, zones and bin locations, cycle counts, stock transfers. Real warehouse mechanics — not an order list with a “fulfilled” checkbox.

04

Hosted or in your own building.

One codebase runs as multi-tenant SaaS or as a single-tenant on-premise install. If your operation needs the software to live on your own hardware, that isn’t a special edition.

05

Multi-warehouse and multi-channel on day one.

Every record with a physical location carries a warehouse. Every order carries the channel it came from. Neither was bolted on later, so the second building and the second channel don’t break the first.

06

An API that treats you as an owner.

Scoped, per-workspace API keys and real REST endpoints — push orders in, read orders, inventory, and warehouses out. Build the integration nobody else was going to build for you.

03 · The fulfillment chain

Dock to doorstep, in one place.

Order import → allocate → wave → pick → pack → ship, with label printing at the end. Pick-to-ship, pick-pack-ship, or pack-ship — whichever shape your floor actually runs. Receiving and putaway feed the same stock the allocator reserves against, so the numbers agree.

Order list showing order number, client code, source channel, customer, status, item count and total
Orders arrive with their channel attached. Shopify and Amazon orders in one list, each carrying the client it belongs to and where it is in the pipeline.
Waving screen with allocated orders selected by checkbox and a create and release wave button
Build a wave from what’s allocated. Select the orders you want on the floor next and release them — or let auto-release rules do it on a schedule.
Wave pick list showing order, client, SKU, quantity required and quantity picked across several client brands
One pick pass, many orders. The released wave becomes a single batch pick list — and in 3PL mode it spans client brands without mixing their stock up.
Putaway task showing SKU, quantity, suggested location, status and a target location selector
Putaway suggests, the operator decides. Each received line gets a suggested bin; confirm it or override it. Stock moves atomically on completion — no half-landed receipts.
04 · 3PL mode

Your clients’ stock stays your clients’.

Turn on clients and every inventory item, order, receipt, and sales channel belongs to one of them. Stock is tracked per warehouse, per client, per SKU — so two clients selling the same SKU never draw down each other’s units. Client codes show up on documents and in the API, and every screen with a list gets a client filter.

Inventory overview listing SKUs grouped by client code with on hand, allocated and available quantities
On hand, allocated, available — per client. Same building, same shelves, separate books. Filter to one client when you’re answering their question.
Usage report showing orders and items received per client per month
The numbers you invoice from. Orders and units per client per month, cancellations excluded — so billing a client is reading a row, not rebuilding a spreadsheet.
05 · Connected

Wired into the stack you already have.

Channels, carriers, and printers are set up through guided wizards that test the connection before they save it — so you find out the token is wrong while you’re looking at the screen, not at 6am when orders didn’t import.

Shopify

  • Four-step setup with a live credential test
  • Order import, verified end to end against a real store
  • Inventory sync and tracking push-back
  • Auto-fulfill when a shipment ships
  • Signed real-time webhooks, or scheduled sync
  • Multiple stores per workspace

Amazon

  • SP-API sales channel
  • Multi-Channel Fulfillment (MCF)
  • FBA status mirrored back into your order list
  • Order cancellation handled both directions

Carriers & labels

  • EasyPost integration — real label purchase, verified live
  • Rate access and tracking
  • Browser printing for shipping and item labels
  • ZPL over the network for thermal printers

Your own code

  • REST API with per-workspace bearer keys
  • Scopes per key — read, write, or both
  • Push orders in; read orders, inventory, warehouses
  • Revoke a key without touching the others
Shopify integration setup wizard showing shop domain, owning client, and merchant or 3PL integration mode
Connect a store in four steps. Point it at a shop, say which client owns it, and choose whether you’re running as the merchant or as their fulfillment service.
API keys table listing key name, prefix, scopes, created date, last used date and status
Keys you can reason about. Named, scoped, and stamped with last-used — so you know which integration is actually running before you revoke anything.
06 · The rest of it

The unglamorous parts, done.

Inventory

  • Stock levels by bin location
  • Adjustments with a reason
  • Transfers between locations
  • Cycle counts
  • CSV import for the initial load

Warehouse structure

  • Multiple warehouses per workspace
  • Zones: receiving, forward pick, reserve, pack, staging
  • Bin locations with type and capacity
  • Every located record carries its warehouse

People & control

  • Team invites with roles
  • Guided setup wizards for warehouse, channels, printers
  • Wave auto-release rules
  • Admin console with TOTP two-factor

Accountability

  • Audit log of every action taken
  • Who did it, when, and whether it succeeded
  • Filter by actor, action, date, outcome
  • API keys are actors too, not anonymous traffic
Activity log listing timestamped actions with actor, description and outcome, filterable by date, action, actor and outcome
Every action has a name on it. When a count is wrong or a customer says the box never shipped, the answer is a filter away rather than a conversation.
07 · The pilot

We’re looking for a few design partners.

Tahona is built and running. It is deployed, the fulfillment chain works end to end, real Shopify orders have been imported and real carrier labels have been bought. What it does not have yet is a wall of customer logos — and we’d rather say that plainly than invent one.

So this is the honest offer: a small number of pilot operations, worked with directly. Hands-on setup, your locations and SKUs loaded for you, a direct line to the people building it, and real influence over what gets built next. Pilot operations keep preferred pricing when we launch.

In pilot · Taking design partners

Tell us about your operation — how many orders a day, how many buildings, which channels you sell on, and whether the stock is yours or your clients’. That’s enough for us to say honestly whether Tahona fits yet.

Write to us about the pilot

Screens on this page are the real product, filled with demonstration data — the SKUs, client brands, and customer names are invented for the screenshots.