Solutions · Order desk

Every order matched to what was keyed, loaded and billed.

Orders arrive through buyer portals, email, texts and phone calls, and someone keys each one into the ERP or the spreadsheet. TrueFlo reads every order where it lands and checks it against what was entered, the price sheet, the loading report and the invoice. What matches is filed. What doesn't comes to a person with both sides on screen. This desk is set up with you, on your own orders and documents.

This desk protects the money between the order and the invoice: the PO nobody keyed, the price off the sheet and the invoice that bills more than was loaded.

Example. Every company and number here is made up.
The job

Customers order however they like. A text at 5 AM, an email with a list pasted in, a portal PO with their own names for your products. Each one gets keyed into the ERP and priced against the sheet, between calls.

What one Tuesday held $13,682at stake

Across the five orders out of fourteen that didn't match what was keyed, including a $6,608 PO that never got a sales order.

ExampleThe order nobody keyed, worked on made-up data
Capabilities

What TrueFlo does.

01

Orders that don't match.

A daily list of orders where the portal, the ERP, the price sheet, the loading report and the invoice disagree. Keyed twice. Never keyed. Last week's price. The buyer's revision not applied. Billed for more than was loaded.

Tuesday

14 orders from iTrade, Procurant, email and texts

9match
5don't
02

The order nobody keyed.

When a buyer's PO has no sales order behind it, TrueFlo drafts one from the PO, with the customer's wording matched to your product list. Nothing goes into the ERP until a person approves it. Anything it cannot place is flagged, not guessed.

Bayline MarketsCaught
Procurant PO BM-558213no sales order
Sales order drafted, $6,608Draft
  • Broccoli crowns120 cartons
  • Carrots, baby80 cartons
  • Celery96 cartons

Prices match this week's sheet

03

Loaded against ordered, billed against loaded.

The loading report is read when it arrives and compared to the order. The invoice is compared to the loading report before it goes out.

INV-88412Caught
Cauliflower billed252
Bill of lading216
short 36Correction to 216 drafted before it goes out
04

“Where is my order”, answered.

When a buyer asks where an order is, the reply is drafted from the confirmations and tracking you already received, for someone to send.

05

Orders from email and text, drafted.

Where the ERP has no order-entry tool, each email or text order is read, matched to the product list, and drafted as an order. A person checks and approves it. Nothing goes into the ERP on its own.

Example. Every company and number here is made up.

Who approves what

It prepares the decision. A person makes it.

What TrueFlo preparesWho approvesWhere it lands
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

Bring last Tuesday's orders and the invoices that followed.

Thirty minutes with our team on those orders and invoices, and what TrueFlo would have caught.

TrueFlo demo30 min · with the TrueFlo team

Bring: last Tuesday's orders and the invoices that followed

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 about this desk.

Something else? Write to zach@trueflo.net.

Why do orders land in so many places?

Each buyer orders the way it always has. Chains send through their portal, regular buyers email or text the rep, and some still call. All of it gets keyed by hand into one system, between calls. TrueFlo reads each place and matches what arrived to what was keyed.

We already use iTrade's Order Agent. Do we still need this?

Getting the order in is solved. Knowing it matches what loaded and what you billed isn't. TrueFlo checks what got in against what the buyer asked for, the loading report and the invoice.

Does it write orders into Famous?

Not on its own. It drafts the order and a person approves it. How an approved order gets into Famous is set up with you: a person keys it with the draft open beside them, or drops it into an import Famous already supports. It never writes to the Famous database.

Which portals?

Whatever your buyers use. TrueFlo reads the exports and emails your portals already send. It does not connect to the portals directly.

What if it's wrong?

Sometimes it will be, like a person. 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.