Custom warehouse management system development

A WMS that checks every scan against the order and shares one stock ledger with your stores.

Start a project

In a busy warehouse, the expensive mistakes are small. A picker grabs the medium instead of the large. Stock is put away in the wrong bin, so the system shows it in stock while the shelf is empty. A return goes back on the shelf without being recorded, and the store keeps saying “sold out”. Each error costs a reship, a refund or a bad review, and nobody can say where in the process it happened.

When a custom WMS is worth building

Warehouse management products, 3PL portals and shipping apps solve this for many sellers. If one matches how your warehouse works, use it.

Custom is worth considering when:

  • You run your own warehouse, or several, and your flows don’t match a product’s: kitting and light assembly, gift wrapping, B2B pallets alongside consumer parcels.
  • You need warehouse stock and channel stock to come from one ledger, not two systems kept in step by a sync.
  • Your team uses paper pick lists because the software in place is slower than paper.

How we would build it

Locations and tasks

The warehouse is modelled as locations: zones, aisles and bins, each with a barcode. Work is modelled as tasks: receive this delivery, put away these units, pick these orders, pack this tote, count this bin. Each task has an owner, a status and a timestamp at each step, so you can see what is waiting and for how long.

The flows

  1. Receiving. Deliveries are checked against the purchase order. Short, over and damaged quantities are recorded on receipt, not discovered later.
  2. Putaway. The system suggests a bin, and the putaway is complete only when the bin’s barcode is scanned.
  3. Picking. Orders are grouped into pick lists by zone or by batch, in walking order.
  4. Packing. Every item is scanned at the pack station. If a scan doesn’t match the order’s next expected item, or the count is wrong, the parcel can’t be closed.
  5. Shipping. Labels come from your carrier or shipping service, and tracking goes back to the store.
  6. Returns. Each returned item is graded (restock, refurbish, write off) and becomes a stock movement.

One stock ledger

Every scan that moves stock writes a movement row to the same ledger the inventory management system uses. On-hand stock is the sum of movements, so the warehouse and the stores can’t drift apart: they read one set of figures.

Integrations

The system would integrate with Shopify through its Admin API and webhooks, with Amazon through the Selling Partner API for orders you fulfil yourself, and with WooCommerce through its REST API. Each incoming order is stored with its platform ID before it creates work, so an order delivered twice creates one pick. If the store needs custom admin screens or rules, we’d build those as a Shopify app.

Checks that keep it honest

  • Scan or it didn’t happen. A putaway, pick or pack is complete only when the right barcode is scanned.
  • Counts don’t overwrite. A cycle count that disagrees with the ledger raises an exception with both numbers. A supervisor approves the adjustment, and their name is recorded.
  • Stop before committing. A receipt that doesn’t match its purchase order is held for a decision instead of going into stock as it is.
  • Every change attributed. Each movement records who made it, on which device and as part of which task.

Proof from our own code

We have not built a WMS before. The control patterns it needs already run in production in Lekhavo, our bookkeeping software for accounting practices:

  • Held imports. When a bank statement’s opening balance plus its transactions doesn’t equal its closing balance, the import is held before a single transaction is committed. It waits for a reparse or a person’s decision. A mismatched goods receipt would be held the same way.
  • One worklist. Everything a person has to decide goes into one queue, sorted by kind and age (this week, this month, older), so slipping items stand out.
  • Refusals that explain themselves. A blocked step returns the specific rows that block it and why, not a bare “failed”.
  • An audit trail. Each data change records the actor, the record, the operation and the fields changed.

What the first version includes

  • One site, with locations and barcodes
  • Receiving against purchase orders, putaway, picking, scan-checked packing and shipping
  • Returns grading
  • Order sync with your store and one marketplace, with tracking sent back
  • Cycle counts with supervisor approval
  • An exceptions queue and an audit trail
  • Source code, a written spec and runbooks

More sites, wave planning and labor reports can follow once the core flow is in use. If the warehouse is one part of a wider operations system, our ERP development work covers the rest.

How the work is run

Tembrant builds with an AI software factory: many agents work in parallel, held to fixed gates. Each change starts from a written spec, gets tests written first, goes through independent reviews and ships only after a person signs off. For a WMS, the tests would replay samples of your real order files, so the first pick lists are checked against orders you actually shipped.

If your warehouse runs on paper pick lists and good memory, tell us how it works today.

Questions

Do we need a custom WMS, or will an existing one do?
If a WMS product or your 3PL's system fits your flows, use it. A custom WMS makes sense when you run your own warehouse with flows the products don't model well, such as kitting, mixed parcel and pallet orders, or several sites sharing stock, or when it has to share one stock ledger with your inventory and accounting systems.
What hardware does it need?
We build the warehouse screens as a web app that runs on handheld scanners and phones. Most handheld barcode scanners type the code into the focused field, so there's no special driver. Label printers are driven by the label files your carriers or shipping service return.
How does it connect to Shopify and Amazon?
It reads orders that are yours to ship through each platform's API: Shopify's Admin API and webhooks, and Amazon's Selling Partner API for orders you fulfil yourself. When a parcel ships, it sends the tracking number back. Stock Amazon holds in its own warehouses stays in Amazon's records, and we'd read it as a separate location.
Have you built a WMS for an e-commerce client?
No. We'd be building yours as a new system. The patterns on this page, such as a check that stops work before bad data is committed, a queue for exceptions and an audit trail on every change, come from our production accounting software, and we'd apply them to warehouse tasks.

Have financial data that has to tie out?

Tell us what you want to build. We reply with questions, a plan and an estimate.

Start a project