ShipBob Pricing: Build Landed Cost From the Line Items

ShipBob pricing is not a single number

Ask for ShipBob pricing and you’ll get a per-order rate first, because it’s the easiest number to say out loud on a sales call. That rate is not what shows up on your monthly invoice. A 3PL invoice is built from five separate categories — receiving, storage, pick and pack, per-order fulfillment, and surcharges for exceptions — and the per-order rate quoted up front is only one of them. Two providers can quote the same per-order figure and land at meaningfully different monthly totals once storage, kitting and surcharges are added, because the headline number was never the whole story.

Order volume decides how much this gap matters. At a handful of orders a month, the gap between a modelled landed cost and a headline rate is small enough to absorb. At the order volume a $3M-$30M Shopify Plus brand runs, that gap compounds every month, and by the time it shows up clearly on an annual spend review, you’re already locked into a contract term. This article does not quote ShipBob’s specific rates, because published figures change and a number printed here would be stale before you read it. It shows you the line items that make up the bill and how to model your own landed cost per order, so a quote — from ShipBob or anyone else — becomes something you can actually compare instead of something you take on faith.

How ShipBob’s pricing model is structured

Every 3PL, ShipBob included, prices fulfillment as a stack of separate charges rather than one flat fee, because the underlying costs it’s passing through are themselves separate: warehouse labor to receive and put away stock, physical space to store it, labor again to pick and pack it, a shipping label and carrier charge to move it, and exception handling for anything that doesn’t fit the standard flow. Understanding the stack matters because a sales quote can legitimately lead with any one line and still be accurate about that line while leaving the total unclear.

The five categories, in the order they hit your inventory as it moves through the warehouse, are: receiving (getting inventory in), storage (holding it), pick and pack (assembling an order), per-order fulfillment (the base fee to process and ship that order), and surcharges (anything outside the standard case — oversized items, address corrections, peak-season labor premiums, dimensional weight adjustments). A complete quote covers all five with a rate or rate range for each. A quote that only covers the per-order fee is not incomplete by accident — it’s the easiest way to make one provider’s number look lower than a competitor’s without changing what either actually costs you.

Receiving: the line item most quotes leave until page two

Receiving is what a warehouse charges to unload, inspect and shelve an inbound shipment before any of it is available to ship. It’s typically billed per unit or per carton, sometimes with a separate charge if the shipment arrives with a discrepancy — wrong count, damaged units, missing paperwork — that requires manual reconciliation against your purchase order.

Receiving is a one-time cost per inbound shipment, not a recurring one, which is exactly why it’s easy to underweight when comparing monthly totals. A brand restocking once a month absorbs it as a predictable line. A brand restocking weekly from multiple suppliers, or receiving frequent small top-up shipments because of tight cash flow on inventory purchasing, pays that receiving fee far more often, and the aggregate can outweigh what looks like a minor line item on a single invoice. Ask for the receiving rate against a real shipment size and frequency from your own supplier cadence, not a round number quoted in the abstract.

Storage: billed by space and time, not by SKU count

Storage charges for the physical space your inventory occupies while it waits to ship, generally billed by pallet, bin, or cubic footage, per month. It has nothing to do with how many SKUs you carry and everything to do with how much physical volume they take up and how long they sit before selling.

Slow-moving inventory is where this becomes an invisible cost. A SKU with a high sell-through rate barely touches storage, because it turns over fast enough that the space it occupies is billed for a matter of days at a time. A SKU that sells slowly, or a seasonal SKU stocked six months ahead of its selling window, accrues storage charges every month it sits, and those charges are easy to lose inside a total invoice that also includes fast-moving, low-storage-cost products. If your catalogue has a long tail of slow SKUs — a common pattern for a brand that’s expanded its line faster than it’s pruned it — model storage per SKU category, not as one blended number, or you’ll misattribute cost to your fast movers and underprice the slow ones in your own margin math.

Also confirm whether your contract carries a minimum storage or order-volume commitment. Many 3PL contracts include one, billed regardless of actual usage in a given month, which functions as a floor under your monthly invoice even in a genuinely slow month.

