Try Pro free for 14 days. No card needed.Start free

    Discogs doesn't have a combined-shipping discount — merging orders works nothing like eBay's

    A buyer orders two records in the same week and asks to combine shipping. On eBay that's a setting that auto-applies at checkout. On Discogs there's no such setting at all — just a manual, irreversible "Merge Orders" button, and the combined shipping charge it produces isn't a discount, it's a replacement.

    A buyer on Discogs wins two of your records three days apart and messages asking if you'll combine shipping before they pay. On eBay, that request is usually already handled — combined-shipping discounts apply automatically at checkout once you've set them up, the same way a Shopify store calculates cart-level shipping from your rate rules. Sellers who run all three platforms tend to assume Discogs works the same way. It doesn't. Discogs has no checkout-level combined-shipping setting at all.

    What Discogs gives you instead: Merge Orders

    The only way to combine two Discogs orders is a manual action on the Orders page, under Sell Music: select the checkbox next to each order, then click "Merge Orders." Per Discogs' own help documentation, that action is irreversible — once two orders are merged into one, there's no splitting them back apart. There's no equivalent button on the buyer's side; it's entirely something the seller does, and has to do before anyone pays.

    The eligibility rules that trip people up

    Merging only works under a narrow set of conditions, and missing any one of them means the button won't do anything useful:

    • Both orders have to be from the same buyer. Obvious, but worth
    • stating since it rules out any informal "I'll combine you with another
    • order" arrangement across two different accounts.
    • Both orders have to be unpaid. The moment a buyer pays one of the two,
    • merging is off the table for that order.
    • Both orders have to be in Invoice Sent status. An order still sitting
    • as a pending request, or one that's already moved past Invoice Sent,
    • doesn't qualify.
    • Canceled orders can't be merged, with anything else.

    That unpaid-and-Invoice-Sent window is usually narrow. If a buyer pays quickly after checkout — which Discogs Payments makes fast — there often isn't time to merge before the first order is already paid. Sellers who get combine requests regularly do better holding off on sending a second invoice the moment they see the same buyer's name on another order, rather than invoicing instantly and losing the window.

    The combined charge is a replacement, not a discount

    This is the part that actually changes your numbers. eBay's combined-shipping tool lets you set a specific discount — full price for the first item, a reduced amount for each additional one — and that discount is a number you chose. Merging orders on Discogs doesn't work that way. Discogs applies whichever shipping cost is the first applicable one from your own shipping policy to the merged order — it isn't the sum of the two original shipping charges, and it isn't a number you enter at merge time.

    What that means in practice depends entirely on how your shipping policy is built. Discogs' shipping policies are tiered by weight or item count, with an "and up" option to set a flat rate above a given threshold, and Discogs considers a policy "complete" only if some tier covers every order your shop could generate. If your policy has a tier that actually accounts for two records shipping together, the merge produces a sensible combined rate. If it doesn't — if your tiers only ever anticipated single-item orders — the merged order falls back to whatever tier applies, which may undercharge for the real weight you're about to pack and ship. Check your shipping policy's upper tiers before you rely on merging, not after a merged order ships at a loss.

    It also changes the fee, not just the shipping line

    Discogs' 9% selling fee applies to the item price and the shipping charge together, not the item alone. A merged order that replaces two shipping charges with one lower one doesn't just save your buyer money — it also shrinks the base Discogs takes 9% of. That's a real, if small, upside to merging correctly that has nothing to do with the goodwill of combining shipping in the first place.

    Payment still has to go through Discogs

    One more constraint worth stating plainly: merging doesn't create an opening to settle the combined total outside Discogs. Collecting payment off Discogs' own payment flow — even for a merged order you set up correctly — is fee avoidance under Discogs' terms of service, same as it would be for any single order.

    What to actually do

    • Build at least one shipping-policy tier for multi-item orders,
    • weight- or quantity-based, before you ever get a combine request —
    • merging only helps if the resulting tier reflects reality.
    • Hold the second invoice, not the first, when you see a buyer has
    • another order open with you. Merging requires both orders in Invoice
    • Sent status; sending both immediately doesn't block it, but a buyer who
    • pays fast can close the window before you act.
    • Don't treat "merged" as "discounted." Check what shipping amount the
    • merge actually produced against what two records really cost to pack and
    • post — it's your shipping policy's number, not a negotiated one.

    PalmFlow imports your Discogs orders so they show up alongside eBay and Shopify in one place, but merging itself happens on Discogs' own Orders page — the Discogs side of the integration is import only, so there's nothing to configure in PalmFlow for this. The fee calculator has Discogs' 9% fee math built in if you want to check what a merged order actually nets once the lower shipping charge is factored in. Free plan, 50 items, no card.

    Built for the business you actually run.