How do you build a refund and refill policy?

If your policy is not written down, you renegotiate on every request. That wastes time and produces inconsistency, and a panel that gives two different answers to the same situation loses trust. A written policy protects both the customer and you.

Separate the three different situations

Three things get confused and their rules should be different:

Situation	What happened	The right response
Order never started	The provider did not process it	Full refund
Partially completed	Part of the quantity arrived	Refund the shortfall
Delivered then dropped	Delivered, then declined	Refill, not a refund

The third one causes the most argument. The service was delivered, and the later drop came from the platform. The right response here is a refill rather than a refund, and it needs a time limit.

Set a refill window

A refill cannot be open ended. The common range in the sector is 30 days. If it varies by service, write it in the service description. A panel promising unlimited refills cannot honour a request that arrives six months later, and so breaks its word.

Keep your refill window in line with the window your provider gives you. If the provider offers 30 days of refill, you cannot offer 60, you would be paying the difference out of your own pocket.

Where should the policy live?

In three places at once:

1. In the service description. The customer should see it while buying, not afterwards.
2. On a separate policy page. Keep the detailed version there.
3. On the post order screen. A line saying "the refill window for this order is 30 days" closes down an argument before it starts.

Decide quickly

The longer a refund discussion runs, the more it costs. There is nothing to gain from haggling over small amounts, a refund on one order costs a few lira while a bad review costs an amount you cannot calculate.

Set a practical threshold, approve requests below a certain amount without asking and review the ones above it. That frees up most of your support time.

But keep records

Approving every refund should not mean ignoring refunds. Track these:

• Which services generate refunds? If a particular service keeps causing problems, the problem is not the customer. Switch the service off or change the provider.
• Which customers keep opening requests? A handful of accounts may be producing most of your refund volume.
• Which provider does not honour refills? This is the most important input to your provider assessment.

A refund rate is not a cost line, it is a quality indicator. Look at it regularly and it tells you which service to drop.