Describe the business, approve exactly what goes public, then publish.

How it works

Describe, approve, publish.

Three steps, and the middle one is the whole point: an approval you can actually read, built from exactly what's about to happen.

Before it goes public

An approval that goes stale the moment you touch anything.

The approval you grant is itemized — pages, prices, payment methods, the domain — and hashed. That digest is recomputed at the instant of publish and compared to the one you approved. Approve, then edit, then publish is refused, because the approval no longer describes what would actually go live.

• One grant, one publish — a used approval cannot be replayed for a later one.
• An expired approval is refused even if nothing else changed.
• "Generate" and "save" never silently mean "go live" anywhere in Kuber.

Take the order anyway

Cash on delivery, with real limits, not just an on/off switch.

A value floor and ceiling, pin-code allow and block lists, and optional phone verification, all evaluated locally at checkout with a stated reason when an order falls outside a rule. Marking the cash as actually collected is a real order-status move now that an orders table exists, refusing a second mark on an already-settled order.

• Rules are evaluated at checkout time, not just displayed as settings.
• A refusal names the reason instead of a generic error.
• Works today with no credential required.

The tax split

CGST and SGST that always sum to the tax actually charged.

GSTIN shape, state code and check digit are validated locally, and the tax is split so the two halves add up exactly to what's charged — including the odd paisa a straight 50/50 split would otherwise drop. Now that orders exist, a numbered tax invoice generates once per order, idempotently, refusing outright rather than guessing if any line's HSN/rate is undeclared. E-invoice IRP registration still needs a GSP account.

• The split is computed, not estimated — no rounding gap between the two halves and the total.
• Changing a GSTIN or state after setup needs an approval.
• A numbered invoice works today; e-invoice IRP registration needs a GSP credential.

Run a promotion

A redemption limit that can't be beaten by two people checking out at once.

Percentage or flat codes with minimums, caps, a validity window, and total and per-customer limits. The limit check and the increment happen in one database statement, so a race between two shoppers can't both slip through — and a repeated order reference replays the original discount rather than granting a second one.

• Available today, with no credential required.
• A conditional update, not a read-then-write — the classic race condition is closed by construction.
• Retrying the same order never double-applies a discount.