Prove what arrived
Count, condition, photos, signature — at the gate.
Captured before the truck leaves, on a phone your storekeeper already carries. Works offline when the network drops.
For goods-receiving operations
Your driver signed a clean receipt.That signature just killed your claim.
When a delivery arrives short or damaged, the question is never what happened — it's what you can prove. TallyCord photographs the gate, records the count and condition, and captures a proper signature before the truck leaves. Then it checks what arrived against what your supplier said they sent.
Lifecycle ledger · live
RS-LAS-2026-0091·STL-LAS-0142
Stocked
[STK]SigningImported into inventory · Lagos Main
09:11 UTC0xa7f9b001Bound
[BND]Sealed to package · device verified
– –pendingPickup
[PCK]Rider scan · GPS captured
– –pendingIn transit
[TRN]Live signature · offline tolerated
– –pendingDelivery
[DLV]Recipient scan · seal intact
– –pendingVerified
[VRF]Locked in · published for anyone to check
– –pending
Hover to pause. Every event signed on-device.
Reconciliation
Find the gap while the truckis still at your gate
Every delivery is checked against the delivery note and your supplier's record, automatically. When they agree, nothing happens — that's the point. When they don't, it's flagged before the driver leaves, not discovered at month-end in a spreadsheet nobody trusts.
Reconciliation · live
RS-LAS-2026-0091
Physical scan
Your system
Delivery status
Delivered · recipient confirmed
Delivered
Seal integrity
STL-LAS-0142 · verified intact
Seal ID matches
Evidence
Photo + signature captured
No evidence on record
Checked against your system in real time.
What this does for you
You are not short of goods. You are short of proof.
Almost every business already checks what arrives. Almost none keep a record that survives a dispute. TallyCord is the record.
Prove what should have arrived
Checked against the delivery note and your supplier's record.
Automatically, load by load — not reconstructed from memory three weeks later when someone finally asks.
Find the gap in time
Flagged while the driver is still on site.
Short, damaged, substituted or missing. Not discovered at month-end in a spreadsheet nobody trusts.
Send a claim pack
One link: photos, count, signature, timestamp.
Exactly what a supplier, carrier, insurer or lawyer asks for — assembled whether or not you are in the office.
TallyCord turns a signature you shouldn't have given into a record you can win with.
Problem
What happens without proof
This is not our description of the problem. These are the words of Nigerian operators, vendors and published guidance already working in this market.
The tools don't work together
“Most medium to large haulage companies have a tracking system and an ERP system in place, but the tools do not work together, and they do not serve the realities of haulage operations.”
✕ You own the data and still can't answer the question
The POD is a phone call
“Transport teams still rely on calls to drivers or WhatsApp messages to obtain journey status updates or share proof of delivery documents (PODs), which causes billing delays and makes data-driven decision-making and process improvement nearly impossible.”
✕ Your evidence lives in a chat thread
A clean signature ends it
“A delivery confirmed only by a rider's word, a WhatsApp text, or an unsigned waybill collapses the moment anyone seriously disputes it — there's simply nothing behind the claim.”
✕ Nothing holds up to scrutiny
Why the record matters
The signature your driver just gave may cost you the claim
A clean, un-notated receipt is treated as proof that the goods arrived whole. Most businesses sign first and argue later — and the argument is the expensive part.
What the law actually says
Where goods are entrusted to a carrier and are then not delivered, delivered short, or damaged, the carrier — as bailee — must show the loss was not caused by its negligence. The shipper proves entrustment and loss first. Then the onus shifts.
“It is settled law that, in bailment, the onus of proving that there is no negligence is on the bailee.”
Supreme Court of Nigeria, quoting Ogugua v Armels Transport Ltd (1974)
What your proof rests on
The receiver's proof chain starts from the consignment note. Sign it clean and you have conceded the goods arrived whole — before anyone has counted a thing.
A delivery confirmed only by a rider's word, a WhatsApp message or an unsigned waybill collapses the moment it is seriously disputed.
Nigerian courts have decided cargo shortfall cases on exactly these documents — including one that turned on whether the waybills matched the load.
The clock starts at the gate
- 60 days
- Admitted insurance claims must be settled within 60 days of notification — ₦500,000 penalty plus monthly compound interest for delay (NIIRA 2025, s.210).
- 12 months
- Carrier bill-of-lading terms typically bar proceedings after 12 months from delivery — sometimes as short as 9.
- Day zero
- Notice of claim must be issued the day the damage is discovered. After that it is reconstruction, not evidence.
A claim is only recoverable if it was evidenced at the gate, on day zero. Everything after that is argument.
Who it's for
If goods arrive at your gate, this is for you
Start with one gate. Most customers run a single receiving point for three weeks before they touch anything else.
Distributors & wholesalers
The claimant. One gate, one scan.
Warehouses & depots
Receiving, inspection, discrepancy.
Manufacturers
What left the plant, in what condition.
Construction sites
Cement, iron rods, materials in.
Hospitals & pharmacies
Pharma and medical supplies in.
Carriers & 3PLs
Prove you delivered it correctly.
Start with
One gate, three weeks
A free gate audit. We record what actually arrives and put it beside what your suppliers said they sent.
You need
A phone and a gate
No hardware, nothing to install, no change to how your suppliers operate. Works offline.
If nothing is wrong
You've lost three weeks
And you'll know your suppliers are clean. If something is wrong, the first claim pack is yours.
Mechanism
From what happened to what you can prove
Seven steps, the same for every physical event: captured, evidenced, reconciled, understood, acted on, verified, and resolved.
Physical activity
Capture
A scan, a photo, a signature — recorded and signed on the device, even offline.
Operational Truth
A record that can't be edited, checked automatically
Every event is written once and locked in place, chained to the one before it. Every scan is compared against your system in real time. The result is one record you can trust — not a reconstruction after the fact.
Nothing gets edited
Corrections are added as new entries that reference the original. The original record never changes.
On-device signing
Every scan is signed by the worker's own registered device. A stolen password can't be used to rewrite the past.
Daily lock-in
Each day's records are sealed together so they can't be altered afterward. Your team can verify this anytime from the Audit tab, or export the full history for an outside auditor.
Physical scan
Your system
Delivery status
Delivered · recipient confirmed
Delivered
Manifest count
42 units scanned
42 units expected
Evidence
Photo + signature captured
No evidence on record
Exception flagged
Routed for review
Sample event · raw payload
[PERSISTED]
{
"id": "EVT-2026-LAS-92114",
"type": "DELIVERY_SCAN",
"seal_id": "STL-LAS-0142",
"shipment": "RS-LAS-2026-0091",
"actor": "DEV-LAG-RD-013",
"client_ts": "2026-05-04T14:21:08Z",
"server_ts": "2026-05-04T14:21:11Z",
"lat_lng": "[6.4541, 3.3947]",
"evidence": "sha256:0x4c91…d7e2",
"prev_hash": "0xa7f9b491…",
"chain_hash": "0xa7f9b5fa…"
}The chain proves this record hasn't been altered since it was written — it doesn't, on its own, prove the physical event occurred independent of the device that reported it.
Intelligence & automation
Recurring risk, surfaced — not hidden in the numbers
When the same kind of exception keeps happening, TallyCord surfaces it as an emerging operational risk, with the evidence behind it, not a black-box score. Where you've defined a policy, TallyCord can respond automatically: notify, escalate, or take a bounded action — always with an approval step and a verification of the outcome. Nothing acts on your operation without a record of why.
Emerging operational risk
Sample
Recurring evidence gaps · Lagos Main
ObservedSeverity
Medium
Probability
62%
PredictedContributing signals
- · 3 discrepancies, evidence predicate: unit_count
- · Branch: Lagos Main, last 14 days
- · Confidence trend: declining
Supporting cases
4 reconciliation cases, last 30 days
Automated response
Sample
- 1Observed
Risk detected
- 2Recommended
Policy matched
- 3Recommended
Approval
- 4Executed
Action
- 5Verified
Outcome verification
Every step requires the one before it — approval is never skipped, and the outcome is verified, not assumed.
Network
More than one organization can trust the same record
A carrier, a warehouse, a receiver — each can participate in the same operational chain, see their own scoped view, and verify each other's claims. No organization gets unrestricted access to another's data.
Carrier
Reports pickup & transit
Sees: their own events + case status
Warehouse
Reports receiving
Sees: their own events + case status
Receiver
Confirms delivery
Sees: their own confirmation + case status
Shared operational case
One record, three scoped views — no participant sees another's full data.
Anyone holding a package can check its status, without an account.
A read-only link, no login, no app — scan the QR code or open the URL and get a clear answer: valid · broken · suspicious · invalid.
The page only shows what you choose to share. Every event on it comes from the same record your team can verify anytime.
/verify/ssv_live_demo
[STAMPED]
Status
VALID · INTACT
Full chain verifiable in the Audit tab
Platform
Built to connect to what you already run
TallyCord isn't a system you migrate into — it's infrastructure that sits alongside your existing business systems. One API for events, evidence, and assertions. Scoped API keys, so a compromised key can only do what it's explicitly allowed to. Webhooks for everything that matters, signed and retried. One error format, everywhere.
One event API
Physical events, evidence, and external assertions all speak the same contract — see docs/PLATFORM-CONTRACT.md.
Scoped API keys
Each key carries an explicit, closed scope. A compromised key can only do what its scopes say.
Signed, retried webhooks
One dispatcher, HMAC-signed, replay-protected, with a queryable dead-letter table for terminal failures.
Sample request · illustrative
[ACCEPTED]
POST /v1/events
Authorization: Bearer sk_live_••••••••••••
Idempotency-Key: 8f2c-4b91-a7d3-0091
event_type: RECEIVING_SCAN
business_object: receiving_line:RL-2026-0091
evidence_ref: sha256:0x4c91…d7e2
status: acceptedOne event API · scoped keys · signed, retried webhooks
Field
Built where the work actually happens
TallyCord's mobile app is what your riders and warehouse staff actually carry, built for the loading bay, the back of the truck, and the front porch, not just the dashboard.
Works with no signal
Scans are saved with the real time they happened, and sync automatically the moment you're back online.
Never loses a scan
A scan that syncs late still keeps its true timestamp and gets flagged for review. Nothing is ever silently dropped.
On-device signing
Every scan is signed by the worker's own device. A stolen password can't be used to fake one.
GPS evidence
Location is captured automatically with each scan, when available, no extra steps needed.
Start with a gate audit
See what your gate is actually losing.
We record three weeks of deliveries at one operational gate — count, condition, photographs and signature — and give you a one-page report of every gap we find. Yours to keep, whether or not you continue.
Gate audit scope · three weeks
[NO CHARGE]
Audit investment
Free
Three-Week Gate Audit
1 gate
Three weeks of deliveries
Count, condition, photographs, signature
One-page report of every gap
Request a free gate audit
No payment and no commitment. The report is yours to keep, whether or not you continue. If you do, the 60-day pilot and monthly pricing are published.
Included in the audit
- Physical Capture
- Evidence
- Reconciliation
What the audit produces
- 01Capture
- 02Reconcile
- 03Report
Use cases
Where TallyCord runs today
Delivery discrepancy resolution
Scan, confirm, reconcile — delivery exceptions get flagged and resolved with a timeline, not a dispute.
Warehouse receiving
Receiving lines checked against the manifest automatically, mismatches routed for review as they happen.
Multi-party operational verification
Carriers, warehouses, and receivers each confirm their part of the same case — independently, without shared access.
Begin