Buyer ordered the wrong Fiverr package: seller options

Message first, compare scope second

Before you pick a path, open the order chat and ask the buyer to confirm what they need. Quote the specific deliverables in your Basic, Standard, and Premium packages, then ask which list matches their brief. Keep the tone collaborative, not accusatory. A screenshot of your package comparison table pasted into the chat creates a shared reference point that prevents 'I thought Basic included X' later.

If the buyer realizes the mistake and agrees to pay more, you have a clear record. If they insist Basic covers it, you have evidence for a mutual cancellation that protects your Order Completion Rate. Fiverr states that orders canceled by the client before they submit requirements do not affect OCR, and mutual cancellations where the client reorders within 14 days also have no OCR impact (per the legacy FAQ, still consistent with current behavior).

Path 1: Deliver exactly what was ordered

Choose this when the buyer's brief fits within the ordered package, or when the buyer confirms they want only the Basic scope despite mentioning more in the requirements. Deliver the Basic deliverables on the Basic deadline. In the delivery message, explicitly list what is included and what is not, referencing the package description. This creates a paper trail: if the buyer later asks for Premium features as a revision, you can point to the delivery message and the original package scope.

A common mistake sellers make is quietly delivering Premium work on a Basic order to 'be nice.' This sets a precedent the buyer expects next time, erodes your package pricing, and gives you no leverage if the buyer leaves a negative review citing missing features that were never in the Basic package.

Path 2: Custom-offer top-up for the difference

Use this when the gap is small — for example, the buyer needs one extra revision or one additional file format that lives in Standard. Send a custom offer for the price difference with a one-day delivery time and zero revisions. Fiverr's custom offer limits are $5 minimum, $20,000 maximum, 1 to 90 days delivery, and 0 to 20 revisions or Unlimited. A top-up custom offer keeps the original order intact, so the original deadline and metrics stay clean.

Illustrative example: Basic is $50 for a 500-word article. Standard is $90 for 1,000 words. The buyer ordered Basic but needs 1,000 words. Send a $40 custom offer for 'Additional 500 words — add-on to order #12345' with 1-day delivery. When accepted, the top-up becomes a separate order line; you deliver the full 1,000 words on the original Basic deadline.

Path 3: Full upgrade via new custom offer

When the gap is large — the buyer needs Premium but ordered Basic — a top-up gets messy. Instead, mutually cancel the original order (protecting OCR if the buyer reorders within 14 days) and send a custom offer for the correct Premium package with the correct deadline. Fiverr allows custom offers up to $20,000 and 90 days delivery, so any package upgrade fits. The buyer pays the full Premium price; you deliver on the Premium timeline.

This path is cleaner for both parties: the order page shows the right package, the deadline matches the scope, and your gig analytics reflect the true package sold. The mutual cancellation must be initiated before you deliver anything on the original order.

Path 4: Mutual cancellation when no agreement

If the buyer refuses to pay the difference and insists the ordered package covers the brief, do not deliver out-of-scope work. Open a mutual cancellation in the Resolution Center. Fiverr's Resolution Center gives the other party 48 hours to accept or decline; if they do not respond, it auto-accepts. A mutual cancellation before delivery protects your Order Completion Rate (client-canceled-before-requirements = no OCR impact; mutual cancel with reorder within 14 days = no OCR impact per legacy guidance).

After cancellation, you can send a custom offer for the correct package if the buyer changes their mind, or simply move on. Document the scope mismatch in your private notes: package ordered, brief requirements, buyer's stated position. This record helps if the buyer later claims you refused to work.

Record-keeping that protects your score

Every path above relies on having a clear, timestamped record. Save: the package comparison you pasted in chat, the buyer's reply confirming or denying scope, any custom offer sent and its acceptance, the Resolution Center thread if used, and the final delivery message listing inclusions and exclusions. Seller OS local client records let you attach these screenshots and notes to the buyer's profile so they are one click away if a dispute arises later.

If the order proceeds to a review, your response can reference the chat where the buyer agreed to the delivered scope. Fiverr's review system allows seller responses with no time limit while the gig is active. A factual, calm response citing the agreed scope carries more weight than a heated rebuttal.

Where Seller OS helps

Seller OS keeps local client records with notes and history, so the package comparison, buyer replies, and custom offer links stay attached to this buyer. The inbox assistant drafts the scope-confirmation message, the top-up custom offer text, and the mutual-cancellation explanation. The gig optimizer can flag when your package descriptions leave gaps that cause buyers to pick the wrong tier.

It cannot force a buyer to accept a custom offer, cannot prevent a buyer from leaving a review, and does not file Resolution Center requests for you. Every mutual cancellation click and custom offer send remains yours.

Related guides