Crosslist from WooCommerce to Discogs — FLUF Connect for WordPress Record Shops

If you run a record shop on WooCommerce — the WordPress e-commerce plugin that now accounts for roughly half of all measurable online stores — you already own the hard part: the inventory, the photographs, the descriptions and the prices. What a WordPress store cannot give you is a buyer who is hunting one specific pressing by catalogue number. That buyer is on Discogs, and this page is about getting your WordPress catalogue in front of them without retyping it.

The gap in the WooCommerce ecosystem

WooCommerce is not a small platform. W3Techs currently puts it at 8.1% of all websites, 11.7% of sites running a known content management system, and 48.1% of all e-commerce systems — roughly half the measurable web store market.

Its marketplace connectivity does not reflect that. The extensions listed on WooCommerce.com cover Amazon, eBay, Walmart and Etsy, largely through a single third-party vendor, at prices that start around £247 a year for a single channel. There is no Discogs extension. There is no Depop, Vinted, Poshmark, Grailed, Vestiaire Collective or Mercari extension either. The entire resale and specialist-marketplace category is unserved.

It got worse rather than better recently. Codisto, the general multichannel plugin many stores relied on, was closed on the WordPress plugin directory on 1 December 2025 over a security issue and is no longer downloadable; its own domain now redirects to a Shopify app listing. Woo merchants who were on it have no upgrade path within the same product.

Meanwhile the two free channel plugins that do exist are not well regarded by the people using them: at the time of writing Meta’s WooCommerce plugin sits at 2.1 out of 5 across several thousand reviews, and Google’s at 2.7. Neither creates marketplace listings in the sense this page means — Meta’s builds a catalogue for Shops and adverts, not Facebook Marketplace listings.

For a WordPress record shop, in other words, the second channel is a build-it-yourself problem. That is the gap this page is about.

Why a record shop on WordPress should be on Discogs

Your own store is the right place for your brand, your margins and your regulars. It is a poor place to be discovered by someone hunting one specific pressing, because they are not searching your site — they are searching the database that catalogues every pressing there is.

Discogs is that database: more than 15 million music releases, with 114.2 million items added to user Collections during 2025, its highest year on record and up from 105.7 million in 2024. Those Collections feed Wantlists, and Wantlists are how obscure stock finds buyers on Discogs without you doing any merchandising at all. A record that will sit unseen on your WooCommerce shop can be sitting on dozens of Wantlists, and Discogs tells those people the moment a copy is listed.

The cost of being there is low in a specific way that suits a store with deep, slow inventory:

• No listing fee and nothing monthly. Discogs states it plainly: starting an account is free, signing up as a seller is free, listing an item is free, and you are charged only when you sell.
• Listings never expire. Leaving 2,000 records listed for three years costs nothing.
• A fee ceiling. The 9% commission is capped at $150 per sale, so a high-value rarity costs proportionally far less than it would elsewhere.

The honest counterweight is that Discogs is passive. Its Seller Policy states the default sort is newest listed first — there is no relevance ranking, no promoted placement and nothing to optimise. Your copy competes on grade, price and seller rating. That is a good deal if your inventory is genuinely good and a slow one if it is ordinary.

The Release rule

This is the constraint that shapes the whole crosslist, and it has no equivalent on any other channel.

Every Discogs Marketplace listing attaches to a Release: a specific catalogued pressing, with its own label, catalogue number, country, year and format. If your pressing is not catalogued you submit it first, and you must have the item in hand to do so. A WooCommerce product, by contrast, is whatever you typed into the WordPress post editor — which might be Blue Monday 12″ — New Order — FAC73 — VG+, or just New Order Blue Monday.

So this is a match, not a copy. FLUF strips the noise out of your product name, searches the Discogs database, disambiguates against a second music database where the result is unclear, and queues anything it cannot match confidently for you to choose by hand rather than guessing. The mechanics are the same on every source channel and are explained at length on the eBay to Discogs page.

