Loading
Because the tariff is a spreadsheet, and there are three copies of it. Sales quotes from the one on their laptop, operations works to the one on the shared drive, and finance bills from the one in the accounting system.
The difference is found on the invoice, argued about for a fortnight, and usually conceded.
Rate cards live in Books, per client, per currency and per term, each with an effective date. Sales quotes from those, not from a copy, and there is no out-of-date rate available to select.
A rate change in April leaves March's quotes and invoices reading what actually applied then, which is the part that makes an audit uneventful.
It is not a transport management system. It does not plan routes, allocate vehicles or track shipments — it holds the customer, the rate and the commitment beside whatever does.
And it will not enforce a volume commitment. It shows you the gap, with a date, which is the useful part of the conversation.
The accepted quote opens the operational record and the billing schedule from the same lines. Volume commitments are on the record rather than in the contract PDF, so a shortfall is visible during the term rather than at renewal.
Desk sees the account when a delivery exception is raised, including what was actually promised.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, per client and per term, with effective dates so history stays correct.
Through the API — it references operational records rather than duplicating them.
Yes, on the deal, compared against actuals during the term.
Half an hour on your own numbers is usually enough to say whether Flow is the right place to start.