How Easyship pricing actually works

Read an Easyship statement carefully and every line resolves into one of two layers. The first is the subscription layer: a monthly tier that decides how many shipments you may create, how many teammates can log in, and which features are switched on for your account. The second is the postage layer: what the couriers charge for the labels themselves, quoted through Easyship's negotiated rates or through courier accounts you connected yourself. The two layers move independently — you can have an expensive plan month with cheap postage, or a cheap plan month wrecked by one heavy international parcel — and confusion between them is where most surprise comes from.

The layers also fail differently. Postage scales with what you actually shipped, which feels fair even when it is large. The subscription layer scales with what you committed to shipping, which is a forecast — and a wrong forecast costs money in both directions. Undersize the plan and the quota mechanics below kick in; oversize it and every quiet month subsidises capacity you never used. Where each platform earns inside the postage layer is the reseller-margin story, and that explainer lives on how does Pirate Ship make money — the economics are the same across the category, ours included.

Quota is the visible meter; feature gating is the quiet one. Across the tiers, capability is distributed the way subscription software always distributes it: the entry tier proves the product works, and the things an operation eventually leans on — automation rules, richer analytics, branding controls, more seats, certain integrations — sit one or two tiers up. The individual assignments get reshuffled between pricing revisions, which is why this page describes the pattern and leaves the current feature matrix to Easyship's own pricing page.

The pattern has a cost the matrix never shows: a feature gate converts a workflow decision into a billing decision. Wanting to automate a repetitive step, or give a packer their own login, becomes a question about the monthly bill — and because upgrading re-prices the whole account, the feature you wanted arrives bundled with a higher fee on everything else. It is worth naming that the gate is a pricing instrument, not an engineering constraint; the software could do the thing on every tier, and the tier sheet is what says it may not.

Now put the same two months through GoatLabels, where the subscription layer does not exist. The statement is one column: top-ups in, labels out. The forty-parcel seller's statement shows forty debits, each the all-in price that was quoted before purchase. The four-hundred-parcel seller's statement shows four hundred of them, and not one line anywhere records a tier, a cap, a seat, or an overage — because the only meter on the account is postage itself. Void a label and the credit appears in the same column, spendable at once; the mechanics of that are on voiding a shipping label.

Two honest footnotes belong on any wallet statement. First, a carrier billing adjustment — a reweigh or remeasure after shipping — posts as its own ledger entry, and if one ever exceeds the wallet balance, a card on file covers the difference; the wallet is the default rail, not a hard ceiling. Second, we earn the same way every postage reseller earns: inside the label price, not beside it. What the model removes is not our margin — it is the forecast. Nothing on a wallet statement required you to predict your month in advance, and that is the entire difference this page has been mapping. The plan-free model in full detail is on the pricing page.