Skip to main content

Pedigree Transfers

A pedigree transfer hands a rabbit and its recorded ancestry to another OmniBurrow account as live records — not a PDF of a pedigree, but the rabbit, its parents, its grandparents, and everything else you have on file, sitting in the buyer's herd. Their future litters then carry the lineage properly. It is a two-sided handshake: you send it, and they accept.

What a transfer does

When a transfer is accepted, the recipient's account gains:

  • The rabbit itself, as an active rabbit in their herd.
  • Its ancestors, as reference rabbits — records they do not own, there so the pedigree is complete.

By default the whole recorded lineage goes across. It can be limited to three generations — the ARBA-standard pedigree depth — if you would rather not hand over your full ancestry.

Two consequences worth knowing:

  • Your copy of the rabbit is marked Sold. Accepting a transfer moves ownership in the records, so the animal leaves your active herd. Its history stays with you.
  • Re-transferring a rabbit back does not duplicate it. If a rabbit returns to an account that previously held it, its existing record is reactivated rather than a second copy being made.

Your buyer does not get your herd — only the rabbit named in the transfer and its ancestry. Nothing about your other animals, contacts, or finances travels with it.

Send a transfer

Most transfers happen without you doing anything separate: recording a sale prepares one automatically whenever the buyer has an email address, and sends them the claim link along with their receipt and pedigree PDF. See Deposits & Sales.

You can also start one directly from a rabbit, entering the recipient's email address and an optional message.

Dashboard → Transfers lists everything incoming and outgoing, with its status.

A transfer sits in one of several states: pending with the recipient, pending invite if they do not have an account yet, then accepted, rejected, cancelled, expired, or unclaimed.

You can cancel a transfer any time before it is accepted, and resend the invite email if it went astray. Invite links expire after 14 days.

Invite emails carry a proper one-click unsubscribe header, so a recipient who does not want them can opt out from their mail client in one action.

Accept a transfer

If you are the recipient and already have an OmniBurrow account, the transfer appears in your Transfers list and you accept or reject it. Accepting drops the rabbit and its ancestors into your herd immediately.

If you do not have an account yet, the emailed claim link is your route: create an account with the email address the transfer was sent to, follow the link, and it is accepted for you. The email address has to match — that is what stops a forwarded link being claimed by somebody else.

The sender is emailed either way, so they know whether it landed.

Multi-rabbit transfers

Selling several rabbits at once creates one transfer covering all of them, not one per animal. The claim screen lists every rabbit name so the buyer can see exactly what they are accepting, and accepting brings all of them across together. When more than one rabbit is claimed, the buyer lands on their transfers list rather than a single rabbit.

That matches how a multi-line receipt sale works — one email, one claim, everything in it. See Kits & Phenotype Buckets.

Why transfers need a connection

Needs a connection — by design, not a limitation

Almost everything else in the mobile app works offline, because your phone holds a full copy of your data and can reconcile later. A transfer is different: it is a negotiation between two separate accounts, and neither device can decide on its own that the other party accepted. There is no offline answer to give.

This is the one feature that is online-only by design. See Offline-First Sync and the feature matrix.

One related behaviour: undoing a sale cancels the transfer that sale created. A claim link you have already emailed stops working, which is what you want when a sale falls through — but tell the buyer, because they will not necessarily be told by the link failing.

Screenshot needed

Mobile transfers list with a pending incoming transfer. Check the sender's rabbitry name and email in the frame before committing.