Marketplace Shipping Setup: Zones, Methods, Classes, and Fees

Marketplace shipping setup is the grid of zones, methods, logistics classes, and fees that decides what the buyer pays for delivery, and the first decision inside it is who has the right to enter a rate at all.

Shipping setup looks like an afternoon of work. It is, in fact, the layer where somebody else's decision walks straight into your P&L.

If you do not settle who has the right to enter a rate, the seller settles it for you, and the buyer sees the result in the cart.

This article breaks down:

• Who sets the shipping rate?
• Which 3 dimensions does a rate live in?
• Who funds the free shipping threshold?
• What happens when no rate exists?

Key insights

• Who sets the shipping rate also sets your commission base: a seller listing at €940 with €60 of delivery costs you €7.20 an order when delivery sits outside the commission, which is €72,000 a month at 10,000 orders.
• A rate lives in three dimensions: the zone, the method, and the logistics class, and four zones by three methods by six classes is 72 pricing cells, each carrying a price for the first item and one for every additional item.
• Who funds the free shipping threshold follows from where the threshold sits: it belongs to a seller's zone and method pair, so a threshold you announce centrally is your money, at €15 a time and €30,000 a month across 2,000 orders.
• When no rate exists for a zone, nothing breaks: a missing rate reads as a quiet refusal to ship there, which is why the grid needs a default rather than a gap.

Who sets the shipping rate on a marketplace?

A rate can come into existence in four places: you enter it, and nobody changes it; you enter it as a default, and the seller overrides it; the seller sets it inside limits you imposed; the seller sets it freely.

The market default is the last answer. Products in this class let the operator lock a rate: enter €12 and take away the right to edit it.

Practitioners from large rollouts say plainly that the operator usually does not do this, because a locked rate becomes the operator's own commitment toward the seller.

The price of that convenience is countable. Take the canonical cart: goods at €1,000 and a 12% commission, which is €120 for you and €880 for the seller.

Now the same seller lists the product at €940 and adds €60 of shipping. The buyer pays the same amount, but if the delivery charge sits outside the commission base, your commission is 940 × 12% = €112.80, and the seller keeps €887.20.

You lost €7.20 on that order, which is €72,000 a month at 10,000 orders. None of this is fraud.

It is a response to an incentive you set up yourself.

The second effect is worse. A product at €940 looks cheaper in comparisons, so the rate grid starts to steer who wins the product page (the rule that picks the winning offer) and what a buyer comparing prices sees (showing the price).

Whether delivery enters the commission base is settled by split payments and who pays the fees. What matters here is that handing over the rate and excluding it from commission are two decisions that have to be taken together.

You have two switches for this. Mandatory means "the seller has to serve this zone and this method if they have offers in this class". Non-editable means "they will not change the amount".

In the products we know, the lock works in one direction only: the seller will neither raise nor lower the rate, but they can still give free shipping, because their own threshold overrides your grid. You are setting a service floor rather than a ceiling on generosity.

Which 3 dimensions does a shipping rate live in?

1. Zone

A zone is a delivery area, in practice a list of postal codes. In some products, it is a file uploaded without interpretation: ranges and wildcards work only when your own code handles them.

Public commercial data standards do the same thing. They describe the shipping area with code ranges, held separately from the dispatch address.

2. Method

A method is a promise about how delivery happens rather than the name of a company: courier to the door, pickup point, collection in store, digital distribution. You promise the method to the buyer, and the choice of a specific carrier stays with the seller (carriers, labels and tracking).

3. Logistics class

A logistics class groups products with a similar shipping profile. Usually S, M, L, and XL.

It is also what connects a product to a method. A product belongs to exactly one class, and a class that is not assigned to a method hides that method from the buyer.

Those are three axes of one table. Four zones, three methods, and six classes give 4 × 3 × 6 = 72 pricing cells, and every cell carries two numbers: the price for the first item and the price for each additional one.

With 200 sellers holding the right to override, you are talking about 14,400 possible rates.

Why does a logistics class miss what the carrier bills?

This is where configuration most often parts ways with the invoice. Carriers bill the greater of two weights: the actual one and the volumetric one, and the second is volume divided by a fixed divisor.

In metric units, that divisor is most often 5,000 or 6,000 cm³ per kilogram.

A box measuring 60 × 40 × 40 cm is 96,000 cm³. At a divisor of 5,000, that gives 96,000 ÷ 5,000 = 19.2 kg of billable weight, even though the scale shows 4 kg.

If your class grid rests on weight alone, that product sits in class S, the buyer pays the S rate, and the carrier invoices you as if for a nineteen-kilogram parcel. The seller usually covers the difference, right up until the day they do the math.

