A Discord commission workflow works best as intake ticket, then an invoice per milestone or per finished piece, delivered inside the same ticket that started the order. Artists, developers, designers, editors and boosters all run into the same problem selling on Discord: work isn't a fixed catalog item, price depends on scope, and payment often happens in stages. This guide covers a ticket-to-invoice flow that handles custom work without forcing it into a rigid product catalog.
Why commission work doesn't fit a normal catalog
A product catalog assumes a fixed price for a fixed thing: a rank, a role, a file. Commission work is scoped per client — a portrait costs different amounts depending on complexity, a Discord bot feature depends on hours, a video edit depends on length and revisions. Trying to list every possible price as a separate catalog product turns into dozens of near-duplicate entries. The better fit is a request form that captures scope, then a manually-priced invoice once you know what the job actually involves.
Step 1: Take requests through a form, not open chat
An open "DM me for commissions" invites vague requests and scope creep before you've even quoted a price. A ticket panel with a form (/ticket form in Noxyr) asks for what you need upfront — reference images, deadline, budget range, revision expectations — before a ticket even opens, so you're quoting against real information instead of a one-line "can you draw my character."
Step 2: Quote and confirm inside the ticket
Once the ticket opens with the buyer, quote the price and scope in writing in that channel, not in a DM. This matters twice: it's the record you'll refer back to if the client later claims a different scope was agreed, and it's what the eventual invoice should match line for line. If you use a fixed TOS for revisions or turnaround, this is also where you point to it — see the seller TOS template for revision and cancelation language you can adapt for creative work specifically.
Step 3: Invoice by milestone for anything over a session
For quick jobs, one invoice at the end is fine. For anything with real duration — a multi-day art piece, a development project, a boosting order spread over days — split it: an invoice for a deposit at the start, and a final invoice on delivery. /invoice create supports this directly:
- product_name and description — name the milestone clearly ("Sketch approval — deposit", "Final delivery — remaining balance") so the invoice history reads as a project timeline, not two unrelated charges.
- discount_percent or custom_price — useful for a repeat client discount or a negotiated final price that doesn't match your usual rate card.
- payment_status — mark the deposit invoice Successful once it clears, and create the final invoice as Pending the moment delivery is ready, flipping it once the balance is paid.
Multiple line items on one invoice (product_2 through product_5) also work if a single payment covers several small extras — a base commission plus a rush fee plus an extra revision round, for example.
Step 4: Deliver in the ticket, gate on the final payment
Send the finished file, access, or completed work in the same ticket the commission started in, after the final invoice shows Successful — the same rule as any other digital sale (see selling digital products safely). Full-resolution files, source access or unwatermarked delivery should wait for full payment; a preview or watermarked draft is a reasonable way to prove progress before that.
Step 5: Close with a transcript and a receipt
Close the ticket with a reason referencing the order ("Delivered, final invoice INV-0231") so the saved transcript and the invoice cross-reference each other. If a client disputes scope or payment months later, you have both the negotiated agreement and the receipt in one place.
Step 6: Ask for a review once delivery is confirmed
Commission work lives on reputation more than most Discord shops — a portfolio of public reviews with the actual delivered work attached (screenshots included) is often the single best thing that converts a browsing member into a paying client. /review submit lets a client attach an image alongside their rating and comment; encourage it right after a smooth delivery while the experience is fresh. More in collecting reviews on Discord.
Handling scope changes mid-commission
The most common commission dispute is "that's not what I asked for" after work has started. Two things reduce this: write the agreed scope in the ticket before starting (step 2), and invoice extras as separate line items instead of silently absorbing them or renegotiating the whole price. An invoice that lists "Base commission" and "Extra revision round (client request)" separately is a lot easier to defend than one lump number that changed twice.
What this workflow doesn't do
It doesn't automate quoting — pricing custom work still needs a human to look at the request and decide a number. It also doesn't handle contracts or IP transfer terms; those belong in whatever TOS or agreement you use alongside the invoice, not in the invoice itself, which is a payment record, not a legal contract.
Common questions
Can I take a deposit and a final payment as two separate invoices? Yes, create one invoice per payment with a description that makes the milestone clear; both will show up under the same customer when you look up their order history.
Does Noxyr calculate hourly rates for me? No, you set the price per invoice yourself, whether that's a flat commission fee or a number you worked out from hours logged elsewhere.
What if a client wants a refund partway through custom work? That's a policy decision, not a bot feature — state your partial-refund rule in your TOS before taking the deposit so it's not negotiated after the fact.
Can buyers look up their own commission invoices later? Yes, the public /invoice check command lets anyone look up an order by its ID, which doubles as a receipt for a client's own records.
Is a ticket form required for this workflow? No, but it's the difference between quoting against real scope and guessing — without one, expect the first few messages of every ticket to just be you asking the questions the form would have asked upfront.