Hukrr
Legal · Effective 2026-11-03

Delivery Policy

Effective 2026-11-03 · MAHAVIR TRADING CO (“Hukrr”, “we”, “us”)

This policy explains how delivery works on Hukrr: when the delivery clock starts, how a creator submits work, how a brand reviews it, what happens when the review window closes, and what happens if the work does not arrive at all. It should be read together with our Terms & Conditions (particularly Sections 8 and 10 on escrow and delivery) and our Refund Policy.

1.Scope — digital delivery only

Every order on Hukrr is delivered digitally. There is no physical shipment, no courier, and no shipping charge on any order. A creator delivers work by uploading files, providing URLs, typing text, or confirming that an item is done through the order's delivery workspace, and a brand reviews it in the same workspace.

This page is served at /shipping-policy because that is the URL Cashfree's onboarding crawler looks for when it reviews a merchant for a payment gateway account. It is a delivery policy that uses that URL, not a shipping policy in the sense of dispatched goods, because nothing on this platform ships.

2.The states an order moves through

An order passes through the following states. The delivery states are the second half; the first half is funding.

  1. a.AWAITING_PAYMENT — the agreement is in force; the brand has not funded escrow.
  2. b.FUNDED — escrow is funded. The delivery clock starts here. The creator can begin work.
  3. c.IN_PROGRESS — the creator has started work. Optional; some creators go straight from FUNDED to DELIVERED.
  4. d.DELIVERED — the creator has submitted work. The brand's three-day review window starts here.
  5. e.REVISION — the brand has asked for a change within the revisions included in the order. The creator's delivery clock resumes.
  6. f.COMPLETED — the brand has approved, or the review window has expired and escrow has released automatically.
  7. g.DISPUTED — either party has opened a dispute. Actions on the order are frozen until the dispute is resolved.
  8. h.CANCELLED — the order ended without delivery. See the Refund Policy.

3.When the delivery clock starts

The delivery clock starts when escrow is funded, not when the order was placed and not when the contract was signed. This is deliberate. A creator cannot begin work until the brand's payment is secured, so charging the creator for however long the brand took to pay would be a silent penalty. A brand who takes five days to fund an order does not shorten the creator's delivery window by five days.

If a revision is requested, the creator's clock resumes from the moment the revision is requested, and the creator has the same delivery window as before to submit the revised work. The revision itself does not restart the escrow clock — auto-release stays paused while the order is in REVISION.

4.The delivery window

The delivery window is stated on each order at the time the order is placed or agreed:

  • For a <strong>Service Order</strong>, the delivery window is the one set by the creator on that service and agreed by the brand when the order was placed.
  • For a <strong>Custom Deal</strong>, the delivery window is the one agreed between the parties during negotiation and recorded on the contract.
  • The window is capped at <strong>30 days</strong> from the date the order is funded. This is a platform-wide maximum, not a creator preference. It exists because the escrow and settlement rails this platform runs on have their own deferred-settlement limits, and an order whose window was longer than that limit could not be paid out on release — a promise the platform cannot keep is not a window we offer.
  • The window is a minimum of one day.

The due date shown on the order page is calculated from the funding date and the agreed window. It is not shown as a range, a guess, or an "approximately". A creator who cannot deliver by the agreed date can communicate that in the order chat; the platform does not extend the window automatically.

5.How a creator delivers

How a creator submits work depends on how the order was set up. Both paths are supported, and both lead to the same state (DELIVERED) with the same downstream mechanics.

5.1 Orders with a delivery checklist

Service Orders placed through the current catalogue carry a frozen delivery checklist generated from the formats of the service being delivered. A deal born from a campaign brief inherits a checklist from the brief's formats in the same way. The checklist is agreed at contract generation and is part of the contract that both parties sign.

Each line item on the checklist requires a specific kind of submission:

  • <strong>A file</strong> — an image, video, or archive. The item specifies what type is acceptable for that line.
  • <strong>A URL</strong> — a live link to a published post, a YouTube video, a pinned comment, or similar. Only <Code>https://</Code> URLs are accepted.
  • <strong>Text</strong> — a caption, a description, timestamps, a partner code, a video ID.
  • <strong>A confirmation</strong> — a checkbox the creator affirms, for example that a paid-partnership toggle was set, or that a link sticker was placed on a story. The platform records the time of the affirmation.

