AMC WMS — modules trucking · warehouse

A scan starts the clock. Loading stops it.

Pickup and delivery runs, receiving scans, spots, stock by shipper, piece labels, picking in walk order, cycle counts, and the storage charges that reach the invoice because two scans wrote down when they started and stopped.

30
Screens
Eleven of them are the field app on the driver’s phone, at /driver.
4
Languages in the field app
The field app only. The staff screens are English.

What it replaces

Most warehouses already do all of this, on paper.

A clipboard on the dockA scan with a time on it
A wall calendar for free daysBusiness days counted by the rule
“Which pallets are his?”Stock by shipper, by spot
Storage remembered at month endA charge line already on the invoice
A phone photo of a signed sheetPhoto, signature and GPS on the record
Re-keying the run when the truck had no signalA queue that sends when it comes back
What is inside

Six places where the work happens.

Receiving

The scan at the door

Pieces scanned in against the shipment, given a spot, and counted into that shipper’s stock. This is the moment the storage clock starts.

Spots and stock

Where it is, whose it is

Locations on the floor, stock held per shipper, and piece labels printed from the record rather than written on the carton.

Picking

In the order the floor is walked

The pick list is sorted by the route through the building rather than by the order the lines were typed into the shipment.

Counts

Cycle counting

A slice of the floor is counted at a time, against the stock the record says is there, without closing the warehouse for a weekend.

Storage

Charges and the rules behind them

Free time in business days, money in calendar days, a minimum applied once. It has its own page because it is where the money is.

Storage charges →

/driver — 11 screens

The field app

Pickup and delivery runs, barcode scanning, proof of delivery with photo, signature and GPS, an offline queue, four languages.

One flow

Receive → store → pick → load. The clock runs down the right-hand side.

Warehouse money is lost between these four rows — not because anybody is careless, but because the start and the end were remembered instead of written down.

1

Receiving scan

Pieces come in against the shipment and take a spot. Whoever scanned it and when is on the record.

Clock starts — 04 Aug 09:12 PDT
2

It sits in a spot, under a shipper

Stock is held per shipper, so “how much of his is here” is a screen rather than a walk around the building.

Clock running — free days first
3

Picked in walk order

The list follows the route through the racks. Pieces are scanned as they are taken, and labels print from the record.

Clock still running
4

Loaded out

Loading closes the clock. The charge line is built from those two stamps and goes to billing with everything else on the shipment.

Clock stops — 20 Aug 15:40 PDT

This is the reason storage reaches the invoice.

A CFS that bills storage from memory bills the boxes it happens to remember. Two scans that already had to happen — one to receive, one to load — are the two ends of the charge, so the line exists whether or not anyone thought about it at month end.

How the days are counted →

The reason the driver’s phone matters.

The stamps are only worth something if they were made where the work happened. That is why the field app scans on the phone, captures the proof of delivery on the phone, and holds the work in a queue when the yard has no signal rather than asking the driver to remember it until it does.

Fig. 1 — The scan starts the clock. The loadout stops it.lib/storage.ts
Receiving scan clock on clock off Storage clock — running counted by the system Load out one line on the invoice Storage — that many days, at the rate already on the file what the warehouse earns stops being something you count on a calendar and forget
Storage revenue that depends on somebody remembering to write down a date is revenue discovered a month later, if at all.
One real screen

The field app, with no signal.

A dock with steel over it is the normal case rather than the edge case. The queue lives in the browser on the phone, and the driver keeps working.

/driver — Run 14 · M. Ortega No signal
3 items waiting to sendHeld on this phone
Stop 4 — Sun Lighting LLC — POD capturedphoto · signature · GPS
Stop 3 — Vela Imports — POD capturedphoto · signature · GPS
Stop 3 — 6 pieces scanned14:02 PDT
Stop 2 — Kim Trading — sent09:41 PDT
Scanning uses the barcode reader built into the phone’s browser, and falls back to zxing where the browser has none.
What happens at the next bar of signal
The three queued items send themselves, in order, with the times they were captured — not the time the signal came back.

Four languages, on the phone only.

The eleven screens the driver uses run in four languages. The staff screens do not — those are English, and AMC prefers to state that here rather than have it discovered after warehouse staff have been hired. The proof of delivery the driver captured here is also the one the customer retrieves on the public site, photo and signature included.

Picking, scanning and counts →

Works with

The other five already know this record.

SCM

The storage line joins the shipment’s other charges at month end, and hired trucking sits there too — where waiting time becomes a charge line instead of an argument.

QMS

A storage rule can charge per revenue ton, which is the same W/M convention the ocean tariff uses: one cubic metre or 1,000 kilos, whichever yields the greater revenue.

ABI

Customs records sit on the same shipment the pieces were scanned against. ISF, AES and AMS are prepared and the responses recorded. AMC does not transmit to CBP.

Portal

The proof of delivery captured on the driver’s phone is what a customer gets back from a POD lookup on the public site, without signing in.

LiveTrack

Stage 1

Delayed, arrived, out for delivery, delivered — the four pushes, off the same record these scans write to.

The platform

WMS is two switches — the warehouse, and first and last mile. One, both or neither can be purchased.

Asked by people who run a dock.

Does the field app work with no signal?
Yes. Scans and proofs of delivery go into a queue in the browser’s own storage on the phone and send themselves when signal returns, carrying the time they were captured rather than the time they were sent.
What if the driver’s phone cannot scan barcodes?
The app uses the barcode reader built into the browser where there is one, and falls back to zxing where there is not. The button does the same thing either way.
How does a storage charge get onto an invoice?
The receiving scan starts the clock and loading stops it. Free days are counted in business days, chargeable days in calendar days, and the line is built from those two stamps. The whole rule is on its own page.
Can it print UPS, FedEx or USPS labels?
No. It prints piece labels from the record. Carrier labels are not produced, in the warehouse or anywhere else in the platform.

All twenty-two questions →

Get a demo

A disputed month of storage is welcome.

The two scans are run, the free days are counted as business days and the charged days as calendar days, and the resulting line is shown — with the inputs printed on the line, so it can be checked against the invoice that was sent.