Welcome to Trackberry

What Trackberry does #

Trackberry manages fresh produce shipments from packing house to final destination. It reads your shipping paperwork, validates it, tracks the container, and tells you when something needs attention.

The problem it solves is data entry. A single shipment arrives as a scatter of PDFs and spreadsheets from suppliers, forwarders, and inspectors, each in its own format. Trackberry reads those documents, turns them into structured pallet data, and keeps that data current as the shipment moves.

The model in one page #

Understanding these four relationships explains most of Trackberry’s behaviour, including situations this documentation doesn’t cover explicitly.

Everything belongs to an organization. Shipments, members, settings, and approved senders are scoped to one organization. You can belong to several and switch between them; nothing leaks across the boundary.

Documents are the input; pallet data is the output. A shipment is not something you type in. It’s what Trackberry derives from the documents attached to it. Attach a better document and the data improves — which is why superseding a document re-extracts and re-checks everything downstream.

Checks validate your data against itself. Quality checks ask whether the paperwork is internally consistent: do the per-pallet boxes sum to the declared total, does the invoice describe the same goods as the packing list. They never assess the produce. That’s what a third-party inspection report is for.

Tracking and monitoring answer different questions. Tracking says where the container is. Monitoring says whether anything has stopped — a carrier gone quiet, an ETA long past, a draft nobody validated. A shipment can be perfectly tracked and still need attention.

Find your task #

How a shipment moves through Trackberry #

1. Documents arrive — emailed to your organization’s inbox by suppliers and forwarders, or uploaded directly.
2. Data is extracted — pallets, produce, calibre, box counts, weights, certifications. Most documents parse locally in seconds; see how extraction works.
3. Checks run — your configured rules validate the extracted data and flag anything that doesn’t reconcile.
4. Your team reviews — approve, reject, or correct.
5. The container is tracked — position, milestones, and ETA, with alerts when progress stalls.
6. Data goes out — to your ERP, a spreadsheet, or a public tracking page for your customer.

What Trackberry does not do #

• It is not a transport management system. It doesn’t book freight or tender loads.
• It doesn’t assess produce quality itself — it reads inspection reports written by others.
• It has no self-serve public API yet. See Integrations & API Access for what can be automated today.

Next step #

Head to the Quick Start guide to set up your organization and receive your first shipment.

Keep up with what’s new #

New features are announced in News, and we post regularly on LinkedIn — product updates, and what we’re learning about container shipping and fresh produce logistics along the way. Follow along there if you’d rather not check back here.