What is specific to a store catalogue is scale and hygiene. A marketplace seller matches ten records at a time; a WooCommerce shop typically arrives with two or three thousand products accumulated over years, in whatever titling convention the person entering them was using that month. Expect the first import to surface a meaningful queue of ambiguous matches, and expect that queue to be concentrated in your oldest products. It is worth working through it once properly, because the mapping is then permanent — every later stock movement resolves against it.

It is also worth using the import as an audit. Products that cannot be matched to any Release are usually one of three things: a title typed too loosely to identify, stock that is not audio at all, or a pressing genuinely missing from the database that you could submit and thereby improve. All three are worth knowing about, and most stores have never had a reason to look.

One consequence for stock planning: Discogs is audio only. Its guidelines allow any item on an audio format from its published list, and video only where audio is the main focus. Because nothing can be listed except against a Release, there is simply no way to put band T-shirts, turntables, styli, music books or posters on Discogs. Those stay on your own store.

How to crosslist from WooCommerce to Discogs

1. Create a FLUF Connect account and start the £1 seven-day trial.
2. Connect WooCommerce. FLUF authenticates against your store’s REST API with a consumer key and secret. Your store needs to be on HTTPS — see the note below, because this is where store connections usually fail.
3. Connect Discogs with a personal access token. No browser extension is needed on either side of this pair.
4. Set up your Discogs seller account first. Discogs requires a verified address, a verified PayPal account, a hobby-or-business declaration, at least one complete shipping policy and agreed seller terms before you can list.
5. Import your products and filter to the audio stock.
6. Review the release matches. Do not skip this on a first run. Confident matches go through; ambiguous ones wait for you.
7. Set Media and Sleeve grades. A default applied across a filtered batch is usually right; adjust the outliers.
8. Crosslist. Listings appear on Discogs attached to the correct Release.

The HTTPS note. WooCommerce’s REST API accepts HTTP Basic authentication — the consumer key as username and the secret as password — only over HTTPS. On a non-HTTPS site it rejects Basic auth entirely and requires one-legged OAuth 1.0a signing instead. Separately, some server configurations strip the Authorization header before PHP sees it, producing a misleading “consumer key is missing” error on a site that is correctly configured; the documented fallback is to pass the credentials as query-string parameters. If your store connection fails, those two things account for the overwhelming majority of cases, and neither is a problem with your credentials.

Installing it from your WordPress admin

The connection is made from inside WordPress rather than from a marketplace dashboard, which is worth spelling out because it is the step store owners expect to be harder than it is.

1. Install the FLUF Connect plugin for WooCommerce from your WordPress admin, under Plugins, and activate it.
2. Generate REST API keys in WooCommerce under Settings, Advanced, REST API. Read and write permissions are needed, because listings have to be able to write stock back.
3. Paste the consumer key and secret into FLUF Connect and confirm the store handshake.
4. Choose your channels — Discogs here, and any others you want the same catalogue on.
5. Map your product data once: which attribute or custom field holds condition, if any, and which product categories are audio stock.

Two WordPress-specific things affect whether this works first time. Your site must be served over HTTPS for the REST API to accept Basic authentication at all; on plain HTTP, WooCommerce rejects it and demands OAuth 1.0a signing instead. And on some Apache and FastCGI configurations the Authorization header is stripped before PHP ever sees it, which surfaces as a “consumer key is missing” error on a store whose credentials are perfectly correct. The documented workaround is to pass the credentials as query-string parameters. Neither problem is caused by your keys, and both are worth checking before assuming the integration is broken.

A note on performance, since it is the first question most WordPress store owners ask about any plugin: the crosslisting work happens on FLUF’s servers against your REST API, not inside your site’s page loads. Your store answers API calls for products, stock and orders. It does not render listings, resize images for Discogs or run matching logic, so the front-end performance your visitors experience is unchanged.

What transfers, field by field

Variable products, stock and the one-copy rule

