Security

What it reads. What it drafts. What it never touches.

TrueFlo reads your paperwork, checks it and drafts the fixes. A person approves before anything goes into your ERP or out the door. Below is where each piece stands today.

Where it stands

Where each piece stands today.

Where each part of TrueFlo's security stands today
WhatWhere it standsWhat that means
Your systems
Access to your systemsNone on day oneYou forward the emails or drop the files in a shared folder, and send the export your ERP already makes. No access to your inbox or your systems on day one.
Writing to your ERPNever on its ownNothing goes into the ERP until a person approves it. How it gets in is set up with you: keyed by a person with the draft beside them, or an import your ERP already supports. The ERP stays the system of record.
Sending to buyers, carriers and packersNever without a personEvery email it writes waits for a person, who reads it and sends it.
The record
Where every number came fromAlways shownClick any value and see the page it was read from. What it cannot read stays blank for a person.
A record of every check, approval and sendKeptWho approved what, when, and why a check was overridden.
Agreement
NDAOn every engagementIt covers what you share with us, starting with the demo.

It doesn't write to your ERP on its own.

The boundary

What it reads, what it drafts, and where it stops.

Reads

Reads the paperwork you forward or drop in a shared folder.

  • Email attachments
  • Shared folders
  • Portal exports
  • ERP and spreadsheet exports
  • Photos and scans someone forwards
  • Booking confirmations
  • Shipping instructions
  • Invoices
  • Packing lists
  • Certificates
  • Bills of lading
  • Purchase orders
  • Remittances
  • Freight bills
  • Cold storage bills
  • Inspection bills

Drafts

Each one lands in a queue a person approves.

  • The request for a missing document
  • The correction to the carrier
  • The reply to the buyer
  • The credit memo
  • The sales order from a PO nobody keyed
  • The dispute

Never touches

These stay with your team.

  • Your money
  • Your ERP, on its own
  • Your buyer's inbox
  • USDA or carrier submissions. It prepares them, you submit them.
Who approves what

It prepares the decision. A person makes it.

What TrueFlo preparesWho approvesWhere it lands
Shipping desk
CompareThe mismatch between two documents, with both pages side by sideDocumentation coordinatorThe shipment file, and the corrected document goes out
RequestA request for a missing certificate, with the shipment, the cutoff and what is missingShipping coordinatorWaits for a person to press send
CheckA booking that disagrees with your commodity rule, with the rule and both sourcesLogisticsA drafted correction to the carrier, waiting for a person
Order desk
DraftA sales order drafted from a buyer's PO nobody keyedSales supportThe ERP, after a person approves it
CompareThe invoice that bills more than was loaded, with both documentsSales supportCorrected before it goes out, after a person approves
Finance desk
GatherA short-pay with the bill of lading, the temperature record and the proof of delivery pulled togetherAccounts receivableA drafted reply to the buyer, or a credit memo for approval
FlagA freight bill that is off its quote or rate confirmation, with the differenceAccounts payableHeld for a person to review
Trust

Every number comes from a page you can click.

Your rulesIn your words
  • Peaches ship at 0.5 °C. Flag any booking that says otherwise.
  • Cartons on the packing list and the invoice must match.
  • No entry is filed until the phyto is on file.
  • Prices come from this week's sheet.
  • Deductions under $100 are let go.

Example rules. We write them down with your team, in your words.

  • 01

    What it can't read stays blank.

    Click any value and see the page it came from. A page it can't read goes to a person, never a guess.

  • 02

    A person approves every fix.

    Nothing goes into your system or out to a buyer or carrier until someone on your team says so.

  • 03

    Your rules, written down.

    The documents each destination needs, the set point per commodity, the price sheet. Written once, checked every time, changed only when you say so.

  • 04

    Built at your desk.

    We sit with the people who do the work and set up each check on your own documents, shown on a normal week's files before your team relies on it.

Bring your security questions and the person who asks them.

Thirty minutes with our team, and every answer in writing afterwards.

TrueFlo demo30 min · with the TrueFlo team

Bring: your security questions and the person who asks them

Book a demo

Times in Pacific time

Book 30 minutes and bring one shipment that went wrong. We'll walk the paperwork with you and show you what would have caught it.

Questions

Questions we get before anyone shares a document.

Something else? Write to zach@trueflo.net.

Will it write to my ERP?

Not on its own. A person reviews each entry and approves it, then keys it with the draft beside them or drops it into an import your ERP already supports. The ERP stays the system of record.

Will it send to my buyer on its own?

No. Every email it writes waits for a person on your team, who reads it and presses send.

Can I revoke its access?

Yes. It runs on access you grant, and you can take that access back.

What if it gets something wrong?

Sometimes it will. It can misread a page. That's why the page is right next to every number, and the other documents check it. If something gets past it, you'll see which check missed it, and that check gets added.