What Breaks When Every RFQ Response Starts From Scratch

Each time a new RFQ lands in the inbox, someone on your team opens a blank spreadsheet — or last month's quote, which was itself copied from the one before — and starts filling in numbers. Freight rate from the forwarder email. Duty rate from memory, or a quick search. Margin on top, adjusted by feel. Twenty minutes later, another one-off response goes out.

Do this fifty times and you have fifty different formats, fifty different assumptions, and a margin profile that's impossible to audit. That's not a process. It's fifty individual decisions disguised as one.

The Real Cost Isn't the Time — It's the Drift

The wasted time is annoying. But the deeper problem is that bespoke quoting creates invisible drift between what you quoted and what you invoiced.

Freight rates get updated mid-month; the quote you sent on the 3rd used last month's rate. Your estimator applied a 12% duty rate to a product that should be 5% — an honest mistake on a fiddly HS code. The FX assumption baked into the quote was 1.92 AUD/GBP; by the time the shipment moved it was 1.84. None of these errors triggered a flag. The invoice just came in lower than expected, and someone had to explain the gap.

That kind of erosion is exactly what the Quote Margin Protector is designed to surface — but a tool only catches drift you feed into it. If your underlying quoting process is unstructured, the inputs are unreliable before you even get to margin analysis.

What "Standardised" Actually Means in an Export Context

Standardising RFQ responses isn't about forcing everyone to use the same font on a PDF. It means deciding, once, what goes into a quote — and making the system enforce that, not a checklist on the wall.

A standardised export quote should capture:

• Origin and destination with port-level specificity (not just "China to UK" but "Yantian to Felixstowe")
• Chargeable weight or CBM calculated the same way every time, using the same volumetric divisor for the freight mode
• Freight cost pulled from a rate card or forwarder integration, not typed from an email
• Duty and tax estimate tied to a confirmed HS code, not a best guess
• Lead time broken into segments: production, transit, customs clearance buffer
• Validity period and the FX rate or buffer used

When those six things are captured consistently, you can compare quotes across lanes, spot where margin is being given away, and hand off a quote to ops without a debrief call.

Without structure, you can't even run a retrospective. You can't ask "why did our margins on Southeast Asia lanes drop 3 points this quarter" because every quote is in a different format, some in email threads.

Where the Breakdown Happens at Volume

A small freight forwarding desk — say, two ops people handling twenty shipments a month — can paper over the gaps with tribal knowledge. One person knows that the FCL rate from Shanghai dropped in March. The other knows the duty rate on your top product line. When they leave, that knowledge leaves with them.

Scale that to fifty shipments, three ops people, two freight forwarders, and a sales team that's quoting directly to customers without checking with ops first — and the cracks become structural.

The most common failure modes we see in export quoting operations:

1. Rate lag. Freight rates are updated by forwarders weekly or even daily during volatile periods. A team that keys rates manually is almost always quoting on stale numbers.

2. HS code inconsistency. The same product gets classified differently by different team members. Over twelve months, this produces a mess that's nearly impossible to reconcile — and HMRC or the ABF won't accept "different people had different views" as a defence. See the broader picture of how this feeds into document-level risk in Why We Kept Humans in the Export Document Review Loop.

3. Forwarder dependency. When your quote is only as good as the response you get from the forwarder, you're at the mercy of their turnaround time. That gap is real and measurable — the Quote Turnaround Gap piece covers how it plays out on the customer side.

4. No audit trail. When a dispute arises — and it will — there's no clean record of what was quoted, on what assumptions, at what rate. The email chain becomes the legal record.

What a System Does About It

The goal of a quoting system isn't to remove human judgement. It's to get the repetitive, lookupable inputs out of people's heads and into a structured data store, so humans can spend time on the decisions that actually require them.

That means:

Rate cards that update in one place. Whether you're pulling from a forwarder API, a manually maintained tariff table, or a combination, the rate a quoting system uses should come from a single source — not from individual emails saved in different people's inboxes.

HS code library with product linkage. Assign HS codes to your product catalogue once, with a review date. Every quote that includes that product pulls the same code. Changes are made centrally and logged.

Calculation templates by freight mode. Air freight uses a different volumetric divisor than sea freight. A system enforces the right calculation automatically based on the selected mode. Manual quoting relies on people remembering which divisor to apply — they don't, consistently.

Quote outputs in a fixed schema. Whatever format you use externally, the data underneath should be structured the same way every time. That's what makes it possible to run a margin report across 200 quotes six months later.

None of this requires a bespoke platform from day one. A well-structured spreadsheet with locked input fields and a product/HS code lookup table will outperform a free-form email process by a wide margin. But spreadsheets cap out fast — once you're coordinating across forwarders, lanes and customer types, the maintenance burden of keeping the spreadsheet accurate usually exceeds the time you saved building it.

That's the point at which most ops teams we talk to start thinking about commissioning something. If you're at that stage, the commissioning guide sets out what you need to specify before you brief a developer — it's worth working through before you start talking to anyone.

Build vs Configure vs Buy

The honest answer to "what system should we use" depends on where your volume and complexity actually sit.

For a team doing under 30 shipments a month across two or three lanes, a structured rate-card spreadsheet with a fixed quote template will handle most of the drift problem. The investment is a day's work to build, not a software project.

For a team doing 50–200 shipments across multiple origins, product lines and forwarders, you're in territory where a configured platform — something like a trade ops module in an ERP, or a purpose-built quoting tool — starts to pay back. The maintenance cost of the spreadsheet version exceeds its value at this point.

Above 200 shipments, or where you need customer-facing portal access, API connections to forwarder rate feeds, or audit trails for HMRC/ABF purposes, you're in custom build or heavily configured SaaS territory. The calculation at that point isn't "can we afford to build it" — it's "what is the drift costing us that we're not measuring."

The comparison below is a rough guide, not a prescription. Your numbers will differ.

The Standardisation Work That Has to Happen First

One thing that catches teams out: building a system before doing the underlying data work. A quoting platform is only as accurate as the rate cards, HS codes and product data you feed into it.

Before you commission anything, you need:

• A confirmed HS code for every product in your catalogue (not "we usually use X")
• A rate card by freight mode and lane, with a named update process and owner
• A decision on how you handle FX — fixed buffer, daily rate, or quoted-at-time
• A definition of what "quote validity" means for your business and which inputs drive it

If those four things are in a spreadsheet and maintained by one person, that's fine — the system can be built around them. If they're in people's heads, the first job is to extract them before anything else.

That extraction exercise is usually where the real standardisation work happens. The software is the easy part.

Useful tool

Try Samvara's Import/Export Quote-Time Estimator — Hours, cost and capacity from slow quotes.