WooCommerce distinguishes simple products from variable ones, and variations carry their own price, SKU, image, stock, weight and dimensions. Woo publishes no hard limit on the number of variations; the only documented threshold is a rendering one, where products with more than about thirty variations switch from dynamic to static dropdowns on the front end.

Discogs has no concept of a variation. A listing is one pressing at one pair of grades at one price.

In practice records rarely need many variations, but stores do use them — a title offered on black vinyl and coloured vinyl, or standard and deluxe editions. Those are genuinely different Releases in the Discogs database, which is the correct way to think about it: each variation should map to its own catalogued pressing, not to a variant of one listing. FLUF fans them out and records each Discogs listing against the WooCommerce product and variation it came from, so stock movements resolve back to the right row.

Quantity deserves a specific warning on this pair. Discogs’ quantity feature assumes your copies are interchangeable — the same version at the same grading and the same price. For a distributor with sealed stock that is true. For a secondhand shop with five copies of the same album in five different conditions, it is not, and each copy should be its own listing with its own grades and its own photographs.

Grading — the field your store does not have

WooCommerce has no condition field. It is a store platform and store platforms assume new goods. Some record shops improvise one as a product attribute or a custom field, but there is no WordPress or WooCommerce standard for it, so nothing can be relied on across stores.

Discogs requires two grades on every listing, one for the record and one for the sleeve, taken from the Goldmine scale — Mint through to Poor, with Sleeve additionally accepting Generic, Not Graded and No Cover. The strings are exact and anything else is rejected. Discogs also publishes what each grade is worth relative to a Near Mint copy, which is the part store owners underestimate: one grade of optimism can halve the money. The full scale and its relative values are set out on the eBay to Discogs page.

The WooCommerce-specific question is where that data should live. Two workable answers:

• Keep it in FLUF. Simplest if your own storefront does not display condition. FLUF stores the grades against the product, so any further channel you add inherits them.
• Create global product attributes in WooCommerce — one for media condition and one for sleeve condition, under Products, Attributes in your WordPress admin, with the Goldmine values as terms. This is more work up front and better if you want condition shown and filterable on your own site too. Global attributes are the ones that can be used across products and drive variations; per-product custom attributes cannot.

Either way the practical route for a large import is a sensible default per product category, applied in bulk, followed by manual correction of the outliers. Grading three thousand records one at a time at the point of listing is how a migration stalls.

Fees and what you keep

• Discogs: 9% of the item price plus shipping, with a $0.10 minimum and a $150 maximum per sale, and published equivalents in each supported currency.
• No listing fee, no seller fee, no monthly fee.
• Payment processing is PayPal’s, taken from the gross payment and paid to PayPal rather than Discogs. A verified PayPal account is required.

On a £40 record with £5 postage, Discogs takes 9% of £45, which is £4.05, with PayPal’s own processing on top — putting the all-in marketplace cost somewhere around 11 to 13% depending on the transaction.

Two edges are worth planning around. The $150 ceiling makes Discogs unusually good for high-value stock: a £2,000 rarity carries a 7.5% effective rate. And the fact that the 9% applies to postage as well as the item is the thing Discogs sellers complain about most, because on a heavy multi-record parcel that is a real amount of money on shipping you have merely collected and passed on.

Against that, remember what you are comparing with. Selling the same record on your own store costs you no commission but does cost your hosting, your plugins, your payment processor and every penny of the traffic. Discogs’ 9% is competing with your acquisition cost, not with zero.

What syncs, and the webhook trap

The trap worth knowing about is WooCommerce’s webhooks. Woo’s own documentation states that a webhook is automatically deactivated after more than five consecutive delivery failures — anything that is not a 2xx, 301 or 302. On a store that goes down for maintenance, hits a plugin conflict, or sits behind an over-eager firewall for an hour, that threshold is easy to cross. The webhook then stays off, silently, and your store stops telling anything about its sales.

For a crosslisting setup this is the exact failure that causes double sales: the Discogs listing stays live because nothing told it otherwise. It is worth checking the webhook status in WooCommerce after any period of downtime, and it is a good argument for a tool that also polls rather than relying on webhooks alone.

