Sign in

Blog Article

Partial, refill and cancel: what they actually mean in real operations

These three labels are often misunderstood. Here is the operational meaning that matters when you review order outcomes.

Published March 21, 2026 for the migrated public content surface.

PublishedMarch 21, 2026Article timing stays visible in the migrated public detail route without theme-template branching.
Reading time2 minReaders now get the same typed article metadata in both `/blog/[slug]` and query-router detail views.
Route/blog/partial-refill-and-cancel-explainedCanonical article detail stays available as a clean public route while the legacy blog handler remains retired.
SurfaceMigrated public articleThe article shell now sits fully in the new frontend and content API stack.
Continue reading
Back to blogQuery view
Product routes
Browse servicesFAQCreate account
Partial, refill and cancel: what they actually mean in real operations

Order states are not cosmetic labels. They explain what happened between your panel request, the provider runtime and the final fulfillment result.

Partial

A partial result means only part of the requested quantity was delivered. The remaining amount should return as balance credit so the customer is not charged for what was not received.

Refill

Refill is not an instant metric reset. It is a provider action request that depends on the provider policy, service support and the actual order history.

Cancel

Cancel can only succeed while the provider still allows the order to be interrupted. Once delivery progresses too far, the realistic outcome is often a rejection rather than a forced stop.

Migration note

  • This article is no longer rendered through legacy Twig templates.
  • The content model now sits in the new Postgres schema.
  • Public detail routes can be smoke-tested directly without legacy fallback.