Refunds and returns
Settle refunds for cancellations: Refunds and returns.
Self-service lets buyers handle routine requests straight from their order or delivery page, no account required. You stay in control: a per-type policy decides which actions happen instantly and which queue for your approval first.
Each request is tied to a non-shipping item (or the whole order) and acts on the underlying entity, the event booking, digital grant, or gift card:
Buyers open these from the tokenized delivery page. The link they receive is the authorization, so there’s no login step, and the seller backend always re-enforces your policy before anything happens.
Go to Settings → Self-service. Rules are grouped per product type, and each type has its own allow toggle, approval toggle, and where relevant a cutoff window, limit, and reason requirement, this is finer-grained than a single returns policy.
Allow cancellation of unfulfilled orders is on by default for quantities that remain unfulfilled. Already fulfilled quantities stay untouched. Approval is configurable and defaults to required; when approval is off, the request is still stored durably before the cancel runs.
Cancellation releases the affected inventory and reduces any outstanding COD/manual collectible. A plain pending ₹1,000 COD order with nothing collected creates a ₹0 refund. If ₹200 was prepaid by store credit and ₹800 remained COD, only real refundable tender—at most ₹200 in this example—is offered. Linked automatic refunds are off by default; you can enable them in policy or choose Create refund while approving, and Sellerlane commits the cancellation and refund together. See Refunds and returns.
Use the Excluded products search to mark specific items ineligible for any self-service. An excluded item blocks all of its own requests, and because a whole-order cancel has no single line, an order is blocked from self-cancellation if it contains any excluded item.
The backend loads your policy, resolves the target, checks exclusions, then:
Pending and decided requests appear in two places:
Approving applies the underlying action (reschedule, cancel, redeliver, reset downloads, resend). Declining opens a note where a reason is optional, and the buyer is notified either way. The lifecycle runs requested → approved → completed, or declined, and every decision is stamped and logged.
See Order & rewards lifecycle for the cross-system COD, refund, fulfillment, and reward examples.
Refunds and returns
Settle refunds for cancellations: Refunds and returns.
Event bookings
Manage reservations and reschedules: Event bookings.
Digital products
Downloads and grants: Digital products.
Gift cards
Issuance and balances: Gift cards.