Field Note

How We Got Our Shopify Carrier Rates Under 500 ms

Built for Shopify requires a carrier-rate endpoint to answer in under 500 ms at the 95th percentile. Ours failed, then passed some days, then passed every day. Here is what we changed at each stage, what each stage cost us, and the numbers.

How We Got Our Shopify Carrier Rates Fast

Built for Shopify has a hard requirement for delivery apps. At checkout, Shopify calls carrier-rate endpoints and asks “what do you want to charge to ship this cart to that address”. If your app provides a carrier-rate endpoint it has to answer in under 500 milliseconds for 95% of calls, measured by Shopify from Shopify’s own cloud, over a rolling 28 days. Come in slower than 500ms and you won’t qualify for BFS.

Getcho’s carrier-rate endpoint is fast, plenty fast to qualify for BFS. This post talks about the engineering measures we’ve taken to make it quick. Because not only are fast rates eligible for BFS - they are also correlated with conversion rate. Every millisecond a customer stares at a loading cart is one they might abandon checkout altogether.

Shopify Partner dashboard showing Getcho's carrier rate endpoint at 419 ms, marked GOOD, with a 28-day chart of daily response time staying under the 500 ms line

One thing to understand about that chart before anything else: Shopify measures from its cloud to ours and back. Most of that time is the network hop. Everything else - compute, inventory lookups, geocoding - adds to the request time, slowing the p95 lookup speed.

Rudimentary: Checking Shopify Inventory Within the Request

What does a Shopify Carrier Rate endpoint need to know? Essentially the origin and destination for each product in the cart. Ideally that’s a single origin (the shipping location) and a single destination (the delivery address). Note: with split carts, a single order can come from multiple locations.

Getcho has an additional need: to know if there are other locations that could fill an order. Shopify sends an assigned location based on order routing rules, but that location might not be the closest one. So we need to also check the inventory for each product in the cart within this one request.

Therefore, the most basic way to calculate rates is to run through each product and:

  1. Call the Shopify Admin API to check whether the items in the cart were in stock at the location we’d deliver from.
  2. Price the cart.
  3. Log the cart so we can track conversion rates
  4. Return rates.

That is several network calls on the hot path before the customer sees a shipping option. On a good day it took 500 ms; on a bad day almost a second. Any one of those services being slow, cold, or briefly unavailable meant a slow or missing rate. That would fail the bar outright.

Level 2: Checking and Caching Inventory Ahead of Time

We kept the backend but stopped letting it touch Shopify during the request. The key piece is the carts/update webhook.

Shopify fires carts/update every time a shopper adds, removes, or changes a line in the cart, seconds to minutes before they reach the shipping step. That is a head start, and we used it to do the slow work early. The webhook handler does almost nothing on its own request: make sure the request is coming from Shopify, pull the relevant product IDs, and kick off a job that fetches inventory levels for those variants from the Shopify API and writes them into Redis with a one-hour TTL (plus a variant-to-inventory-item map with a 24-hour TTL so later warms skip a lookup). carts/create does the same for a brand-new cart.

So when the CarrierService callback arrived, the rate handler read inventory straight from Redis and only fell back to the live fetch if a key was missing or expired.

Two lanes. Top lane, on the request and timed by Shopify under 500 ms: Shopify asks for a rate, we read stock from Redis in about a millisecond, price the cart, and return rates. Bottom lane, in the background and not timed: the carts/update webhook fires when the shopper edits the cart, we call the Shopify Admin API for stock levels, and write the result to Redis for one hour. A dashed line links the Redis write to the Redis read.

This got cache hits down to 10–50 ms. It fixed the median. It did not fix the tail. Cache misses and cold starts on a shared API still landed in the 95th percentile, and the 95th percentile is the only number Shopify looks at. This improved our average by 70ms.

Current Approach: Blazing Fast Cloud Functions, Data in Memory

The version that works has almost nothing in it. Each merchant gets its own Google Cloud Function located physically close to the cloud region Shopify calls from. It has minimum instances set to one so it never cold-starts. The zip allowlist, price table, SKU eligibility, and cutoff times are data inside the function. There is no database, no Redis, and no geocoder on the request. If anything goes wrong, the function returns 200 {"rates": []} so Shopify gets an answer rather than a timeout.

At launch we measured 3 ms at the median and 45 ms at the 90th percentile inside the function.

The cost: we update the function constantly

Removing every network call from the request path means the function has no way to learn that anything changed. Inventory, prices, zip coverage, promotions — all of it is data inside the function, and all of it goes stale the moment the real world moves. Keeping it current is now an ongoing job, and it is a different job for each merchant.

One merchant, one day. A top timeline shows dozens of inventory changes we are notified about; four of them, where a SKU went out of stock or back in stock, are highlighted. A bottom timeline shows the rate function being republished only at those four moments.

So the honest description of stage 3 is: the request is fast because all of the work is done ahead of time, off the request. For a rate table that changes a few times a year that is fine. For inventory that changes every day it means a recurring scan-and-redeploy, and a window between scans where the function is quoting against stale stock.

Summary

  • Don’t make network calls inside the CarrierService callback. Load what you need ahead of time.
  • Keep at least one instance warm so the first request after idle isn’t slow.
  • Host in the same cloud region Shopify calls from (us-central1).
  • On any error, return 200 {"rates": []} rather than letting the request time out.
  • Budget for keeping the baked-in data current. That is where the work went, not away.

If you’re building a carrier-service app and want to compare notes, we’re happy to — get in touch.

← Back to the blog

See where you can save.

A 20-minute call to set your cutoffs, radius and prices. Then we run a few test orders with you before it goes live.

Book a demo

From our customers

