A Carrier Network Is Not a Rate Card: Absorbing a Surcharge Season Without Re-platforming
In our previous article we went through the 2026 surcharge calendar and the end of the UPS and FedEx duopoly, and ended with four things the retailers who are ready for this peak seem to have done: modelled the effective cost rather than the headline, made the alternative carriers real options before Black Friday, decided in advance which parcels move and which do not, and kept the customer promise the same whoever carries the parcel. This post is about how a merchant on Carriyo actually does those four things, and why we think the answer has less to do with which carriers you have than with what sits around them.
We will keep to what is in the product today and documented publicly. The links are at the end.
The difference between a rate card and a network
A rate card is a list of prices for one carrier. When UPS moves its residential fee from $0.50 to $0.75 on 22 November, the rate card changes and the merchant's cost changes with it, and if the merchant's shipping setup amounts to "residential goes to UPS", there is nothing in between the two. Every surcharge in that article goes straight to cost per order.
A network, in the sense we mean it, is different in two ways. The first is that there is more than one price for a given parcel, because more than one carrier can carry it. The second is that something in between the order and the label is comparing those prices, checking that the carrier can actually take the parcel today, and choosing. When the fee tables change, that layer changes its decisions rather than just passing the cost through. That layer, more than the number of carriers connected to it, is what we think a merchant is really buying when they buy a carrier network, and it is the part that takes years to build well, because it has to know how each carrier behaves when things go wrong, not only what it charges when things go right.
Carriyo connects 130+ carriers through a single integration. UPS, FedEx, USPS and Amazon Shipping are on that list, and so are regional and alternative carriers across the markets we serve. An individual merchant only ever needs a handful of them, though, so the count is evidence of the know-how encoded around the connectors rather than the point in itself. What follows is that know-how as it applies to a surcharge season.
Knowing the cost of every option before you book
The first of those four decisions was to model the effective cost rather than the headline, and on Carriyo that starts with two ways of knowing what a shipment will cost with each carrier before it is booked.
The first is live rates. For carriers that expose a rates API, a merchant can switch on the Carrier Shipping Rates option and Carriyo calls the carrier's rates endpoint in real time when a shipment is being created or estimated. The number that comes back is the carrier's own quote for that parcel on that date, so the comparison runs on what the carrier is quoting at the time rather than on a rate card loaded months earlier.
The second is costing profiles, which are the merchant's own contract expressed as rules. A costing profile can carry a fixed cost per shipment or an incremental cost by gross weight tier, in a chosen currency and with tax, with cash-on-delivery surcharges as a fixed fee or a percentage. What matters for this season is that each costing rule can be restricted to a date range, with the "apply to a period" setting, and to conditions on drop-off geography, service level, weight range or custom attributes, with a default cost when nothing matches and a priority order between rules. That is enough to hold the peak-period version of a carrier contract alongside the standard one, dated to match the surcharge windows in that calendar, so that the cost Carriyo sees on 22 November is different from the one it saw on 21 November without anyone editing anything on the day. Costing profiles also serve as the fallback when live rates are switched off or the carrier does not offer them.
Either way, the merchant can see the answer. The Get Shipping Rates action on a draft shipment lists the rate for every configured carrier account side by side, and Estimate Shipping Cost, in the dashboard or through the API, gives the estimate with its breakdown before booking. The Calculate Shipment Cost guide covers the same check for a new or draft shipment in the dashboard, from the carrier's API or from a costing profile. So "what does this parcel cost with each carrier this week" is a question the platform answers rather than a spreadsheet exercise.
Letting the rules move the volume
The second and third decisions, making the alternatives real options and deciding in advance what moves, are what shipping rules are for.
When a shipment is created without a carrier specified, Carriyo's rule engine evaluates the shipping rules for that merchant, direction and country in priority order. A rule's conditions can be set on native and custom attributes of the shipment, so "lightweight, long-zone, non-urgent, residential" is a condition set rather than a judgement call. When a rule matches, the account it points to is checked for eligibility before anything is booked: the account has to be active, authorised for the merchant, covering the destination under its network profile, and within its capacity thresholds. If it fails any of those, the engine tries the next matching rule, and if nothing eligible is left the shipment errors immediately with the reason attributed to Carriyo rather than to a carrier, so the operations team sees it straight away.
Two of the rule actions matter most in a surcharge season. Cheapest assigns the shipment to the carrier account with the lowest shipping cost, using the live rates or costing profiles described above, which means that when the fee tables change on a given date the decision changes with them. Round Robin distributes shipments across accounts by percentage quota, which is the simplest way to give an alternative carrier a defined share of eligible volume during October so that it has been run on live orders before Black Friday. Rules can also carry a daily assignment limit and a schedule, so a rule only applies within a time window on the days you choose.
Capacity profiles sit alongside the rules. A capacity profile caps how many shipments the rules can route to one or more carrier accounts, either as a daily booking capacity that resets at a set time or as an in-flight capacity on open shipments, and when the cap is reached the rules skip those accounts until the count drops. Profiles can apply to forward shipments, reverse shipments or both, and conditions such as drop-off geography let a merchant cap international volume while leaving domestic uncapped. One use of this in the coming weeks is fairly obvious. UPS and FedEx both tie their volume-based demand surcharges to a customer's baseline activity, so a merchant who knows their baseline can cap daily volume to that account and let the overflow route to the next rule. It is worth saying that capacity only constrains automated selection; a shipment assigned to a carrier by hand, or with an explicit carrier in the API call, bypasses both the rules and the caps.
When a booking does fail, the shipment can be reprocessed with edits or reassigned to a different account, and reprocessing without naming an account lets the rules pick again. Carrier account health is visible in the same place. Carriyo tracks whether shipments are being assigned to an account, whether its open shipments have received a status update in the last 48 hours and whether any bookings have outstanding errors, and marks the account healthy, in trouble, idle or inactive accordingly, so a carrier that is quietly falling behind in the second week of December is caught before the customers feel it.
Keeping the promise the same whoever carries the parcel
The fourth decision was to keep the customer experience independent of the carrier, and this is the part of a network that is hardest to see and hardest to build.
Every carrier reports status in its own vocabulary. Carriyo translates each carrier event into one canonical set of shipment statuses, documented in the status codes reference, so a merchant's tracking page, notifications, reports and downstream systems all work against one model regardless of which carrier produced the event. Where the carrier supports real-time callbacks, updates arrive in seconds; where it does not, Carriyo refreshes proactively on a schedule that is hourly in a shipment's first week and daily after that, for up to 60 days. Each shipment carries a map of key milestones, recording the first time it reached each status, and webhooks push the full updated shipment to the merchant's own systems on every event.
The practical result is that moving a share of residential volume from one carrier to another in November does not change what the customer sees, because the tracking page, the estimated delivery date and the notifications are Carriyo's, built on the normalised status rather than on any one carrier's feed. That is also what makes the reporting honest. The carrier performance report gives SLAs, exceptions and transit times per carrier on the same definitions, with service level performance, transit time, failed delivery and shipment ageing reports alongside it and a settlement report for carrier invoicing data, so a merchant can tell after the first fortnight whether the cheaper carrier was in fact slower or less reliable, and adjust the rules rather than argue about it. Over time that becomes the merchant's own data asset: which carrier is actually cheapest and most reliable for which lane, at which point in the season, on their own parcels rather than on an industry average.
Three ways to run it
Like every capability on Carriyo, the shipping layer can be operated in three modes, and during peak most merchants use all three.
The traditional mode is the dashboard, where the operations team compares rates on a draft shipment, assigns or reassigns carriers, resolves errors and watches account health. The automated mode is everything described above: costing profiles dated to the surcharge windows, shipping rules with Cheapest and Round Robin actions, capacity caps and schedules, all running on every shipment with nobody in the loop. The third mode is AI agents, through Carriyo's native MCP layer. The shipment tools let an agent create, edit, book, schedule, cancel, reassign and label shipments; the report tools give it carrier performance, SLA compliance, transit time and failed delivery analysis; the automation rules tools are read-only and exist, in the documentation's own words, for "an agent diagnosing why a shipment was routed the way it was"; and the system log tools let it inspect the carrier interactions behind an error. An agent acts with the permissions and merchant scope of the dashboard user who authorised it. A merchant could, for example, have an agent review each morning's errored shipments, reassign the ones where a second carrier is eligible, and report which rule sent them to the failing account in the first place.
Why this is the de-risked way through a surcharge season
There is nothing in this post that a strong engineering team could not build, and a merchant could certainly integrate three or four carriers on their own. What is hard, and what takes longer than the weeks left before Black Friday, is the part underneath: an eligibility and fall-through model that already knows how each carrier fails, cost data that can be dated and compared across carriers, capacity logic that respects a surcharge baseline, status normalisation across every carrier you might add next year, and reporting that measures them all the same way. Carriyo's version of that has been shaped by the delivery data accumulated across 100+ brands and enterprise customers, $5B in GMV and shipments spanning 200 countries. The modular point matters too. A merchant can adopt the shipping layer on its own, keep its existing order and warehouse systems, and add the rest of the platform when it becomes useful, and the shipping data it accumulates in the meantime is what the rest of the platform, and any agent it later runs, will stand on.
If you are at DELIVER America in Las Vegas on 7 and 8 October, we would be glad to sit down with your carrier mix and this year's fee tables and work out what should move. Otherwise, get in touch with our team at carriyo.com/contact. The shipping documentation is at carriyo.com/docs/platform/shipping.
Carriyo is The Intelligent Commerce Platform, from checkout to doorstep.
---
Sources
1. Carriyo. Shipping overview and booking flow documentation. https://carriyo.com/docs/platform/shipping/ and https://carriyo.com/docs/platform/shipping/booking-flow/ 2. Carriyo. Tracking documentation. https://carriyo.com/docs/platform/shipping/tracking/ 3. Carriyo. Shipment status codes reference. https://carriyo.com/docs/reference/status-codes/ 4. Carriyo. Automation guide: create a shipping rule. https://carriyo.com/docs/guides/automation/create-a-shipping-rule/ 5. Carriyo. Carriers guides: set up costing profiles; set up capacity profiles; monitor carrier account health. https://carriyo.com/docs/guides/carriers/set-up-costing-profiles/ ; https://carriyo.com/docs/guides/carriers/set-up-capacity-profiles/ ; https://carriyo.com/docs/guides/carriers/account-health/ 6. Carriyo. Shipping guides: get shipping rates; estimate shipping cost; calculate shipment cost. https://carriyo.com/docs/guides/shipping/get-shipping-rates/ ; https://carriyo.com/docs/guides/shipping/estimate-shipping-cost/ ; https://carriyo.com/docs/guides/shipping/calculate-shipment-cost/ 7. Carriyo. Recipe: fix or reassign a shipment. https://carriyo.com/docs/recipes/shipping/fix-or-reassign-shipment/ 8. Carriyo. Reports guide. https://carriyo.com/docs/guides/reports/ 9. Carriyo. MCP server documentation and tools catalog. https://carriyo.com/docs/mcp/ and https://carriyo.com/docs/mcp/tools/ 10. Carriyo. Carriers. https://carriyo.com/carriers 11. Supply Chain Dive. "Amazon Shipping readies 2026 holiday delivery surcharges" (UPS and FedEx volume-based surcharges tied to baseline activity), 3 September 2026. https://www.supplychaindive.com/news/amazon-shipping-readies-2026-holiday-delivery-surcharges/829550/ 12. Carriyo. "The Most Expensive Peak Yet, and the First Without a Duopoly" (Carriyo blog, October 2026). https://carriyo.com/blog/expensive-peak-first-without-duopoly-2026-10-01/ 13. Carriyo. "Carriyo's MCP Server Turns AI Agents into Operators" (Carriyo blog, May 2026). https://carriyo.com/blog/carriyos-mcp-server-turns-ai-2026-05-23/