The creator submits each line item individually as it is ready. The checklist does not need to be completed in one sitting, and an item that has been reviewed and approved by the brand is locked — it cannot be edited afterwards. Approved items contribute to the order's progress but are not re-reviewed.

When every required item on the checklist has been submitted at least once, the creator can mark the order DELIVERED. The order does not enter DELIVERED before this; a submission that is missing a required item is refused.

5.2 Orders with a free-text delivery

Orders placed before the checklist existed, and orders whose formats do not have a defined checklist, deliver through a free-text box and a file upload. A creator submits a description of what was delivered, a set of files, or both, and marks the order DELIVERED. At least one file must be attached for a free-text delivery to be accepted.

Deliveries submitted through the free-text path remain available on the order page for the brand's review, and are the record of what was delivered in the event of a dispute.

5.3 File limits

Files attached to a delivery — whether through the checklist or the free-text uploader — are limited to 10 MB each. The platform does not accept larger files, and a file that exceeds this limit is refused before the upload begins. A creator who needs to send larger files should upload them to their own storage and submit the link through a URL line item, where the checklist provides one.

6.How a brand reviews

Once the order is DELIVERED, the brand has three days to review. The review window is the same whether the order used a checklist or a free-text delivery, and the same for a Service Order and a Custom Deal.

On an order that carries a checklist, the brand reviews each item individually:

  • <strong>Approve</strong> — the item is accepted. Approval is final; an approved item cannot be sent back for revision later.
  • <strong>Send back</strong> — the item needs a change. The brand writes a reason, and the creator can resubmit that item. The reason is shown to the creator against the specific item.

The order-level review (approve, request a revision, or open a dispute) is only available to the brand once every required item on the checklist has been approved individually. Approving the order is the brand's final confirmation; per-item approval is what makes that confirmation meaningful.

On a free-text delivery, the brand has the whole submission available on the order page and reviews it as one unit. There is no per-item approval on this path because there are no items.

7.Approving delivery

When the brand approves, escrow is released and the creator's share is paid out as described in Section 12. The order moves to COMPLETED. Approval is final from the brand's side — the order cannot be un-approved.

Approval is blocked while a required checklist item is unapproved. If a brand tries to approve the order without approving every required item first, the platform refuses and names the items still awaiting review. This is deliberate: an order-level approve button that could release money over unapproved items would make the per-item workflow advisory rather than binding.

8.Requesting a revision

If the delivery is close but not right, the brand can request a revision instead of approving. Each order carries a number of revision rounds agreed at purchase — typically one, two or three depending on the service — and the number is frozen onto the order.

A revision request requires a description of what needs changing, and can optionally include reference files. Submitting it moves the order back to REVISION, pauses the review window, and gives the creator the same delivery window as before to resubmit.

Revisions are limited to the count agreed. Once the count is used up, the brand's options are to approve the delivery or open a dispute. A brand that has used every revision available to them cannot ask for another through the revision workflow; if the work still is not right, a dispute is the route. Extra revisions beyond the count can be offered by the creator as a priced add-on when the service is set up, in which case they form part of the contract.

The revision history is retained on the order page: what the brand asked for, what files (if any) were attached, and when. A creator cannot edit an earlier revision request, and a brand cannot withdraw one once the creator has seen it.

9.Auto-release after three days

If a brand neither approves nor requests a revision nor opens a dispute within three days of delivery, escrow releases to the creator automatically. The order moves to COMPLETED.

This is deliberate and is not a courtesy to the creator. It is what prevents a brand from holding a creator's payment indefinitely by simply not opening the order page. A three-day window is long enough for a brand to review properly and short enough that a creator is not left without their money for weeks. The three days run from the moment the creator marked the order delivered, not from the moment the brand first opened the page — a brand who never opens the order page does not stop the clock.

Auto-release does not check per-item approvals. On a checklist order, the brand's manual approval is blocked until every required item has been approved; the automatic three-day release is not. This asymmetry is intentional. The per-item gate stops a brand releasing by accident; the automatic release stops a brand holding a creator's money by doing nothing. The creator already cannot reach DELIVERED without submitting every required item, so there is always work to pay for. A brand that needs to hold a release because an item is not right must open a dispute or send that item back before the window closes.

