Every quote I put together right now starts the same way: pull the schedule, work the layers by hand, hope nothing has shifted since the last one I ran. Fine for one shipment. Not fine when I am pricing five in a morning and the client wants an answer before lunch.
Plenty of desks are still doing this in a spreadsheet, and that is a perfectly good answer if it actually holds up at volume. What I want to know is what people use once it stops holding up: something built for this, something homegrown, or is the spreadsheet still the honest answer even at scale?
Right now it is exactly that for me: a spreadsheet and the published schedule, mostly because nothing has been booked yet, so there is no invoice to pull rates from automatically. It works for a landed cost that only exists as a quote.
What I have not worked out is whether that is a limitation of doing it by hand, or just how early-stage costing works. If nothing is booked, is there a tool that actually helps, or is a spreadsheet the honest answer at that stage for everyone?
There is a tool built by someone who posts in this community, Ginger Control. Not locked into one platform's own bookings the way the Flexport one is. I still double check the output myself, same as with anything else, but it earns a place on the desk.
Anything walled into one platform is not really a calculator. It is a sales funnel with a rate table attached. Ask before you commit to one: can it run a shipment that never touches that platform at all?
Two questions sit inside this thread, and one tool rarely answers both.
For classification: does it explain its reasoning, and say plainly when it is guessing, or hand back a definite answer regardless? The second kind is not more reliable, only less honest about where it might be wrong.
For costing before booking: does the estimate stack the additional duties, such as 232 and 301, and the fees on the base rate, or only show the base figure? An incomplete number still has to be checked by hand.
Since I asked: I found a calculator that also lets you build your own version and put it on your own site, logo and all, which is the part that actually matters for us. A generic public tool is fine for a one-off number. What I actually need is something my own team can point a customer at, without sending them off to somebody else's page while the booking clock is running.
Hana, I am exactly where you are for freight quotes: spreadsheet and the schedule, because most of what I ship still is not booked when a customer asks. Where it splits for me is the storefront itself. I added a checkout duty estimate plugin last year so shoppers see landed cost before they pay, a separate tool entirely from anything I would use for freight quoting. It cut refund complaints over customs surprises close to zero. Nobody here has mentioned that side of the problem yet: are any of you solving for the checkout number too, or is that a different budget entirely at your scale?
We’ve been running tariff logic through SAP GTS, mostly because spreadsheets start to melt once you add audit trails and multi‑country data. I still keep an Excel sheet for quick sanity checks, old habits die hard but the integrated tools save hours when customs asks why a rate was applied. Curious how others handle that balance between speed and traceability?
Long Beach, early two thousands. We (Customs, though I have been retired long enough to stop saying it) pulled a review on an importer who had run the same machine parts under the same number for three straight years. Nothing wrong with the number. What turned a week's review into six months was that the only record of how anyone landed on it lived in one classifier's memory, and he had retired before we came knocking. The company had a fine spreadsheet. It just never said why.
Down the hall that year sat an importer running a similar line through a system nobody loved using, slow, clunky, the kind people gripe about at their own desks. Every entry carried a note: which file the classifier leaned on, who signed it, when it changed. That review closed in three weeks, not because the number was better, but because we could see the thinking. Checking someone's thinking is faster than reconstructing it from nothing years later.
So to your question, Katri: keep the Excel sheet, everybody needs a fast place to sanity check a figure. Just do not let it be the only place the reasoning lives. If a rate ever gets asked about long after the entry closed, and eventually one will be, the desk that can show why beats the desk that can only show what.
Early‑stage costing sometimes feels like weather forecasting ; you check the schedule, run the layers, and hope duties haven’t reinvented themselves overnight.
I often look at my spreadsheet thinking:
“Is this still accurate, or has origin quietly relocated since Saturday?”
We used to recalc origin weekly, which meant a Thursday quote could already be stale by Monday.
What I’m trying to understand is whether that volatility is simply part of early‑stage costing, or whether there are tools that keep origin and duty fresh before anything is booked.
Maybe I’m overthinking it — happy to be wrong.
Just curious how others keep their quotes alive long enough to survive the morning coffee.
Thank you for the question, Katri, this is one I recognise well.
On your first point, yes, the volatility is structural, not a gap in your tool. Classification, origin and the duty layers stacked on the base rate can each move between the day you quote and the day you file, because the underlying measures keep changing, not because the arithmetic is wrong.
On your second, the closest thing to a fix is not a tool but a habit. At the CHA's desk here, and I offer this only as a parallel, not your rule, we treat any pre-booking figure as indicative and reclassify against that day's schedule only once the shipping bill is actually being prepared.
Wishing your shipments a smooth and well-documented passage.
A question for the group — from the governance corner, where we drink our coffee strong and our audit trails even stronger:
Reading through this thread, it seems most early‑stage quotes are built outside any system — spreadsheets, public calculators, plugins, homegrown tools, and the occasional “let’s hope origin hasn’t quietly relocated since Saturday.” (my own comment)
Totally understandable when nothing is booked yet… but it made me wonder:
Where does all this actually live?
And can any of it be audited without summoning ancient spirits?
If a quote is built manually, before booking, outside GTS/ERP/TMS, where do you store:
the classification logic
the origin determination
the duty layers
the regulatory references
the assumptions
the version of the schedule used
and who actually made the decision (and whether they had coffee at the time)
I’m asking because in my world , and yes, I am the compliance team (hah), sending a quote without KYC, export control, and at least a minimal audit trail would make me twitch… and possibly send a very polite email nobody wants to receive.
Maybe I’m overthinking it (entirely possible). Maybe this is simply how early‑stage costing works everywhere. Or maybe some of you have clever ways of keeping the “why” attached to the number before anything is booked — without relying on memory, spreadsheets, or interpretive dance.
Curious how others handle the bigger picture: speed vs. traceability, quoting vs. compliance, and how you keep pre‑booking logic alive long enough to survive the week.