Pick and pack: where order complexity changes the price

Pick and pack is the labor to walk the warehouse floor, pull the right SKUs and quantities for an order, and pack them correctly. A single-SKU, single-unit order is the cheapest version of this to fulfil, because it’s one pick and one pack decision. Add items to the order and the labor time — and typically the price — rises with it.

Kitting adds a further layer: when multiple SKUs are combined into one sellable unit, either pre-assembled and held as a kit SKU or assembled at time of pick, the labor to do that assembly is generally billed as an added line rather than folded into the base pick rate. A subscription box brand or a bundle-heavy catalogue should model pick-and-pack cost per order type — single-item, multi-item, kitted — separately, because a blended average across all three will understate the true cost of your most complex order type and overstate the cost of your simplest one. Ask specifically whether kitting is billed per component picked or per finished kit assembled, since the two can produce meaningfully different totals on an order with several components.

Per-order fulfillment: the “headline” rate isn’t the whole order

The per-order fulfillment fee is the base charge to process and ship an order once it’s picked and packed — the number most sales conversations lead with, because it’s the single figure that sounds most like “the price.” It usually does not include the shipping label and carrier charge itself, which is typically passed through separately at the carrier rate for the parcel’s weight, dimensions and destination zone, nor does it necessarily include packaging materials, which some contracts bundle in and others bill apart.

Treat the per-order rate as one line among five, not as “the price.” A quote that leads only with this number, without volunteering the other four, is not lying about the number — it’s letting you assume the number is the total, which is a different thing. Ask directly what the per-order fee does and does not include before you use it in any cost comparison.

Surcharges: the line that moves your total the most at volume

Surcharges cover anything that falls outside the standard pick-and-ship flow, and they’re the line most likely to move your actual invoice further from your modelled one, because they’re triggered by conditions you don’t fully control. Common triggers include oversized or overweight parcels exceeding a carrier’s standard dimensions, address corrections when a customer enters an invalid or incomplete address, dimensional weight adjustments when a package’s volume outweighs its actual physical weight under a carrier’s DIM pricing policy, and peak-season labor premiums applied during a defined high-volume window.

Dimensional weight is worth understanding on its own, because it’s a structural mechanism, not a 3PL-specific fee: major parcel carriers price a shipment by whichever is greater, its actual weight or a calculated weight based on its box dimensions, a policy both FedEx and UPS publish for their own services. A lightweight product in an oversized box can trigger a DIM-weight surcharge that has nothing to do with the 3PL’s own pricing and everything to do with your packaging choice. If your product ships in a box larger than it needs, this is one of the few line items you can reduce directly, by right-sizing packaging, rather than negotiate away.

Ask for a full surcharge schedule with the trigger condition for each one, and ask what share of your specific order profile — average parcel weight and dimensions, return-address-correction rate, whether you sell heavily in a peak season — is likely to hit each trigger. A surcharge schedule you’ve never seen against your own order data is a number you cannot model.

How do you audit a ShipBob invoice against your original quote?

An invoice audit means matching each line on the bill against the rate you were quoted for that specific line, not against a gut sense of whether the total looks reasonable. Pull a few consecutive months of invoices if you have them, and lay each of the five categories out separately: receiving, storage, pick and pack, per-order fulfillment, surcharges. Compare each line’s rate, not just its dollar total, against the written rate card from your contract or onboarding documents, and flag anything that doesn’t match what’s on paper.

Two patterns are worth checking for specifically. The first is a surcharge appearing on orders that don’t obviously meet its trigger condition, an oversized-parcel surcharge on a product you know ships in a standard box, for example. Raise this directly rather than assuming it’s correct, because dimension data is sometimes captured wrong at receiving and never corrected downstream. The second is a storage rate creeping up between billing periods without a matching contract amendment; ask for the rate-change notice clause in your contract and confirm any increase was actually disclosed within it.