The auto-release runs hourly. The precise minute the release lands is therefore up to one hour after the three-day mark, and the order will show COMPLETED as soon as the release succeeds. A brand who opens a dispute moments before the release lands freezes escrow before the release can run; a dispute opened after the release has run does not reverse it — the dispute is then between the parties and the platform's dispute funnel is the route, not the escrow.

10.Overdue delivery — grace period and cancellation

Escrow holds the brand's money for the whole delivery window. An order that is never delivered cannot sit in escrow indefinitely.

On the day the agreed due date passes, the order becomes overdue. Both the creator and the brand are notified that the deadline has passed, and the creator is given a seven-day grace period.

If the creator delivers within the grace period, the order proceeds normally: the brand reviews, the three-day auto-release clock starts, and the money stays in escrow until it is either approved, released automatically, or refunded through a dispute. The overdue warning is not a black mark against the creator, and the brand cannot use it as grounds to cancel once the creator has delivered.

If the creator has not delivered at the end of the grace period, the order is cancelled automatically and the brand is refunded in full — including GST — to the payment method the brand used. The creator is notified at the same time. See the Refund Policy for how the refund is processed.

Overdue cancellation applies to Service Orders. A funded Custom Deal is not swept by this automation; if a funded deal is not delivered and the parties cannot agree, a dispute is the route. See Section 11.

11.Opening a dispute instead

Instead of approving, revising, or (on the brand side) accepting an overdue cancellation, either party can open a dispute. A dispute can be opened once the creator has marked the order DELIVERED or REVISION; the order then moves to DISPUTED and all actions on it are frozen.

A dispute does not cancel an order and does not release or refund money immediately. It routes the question through a three-stage process — settlement window, evidence window, arbitration — that is described in Section 13 of the Terms. A settled dispute ends the order: it may release the money to the creator, refund the brand, or split it between them.

A brand who is considering cancelling an order for non-delivery on a Custom Deal — where the automatic overdue cancellation in Section 10 does not apply — should open a dispute if the creator has not delivered or is not responding. Waiting past the delivery deadline without doing anything does not auto-cancel a deal.

12.Payment routing on release

When an order is approved (whether manually, automatically, or as the release outcome of a dispute), the creator's share is sent to the bank account the creator registered and verified with the platform's payments partner. This happens automatically; there is no withdrawal step. The creator is notified, and the payment appears in the creator wallet history.

A creator must have a verified payout account before the order can be signed, let alone delivered. If a verification has lapsed between signing and delivery, the release may be held and the creator prompted to re-verify. In that case, the funds remain in escrow until the verification clears — the creator's share is not lost, and the release runs as soon as the account is payable again.

The full breakdown of what the creator receives — their price, GST on it, platform commission, GST on commission, TCS, and TDS — is frozen onto the contract and shown on the order page. The Terms describes that breakdown in Section 9.

13.What this policy does not cover

This policy describes the mechanics of a delivery on the platform. It does not describe:

  • Whether the work is good. The platform does not judge quality. Approving is the brand's call and the review window is what forces that call. If the brand believes the delivery does not meet the agreed scope, the answer is a revision within the allowance, or a dispute — not the platform.
  • Refunds and cancellations. Those are in the Refund Policy.
  • Tax on the settlement. That is in Section 9 of the Terms.
  • Deliverables to a third party. Nothing on the platform ships. A creator who needs to send a physical product does so off-platform; the platform only receives the files, URLs and confirmations the checklist asks for.

14.Contact

Delivery questions should go to hello@hukrr.com with the order number in the subject line. A creator who cannot deliver by the deadline should say so in the order chat as early as possible; communicating a delay is always better than silence, and is what distinguishes a grace period that is used from one that lapses.

Support
hello@hukrr.com
Telephone: +91 9419135248 · Mon–Sat · 10:00–18:00 IST

For complaints about how a delivery was reviewed or how the platform handled a delivery-related decision, the Grievance Officer's details are in Section 20 of the Terms.

Draft notice. This policy is a working draft prepared for the Hukrr platform. It reflects what the current code does; it has not yet been reviewed by counsel and should not be relied on as legal advice until it has been. It is served at /shipping-policy because Cashfree's onboarding crawler looks for that URL when reviewing a merchant for a payment gateway account; the content is a delivery policy, not a shipping policy, because every order on the platform is delivered digitally.