Ordering a service, delivery, and revisions

How service orders start

When you order a service on IVOTIA, the payment goes into escrow first instead of going directly to the seller.

The service order is then created with the agreed price and the service details saved in the order snapshot, including delivery time and any revision allowance that came from the service listing or offer.

Requirements come before the work starts

For service escrow orders, the buyer usually needs to submit requirements before the normal delivery clock starts.

Requirements can include written instructions and attached files.

Once the buyer submits requirements, IVOTIA records the submission time and starts the estimated delivery window using the service delivery time stored on the order.

What happens if requirements are not submitted yet

Until requirements are submitted, the order stays in a waiting state for that part of the workflow.

This matters because the seller is still waiting for the information needed to begin properly.

It also matters for cancellations: the buyer can still qualify for a pre-requirements cancellation while escrow is held and requirements have not been submitted yet.

Delivery and completion flow

After requirements are in place, the seller completes the service and marks the order as delivered from the order flow.

When the seller marks a service order as delivered, the escrow status moves to SERVICE_COMPLETED and the buyer review window starts.

At that stage, the order is delivered for review, but the seller still has not been paid out yet.

How revisions work

If the buyer needs changes after delivery, the buyer can request a revision while the service order is in the delivered review stage.

When a revision is requested, IVOTIA moves the order back to HELD, increases the revision count, and stops the auto-release timer.

That sends the order back into an active work state so the seller can deliver the revised work again.

Buyer confirmation and payout

After the seller delivers the work and the buyer is satisfied, the buyer confirms the order.

That moves the order into RELEASE_PENDING and starts the escrow release countdown.

If the order is not blocked by a dispute or another valid issue, escrow is then released to the seller wallet through the normal IVOTIA payout flow.

Cancellation and dispute paths

Before requirements are submitted, a buyer can qualify for an immediate pre-requirements cancellation on a service escrow order.

If the delivery is late enough, a buyer may also qualify for a forced late-delivery cancellation depending on the order deadline and status.

After delivery, the buyer can request a post-delivery cancellation or refund path if the delivered work does not meet requirements.

If the issue needs formal review, the order can also move into the dispute flow, which freezes release while the case is being resolved.

Important things to know

Service orders are paid into escrow first.

Requirements submission is part of the real order flow and starts the service delivery clock.

Seller delivery moves the order into a review stage, not straight into payout.

Requesting a revision moves the order back to HELD and stops auto-release.

The seller is paid only after the confirmation and release flow is completed.