Brands that move with Getcho.

Getcho crushed the busy season, we had no issues. The prior year was a nightmare.

Eataly Vino

Frankie Nunez

Category Manager · Eataly Vino

Alex Weir

Alex Weir

Customer Experience, Strategy & Operations · Parsel

We used to waste hours investigating shipment drop offs and inspecting proof of delivery photos. Now Getcho catches and fixes issues before they become a headache.

Richard Hurley

Richard Hurley

CEO · Highline Commerce

Getcho has solved not only the reliability, but also the visibility into costs, and most importantly a trusted customer experience — serving some of our biggest customers like Coca-Cola and Delta.

What business customers are saying

And their customers.

Join the best businesses in the world and start using Getcho to orchestrate all your local deliveries.

Operational Impact

Caught every time. Fixed most times. Paid the rest.

Every delivery, audited

We catch all of them. Every pickup and drop is scored against the order, the address and the notes — nothing is sampled and nothing is skipped.

0%
Caught and fixed in flight

Most problems get solved while the package is still moving — the driver redirected, the wrong door corrected, the stall called in. Your customer never finds out there was one.

0 in 3
Claims we file and win

When a delivery cannot be saved, we file the claim with the evidence already attached and manage it to payout. Every carrier in one queue, filed before your customer complains.

0%

FAQ

Questions, answered

Can't find what you need? Send us a delivery and we'll quote it, or email the team.

What is Getcho?

Getcho ("get-cho") runs shipping and delivery for brands and 3PLs at every location. Any store or warehouse can fulfill: Getcho prices each order across carriers and local couriers, dispatches it through partners or your own drivers, and watches it to the door. Checkout offers live rates, same-day delivery and pickup. Stock moves between locations. Failed deliveries are caught and claimed.

Can my stores ship online orders?

Yes. Getcho lets any location fulfill, not only a central warehouse. An order can ship from the store holding stock — with a parcel label for standard shipping, or with a local delivery partner when the customer is nearby.

Does Getcho show live shipping rates at checkout?

Yes, on Shopify. Live rates replace flat shipping fees at checkout, with box and weight logic so the quote matches what ships. Getcho assigns the cheapest available carrier that meets each order, and nearby customers can also choose same-day delivery or pickup.

How does Getcho scale with my business?

Getcho helps businesses handle high delivery volumes by enabling one manager to oversee many deliveries at once, cutting costs and improving efficiency.

What scale of deliveries can Getcho handle?

Getcho can handle very large delivery volumes. We've successfully processed over 100 orders in under 2 hours for clients. Our AI-powered platform scales to meet your business needs, whether you're doing 10 deliveries a day or 1,000+.

What kind of analytics does Getcho provide?

We provide comprehensive analytics including cart conversion data, customer sentiment analysis, and detailed delivery metrics. These insights help you optimize your delivery operations and improve customer satisfaction.

Does Getcho offer white-label delivery tracking?

Yes, you can custom-brand all tracking experiences to match your business. Your customers get a consistent, branded experience regardless of which fleet delivers their order. Branding is optional and fully configurable. Branded tracking is included on every plan.

Can I manage multiple locations with Getcho?

Yes, Getcho supports multi-location businesses by centralizing delivery management, enabling seamless coordination between stores, warehouses, and customers.

Show all 20 questions
Can I customize delivery zones and hours?

Yes, you can configure custom delivery zones by zip code or radius from your store locations. You can also set specific delivery hours and days to match your business operations.

Does Getcho support bulk order uploads?

Yes, we allow bulk order imports to streamline large-scale delivery scheduling and processing.

What areas does Getcho service?

Getcho dispatches in all 50 US states. Same-day local delivery runs wherever our courier partners operate, and parcel and freight go anywhere in the US. In Canada, Getcho dispatches local delivery. Which options you can offer depends on where your locations are.

What can my business send with Getcho?

Businesses use Getcho to deliver items like retail orders, returns, rental equipment, and more. We support everything from sedans for a few items to box trucks with lift gates and freight—our AI finds the best fleet for each delivery. Contact us if you have special delivery requirements.

Can I track my delivery?

Yes. All deliveries include real-time tracking, audit logs and proof-of-delivery photos. A custom branded tracking link is included on every plan, and premium plans also let multiple recipients receive updates and notifications on orders.

What types of notifications do my customers receive?

Customers receive real-time updates via SMS or email, including order confirmations, delivery tracking, and proof-of-delivery notifications.

What happens if a delivery goes wrong?

We use AI-powered follow-ups to resolve issues quickly, reducing claims and improving customer satisfaction. In cases where issues cannot be resolved immediately, insurance coverage options are available to protect your shipments.

Can Getcho handle returns?

Yes, Getcho supports local returns, including same-day return pickups. We also offer a Shopify integration that streamlines the return process for both regular purchases and rental items.

Does Getcho support round trips?

Yes. Getcho supports same-day round trips, where a single driver completes the delivery and returns to your store on the same run — bringing back signed paperwork, reusable totes and containers, or equipment. A driver can also make a stop and come back to where they started, all in one dispatched job.

Can Getcho handle recurring deliveries?

Yes, we support recurring and subscription-based deliveries. We save customer profiles and delivery preferences, so the experience is consistent—customers don't have to repeat their instructions with each delivery.

Can I schedule a delivery in advance?

Yes, deliveries can be scheduled up to 7 days in advance, ensuring flexibility and convenience.

How quickly can Getcho deliver a package?

Deliveries are typically dispatched within minutes. Multi-signal dispatch sends your order to multiple fleets simultaneously — the first available driver wins the job. Most orders are completed within hours. We also support scheduled, next-day, and recurring deliveries.

Last updated: