Skip to content

One record

Everything that moves through your warehouse, in one system.

From the truck at the dock to the signed delivery note. MulaWMS handles receiving, quality control, putaway, storage, picking, packing, loading, dispatch, returns and counts against a single inventory record, whether you are managing your own stock or storing goods for a dozen different clients.

  • In Spanish
  • In your timezone
  • On any browser
  • No per-device licensing
LPNLPN-0004821
CLI-ANDINA
  1. 06:12ReceivingDOCK-02
  2. 06:41InspectionNo defects
  3. 07:03PutawayA-04-03-B
  4. 09:18TransferA-04-03-B → P-01-12
  5. 11:20AllocationORD-1042 · FEFO
  6. 13:55Picking8 CS
  7. 14:20Packing8 CS · 142.6 kg
  8. 14:30Loading4.2 °C · WGK-482
  9. 15:02DispatchDN-8817
One day of one pallet

Nine transactions, one record. Nothing is edited in place: when a number looks wrong, you can walk backwards through exactly what happened to it.

Why centralizing matters

Every handoff is a place where reality and records drift apart.

The typical warehouse runs on four or five disconnected things. Between each of them, someone retypes a number.

Before

  • A spreadsheet for stock
  • A WhatsApp group for tasks
  • Printed sheets for counts
  • An accounting system for invoices
  • Someone’s memory for everything else

With MulaWMS

One movement ledger

Receiving a pallet, moving it, picking it and shipping it are the same record at different moments.

Your inventory number, your KPIs and your client invoice all come from that one source, so they agree with each other by construction.

One place to look when someone asks where the merchandise is.

1PL and 3PL

Built for both models from day one.

Most warehouse systems are written for one company storing its own product, and then bolt on multi-client support later. MulaWMS treats both as first-class from the ground up.

1PL

You store and ship your own inventory

You get the full operation without any of the third-party overhead: your products, your warehouses, your orders, your people.

3PL

You store and handle goods for other companies

Every product, every pallet, every location and every movement carries a client.

  • Register each client with their own code, contacts and storage arrangement: shared or dedicated space
  • Reserve specific locations for a single client so their stock never mixes with anyone else’s
  • Set tracking defaults per client, such as lot, expiry or catch weight, so their products inherit the right rules automatically
  • Give each client separate inventory, order and billing views inside the same warehouse
  • Run several operating companies on the same platform, each fully isolated, with tenant switching for administrators

Both models run on the same engine. A 1PL that starts taking on third-party volume doesn’t migrate anywhere: they just start creating clients.

Warehouse model

Modeled the way you walk it.

Not every warehouse works the same way, and forcing a distribution center to behave like an e-commerce pick line is how systems get abandoned. Each warehouse gets its own operating profile.

Location hierarchy
WarehouseBOD-01
ZoneZ-A
AisleA-04
LocationA-04-03-B
Type
Receiving · Storage · Picking · Packing · Shipping · Quarantine
Status
Available · Occupied · Blocked · In maintenance
Limits
Max weight · Max volume · Dimensions · Unit capacity
Route
Pick sequence
Client
Optional location owner

Warehouse types

Cold storageE-commerce hubDistribution centerFulfillment centerCross-dock terminalBonded warehouse

Receiving strategy

Dock then putawayReceive to locationPalletize at dockCross-dock

Storage unit

Loose stockLPN-strict

Dispatch strategy

Pick-to-packPick-to-loadStreaming pick-and-loadCross-dock

Allocation strategy

FIFOFEFOLIFO

Movement ledger

Inventory you can actually trust.

Stock is held per product, per location, per lot, with quantities split so an allocated pallet is never accidentally promised twice.

SKU-4471 · A-04-03-B · Lot L-2291240 On hand
ReservedAvailable
Lot and expiry
For anything with traceability or shelf-life requirements.
Actual weight in kilos
For catch-weight products, where two boxes of the same SKU aren’t the same thing.
LPN
A unique license plate per logistics unit, enforced unique across the company.
Status and unit
Available, reserved, picked, damaged or on hold. Each, case, pallet, crate or sack.
MulaWMSClient · CLI-ANDINA

LPN

LPN-0004821

SKU

SKU-4471

Qty

48 CAJ

Loc.

A-04-03-B

Lot

L-2291

Exp.

2026-04-18

4×6 · ZPL

2026-04-18 07:03

Pallet label

Transaction types

ReceiptPutawayAllocationDeallocationPickPackShipTransferReplenishmentCountAdjustmentReturnScrapDamageQuarantine release

Any stock record prints with its LPN, SKU, quantity, location, lot, expiry, client and a QR code that scans straight back to that exact pallet. There’s a formatted 4×6" version for Zebra thermal printers (ZPL) that prints from the workstation over the local network, and a browser-printable version for everything else.

Operations

From the dock door to the signed delivery note.

Every stage writes to the same ledger, so the status the supervisor sees is the real status of the merchandise.

End-to-end flow
  1. 01Receiving
  2. 02Quality
  3. 03Putaway
  4. 04Storage
  5. 05Allocation
  6. 06Picking
  7. 07Packing
  8. 08Loading
  9. 09Dispatch

Receiving and quality control

At the dock the screen adapts to the warehouse profile and captures lot, expiry and actual weight line by line. Discrepancies against the expected quantity are recorded rather than hidden: a short receipt is a real, visible status, not a silent adjustment.

  • Standard, detailed, sampling or full-count inspection
  • A defect-code catalog you maintain yourself
  • Rejected goods go to quarantine and only leave through an explicit release
  • Printable goods receipt note (GRN)

