Fiverr milestones: split big orders safely

How a milestone order works

Instead of one delivery at the end, the project becomes a sequence of stages, each with its own scope, delivery, and price. The client sees the full workflow and pricing before ordering, and Fiverr's help center states that you are reimbursed as each milestone completes rather than when the whole order finishes. Stages can be set up in the Gig's Description and FAQ tab or through a custom offer.

The payment sequence is the part sellers care about most. Clients are charged for the first milestone when the order starts and for each following milestone when they approve the previous one. You are not carrying the full project cost between stages, and the client is not paying for work that has not been agreed yet.

Who can actually add milestones

The gate is category and price, not your seller level. To add milestones to a Gig, Fiverr's milestones article requires the basic package to be at least $100, each milestone to be at least $50, and between two and five milestones per Gig; the same article notes custom offers allow up to six. Fiverr does not publish a level requirement for this feature.

Availability is limited to specific subcategories. Fiverr's published list includes Logo Design, Website Design, Video Editing, Voice Over, SEO, Legal, and Business Plans among others, so a seller outside those subcategories will not see the option. Do not assume every category can use milestones; check whether your subcategory appears before promising a staged plan to a client.

How the money and the clocks move

Each stage has its own timeline. The client has 8 days from a delivery to request a revision or accept, then 10 days to pay for the next milestone after accepting; if they do not pay, the order stops. Clearance runs 14 days, or 7 days for Pro, Top Rated, and Seller Plus freelancers. If no one acts after delivery, milestone orders auto-complete after 8 days.

Stopping is a real state, not a pause. A client can stop the order after any accepted milestone, and a stopped order cannot be resumed. Each milestone can also be cancelled individually, and Fiverr's article states that if at least one milestone was completed, the order still counts as completed, so a partially finished project does not vanish from your record.

When milestones beat one big order

Stages make sense when the project has natural checkpoints and the price is large enough that a single payment feels risky to both sides. An illustrative example (not platform data): a $900 website project split into three milestones of $300 for structure, $300 for design, and $300 for launch. You are paid after each acceptance, and the client approves direction three times instead of once at the end.

A single order still fits better for fast, contained work: a $150 logo with a two-day turnaround does not need a funding schedule, and adding stages only adds waiting. The test is whether each stage has an output a client can accept or reject on its own. If a stage cannot be judged independently, it is one order pretending to be three.

Keeping the stages from blurring together

The common mistake with milestone orders is writing stages that overlap, then absorbing the confusion as revisions. If milestone two is the design and milestone three is the design plus two extra pages, the client reasonably reads one as covering the other, and the disagreement lands on your metrics. Define each stage by a file or outcome the client can point at, not by a phase name.

Write the boundary into the milestone description: what is included, what is explicitly out, and what triggers a new stage. Extra requests in the middle of a stage belong in a reply on the order, with a custom offer for the addition rather than silent absorption. The scope creep guide covers that conversation, and moving to larger projects covers the pricing side.

Milestones versus the other contract types

Three alternatives cover nearby situations, and they behave differently. A single custom offer is one payment with one delivery; hourly contracts bill weekly against logged hours for open-ended work; subscriptions recur at intervals for repeat business. Milestones sit in the middle: fixed prices, defined stages, sequential funding.

Pick by how well the work can be described up front. If you can list deliverables and dates, milestones give the client visibility and you staged payments. If hours will wander, hourly fits. If the same small job repeats monthly, a subscription fits. One published constraint helps the decision: milestone and subscription orders cannot be combined and offered simultaneously, so a Gig cannot carry both models at once. Illustrative split (not platform data): a $1,200 edit booked as three $400 stages — rough cut, revision round, final export — gives both sides a checkpoint, while the same project as one $1,200 custom offer pays only at the end and five logged hours would bill whatever the week actually took.

Where Seller OS helps

Seller OS keeps the boundary work honest. Package pricing review checks your stage prices against your profit assumptions, and local client records keep each project's agreed scope where you can see it when a mid-stage request arrives.

It drafts and fills; a person performs every final Send, Save, Continue, or Publish action. It does not create milestone orders for you, release funds, or negotiate stages with your client.

Related guides