Then they raise the price or disappear.

The second mismatch is on the sales side. A class belongs to the offer and does not change with quantity.

A thousand pairs of socks is still class S: at €12 for the first item and €2 for each additional one, the buyer sees 12 + 999 × 2 = €2,010 for delivering a single pallet. With a €0 surcharge, the same pallet ships for €12.

Both numbers are untrue, and the fix is not a pricing one: a bulk pack has to be a separate offer with a class of its own.

The third mismatch is physical. Practitioners describe it with one picture: a seller assigns class S to a treadmill because that is cheaper, and the buyer is offered a pickup point the treadmill will never fit into.

Goods that need special handling narrow the list of methods for transport reasons.

Liquids, aerosols, battery cells and long items are the usual cases. Whether you are allowed to sell them at all is covered by restricted and prohibited products.

A heuristic that holds up: five to ten classes is enough. Fewer will not reflect real dimensions, and nobody maintains more, because you price every class in every zone and every method.

How do you keep a shipping grid maintainable?

Nobody fills seventy-two cells by hand. You fill in the root, and the levels below take their value from above until they are given one of their own.

Remove a value from a branch, and it goes back to the parent value. You set five numbers instead of seventy-two.

Both switches inherit the same way: set on the zone, they come down to every method and every class beneath it.

The same mechanics run on a second tree: categories. A logistics class comes down to subcategories, products, and offers, and the lowest level wins.

The offer beats the product, the product beats the category, and the category beats its parent.

And here is the sentence the whole section rests on. Every exception to inheritance is a debt somebody has to remember, because an overridden node stops obeying its parent.

Count what that costs. You raise the courier rate in the domestic zone from €15 to €19, because the carrier raised its price list.

Six categories with a rate of their own from two years ago stay at €15. If 3,000 orders a month run through them, you are covering 4 × 3,000 = €12,000 a month.

No report will show it, because the change "went through fine".

Three rules keep this in check: an exception gets an owner, a reason, and a review date; a change higher up shows the list of branches it will not touch; and a tree with more than every tenth node overridden is already a list maintained by hand.

There is a fourth axis on top of that. In some products, a rate is defined per currency, so entering a second country multiplies the whole grid by two.

Who funds the free shipping threshold?

A threshold is not a property of the cart. It is a property of the rate.

It sits on the zone and method pair of one specific seller, and public commercial data standards describe it the same way: a free shipping threshold belongs to the set of rates rather than to the order. Everything else follows from that.

If the seller sets the threshold, the seller funds it, and your role ends at making sure the buyer understands it. The presentation of the threshold is covered by a cart with several sellers.

If you announce a threshold centrally, you are spending somebody else's money until you put something different in writing. The seller's suborder comes to €180 and delivery costs €15.

Your promise of "free delivery over €150" means you owe that seller €15, and at 2,000 such orders that is €30,000 a month out of your margin. The third variant is co-funding in a stated proportion (on a 60/40 split you pay €9 and the seller pays €6), and then there is exactly one condition: a separate line in the settlement rather than a discount melted into the total.

Watch for one behavior you will not see in a demo. In the products we know, the shipping fee is not recalculated when an order shrinks.

The order crossed the threshold; the seller rejected one line; the value fell below the threshold. Delivery stays free.

What happens when no rate exists for a zone?

This warning appears in no feature matrix. A missing rate is not an error.

It is a quiet "we do not ship there".

In the products we know, an offer with no configured fee for its class, its zone, and its method never becomes active. There is no message, no queue, and no task for anyone.

Fees are also recalculated in batches, so "it will show up in a moment" looks exactly like "it will never show up". Outside the platform, it works the same way: sales channels reject a product for which no shipping service matches the destination country.

The arithmetic is simple. You open a fifth zone: six classes times three methods is 18 cells.

You fill in twelve and forget about six. If those classes cover 18% of the catalog, then at 40,000 offers, 7,200 offers do not exist in that zone.

In the report, it reads as weak demand in a new region.

The cure is cheap and almost never switched on. You need two separate states: a default rate for everything you have not priced, and an explicit "we do not ship here".

Public offer description standards have two different fields for this, because the first is a safety net and the second is a decision. A system with one state turns your oversight into commercial policy.

Which 4 regimes can set the shipping rate?

What does the shipping grid change about the rest of your build?

1. The rate grid is an input to offer ranking, so you design the two together

If the winner on the product page is decided by price with delivery included, a seller with cheap shipping wins even with more expensive goods. That is a decision rather than a side effect.

2. Classes and zones are the condition for promising anything in the cart