Order fulfillment

Orders move through the full lifecycle, from draft to shipped. Allocation applies the right strategy for each product and reserves stock so nothing gets double-committed.

  • Allocation can be saved as a draft and reviewed before it’s confirmed
  • Pick tasks are assignable and tracked
  • Short picks are a named status, not a quiet shortfall
  • Plate, driver and truck temperature on cold-chain loads

Replenishment, transfers, returns and counts

Replenishment runs on its own: an automatic sweep checks the whole operation every 15 minutes and generates tasks before the picker finds an empty slot.

  • Min/max rules per product and pick location
  • Transfers with a reason and full audit on both sides
  • Complete reverse logistics with RMA authorization
  • Cycle counts with a printable sheet and a variance summary

Product catalog

More than a SKU list: dimensions, weight and volume, storage type, units per case and cases per pallet, reorder point, shelf life, and the tracking rules that govern each product.

  • Lot tracked, expiry tracked, weight tracked, inspection required
  • GS1 GPC classification with bilingual Spanish/English titles
  • For 3PLs, products inherit their client’s tracking defaults

Want to see it with your warehouse’s actual flow?

Request a demo

3PL billing

The part that usually lives in a spreadsheet.

If you charge clients for warehouse services, this is where money leaks. MulaWMS captures billable activity automatically as the work happens, tied to the client, the warehouse and the document that generated it.

Billable activity

ReceivingDaily storagePickingPackingLoadingShippingReturnsValue-added services

Storage billing is the hard one, and it’s solved properly.

Instead of taking a single snapshot and hoping, MulaWMS reconstructs daily location occupancy from the movement ledger itself, walking the transactions in time order against each client’s own local calendar day. A location counts as occupied for a client on a given day if that client’s stock was in it at any point during that day, including a pallet that arrived in the morning and shipped that afternoon.

Idempotent and duplicate-proof

Re-run the calculation for the same period and you get the same answer. Activity records are append-only and protected against duplicates, so the same pick can’t be billed twice.

Daily occupancy, reconstructedCLI-ANDINA
MTWTFSS
A-04-03-B
A-04-04-A
B-02-01-C
MUELLE-02
15billable location-daysArrived and shipped the same daytransit, not counted

Transit locations, such as docks, staging and packing benches, are excluded, because those aren’t storage.

Reporting

KPIs that are history, not a query run against today.

Daily KPI snapshots are generated automatically for every warehouse, so trends are real history and not a query run against the current data.

Daily KPIs per warehouse

Orders shipped

184/ day

Trailing 30-day average

Units received

12,480units

Period to date

Units picked

11,902units

Period to date

Dock-to-stock

2.4h

Arrival to storage location

Order cycle time

9.1h

Order to shipment

Average inventory age

18days

Weighted average

Inventory dashboard

Stock by warehouse and by zone, the 20 lowest-stock products, and the 20 oldest stock positions sitting in your building.

Receiving and dispatch dashboard

Inbound and outbound volumes with the full status funnel, so you can see where orders are piling up.

Operations dashboard

Active versus closed task load across the operation.

Roles and permissions

Everyone sees their own work.

Access is controlled per resource and per action: seventeen resources across seven actions. Seven roles ship ready to use, and you can build your own by checking exactly the permissions you want.

17 resources × 7 actions · Role shown: Picker
ViewCreateUpdateDeleteApproveAssignExport
Orders
Inventory
Products
Suppliers
Customers
Inbound
Shipments
Pick tasks
Cycle counts
Users
Reports
Configuration
Billing
Settings
Returns
Replenishment
Transfers

Roles included

Super AdminAdministratorManagerReceiverPickerPackerViewer

The practical effect: a picker opens the system and sees their tasks. A manager sees approvals and assignments. A client-facing account sees read-only. Nobody has to be trained around screens they shouldn’t be looking at.

Questions

How easy is it, really?

Is there anything to install?

Almost nothing. It runs in the browser: desktop in the office, tablet on the floor, laptop at the dock. The only thing you install is a print agent on the workstation that sends labels to the Zebra printer (ZPL) over the local network; everything else prints straight from the browser. No updates to push, no per-device licensing.

Does anyone have to refresh the screens?

No. When a receiver closes a receipt, the putaway queue updates on the supervisor’s screen. When a picker completes a task, the order status moves. Nobody works off a stale number.

Is it in Spanish?

Yes: the interface, the roles, the statuses and the documents, running in your own timezone.

Do operators have to skip past fields that don’t apply?

No. Screens are built around the job, not the database. The receiving screen only asks for lot and expiry when that product tracks them. The dispatch screen asks for plate, driver and temperature when it’s a cold-chain load and skips it when it isn’t.

Where do documents print from?

From where you are. Pallet labels, Zebra labels, receipt notes, count sheets and delivery notes come out of the same screen where you did the work.

Does it work if I handle goods for several clients?

Yes. Every product, pallet, location and movement carries a client, with shared or dedicated space, tracking rules inherited per client, and separate inventory, order and billing views inside the same warehouse.

Demo

Tell us how your operation runs.

We’ll show you MulaWMS with your warehouse type, your receiving strategy and your tracking rules. No generic walkthrough.

We respond within one business day.

No forms or ticket queues. Your message goes straight to our team.

Direct contact

Start with an email.

Tell us what kind of warehouse you operate and what you need to improve. We’ll reply personally and coordinate the demo from there.

Emailhola@mulawms.comEmail us