Discogs logo Discogs automation · runs daily

Update Discogs orders and message buyers

An order lands in Payment Received, you pack it, and then you still open the order page, change the status, paste the tracking number and write to the buyer. Do that for twenty orders and a few get forgotten.

Cotlet does it in your own Discogs account with list_orders, get_order, update_order_status and send_order_message, called by your AI agent, an n8n workflow or a script.

Hosted · nothing to install or maintain

Can Discogs do this on its own?

Discogs changes an order status by hand, one order at a time, in the web app (checked 17 Oct 2026). Only the seller changes an order status, and the Manage Orders page bulk-moves orders to In Progress only. The API can change an order status and add a message, but you run the token and the script yourself, and no official MCP server exists.

How you do it in Discogs today

  1. You open the order from the Orders page.
  2. You click the green button below the order table to move the order to the next status.
  3. A pop-up lets you add a message before you confirm.
  4. For Shipped, you add the tracking number to the order page if there is one.
  5. On the Manage Orders page you can move several Payment Received orders to In Progress at once, but Shipped is set order by order.
  6. Discogs asks sellers to contact the buyer or send an invoice within 24 hours of a new order and to update the order within 4 days at the latest.

How to update Discogs orders and message buyers

Prompt

List my Discogs orders in Payment Received. For each one that has a tracking number in my shipping sheet, set it to Shipped with the tracking number and a short message to the buyer. Tell me about orders older than 3 days without one.
  1. 01

    Find what waits

    list_orders with status Payment Received returns the orders to ship with their dates. The agent sorts them by age, so the oldest are handled and reported first.

  2. 02

    Read each order

    get_order returns the items, buyer message thread and current status. The agent checks that the order is still in Payment Received, because a status cannot go back.

  3. 03

    Match the tracking number

    The agent takes the tracking number from the source you named in your prompt, such as a sheet or a message. An order without one is not set to Shipped and goes on your list.

  4. 04

    Set the status

    update_order_status sets Shipped with the tracking number. It asks for your OK per call until you switch confirmation off for it.

  5. 05

    Write to the buyer

    If the buyer asked something on the order page, send_order_message answers it in your wording. The agent never sends a message you did not ask for.

What you get back

Example data

Orders in Payment Received: 14
Set to Shipped 11, with tracking number and your shipping message
Left for you 3:
- 1234567-91 older than 3 days, no tracking number
- 1234567-95 buyer asks to combine shipping
- 1234567-96 buyer asks about condition

Other ways to ask

  • Move every new Payment Received order to In Progress and tell me the count.
  • List orders with an unanswered buyer message and draft a reply to each, but send nothing.
  • Every evening, list orders in Payment Received that are older than 2 days.

What Discogs allows, and what to know first

  • Only the seller can change the status of a Discogs order.
  • After the buyer pays, a Discogs order moves to Payment Received on its own.
  • In Progress is optional, can only be set straight after Payment Received, and a status can never be moved back to an earlier one.
  • Discogs does not allow a status change on an order after 90 days.
  • A buyer who gets no answer from the seller within four days can file a Seller Not Responding report.

update_order_status and send_order_message ask for your OK by default. To run it daily without you, switch confirmation off for those tools in your dashboard.

Sources: Discogs Help: How can I update the status of an order? · Discogs Help: What do the different order statuses mean? · Discogs Help: Seller Guidelines and Best Practices

Call update_order_status from a script

curl

curl -X PATCH https://cotlet.dev/api/v1/discogs/orders/1234567-89/status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"Shipped","tracking_number":"RB123456789GB","message":"Shipped today, tracking number is on the order page."}'

Example response

{
  "order_id": "1234567-89",
  "previous_status": "Payment Received",
  "status": "Shipped",
  "tracking_number": "RB123456789GB",
  "message_sent": true
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is discogs_write → update_order_status. Example data.

Schedule it in n8n, Make, Zapier or cron

Discogs tools this automation uses

Cotlet Discogs tools used to update Discogs orders and message buyers
Tool Parameters
list_orders status, page
get_order order_id
update_order_status order_id, status, tracking_number, message
send_order_message order_id, text
All 13 Discogs tools with descriptions

Frequently asked questions

Is it safe to connect Discogs to Cotlet?

Yes. You sign in to Discogs yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Discogs once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

Give your agent access to Discogs.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Discogs.