Dockside · offline catch capture

The landing is written on paper, and then it dies three times.

Somebody writes the tote weights on a tally sheet on the wharf. At nine that night they key them into a spreadsheet. In the morning the same numbers get typed into the purchase slip, and later into the settlement. Four copies of one fact, three chances to differ, and no way to tell afterwards which one was right.

Dockside is the build that stops that at the source: the landing is captured once, where it happens, by the person who saw it, on a phone with no bars.

Try the capture demo Or read what offline first has to mean

Runs on: Phones and tablets, gloves on, in weather
With no signal: Full capture. Records queue on the device and drain in range
Produces: The dock receipt, and the lot every later record inherits
Talks to: Floor scales, your office view, Settle, your accountant

01What the build is

What does Dockside actually record?

The landing, in the detail an operation already works in: the vessel and its CFV number, the harvester and licence being paid, the trip, the buyer site and the time, and then the hot loop, which is container after container of gross, tare, ice, species and grade, with a running total per species always on screen.

A lot code is assigned the moment it is recorded, so everything downstream inherits its weights, its species and its harvester instead of being re-entered against them. The landing is the birth certificate of the lot. Get it wrong here and every report after it is wrong in the same direction.

What happens when there is no signal?

Capture keeps working, and so does reading. Records queue in an on device outbox that survives the app closing and the battery dying, the lists keep serving from what the phone already holds and say how old that is, and the queue drains itself when you come back in range. Sync is idempotent, so a retry after a dropped connection never books the same landing twice.

What comes out the other end?

01The dock receiptThe tally the harvester signs and takes away: net per species, price at landing, and the payable, rendered server side so there is one version of the document and it is the same one every time.
02The office viewLandings by day, vessel and species, with the exceptions on top rather than buried: a variance against the dockside monitor's certified weight, a landing still in draft, a device that has not reported in.
03The feed to everything downstreamThe lot goes to grading, the value goes to the settlement, the totals go to the bookkeeping. Nobody keys the landing a second time, which was the entire point.

Does it work with our scales?

Usually, and the answer depends on the indicator rather than the brand. A scale with a serial or network output reads directly. One without gets the camera path we are building on the wharf now, which reads the weight off the indicator’s own display with nothing to wire in. And there is always manual entry with the source logged, because a capture app that stops when the hardware does is not a capture app.

Is this the right build?

It is, if the data is born on paper at the wharf and re-typed later. It is not, if your landings already arrive clean in an office system and the pain is what happens after that. In that case start with Settle or GradeLine, and we will say so on the call rather than sell you the bigger one.

02What it costs

The build, one time: $8,450
Monthly, required: $299/mo

Where you land in the range is set by how many wharves and devices, how much has to keep working with no signal, what the dock receipt has to say, and what it has to talk to. The monthly runs the hosting, the sync infrastructure, support, and the engine updates. It does not climb with your headcount.

Book a 20 minute call How the ranges work