One further caution specific to Discogs: buyers are given several days to pay after committing to an order. Sellers report a meaningful share never paying. Do not treat a Discogs order as final until the money has actually arrived.

Before and after

Before. Export your products. For each record, search Discogs, identify the exact pressing from the catalogue number on the label, open that release, sell a copy, choose two grades, retype the notes, re-photograph the item square-cropped because you cannot reuse an image across listings, and set the price. Then reconcile two systems by hand forever, because your store does not know Discogs exists.

After. Connect the store’s REST API and a Discogs token. Import. Confirm the matches FLUF flagged. Set default grades per collection. Push. A sale on either side updates the other.

The photography rule is the one irreducible piece of manual work, and it is worth budgeting for: Discogs will not let you reuse an image across listings even for identical releases, so multiple copies of the same record each need their own photographs.

What it costs

FLUF Connect is £1 for 7 days, then plans from £9/month on Starter. Seller is £29/month and Pro is £99/month; every plan is unlimited on listings and marketplaces, and the tiers differ by how often we check your channels for sales. There is no free plan. Crosslisting, inventory sync, automated relisting and offer management are included on every plan rather than sold as extras, on the channels that support them. Full detail on pricing.

For comparison, the single-channel marketplace extensions listed on WooCommerce.com are priced per channel per year, with the eBay one at around £247 a year. Discogs charges nothing to list and nothing monthly, so beyond the subscription this pair has no fixed cost at all.

Sources and verification

• WooCommerce market share: W3Techs, read 31 August 2026.
• Codisto closed on the WordPress plugin directory over a security issue: plugin page. Free channel plugin ratings: Meta for WooCommerce and Google for WooCommerce. Paid marketplace extension pricing: eBay Integration for WooCommerce.
• WooCommerce product model, variations and the thirty-variation rendering threshold: variable products and variation dropdown limits. Brands in core: WooCommerce developer blog.
• REST API authentication, the HTTPS requirement, OAuth 1.0a on non-HTTPS and the query-string fallback: WooCommerce REST API documentation. Webhook auto-deactivation after five consecutive failures: WooCommerce webhooks.
• Discogs fees, the minimum and maximum per sale and the per-currency table: what are the fees. No account, seller or listing fees and the 15-million-release database: selling on Discogs. Payment processing and the PayPal requirement: PayPal Payments Solution FAQ.
• The Release requirement and submitting a new release: how to sell music on Discogs and database guidelines. Listing fields and quantity: how to list items for sale. Grading and relative values: how to grade items. Photo rules: item photos guidelines. Newest-first default sort and seller account requirements: seller policy and seller account setup. Supported formats: format list.
• 2025 Collections record of 114.2 million items: Discogs news, 28 January 2026.
• Seller experience: the Discogs fee arithmetic thread (October 2025), unpaid orders (September 2025) and WooCommerce double-selling on single-quantity items. Read 31 August 2026.
• Release matching, grading maps and sync behaviour: verified against FLUF’s WooCommerce and Discogs integrations, August 2026.

Discogs publishes no live listing count, active seller count or GMV figure, so none is quoted; figures circulating in third-party blogs are not sourced from Discogs, and Discogs publishes no character limit for listing notes. WooCommerce documents no maximum number of product variations and no maximum gallery size, so neither is stated. PayPal’s processing rate varies by country, card type and whether a transaction is international, so no single percentage is given. Community quotes are individual sellers’ experiences, not measured data. Fees and policies are current as of August 2026.

Related pages

• Crosslist from Discogs to WooCommerce — the reverse direction, into your own store
• Crosslist from eBay to Discogs — release matching from a marketplace source
• Discogs vs Etsy — where records are actually allowed to be sold
• Sell on Discogs — the full marketplace guide
• Sell on WooCommerce — the WordPress store owner’s guide
• Crosslisting hub — every supported channel pair