Keep your own running count of orders shipped, units received and average storage footprint each month, independent of the 3PL’s own reporting. A gap between your count and the invoice’s stated order count is the fastest way to catch a billing error, and it’s far easier to raise a specific, evidenced question than a vague one about whether a bill “looks right.” Naming the exact figures on both sides gets a faster, more useful answer from an account manager than a general complaint does.

If a discrepancy repeats, escalate it as a pattern rather than a one-off. A single mischarged order is plausibly a mistake somebody can fix in one call. The same type of mischarge appearing across several consecutive invoices is either a system default working against you or a rate that changed without proper notice, and either one is worth a direct, documented conversation with your account manager before your next contract renewal.

How to model your landed cost per order

Landed cost per order is the sum of all five line items, allocated across your actual order volume for a given period, not the per-order rate alone. The method, illustrated with invented numbers to show how the pieces combine — not ShipBob’s actual pricing, and not to be reused elsewhere as if they were real — looks like this.

Say a brand ships a hypothetical 2,000 orders in a month, averages 1.4 items per order, and carries enough inventory to need a certain amount of pallet space that month. Illustrative monthly totals: receiving across that month’s inbound shipments might land at some total dollar figure; storage for that pallet space at another; pick and pack across 2,000 orders, weighted for the items-per-order average, at another; per-order fulfillment fees across all 2,000 orders at another; and surcharges hitting some percentage of those orders at another. Add the five totals and divide by 2,000 orders, and the result is landed cost per order — a single comparable number that reflects your actual SKU mix and order pattern, not a vendor’s headline rate.

Run this model against every quote you collect, using your own order data for the inputs, and ask each provider — ShipBob included — to confirm current rates for all five lines in writing before you compare totals. A vendor’s willingness to quote all five lines against your real order profile, rather than just the per-order rate, is itself useful information about how the relationship will run once you’re a signed customer instead of a prospect.

What does ShipBob cost compared to running fulfillment in-house?

ShipBob cost and in-house fulfillment cost aren’t directly comparable line for line, because in-house fulfillment bundles warehouse lease, equipment, staffing, software and management time into overhead that doesn’t appear as a per-order charge but exists all the same. A fair comparison models your fully loaded in-house cost per order — rent, labor, packaging, software, management time divided by order volume — against a 3PL’s landed cost per order built with the same five-line method, not against ShipBob’s per-order rate alone.

The comparison tends to favour a 3PL below the order volume where a dedicated in-house team and space are hard to keep fully utilised, and tends to favour in-house above the volume where warehouse labor efficiency and negotiated carrier rates outperform a 3PL’s blended pricing. Where that crossover sits is specific to your SKU mix, order volume, and how much of your in-house overhead is fixed versus variable, so treat any generic volume threshold you hear quoted as unverified until you’ve modelled your own.

When does ShipBob’s pricing model stop making sense for a growing brand?

A per-order, line-item pricing model suits a brand whose order volume and SKU mix are still changing, because it scales with actual usage rather than committing to fixed capacity. It stops making sense once your order volume is large and stable enough that negotiated in-house labor and carrier rates would beat a 3PL’s blended per-unit pricing, or once a specific line — storage on a large, stable inventory footprint, most commonly — would be cheaper owned outright than rented monthly.

The pricing model also stops making sense earlier than volume alone would suggest if your SKU mix needs something it doesn’t reward: heavy kitting billed per component when a flat kit rate would serve you better, or a return rate high enough that returns processing becomes a larger line than the per-order fee it’s often compared against. Re-run your landed-cost-per-order model at each contract renewal, against your then-current volume and SKU mix, rather than assuming the rate that made sense at signing still reflects your actual usage a year later.

Modelling landed cost per order instead of comparing headline rates is, at its core, an ops-automation problem: pulling your own order, inventory and SKU data into one place so a vendor quote can be tested against reality rather than taken at face value. That’s the same discipline behind Pointerflow’s ops-automation work — building the data pipeline that turns five separate invoice lines into one number you can actually compare, before you sign, not after the first surprising invoice arrives.