List something on eBay and the listing form is the whole process: you fill in a title, a price, some photos, and it's live. Try the same thing on Discogs with a record that isn't already in the database, and there's nothing to click — no "sell this item" button exists until a release page for that exact pressing exists first. Sellers new to Discogs often assume the search just missed it, when the real issue is that nobody has entered that pressing into the database yet, and listing it for sale means doing that first.
Discogs separates "the database" from "the marketplace"
eBay and Shopify both work the way most sellers expect: the listing you create is the product record. Discogs splits the two apart. The database — releases, artists, labels, pressing variants — is a shared, community-edited catalog that exists independently of anyone's inventory. The marketplace is layered on top of it: every for-sale copy is attached to one specific release page in that catalog, down to the exact pressing, country, and year. A 1972 first pressing and a 2019 reissue of the same album are two different release pages, each with their own copies for sale, even though it's "the same record" to a casual buyer.
That's why the fix for "I can't find my record" is almost never a better search query. If a matching release page genuinely doesn't exist yet, no amount of searching will turn one up — you have to create it.
Before you submit: search like you mean it
Discogs' own contributor guidance is blunt about this: double- and even triple-check that the release hasn't already been entered before you add a new one. A duplicate submission wastes a voter's time undoing it later, and it's astonishingly easy to create by accident — a slightly different catalog number, a regional variant, or a reissue with the same cover art can all look identical at a glance but need their own release page. Check matrix/runout etching, label text, and catalog number against what's already in the database before concluding it's missing, not just the title and artist.
Adding the release: what the form actually asks for
Once you're sure it's genuinely missing, Discogs' submission form — reached from the "Add Release" option — wants the record in front of you as you fill it in, not from memory. You're entering the tracklist, label and catalog number, format and country, release year, and credits, and Discogs' own guidance for first-time contributors is to start with something simple — a single-artist LP or CD with a short tracklist — rather than a box set or a various-artists compilation with a dozen contributors, since those are far easier to get wrong on a first attempt.
The part that catches people off guard: your submission goes live immediately. There's no review queue that holds it back from appearing in the database. That's also exactly why Discogs tells you to check your work before submitting — once it's live, the correction process is public and visible, not a quiet edit you make before anyone sees it.
The voting system is quality control, not a listing gate
What goes live immediately is one thing; nothing stops you from attaching a copy for sale to that release page right away, through the same "sell this item" flow you'd use on any existing release. What the community-voting layer controls is the data's accuracy, not your ability to sell against it.
Other Discogs users can vote on your submission along a scale from "Entirely Incorrect" up to "Correct and Complete," with "Needs Minor Changes" and "Needs Major Changes" in between. The database uses color to show where a submission sits: an unvoted entry is flagged for voters to look at, one voted down to "Needs Minor/Major Changes" gets marked for correction, and one voted "Correct" or "Correct and Complete" becomes fully active with no flag at all. Not every account can vote — Discogs assigns voting rights based on a pattern of good contributions over time rather than a fixed submission count, so a brand-new contributor's own first entry typically waits on someone else's review to get that flag cleared, even though the page itself and any copies attached to it are already live and findable.
What this means for a seller holding an unlisted record
- Search by matrix number and catalog number, not just title. Pressing
- variants are the single most common reason a record "isn't in the
- database" when a near-identical entry already is.
- Have the physical copy in hand when you submit, and enter what's
- actually printed on the label and runout, not what a similar release's
- page already says — copying from a near-match is how duplicate-adjacent
- errors get made.
- Start your first submission with something simple if you're new to
- contributing. A single-artist LP is a much smaller place to make a
- mistake than a various-artists comp.
- You can list a copy for sale as soon as the release page exists — you
- don't need to wait for votes to clear before attaching your inventory to
- it. Just expect the page itself to carry an unvoted flag until another
- contributor checks it.
- Treat a wrong submission as public from the moment you submit it.
- There's no private draft step, so the double-check happens before you
- click submit, not after.
PalmFlow imports both your Discogs listings and your Discogs orders, but it works one layer up from all of this: it reads copies you've already attached to an existing release page, the same way the Discogs website does. It can't create a new release in Discogs' database or push a listing to one that doesn't exist there yet — that's a Discogs contribution, not an inventory sync, and it stays something you do on discogs.com itself before PalmFlow ever sees the item. Free plan, 50 items, no card.
Disclaimer: this is general information based on Discogs' own published contributor guidance, not a substitute for it. The submission form, voting thresholds, and contributor requirements are Discogs' own policy and can change — check Discogs' Help Center before submitting a new release if anything above doesn't match what you see on the site.