What we're building

Shared across every signed-in device, updating without a refresh. Calendar, day counts, search, and approval for carrier-proposed slots.

A sign at the gate, a camera app the driver already has, and eight languages. No app to install and no account to create.

A waiting list with the clock running, and a gate sent from the office straight to the driver's phone.

One private link per carrier and per supplier. Their deliveries, slot requests, declarations, dispatch, proof of delivery and your site details — with no password in the way. Each side sees only its own.

Scan the supplier's own GS1-128 label and the product, batch, date and case count come straight off it.

Declared against arrived, from the photographed note, a pasted spreadsheet, or the carrier's own portal — and the driver is held until a discrepancy is looked at.

Two scans to give a pallet an address, a colour-coded map of every aisle, and first-expired-first-out picking with every exception recorded and reasoned.

Mark any slot as a picking slot, map each company's own case barcodes, and hand pickers their lists in a scanner-first app at its own address. Every scan deducts stock, shorts are recorded with a reason, and a list finished with no pallets recorded is flagged to the office.

A screen for whoever runs the floor: every picklist today with live progress, reassign a picker mid-shift, a queue of shorts waiting on a decision, expiring stock in the racking, and put-away checks that catch a pallet in the wrong slot.

Batches with born, reared and slaughtered declared, every transformation recorded, and a recall drill that walks the chain both ways in under a second and times itself. Beef's three-plant limit and the minced-beef single-origin rule are enforced by the form, not the auditor.

Scan the supplier's GS1 barcode, pick the batch — or two or three when a box carries several tracing codes — type each case's weight and print. Every case leaves goods-in with a DockLedger code the butchery scans later.

Scan the box off the rack, tap what you made, print labels with use-by, cooking and allergens from a spec the office signed off. Labels are designed at millimetre size in the app, print to any thermal printer through the browser, export ZPL for Zebra, and carry your logo.

A touch screen with a USB scanner and a serial scale, replacing the OSM terminal: scan the box, tap the product, put each pack on the scale and its label prints with that exact weight. Licensed per bench, with honest green and amber lights for scanner, scale and printer.

Your logo and name where the DockLedger mark sits — in the console, on the driver check-in screen, on the portal, at the top of every evidence pack and on every label.

Every site starts on the £129 platform — live bookings, driver check-in, contacts, your own branding — and adds exactly the modules it uses. A haulier yard pays a yard price; a meat plant pays for traceability and its bench stations. Switch modules on and off from Plan & billing, pro-rated.

Bot checks on every sign-in page, row-level isolation on every table, daily off-site backups, and a plain-English security page that says what we do — and what we don't claim.

Count a slot, compare against expected, keep the variance on record. For a proper count: a blind counting app that never shows the expected number, with percentage counted and variances landing live in the office.

A PDF per carrier per period, built from timestamps nobody had to remember to write down, priced against the free time and rate you agreed with them.

CSV, XLS and XLSX, forgiving about column headings, with a preview before anything is saved. Nobody retypes forty carriers.

Each aisle as you would see it standing in it — racking left and right, a bar per level, red where stock is past its date and amber where a pick face has run empty. Click a bay to see what is on each level and how many days it has left, and design the racking itself from the same screen.

Sign a driver in, change a gate, move a slot, scan a pallet — every console on the site shows it within a second, with no refresh. The board, the yard, goods in, the pick board and the rotation record all repaint from the database's own change feed.

The Stock screen names the exact pallet to take next for every product, records a pick in one tap, asks for a reason when someone takes a different one, and keeps a 30-day rotation record for the auditor.

Your customers get a login of their own — the office issues it from the customer's card, they set their own password — and order from their price list on a phone. You confirm, decline or send it straight to the pick board; they see every step and their delivery notes. An office order pad and per-customer price lists sit behind it.

A connector layer with Sage 200 first: customers, products and price bands pulled in, confirmed orders pushed out as sales orders, with a retry queue you can read. An orders API with per-customer keys for EDI hubs and customers' own systems, so an order placed anywhere lands in the same book.

Drop the week's inbound schedule in as CSV or Excel and it becomes bookings. Columns matched by heading, dates read as written, a preview of exactly what will land on the board, and your PO number kept on the booking as its own searchable reference.

On a groupage vehicle every expected line says whose it is. A supplier declares and sees only its own lines on its portal; the site assigns anything typed in from the paperwork. Confidentiality between suppliers on the same lorry, without hiding the list from them entirely.

Purchase orders, what to order next from real 28-day usage, and a supplier scorecard, in one page with three tabs. An order and its delivery are one thing: book the lorry from the order, link one already on the board, import a schedule carrying the PO number, or let the supplier ask for a slot against it on their portal. The checker's expected lines come from the order and the lorry signing in marks it landed.

The written guide for a carrier's office, a supplier's despatch desk and the driver at the gate, in every language the portal speaks. Drafted by the team, being read through by native speakers.

The other direction gets the same discipline. A confirmed order books its collection on the dock diary as an outbound slot; the loading check confirms what actually went on the lorry line by line, records any short with the order, closes the pick and mints the despatch — and the customer's portal shows the collection, the despatch and what was sent against each line the moment it leaves.

Every open purchase order sits on the supplier's portal with its lines. They confirm the quantity they will actually send, a promised date and a note, before anything is booked; the buyer sees the confirmation on the order, and the scorecard reads fill rate — cases ordered against cases the bench scanned in — and how often each supplier confirms at all.

A WMS, TMS or ERP is told the moment a slot is requested, approved or moved, a vehicle arrives, reaches a gate, is checked or released, an order is placed, confirmed or despatched, a purchase order is confirmed or landed. One signed POST per event with a secret you hold, retried with backoff for eight tries, a delivery log and a test button, all from Orders → Integrations.

Beside Sage 200: paste the developer app's details once, press Connect, and confirmed orders go out as draft invoices (Xero) or estimates (QuickBooks) while customers and item prices come back in nightly. Credentials live in the vault and are never shown again.

A personal home screen under the Overview: pick the panels your job needs — late today, slots to approve, POs the supplier has not confirmed, expiring stock, next vehicles due — and they are yours alone. Numbers come from one company-scoped query, each tile opens the page behind it.

Out-of-rotation picks by reason and by person with the last fifty breaks listed took-versus-should; short deliveries by supplier week by week and despatches with shorts by customer; and the purchase-order fill rate, confirmation rate and on-the-day rate per supplier. Any range, exported as CSV.

The next two connectors on the same layer as Sage 200, Xero and QuickBooks, as customers ask.

The supplier confirms on the portal today; next is the order itself going out from here as a PDF and a portal link, so nothing is retyped at either end.

The rotation, shorts and fill reports arriving on a schedule to whoever should read them, alongside the weekly site report.

So a customer's or carrier's own system can create and move bookings without a person in the loop — the orders API already shows the shape.

For operators running several workspaces who want one view across them.

Recording the probe reading against the delivery, for chilled and frozen sites — and against each batch for meat plants.

The station prints through the browser today; next is talking to a Zebra directly so a bench label prints with no dialog at all.

The pallet plates exist at goods in; this is the full SSCC label for suppliers who send pallets with nothing scannable on them, so your label becomes theirs.