Refund rules when a service request is still waiting to start

When a request is still parked, not processed

If you have placed a digital service order and then paused, the main question is not whether you changed your mind. It is whether the request has actually entered active work. That boundary matters because once an order moves into research, preparation, outreach, or coordination, you are no longer looking at a simple unopened purchase.

Oltora’s Refund, Cancellation and Returns Policy separates orders that are still waiting from orders that have already consumed time or outside resources. That distinction is the architecture behind the decision: one part of the order is the customer’s request, another part is the work state, and those two things are not the same.

What has to stay separate

To judge the right remedy, keep three pieces apart in your mind:

• the purchase itself, which may still be untouched
• the work state, which shows whether substantive work has begun
• the remedy, which may be cancellation, a refund, or no refund depending on what happened

That separation sounds basic, but it prevents the most common mistake: treating any post-purchase concern as if it were still a clean cancellation. A service order can look idle from the outside while still being in the middle of internal review, and that is where the timing question becomes important.

What counts as active work

For Oltora services, work may begin before a final deliverable exists. The policy treats activities such as research, website or opportunity analysis, prospecting, publisher or website evaluation, outreach, content preparation, content editing, placement preparation, link building activity, external visibility work, manual review, report preparation, third-party ordering or reservation, project-specific analysis, and other substantive fulfillment tasks as work that has already started.

That means the state of the order matters more than the buyer’s mood on the day they ask. If the order is still waiting, the route is simple. If it has already moved into active work, the order has crossed into a different category.

Why timing changes the remedy

A service request that has not started can usually be handled more cleanly than one that already has. Once work begins, there may be earned effort, incurred costs, or third-party coordination already tied to the order. That is why the policy does not treat every request as if nothing happened.

Think of it like a workflow with a checkpoint. Before the checkpoint, the request is still just an order. After it, the order has state attached to it: notes, analysis, outreach, reserved placements, or other steps that cannot simply be erased because the customer now wants a different outcome.

What to do before you ask for the wrong remedy

If you are reviewing a service request, ask three practical questions:

• Has anyone started substantive work on this order?
• Has the work moved beyond internal waiting into research, review, or outreach?
• Is the issue about stopping the order, or about what has already been completed?

Those questions help you choose the right path. If nothing has started, you may still be in cancellation territory. If work has begun, the order may need to be reviewed as a partly completed service instead.

Where this matters most

This timing boundary is especially relevant for services that depend on manual effort or outside coordination. SEO, backlink, outreach, external visibility, consulting, development, and custom deliverables all carry some amount of project-specific work. The same is true for digital reports, audits, or research-based deliverables once preparation begins.

That does not mean every paid order is automatically non-refundable. It means the design of the order matters. Some purchases are covered by a defined refund window, while others depend on whether work has already started. The policy is built to follow that split instead of assuming every digital purchase behaves the same way.

When the order has not moved yet

If a request is still waiting and no substantive work has begun, the situation is straightforward. The order has not yet accumulated the kind of project state that makes reversal complicated. In that case, the next step is to use the cancellation path that matches the purchase type and the written terms attached to it.

If work has already started, the question changes. You are no longer asking, “Can this be stopped before anything happens?” You are asking, “What parts of the order were already performed, and what remedy applies to the unfinished portion?” That is a different decision, and it should be treated that way.

For readers who also need the broader policy context, the main policy page is the right place to check before opening a refund request or assuming a service can be reversed in the same way as an untouched order.

The practical takeaway is simple: know whether the request is still waiting, already moving, or partly completed. That one distinction usually tells you which remedy makes sense next.