The list of methods for the whole cart is the intersection of the individual sellers' lists, and the delivery date is a separate layer, alongside the delivery date you promise.

3. A return touches the same number

Whether the buyer gets the delivery cost back, and what happens to the commission charged on it, are settled by who pays for a refund and the commission on a refunded order. Here you settle how large that number is and whose it was.

How do you check the shipping grid with a vendor?

Ask for an operation on screen rather than as a description in a feature table.

1. Remove the value from one node of the fee tree and show which rate the level below inherits, and where you can see that it is inherited.
2. Change the rate at zone level and show the list of branches the change will not touch. The absence of that list is your future debt.
3. List every dimension of a rate: zone, method, class, currency, seller. Each additional one multiplies the grid.
4. Set a rate as non-editable and show the seller panel: can they still give free shipping and set a threshold of their own?
5. Delete the rate for one class in one zone: show what happens to the offers and after how long. Ask whether a state of "we do not ship here" exists that is different from "no rate".
6. Set a co-funded 60/40 threshold and show the line in the seller's settlement. Without that line, the threshold is a promise with no booking behind it.

Which mistakes do operators make about shipping setup?

1. A rate handed to the seller without settling the commission base

The price of the goods travels into the delivery fee, the commission melts away, and the ranking rewards whoever did it first.

2. A grid built out of exceptions instead of inheritance

A carrier increase never reaches the places where somebody once made an exception, and you cover the difference for years with no line in any report.

3. A logistics class derived from weight alone

Light and bulky parcels priced like small ones, while the carrier counts volume. The margin disappears on cardboard rather than on prices.

4. A free shipping threshold announced centrally with no position in the settlement

A promise made out of somebody else's pocket, and the seller finds out about it from the first statement.

5. A missing rate treated as a temporary state

Offers that never became visible, and a report in which that reads as an absence of demand.

What do you still have to settle about your own grid?

This article does not settle the delivery date, or anything that happens after the parcel is dispatched: carriers, labels, and statuses are carriers, labels and tracking. The presentation of the threshold and the progress bar belong to a cart with several sellers, and shipping cost optimization between sellers is something we do not build at all.

This article does not settle questions that look like shipping questions and are legal ones. Whether the buyer gets the delivery cost back is who pays for a refund.

What you have to show before an order is placed is who delivers the buyer's rights. Whether you are allowed to sell goods with special transport requirements is restricted and prohibited products.

The form your terms toward sellers have to take is carried by the rules on decisions about sellers.

This article does not settle the fulfillment model. An operator warehouse, its own carrier network, or collection in store does not change the rate.

And the most important number, the one that appears in no documentation: your real shipping cost per class, taken from carrier invoices, set side by side with the rate you show on the front end. All the numbers above are openly hypothetical.

The arithmetic travels, the values do not. Until you put those two columns next to each other, you do not know whether you are subsidizing shipping or earning more on it than on commission.

Summary: What does a shipping grid really decide?

Who pays for delivery, and how much of the cart your commission sees. The grid itself is three axes and seventy-two cells, which nobody maintains by hand, so it runs on inheritance, and every exception to that inheritance is a silent debt: a rate overridden two years ago keeps its old value when you raise the one above it.

The classes underneath are brackets that the carrier does not share, because carriers bill volumetric weight, and a 60 by 40 by 40 box is nineteen kilograms on the invoice and four on the scale. And the threshold everybody treats as a marketing setting is a property of somebody's rate, which is why announcing one centrally spends the seller's money or yours depending on a sentence nobody wrote down.

Ask a vendor what the buyer sees when a seller has no rate for a zone, and who can override a rate you locked. Building a marketplace where the shipping grid inherits, and every exception carries an owner and a review date?

Talk to us about the build.

Frequently asked questions on marketplace shipping setup

Who should set shipping rates on a marketplace?

Shipping rates can be set in four places, and the market default is the one that costs you most: the seller sets them freely. Locking a rate makes it your own commitment toward the seller, which is why most operators do not.

What has to be decided alongside it is whether delivery enters the commission base, because those two decisions are one.

What is a logistics class on a marketplace?

A logistics class groups products with a similar shipping profile and connects a product to the methods it may travel by. A product belongs to exactly one class, and a class not assigned to a method hides that method from the buyer.

Five to ten classes is the working range: fewer will not reflect real dimensions, and nobody maintains more.

Who pays for free shipping on a marketplace?

Free shipping is paid for by whoever set the threshold. A threshold sitting on a seller's zone and method pair is theirs to fund.

A threshold you announce across the platform is yours, unless a co-funding split is written down and appears as its own line in the settlement rather than as a discount melted into the total.