Customer Support Dashboard

Customers, pets, orders, payments and organizations

Two-step sign-in

Enter the 6-digit code from your authenticator app.

or

Set up two-step sign-in

Every sign-in to this admin now needs a code from an authenticator app on your phone — Google Authenticator, Microsoft Authenticator, 1Password, Authy or any other.

  1. In the app, add an account and scan this code: QR code for the authenticator app On this phone? Open it in the app
  2. Can't scan it? Enter this key in the app (time-based):
  3. Type the 6-digit code the app shows now.
Customer Support Dashboard
Organizations
Free microchips
SHOP
Integration requests
Hotline
DateCustomerContactsAddress ProductAmountStatus
DateCustomerContactsAddress ProductAmountShopify
DateFromForAmountStatusShipmentsActions
Finder data requestA finder asks to delete their data: find their scans and messages by the phone or email they give.
DateApplicationOrg nameOrg typeContactAddressStatus
We promise owners a review within 72 hours; requests older than 48 hours are highlighted.
RequestedPetMicrochipOwnerTypeClaimedFilesStatusTaken by

Days are UTC days, as in the growth table. Every day of the period is a row, a day with nothing is 0. Columns in the order of the table's tabs: Users, Reports, SBP, Helps. USA / Non-USA — by the country of the address; an account without one by its pets', a report without one by its author's; nothing to tell by counts as USA.

Reports API: STATS_API_TOKENS is not set in this admin, so the partners' transfers aren't counted.

The partner's modal (Pet Insurance Quotes) on the pet's page. Days are UTC days. Events — how many times the modal was opened, closed and clicked through; Pets — how many different pets it was opened, closed, clicked for (a double click or a second visit is one pet; in Total, a pet of two days is one). CTR = clicked / opened (of events it can pass 100%: a double click is two clicks). Context — why it was shown; Other is any other mark (from Aug 26 to Sep 23 the site wrote the pet's page there). Dashboard page — the same offer as a page of the dashboard (Pet insurance): its views and clicks, not in All. Staff, test and autotest accounts are left out.

Transfers of the UKM shops (the shops sharing one partner API token, as the finance admin's billing group) that the new owner hasn't accepted, by the month the transfer started — New York time. Resend… puts the email and/or SMS of the month's transfers back into the senders' queue: the same message, link and address as the first time. Not sent: a message the shop chose not to send, one still waiting in the queue, a transfer resent in the last 30 days (here, by Resend link or by the shop) or first sent less than 7 days ago, an address the validator found dead.

Month Not accepted Emails to send SMS to send Resend Not sent

Resend jobs

TimeUserActionTargetJustificationIPDetailsRevert
UsernameRoleStatus2FACreated

How to use the Customer Support Dashboard

Every order paid through Stripe lands here. Once a day, the system (a Lambda function) automatically picks orders up from here and creates them in Shopify. This panel is for seeing what's happening, fixing an address before an order ships, cancelling an order that shouldn't go out, and checking who paid and how much.

Two senders, same rules (once a day at 09:00 UTC, orders older than a day). Orders paid through a Stripe Payment Link are sent by the Lambda. Orders from the site's new checkout (the product cell says "new checkout") are sent by the internal sender built into this panel — the strip above the Queue shows when it runs next and how its last run went. The internal sender also checks Stripe right before sending: if the payment was refunded or disputed, the order is put on hold for a person to decide instead of being sent.

Staging only (the test copy of this panel, never the live one): super-admins also get buttons in that strip — Run intake now, Send ready orders now and Send all now (ignore the 1-day delay) to run the internal sender by hand, and — where Cancel & refund is switched on — test orders for Cancel & refund (Not in Shopify, In Shopify (unfulfilled), In Shopify (fulfilled)). A test order is a Stripe test payment plus, optionally, a Shopify order tagged TEST; Delete test order removes it when you're done.

The menu

The sections are in the column on the left; on a phone the column opens with the ☰ button in the top left corner, which also names the section you're in. Two buttons of the main menu are groups. Organizations gathers what every organization goes through, whatever form it applied with: the Applications of all the forms, the Organizations themselves, Shop employees, the Letters they get and, for super admins, the Samples kits and the Shopify connection. Free microchips gathers what is only the Free Microchip Program's: Chip orders, Program settings (SKUs & stock and Settings) and Program feedback (its applications are in Organizations → Applications with the others'). Click a group, and the column shows its sections instead of the main menu — Back returns to the main menu. While one of its sections is open the column stays on them, and in the main menu the group is marked as where you are. A group's number is the sum of the numbers on its sections.

Every change asks why

Every button that changes a customer's data asks for a justification — three fields:

  • Explanation — what you change and why: what the customer asked, what you checked;
  • Customer's request in the helpdesk — the link to the ticket or chat;
  • Escalation in Slack or Jira — a link, when there is one (optional).

A plain admin must fill in the explanation and the helpdesk link; for a super-admin all three are optional. A link must be a full https:// one. That covers editing an order's address; Clear error & retry; cancelling, reverting or deleting an order record; a refund and Cancel in Shopify; Unlink, Mark stolen / Not stolen anymore, Cancel transfer, Cancel subscription, Resend link and Merge in Customer Search; approving or dismissing an application; editing an organization; the record actions (change owner, organization, premium, delete account); Return to organization, Surrender to a shelter and Edit registration; and a revert. Nothing is changed without what your role requires.

The justification goes to the Audit log (its own column, and the log can be searched by it). The changed record itself keeps the value it had before its first change in <field>_bkp (a later change never overwrites it) and, in <field>_upd_comment, the links of the latest change with who and when, as the team does by hand — only the page of a HubSpot ticket or conversation, a message in our Slack or a Jira issue (what follows ? or # is left out; a search, a board or any other page is not put there — its text can be a customer's email or phone), and not the explanation: the site shows records to anyone who asks (any other link stays in the log, and the comment says so). Every change in full is kept in the database next to it (the upd_history collection), and a super-admin can undo most of them from the Audit log (Revert, below); an admin can undo the operations of support's tools there (Return, Surrender, Edit registration, photos). Deleting an account is the one exception: the person's own data is not kept in the records, the backups or the change history (the site's own logs and this panel's audit log of earlier actions are not rewritten).

Queue tab

Orders that have not been sent to Shopify yet.

  • Edit address — fix the shipping address, name, email, or phone. This is a real edit: this exact data is what gets sent to Shopify once the order ships.
  • Under each status: sends <date> · via Lambda or via internal sender — when the order goes to Shopify and which sender takes it.
  • Cancel shipment — cancel the order. It will not be sent to Shopify. The order isn't deleted — it moves to the Sent tab marked "Cancelled", so the history is always visible and the order can be brought back if needed. Right after cancelling, the Cancel & refund window opens: choose a full refund, a partial refund or no refund of the customer's payment.

Order status in the queue:

StatusWhat it means
WaitingThe order is fresh (created less than a day ago) — the system isn't touching it yet, that's normal, it's just too early.
Ready to sendA day has passed, the order is waiting for the next automatic run — it will be sent on its own, nothing to do here.
Sending…New checkout only: the internal sender is creating this order in Shopify right now. Editing and cancelling are blocked for that minute.
Outcome unknownNew checkout only: Shopify didn't answer clearly (timeout, server error), so the order may already exist in Shopify. It is never re-sent blindly. Clear error & retry first looks the order up in Shopify: found — it's marked as sent; not found — it goes back to the queue.
Refunded — on hold
Disputed — on hold
New checkout only: the payment was refunded (or disputed) in Stripe before the order shipped. Cancel the shipment, or Clear error & retry to send it anyway.
New checkoutAn order of the new checkout. You can cancel its shipment here; refunds, address edits and everything else are done by a new-checkout administrator.
ErrorClick the badge to see why it failed in plain language, jump straight to Edit address with the likely problem fields highlighted, and clear the error once it's fixed. Clearing it doesn't send anything itself — the Lambda already retries automatically on its next run regardless, this just resets what the badge shows.

Sent tab

Orders that have already been processed — either genuinely sent to Shopify, or cancelled by hand.

  • The Shopify column — if the order was actually created in Shopify, you'll see a link like #12345678. Click it to open the order in Shopify in a new tab — that's how you "go to Shopify".
  • If it says Cancelled instead of a link — the order was cancelled in this panel (the Cancel shipment button on the Queue tab), it was never created in Shopify at all.
  • If it's just a dash "—" — the order is marked processed but has no saved Shopify link (usually older records, from before that was saved).
  • via internal sender under the link — the order was sent by the panel's own sender (new checkout), not the Lambda.
  • TEST — deleted (staging only) — a test order: it was really created in Shopify with the TEST tag and deleted right away, so there's no link. TEST still in Shopify! means deleting it failed — delete it in Shopify by hand.
  • For genuinely sent orders — Delete record: hides the record in this panel, to keep the list tidy. It stays in the database (the justification in the audit log), and the actual order in Shopify is not touched. (A new-checkout record could never be erased anyway — the internal sender would find the payment in Stripe again and send it a second time.)
  • For cancelled orders — Revert: puts the order back in the queue, as if it had never been cancelled. The system will pick it up and send it next time around. Not available once the payment was refunded or the order was cancelled in Shopify — the tag would ship for free.

Cancel & refund

Cancelling an order and giving the money back is one flow here, so the refund can't be forgotten. Open it with Cancel shipment (Queue) or Cancel / refund (Sent). The window re-reads the payment in Stripe and the order in Shopify every time and shows the next step:

  • Not in Shopify yet — the order is already cancelled in the queue; only the refund is left.
  • In Shopify, not fulfilled — Cancel in Shopify cancels it there; the customer gets Shopify's cancellation email. Cancelling in Shopify does not return money — the payment went through Stripe, so refund it below.
  • At Flexport — cancelling in Shopify alone does not stop Flexport. Ask Flexport to cancel sends Flexport a cancellation request; Flexport answers later — press Refresh, and once it accepts, cancel the order in Shopify. If the panel can't see the Flexport status, cancel it in Flexport by hand.
  • Already fulfilled — it has shipped; Shopify is not touched, only a refund is possible.

The steps in Shopify and Flexport are a super admin's; a plain admin's window shows the state only.

Your limit and requests: a plain admin refunds on his own up to his limit on the payment — the window says Your limit on this payment: … · used … · left … (a super admin sets the limits in Shipments settings → Refund rules). Above it the button becomes Request approval: write the reason, and the request waits for a super admin in Shipments → Needs super admin; no money moves until then. One open request per payment. The window shows its state (waiting, approved, declined with the comment), and its author can Withdraw it while it waits. A super admin refunds without a limit, decides requests there — Approve, Change amount & approve, Decline with a comment — and repeats a refund Stripe refused with Retry refund.

Refund: full (whatever is left of the payment), partial (an amount in the payment's currency — USD, AUD or CAD — never more than is left) or no refund. The justification is asked for every time. A double click never makes two refunds. Every step, including errors, is in the Audit log and on the record itself; each refund is also posted to Slack. A failed refund shows as Refund failed — the cancellation itself stays.

Subscription: if the purchase started a monthly or annual subscription, the window shows it and its status. A refund on its own does not stop it, so a full refund cancels the subscription right away — no more charges, and the site moves the pet back to its previous plan. For a partial refund, tick Cancel the subscription too (off by default); a partial refund of everything that is left counts as full. If the refund went through but the subscription was not cancelled, the window says so and Cancel subscription now tries again. A full refund made in Stripe Dashboard cancels the subscription too — the site does it.

Cancel the subscription without a refund: the same window has Cancel at period end — the customer keeps the plan until the period they paid for ends, then Stripe stops the subscription and the site moves the pet back — and Cancel subscription now, which stops it right away (no money is returned). Open it from the Payments tab (Cancel subscription on the payment's row) or from Cancel / refund in Sent.

Badges on an order after a cancellation or refund (Sent tab and Payments):

BadgeWhat it means
Refunded 12.50 USDThis much of the payment was returned to the customer through Stripe. In Payments the sum is read from Stripe itself, so it includes refunds made in the Stripe Dashboard (a line next to it says how much of it); if Stripe doesn't answer, the row says so (Stripe did not answer) and the refund badge is this panel's own record — refunds made in the Dashboard are not in it. Hover over it for each refund: amount, who made it, when and why.
Refund in progressA refund was just requested and Stripe hasn't confirmed it yet — wait a moment and reload.
Refund outcome unknownStripe didn't answer whether the refund went through. A super-admin opens Cancel / refund — the window checks Stripe and settles it. It never refunds twice.
Refund failedStripe refused the refund; no money moved. The cancellation itself stays.
No refundA super-admin cancelled the order and deliberately chose not to refund (the reason is in the tooltip).
Cancelled in Shopify Oct 3, 2026The order was cancelled in Shopify too, on that date (the customer got Shopify's cancellation email). A cancelled order in Payments also says Order cancelled <date> (<who>) under its status.
Flexport: cancel requestedFlexport was asked to stop the shipment and hasn't confirmed yet.
Shopify cancel failedCancelling the order in Shopify didn't work (the reason is in the tooltip) — the order is still live in Shopify. A super-admin opens Cancel / refund and tries again, or cancels it in Shopify by hand.
Subscription cancelled Oct 3, 2026The subscription this purchase started was cancelled on that date, after the refund — it no longer charges.
Subscription ends Oct 31, 2026The subscription was set to end at the end of the paid period, without a refund — it charges no more after that date.
Subscription NOT cancelledCancelling the subscription failed (the reason is in the tooltip) — it keeps charging. A super-admin opens the payment's window (Refund or Cancel subscription in Payments, Cancel / refund in Sent) and cancels it again.

Shipments: what you can change before the warehouse

A shipment that is Scheduled or Blocked and not yet sent to the warehouse can be changed from its card (Shipments → click the row). Once it is sent, the card says Just sent to Flexport — use Recreate. Every window asks the three fields (explanation, helpdesk link, escalation link) and shows a confirmation with the result in one sentence before anything is saved; Back keeps what you typed. Notify customer is on by default: the customer gets «Order updated» or «Order cancelled» in their language. If someone changed the shipment meanwhile, the window says Updated by … at … — reload to see changes. A super admin can undo a change with Revert in the Audit log while the shipment is still before the warehouse.

  • Ship now — sends it in the next cycle instead of waiting for its release time. In the list, tick several Scheduled rows and press Ship now (N): rows with a blocking alert are skipped and named in the result.
  • Edit address — name, phone and the address by parts with Google's suggestions; Check address asks Google before saving (Verified, «Did you mean …?» with Use suggestion / Keep mine, or an error). A wrong street keeps the shipment Blocked (A-02) until it is fixed or you press Ship to this address anyway.
  • Edit email — the email this order's letters go to (the customer's account does not change).
  • Edit items — another variant of the same product, fewer, Remove, or a free item (Goodwill, Our error, Other). Removing an item can refund its value — the smaller of its refund value and what the customer paid for its line. Removing the last item is a cancel.
  • Change warehouse — the list says why a warehouse can't take it; your choice is pinned to the shipment.
  • Merge with… — two shipments of one customer go in one package: the window compares them (Same / Different) and asks whose name and address to ship to. Unmerge on the package gives the order back its own shipment; if the package's address changed after the merge, the window says where the order goes back to. Keep separate (A-15) and Keep both (A-16) answer the system's merge suggestions.
  • Cancel… — the whole shipment or selected items, and for each payment: a preset, Full, Item values, Custom amount or No refund, and the subscription (Keep, Cancel now, at period end). Above your limit on the payment the button becomes Request approval: write the reason, the cancel happens now and the refund waits for a super admin.
  • Cancellations & refunds on the card lists each refund of a cancel: Retry refund after Stripe refused it (the same amount, never twice), Request approval for one that Needs approval.

No ticket — system alert / internal is offered only when you act from an alert's own button (Fix address, Ship anyway, Keep separate, Keep both, Merge, Retry refund): the explanation is still required. When a customer deletes their account, the shipments of their orders lose their name, address, phone and email — at once, or right after shipping if the package has not left yet — and no more letters go to them.

Shipments at the warehouse: statuses, alerts and buttons

Once a shipment is sent, its status is the warehouse's: Sending (we are talking to the warehouse), Retrying (no answer yet — it tries again by itself, up to 3 times), At warehouse, Cancelling (we asked the warehouse to cancel and wait for its answer), Shipped / Partially shipped (with the tracking), and Replaced (a Recreate made a new shipment; the old one stays in the Cancelled and All tabs and says Replaced by SH-…). The card shows the warehouse, its mode (Test is a rehearsal — nothing real is shipped), the order number there, the warehouse's step, the packages with Copy and Track ↗, and the time of the next check. Related shipments link to the other shipments of the same payment.

An open alert is a box at the top of the card, in plain words, with its own buttons; if there are several they share one box, the blocking one first. A red box blocks the shipment (its buttons are the only way on); a yellow one only tells you something. In the list the row's badge says the alert's code and name, and the row's button is the box's first one — it opens the same window.

AlertWhat it means and what to press
A-07 Warehouse errorThe warehouse refused the order; the box says why in our words and repeats the warehouse's own text. The main button depends on the reason: Fix address & recreate (the address was not accepted), Choose another warehouse & recreate (an item is not stocked there), Recreate (anything else). Wrong product data at the warehouse is for a super admin: Open Products for a super admin, Copy shipment number to pass it on for an agent. Cancel… is there too.
A-08 Warehouse unavailableNo answer after 3 tries; we don't know if the order was created. Check status asks the warehouse by our shipment number. If it says the order is not there, Retry appears and sends it again; if it is there, the shipment becomes At warehouse. Recreate is not offered until then (it could create the order twice). Cancel… is.
A-09 Sending stuckNo answer for 10 minutes after the last try. Check status.
A-17 Cancel request needs a replyA cancel did not work (the warehouse refused, or it shipped meanwhile): reply to the customer within 1 business day — the box counts the time left. Refund from Cancellations & refunds or Payments. (Mark as answered comes later.)
A-18 Cancelling too longThe warehouse has not confirmed the cancellation in time; the box counts the time left to reply to the customer (1 business day from the alert; Saturday and Sunday do not count). Check status asks it again. Stop cancelling returns the shipment to At warehouse. Mark as cancelled (super admin only, with the ticket number) is for when the warehouse's support confirmed the cancellation by email — the refund then goes ahead.
A-19 Cancelled by warehouseThe warehouse cancelled the order itself (the reason is in the box). Recreate makes a new shipment (nothing to cancel at the warehouse); Cancel & refund… cancels it for good.
A-20 BackorderEFS is waiting for stock. It clears by itself when the item ships; Recreate on another warehouse moves it.
A-21 Held by warehouseThe warehouse put the order on hold (the reason is in the box). It clears by itself when the hold is lifted; Recreate or Copy warehouse order no. to quote it when you contact the warehouse.
A-22 No tracking 48hAt the warehouse for 2 days without a tracking number. Check status reads the order again; Copy warehouse order no. is for the email to the warehouse. It clears by itself when the tracking arrives.
A-25 Customer email problemThe "Your order has shipped" email could not go (no valid address, or it bounced). Edit email (tick Resend the last email to send it again at once) and Resend email.

A-10 Release cycle stopped is one red box over the whole list, for everyone: shipments aren't being sent — sending is switched off, the cycle hasn't run for 30 minutes, or shipments are overdue. Tech has been notified; there is nothing to press. It goes away by itself when sending works again.

  • Check status — asks the warehouse now and shows its answer in the window; Check again after says when it is worth asking again. It is offered with A-08, A-09, A-22 and while Cancelling.
  • Retry — only after Check status proved the warehouse has no such order.
  • Recreate — for a shipment at the warehouse: the address, items and warehouse to change (or none); the warehouse is asked to cancel its order, then a new shipment goes out in the next cycle and this one becomes Replaced. It does not refund removed items — refund them from Payments.
  • Cancel… at the warehouse — the warehouse is asked first; the refund happens after it confirms.
  • Resend email / Edit email at the warehouse — the shipping email by order; Edit email keeps working on a Cancelled shipment while A-25 is open.

Payments tab

Every payment in one list, newest first — who paid, for what, and how much. Every admin can read this tab (the new checkout's payments and renewals too); the Refund, Cancel subscription, Sync now and test buttons are the super-admins' — a plain admin doesn't see them, and the server refuses them. A payment that must be refunded: a super-admin can refund it from Payments. For a plain admin it is read-only: both kinds of payment (first payments and renewals), the refund sum and the cancellation date as text, never a card number. Looking at it is logged, and opening the list and every search count in the same soft daily limit as Customer Search (as-you-type refinements of a search, opening the tab again within half an hour and turning to the next page don't):

  • First payments — the purchase itself (a tag, a plan with a tag). Its status is the order's: Paid & sent In queue Send failed Cancelled — and for new-checkout orders also Sending… Outcome unknown On hold (the same as in the Queue: being created in Shopify right now; Shopify's answer was unclear; refunded or disputed in Stripe before shipping).
  • Renewals — everything a subscription charged after the purchase: each monthly or annual renewal (Renewal · monthly), and the extra paid when the customer switched plans (Plan change), with the period it paid for and the subscription and invoice numbers. Status Paid. The panel copies them from Stripe every few minutes — the line above the list says how often and when it last did, and Sync now fetches them right away. The search box finds them by name, email, phone, subscription (sub_…) or invoice number too.

Refund badges from the table above show under the status. On every row, Refund opens the payment's window: full or partial refund, and for a payment of a subscription the subscription itself (a full refund cancels it, as above). A first payment that is still in the queue says Cancel & refund — the shipment is cancelled first, so the tag does not ship for free. Cancel subscription opens the same window at the subscription, to cancel it at the end of the period or right away without a refund.

Support requests and Agent requests tabs

Super-admins only, two tabs with the same buttons, each with its own red number: Support requests are asked by the support team, Agent requests by the AI agent. An AI agent can look things up and prepare changes, but a refund (an order or a renewal), a Shopify cancel and an account deletion it can only ask for. The asks wait here; nothing happens until a person decides. The list shows Waiting requests, the oldest first; the box above it switches to All (the latest 100, the newest first).

  • Approve… — shows what will be done, as the system read it when the agent asked, and the agent's reason. The operation then runs at once, as you; the Audit log shows that the agent asked and that you approved. If the order or account changed after the agent asked, nothing is run and the request says Not run — changed since. To delete an account you type its e-mail first.
  • Reject… — asks for a reason (3 to 500 characters); the agent can read it.
  • Retry… — only for Result unknown (the answer of Stripe or Shopify was lost, or the deletion did not report back). It first checks whether the operation already happened, so a refund is never made twice.

A refund needs refunds to be switched on in this admin, like the Refund button. Requests about the new-checkout orders are shown only to those who see that checkout elsewhere. Every request stays in the list with its result.

Search boxes (Queue, Sent and Payments)

These tabs all have a search box up top — it searches by customer name, email, or phone within that tab's own list.

Customer Search tab

A different kind of search: this one looks up a person or pet across all of findpet — not just Stripe orders. Use it to answer "who is this microchip/tag/email/phone registered to, what pets do they have, and were any pets transferred?"

  • Five separate search boxes at the top: Tag, Microchip ID, Email, Phone, Name. Fill in the one you have and press its own Search button (or Enter).
  • Results are grouped the same way every time: owner → their pets → each pet's transfers, shown as cards.
  • Email and Phone also look at a pet's extra contacts — the card shows them as Other contacts, so you can see why the pet was found.
  • A pet with no matched owner still shows up, under "Pets without a matched owner" — that happens when the owner account was deleted or the pet was never linked to one.
  • A transfer with no matched pet shows up under "Transfers without a matched pet" — the contact info matched, but we couldn't tie it back to a specific pet record.
  • Addresses link out to Google Maps; pet names and organization names link to their page on findpet.com.
  • A search by Pet link takes what a customer sends: findpet.com/r/… with or without https:// and www., the Spanish /es/r/… form, a link with ?… or #… after it, or just the part after /r/. Another site's link, or another page of findpet.com, answers "Not a findpet pet link". A link of a duplicate that was merged shows the main record; the link of a pet that was surrendered to a shelter shows the original and, on its card, Surrendered to … open it — the shelter's copy (and the copy says Made from). A link …/#search/link/<slug> that comes from outside (the dispute e-mail has one) opens Customer Search with the link already in the box — press Search: a page cannot make the panel look a customer up by itself, and the search is logged and counted like a typed one. A link on a card of the panel itself (open the shelter's copy, History) searches at the click.
  • History on a pet's card (every admin) shows who had the pet and what was done with it, oldest first: owners, transfers, returns to an organization, surrenders, edits, disputes — read from the panel's and the site's own records, nothing is stored on the pet. A deleted account is shown as "account deleted"; where records start later than the pet, it says Transfers before … were not logged. Looking at it is logged.
  • The small buttons on a card say what they do when you hover over them (and a screen reader reads it).
  • A search by Tag shows the tag's own card: its PIN, whether it is activated, and its Status. findpet.com and the app use a tag only while it is available; any other status means it is out of use — scanning it shows "not found" and it can't be activated. Deactivate tag… on that card (every admin) takes it out of use and unlinks it from its pet, if it has one — for a lost or stolen tag, or a tag that must never be linked again. A pet that only has a stale copy of its code shows up in the same results: unlink it with its own Unlink. A super-admin can revert it.
  • Super-admins see a confirmation link on a transfer that is still open — the page where the new owner accepts the pet, the same one they got by email/SMS. Handle it like a key: whoever opens it while logged in on findpet.com and presses accept gets the pet. Never press accept yourself; give it only to the new owner (or use Resend link…, which goes to their email/phone). Finished or replaced transfers have no link.
  • Finder data request (under the search boxes): a person who found a pet asks to delete their data. Type the phone or the email they give and press Find: the window lists their scans and messages, newest first. Exact matches are ticked; a possible match (the same last 10 digits under another country code) is shown but can't be ticked; a hotline message that is still being delivered waits. Untick what is not theirs, type the phone or email once more and the reason, and press Delete finder data: their name becomes «Deleted user», their phone, email, message, place, photos and the texts of the letters with them are removed; the records stay. It cannot be undone.

Every search you run here is logged (who searched, which field, what value) — this is sensitive customer data, so don't go searching around out of curiosity. There's also a soft daily limit per person (searches here and in Payments, and opening Payments, count together); going over it doesn't block you, it just quietly flags it for review.

Resend link… on an open transfer (everyone can use it) sends the new owner the transfer email again — the very same email, with the same link to accept the pet — and, if you choose Email + SMS, the text message too. The window shows what was sent and where; the SMS option only appears if an SMS was really sent the first time. If there's no email to resend (the address failed validation) but the SMS went out, you get SMS only instead. Nothing is sent from the panel itself: the message goes back into the queue and the regular sender delivers it within a few minutes. It's a real email/SMS to a real person, and it's logged — only use it when the person asked for it.

Possible duplicates (everyone can merge). When you search by email, two records that look like one pet entered twice — typically the shop registered the microchip and the owner then registered the pet again with a tag and photos — are shown side by side at the top, with why they look alike. Merge… opens a window of two steps:

  • Which record stays (the main record) is decided for you and the window says why: a shop's or shelter's record first, then the one with the microchip, the paid plan, the tag, photos; otherwise the older one.
  • Step 1 lists the fields where the two differ: what the main record has now, what the duplicate has, and which one stays. By default the main record keeps what it has and takes what it's missing; for photos you can also keep Both. The duplicate's tag, microchip and paid plan move to the main record — scanning the tag then opens it.
  • Step 2 shows the main record as it will be after the merge (values from the duplicate highlighted) and what moves. Nothing is changed until you press Merge there; Back lets you change your choices.
  • Backup plan — what the organization keeps is shown on both steps when either record belongs to an organization or has a plan. Of two records of one organization the main record gets what it lacks of the duplicate's partner pet id, SMS alerts phone and Registered until date, and the SMS plan stays with it; every row says where its value comes from (the main record, the duplicate or none). The duplicate loses these fields either way — what it could not give is kept in its merge backup. The record id the organization uses is the one the organization's partner API knows the pet by; if that is the duplicate, the line says it stays merged. The organization's old record (created through the partner API, already inactive) can be merged into the owner's published record of that organization: the previous owner's account, contacts and address are not moved and stay on the old record. The previous owner's SMS alerts phone is not moved either: the block shows the number and says it is kept only in the duplicate's merge backup (the old record loses it). The SMS plan of the duplicate still moves to the main record; when there is nothing to choose, the Plan row says so instead of offering a choice.
  • Merge with another record… is on the pet's card (every admin). The window lists the records that have the same microchip, with the id's last six characters, the type, the owner or organization and the creation date; a record that can't be merged is grayed out and says why (already merged, inactive, a saved search). If the one you need is not there, paste its link (findpet.com/r/…) or its 24-character id and press Find; Next opens the two steps below. Looking records up counts in the daily limit of Customer Search — over it you are not stopped, a developer is told. After you assign an organization's pet (or the new owner accepts an invitation for it), Merge now opens the same window for the new owner's other record with that microchip. While it merges the button says Merging….
  • After the merge the duplicate is deactivated, not deleted: the owner no longer sees it on findpet.com or in the app, and it disappears from this search. The main record's card shows Merged in with its name and date. If a merge was wrong, a super-admin can revert it from the Audit log (the duplicate comes back as a record of its own); everything is kept and logged. Merge starts from the Possible duplicates pairs after a search by email, from Merge with another record… on a pet's card (records with the same microchip, or a link or id) and from Merge now after a pet is given to an account (every admin).
  • The window refuses a merge it can't do safely and says why: two different microchips or tags (unlink the wrong one first), an active subscription on both pets, a pet in a transfer, records of two different organizations, records of two different people (no shared account, email or phone) or of two different owner accounts (one of them would lose the pet). A search by an email or phone only the duplicate had still finds the pet — its main record. If someone changed either record while the window was open, it reloads instead of merging. Two more refusals: a published record the organization's partner API manages by its own id (it would be hidden — ask a super-admin, data fix), and the organization's old record that belongs to another owner when the two records share no microchip, or that carries the previous owner's paid plan or subscription (ask a super-admin, data fix).

Every admin also sees these buttons on a pet's card:

  • Edit registration… — changes what the owner could change on findpet.com, on the owner's request: the name, type, breeds, colors, gender, age, date of birth, size, coat, in/outdoor, description; the photos; and the pet's own contacts (name — or the organization name —, email, phone, extra emails and phones, address, show phone). The window shows only what you changed, Now → After. It does not change the owner's login (the account's email and phone — the owner does that at findpet.com/dash/profile), the microchip, the tag, the record type or the organization. Photos: Upload a photo and Remove are saved at once (the file stays on the site, it just leaves the pet; the photo search index follows); Make main is saved with Save changes. The photos of pets imported from PetPoint and RescueGroups are shown as pictures too (they stay on those services' servers — g.petango.com and cdn.rescuegroups.org, and no others); a photo from any other website is only a link, external photo ↗. Changing contacts needs How ownership was verified. It also emails the previous owner (see below). A phone is the standard phone field: pick the country from the flag menu, type the number (only digits and the usual signs go in), and a number that is not valid is marked when you leave the field; a phone you do not touch stays as it was; the address offers Google suggestions to every admin, and picking one also moves the map point. An address typed by hand keeps the old map point only while the city, postal code and country are the same and not all empty; otherwise the point is removed. A pet that a PetPoint or RescueGroups import keeps in sync (no owner yet) shows a warning that names the fields the import writes over on its next run — change them at the source too.
  • Return to organization… — gives a pet back to the organization it came from (every admin; another organization is a super-admin's choice). See below.
  • Surrender to a shelter… — hides the pet from its owner and gives a copy of it to a shelter or rescue. See below.
  • Unlink next to a Tag — detaches it from that pet. The tag becomes free to link to a different pet.
  • Deactivate… next to a Tag — detaches it from that pet and takes it out of use: scanning it shows "not found" on findpet.com and in the app, and it can't be activated again. Only a tag record linked to this pet; if the record is linked elsewhere or to no pet, the panel says so and changes nothing — search by the tag and decide there.
  • Cancel transfer — cancels an in-progress ownership transfer and restores the pet's original owner info; a person's own pet stays in their account. Shown only on the pet's current, still-open transfer: an older transfer that was already accepted, cancelled or replaced (for example by the shop through the partner API, or from the site's dashboard) shows neither Cancel transfer, Resend link nor a confirmation link — and the panel refuses to cancel one even by a direct request (the new owner keeps the pet).
  • Mark stolen… next to the Report type — the pet becomes Lost, marked stolen, as a shop marks it through the partner API: findpet.com shows "reported as stolen" on the pet's page and its tag page, and the AAHA microchip lookup shows the pet. The type it had is kept. Not stolen anymore… takes the mark off and puts that type back (a pet marked by hand without it stays Lost — the window says so). Not offered for a found or seen pet, a saved search, a pet in a transfer (cancel the transfer first), a merged or removed record.

Super-admins only also see a few more — these change real customer data, so think before clicking:

  • Unlink next to a Microchip — detaches it from that pet. The chip stays in the organization's inventory, free to link to a different pet.
  • Cancel subscription — shown on a pet's card only when it has a real recurring Stripe subscription (monthly/annual — a lifetime tariff is a one-time payment with nothing to cancel). Pick at period end (the usual choice — the customer keeps access until what they already paid for runs out, then it lapses on its own) or immediately (access ends right now). Either way this calls Stripe for real; the subscription's own webhook is what updates the pet's tariff back to free once it actually ends. The justification also goes to Stripe, as the cancellation comment.

Record actions — buttons at the bottom of a card. They do what support used to do by hand in the database. Remove premium…, Delete account… and Deactivate pet… are for every admin, and so are Return to organization…, Surrender to a shelter…, Change owner… and Edit registration… (above); Change organization… — for super-admins. Each opens a window that first shows what changes (Now → After) and what stops it; only Confirm, with the justification, changes anything. If the records change while the window is open, it checks again instead of writing.

  • Change owner… (a published pet of a person) — the button is Change owner / Transfer… while invitations are on — gives the pet to another FindPet account, found by its email, without the new owner accepting it.
    • Only a super-admin gives a pet directly. A plain admin who opens the window is told so: "Only a super-admin can give a pet directly. Ask a super-admin." The pet is not looked at and no account is searched.the window shows only the invitation (below) — there is no Assign now for him.
    • What it does: the window makes a new record of the pet for the new owner. The description, photos, microchip, tag and paid plan move to it; it gets the new owner's name, email and phone (and their address, if you tick the box — it is there only when the account has an address); the old owner's extra contacts are not copied.
    • The old record stays as a backup: out of service, with the chip, tag and plan taken off. Its card shows Deactivated · given to another account with a link to the new record; the new record's card shows Owner changed from record …. The purchase history and the free certificate stay on the old record (the window warns). Its card has no Edit registration… and no Change organization…: a change made to a backup would come back with the Revert.
    • Refused for every role: a pet linked to an organization (use a transfer — the organization starts it, not this panel — or Return to organization…), a record that is not in service, a lost, found or stolen record (use Edit registration… / Not stolen anymore… first), a pet with an open invitation or transfer or another change in progress, and a pet with a Stripe subscription, a Payment Link plan or a lifetime plan (cancel the subscription in Payments first, or use a transfer). The window says why and its button is off.
    • No button on the card at all: a sighting, a reunited record, a shelter's copy made by a surrender, and the backup of an earlier give (open the current record from its card).
    • The new owner needs an account first: if the window says no account uses the email, ask them to sign up at findpet.com with that exact email, then press Check again.The new owner does not need an account first: if the window says no account uses the email, it offers to send an invitation (below). If several accounts use the email, the window lists them (name, email, since when, how many pets) and you choose one.
    • Fill in: the Explanation (required of a super-admin here, the other two links are optional), How ownership was verified and How the previous owner was told. FindPet does not email anyone about it, the previous and the new owner included — tell them yourself.
    • Undo it from the Audit log (Revert…, super-admin only): the new record is taken out of service and the old one goes back as it was; it is refused, with the way to a /data-fix, if the new record was changed, given on, merged or deactivated, a plan or tag was bought for it, or an account was deleted. Older Change owner rows (the same record, a new owner) are undone as before.
  • An organization's pet in an open transfer (a super-admin, with a required explanation; a plain admin's window says Only a super-admin can assign this pet. Use Resend link… so the new owner accepts the transfer.; the card shows the organization and the record type Transfer, no owner) — the same Change owner… window gives it to the account you check. The window shows Closes (the organization's transfer, with its date — it was never accepted) and Stays with the pet (only what the pet has: the organization, the SMS plan, the registration's end date, the partner pet id). The pet gets the account's name, email, phone and address, or none of an address — there is no box to tick. Nobody is emailed, the organization and the new owner included — tell the new owner yourself; How the previous owner was told is not asked. A warning says the organization can still take the pet back through its own system at any time; another says if the organization is paused for unpaid invoices (you can still go on). It is refused while the organization's request about this pet is still being processed (try again in a few minutes) or stuck (ask a super-admin), when the pet's transfer record does not match (a super-admin fixes the data), and while this is switched off. There is no Revert for it: the way back is Return to organization…. After Assigned the window shows Merge now when the new owner has another record with the same microchip.
  • An organization's pet that is not in a transfer (a shop's In store record, a shelter's Adopt record) is never given to a person by Change owner — the window says so. Ask the organization to transfer it, or use Return to organization… / Change organization. The same rule holds for Merge: such a record can be joined with the record that went to a person, never the other way round — the person's record stays and the In-store record is deactivated and loses the microchip.
  • Send an invitation (every admin; in Change owner / Transfer…) — gives the pet to a person who has no FindPet account, or to an account that should accept it itself. Check the email: if no account uses it, the window shows the form; if one does, a super-admin may choose Send an invitation instead of giving the pet at once; a plain admin has only the invitation. Type the new owner's first and last name, the phone (the standard phone field with the country menu; needed only for an SMS; a landline, toll-free or premium number is kept but cannot get an SMS, so only the email goes — or clear the phone), the language (English or Español) and how to send it — email, SMS or both. The new owner gets a message from FindPet Support with a link; they sign in or sign up on findpet.com and press Accept. Only then does the pet move to their account, as a personal pet (its tag, microchip, plan and organization stay); nothing changes before that. The link works 30 days. The previous owner gets one email when you send it (the window shows the address and the language): a new owner was invited, nothing changes unless they accept, and a link to dispute it. Write How the previous owner was told only when they have no email address. Refused (the button stays off): a lost, found or stolen record (mark it found or not stolen first), a sighting or a reunited record, a pet that already has an open invitation, a pet in a transfer, a plain admin's cases of Change owner (subscription, hidden record, organization's pet), and an email that is the current owner's. On the pet's card, Invitation shows the state (open, on hold, accepted by …, refused, expired, cancelled, no longer valid), the term, and how each message went — waiting, queued, sent (with Delivered: unknown — FindPet does not learn whether an email or SMS arrived or was opened), failed (Retry), or not sent after 15 minutes. Resend… makes a new link and a new 30 days: the old link stops working; the previous owner is not emailed again. Resend… goes to the same address and number, so it does not fix a mistake in them: if a message did not arrive or failed, check the address; if it is wrong, use Cancel invitation and send a new invitation with the right one. While the invitation is on hold there is no Resend…. Cancel invitation kills the link: nothing changes on the pet and nobody is emailed. If the previous owner disputes the invitation, it goes on hold until you press Resume or cancel it. Whoever opens the link and signs in can accept it (invited email: yes/no on the card says whether they used the invited address). After it is accepted, the audit log has a Change owner row (done by the invitation): undo it with Revert… like any Change owner — the previous owner then gets an email that it was undone. A pet that changed after the invitation (another owner, status, type, stolen mark, organization or a transfer) says no longer valid to the new owner.
  • Return to organization… (every admin; a pet that came from an organization) — the pet stops being its owner's and goes back to the organization it is in or has been with (the window lists them; another organization — super-admins). It gets the organization's record type (a shelter's and rescue's pets are Adopt, a shop's are "in shop", a clinic's "in vet"). Tick the box to put the organization's contacts and address on it. Write How the owner was told.The previous owner gets an email that the pet was returned, with a link to dispute it; the window shows the address (the account's and the pet's) and lets you choose English or Español. Write How the owner was told only when they have no email address. The previous owner no longer has the pet. A pet with an active subscription is refused for a plain admin ("needs super-admin: subscription"); a super-admin gets a warning to cancel the subscription, or it keeps charging. A hidden pet is not returned by this window, for anyone — a super-admin included: a deactivated, merged or removed record would become visible again. Undo its Deactivate pet row in the Audit log first (a super-admin). A pet in a transfer, or of a paused shop, is refused too.
  • Surrender to a shelter… (every admin; a pet of a person) — the owner's record is deactivated and the shelter gets a copy of the pet without an owner (name, photos, description; the chip and, if you choose, the tag move to the copy; no partner token, no billing history). Find the shelter, rescue or volunteer organization by name, city or org_id: only the ones somebody manages on FindPet can take a pet; a result shows Imported from RescueGroups · Managed on FindPet if an import also keeps it — that import may list the pet again. Write How the owner and the shelter were told.The previous owner and the shelter get an email each (the window shows the addresses and the language of each); write How the owner was told only when the owner has no email address. A shelter with no address is only a warning. Same rules for a subscription as for Return. Not for a stolen pet, a pet in a transfer, a found/sighted animal, or a pet that a PetPoint or RescueGroups import keeps in sync (change it there). A copy with no owner can be surrendered again.
  • FindPet does not email the owner or the shelter about these changes yet — tell them yourself. This is about Return to organization, Surrender to a shelter and Edit registration; Change owner (above) sends no letter at all. The window asks you to write how you did. A letter from FindPet for Return, Surrender and Edit comes with the next release.
  • FindPet emails the previous owner after a return and a surrender, the shelter after a surrender, and the previous owner when the pet's contacts are changed (the email says what kind of contact changed, not the new values), and when you send an invitation (a direct give sends no email at all). Each email has the pet's name, what was done, the date, how to reach FindPet Support, and a link to dispute it — never what you wrote as the reason. The window shows the addresses and the language (English or Español); the addresses are FindPet's own records, you cannot type another one. On the pet's card, Emails of the last … shows where each email is: waiting, queued for sending, failed or cancelled. A failed one has Retry letters. An email that has not gone out for 15 minutes is reported to the team's Slack.
  • "I didn't agree to this". When the previous owner opens the link in the email and says so, the pet's card (the original and the shelter's copy) shows Disputed by the previous owner on … with their words and Revert… — the same window as in the Audit log; after the revert it says resolved: reverted. The Audit log gets a row dispute_received, and hello@ gets a message with a case number. Nothing is undone by itself.
  • Undoing support's operations. A return, a surrender, an edit and a photo change can be undone by any admin from the Audit log (a change of owner — by a super-admin only) (Revert… on the row): the window shows Now → After, refuses if the fields changed since, and lists anything the shelter changed in its copy. A surrender's undo gives the pet back to the owner and takes the shelter's copy out of service. Nothing is emailed by the undo either.The undo emails the previous owner (and, after a surrender, the shelter) that it was undone — only those whose email of the operation was queued; the window shows who and lets you choose the language. An email that was not sent yet is cancelled. An operation done without emails sends none. The audit rows of these operations show what changed, before and after, to every admin in the Details column.
  • Undo the unfinished surrender… (super-admins) — if a surrender stopped half-way (the Audit log row says incomplete; Slack gets an alert), this puts back what had been written. If the panel says the history is incomplete, a developer repairs it by hand (/data-fix).
  • Change organization… (pet) — moves the pet to another organization by its org_id. An organization's own pet also gets the new organization's record type, so it shows on its dashboard; a pet that belongs to a person only changes where it came from. Past invoices don't change. Not possible for a shop deactivated for unpaid invoices (either side), for a pet in a transfer, or for a record kept in sync with PetPoint (change it there).
  • Paid · nothing to ship in Payments — the owner moved a pet from a Monthly or Yearly plan to Lifetime on the site. The tag isn't sent again, so there is nothing to send to Shopify: such a payment never appears in Queue or Sent, and a super-admin can refund it from Payments.
  • Remove premium… (pet, or owner — then tick their pets) — takes the paid plan off the way the site does when a plan ends: back to the backup tariff (free, or SMS alerts if that was the backup). Not possible while a Stripe subscription is active — cancel it first, or Stripe keeps charging. A monthly or annual plan bought through a Payment Link may still renew in Stripe: the window warns you to check Stripe by hand.
  • Deactivate pet… (pet) — hides the pet at the owner's request (it died, was given away, the record isn't wanted): the owner no longer sees it on findpet.com and in the app, nobody finds it in search or by its photos, and the card shows Deactivated. Nothing else of the record changes. Its tag, in the same window: unlink it (the default), unlink and deactivate it (it stops working), or keep it on the pet (scanning still opens the pet's page). The pet's page still opens by a direct link — findpet.com doesn't check the status there. Not possible for a pet in a transfer (cancel it first) or with an active Stripe subscription. A super-admin can revert it.
  • Delete account… (owner) — deletes the account at the person's request, the same way the app does: name, email, phone, address, password and sign-in links are removed, they are signed out everywhere, their own pets disappear from the site and the app (without contacts, address or tags) — also the ones they adopted or bought from a shelter or a shop, their contacts are also cleared from the backups of pets that were theirs before, organizations' own pets stay. Type the account's email to confirm. It cannot be undone. Not possible with an active Stripe subscription or a pet in a transfer. A staff account (an organization's or findpet's role, or findpet's own FINDPET account) — super-admins only: the person would lose that access for good.
  • Change sign-in email… (owner; every admin, a super-admin for a staff account — an organization's or FindPet's role) — when the owner lost the mailbox they sign in with, or wants another one. Check first that the account is theirs (an ID, the last order, the pets' details — not just that they know the email) and write it in How ownership was verified. Type the new email and press Check: the window refuses an address that is not an email, the same as now, used by another account, recently changed on a FindPet account, or one that cannot get mail. It shows Now → After and what to know first — a Stripe subscription (Stripe keeps the old email), open transfers to the current email (the app will not accept them after the change; the link on the site still will), pets with the current email as a contact (ticked ones get the new email), letters to the current email that do not arrive, other accounts with the current email, sign-in only with Google, Facebook or Apple. Choose the language of the letters (English or Español). An admin's request waits for a super admin: nothing is sent until a super admin presses Approve… (on the account card or in the list above the search; Reject… needs a reason you will read on the card; nobody decided in 7 days — the request closes). A super admin's own request starts at once. You see both addresses in full. Nothing changes yet: once approved, the new address gets a link (it works 48 hours; Resend… makes a new one, up to 5 times) and the current address gets a notice with "I didn't ask for this". After the new address confirms, the email changes 24 hours later. Then the account is signed out everywhere, its password and its Google, Facebook and Apple sign-in are removed: the owner signs in with the new email and Forgot password (or Google with the new address). Both addresses get a letter. On the card, Sign-in email change shows the state, the terms (New York time), how each letter went and the disputes. If the current address disputes it, the request goes on hold: only a super-admin can Resume… it (after speaking to the owner), any admin can Cancel request…. Revert… gives the account its old email back for 30 days after the change (it is signed out and loses its password again; pets that got the new email get the old one). For those 30 days the old email is held: nobody can sign up with it or put it on a profile, and the account cannot change its email in its profile ("contact support"). A role or an organization the account got after the change is not taken off by Revert. A request that stopped half-way is Not finished: press Retry… before the date of Address held until — after it the old address is free and the undo is not offered; a disputed one is retried by a super-admin. A deleted account's change cannot be undone. A request that closed Not changed — the account changed or Cancelled after the change had started keeps the email, but sign-in was taken away: the owner was signed out everywhere and signs in again as before. A letter that failed has Retry while it still says something true (the current link of an open request, the notice before the change, the letters of a change or an undo).
  • Release reserve… (super-admins; on the card of a deleted account) — the old email of a changed account is held 30 days, also after the account is deleted. Search the old email: the deleted account's card shows Address held until …. Press Release reserve… only when the account was deleted at its owner's request and the owner of the old address — checked by you, written in How ownership was verified — wants to sign up with it before the 30 days are over. Otherwise the reserve ends by itself on that date. It is not offered for an account that is not deleted: use Revert… there.

Pictures: the pet's card, Merge and Change owner

How the windows look, step by step. Shot on a test stand with made-up people and pets — your screen shows the real ones. Click a picture (tap on a phone) to open it full size.

A pet's card in Customer Search with its support buttons at the bottom
The pet's card. The support buttons are at its bottom. Every admin sees Edit registration…, Return to organization…, Surrender to a shelter…, Change owner…, Merge with another record… and Deactivate pet…; Change organization… and the Unlink buttons next to the microchip and tag are for super-admins. The card has more buttons (Mark stolen…, History, Remove premium…) — this list is not complete.
Possible duplicates: two records of one pet side by side with a Merge button
Possible duplicates. Search by email: two records that look like one pet are shown side by side, with why they look alike. Merge… opens the window.
Merge window, step 1: the main record, the duplicate and the fields where they differ
Merge, step 1. On the left the main record (it stays), on the right the duplicate (it is deactivated, not deleted). The table lists only the fields where they differ; where a choice is possible, pick Main or Duplicate.
Merge window, step 2: the main record as it will be after the merge and what moves
Merge, step 2. The main record as it will be after the merge (values from the duplicate are highlighted) and what moves. The Backup plan block says what the organization keeps. Nothing changes until you press Merge here; Back lets you change your choice.
Change owner window after Check: the account found, Now and After, and the two required fields
Change owner… Type the new owner's email and press Check: the window shows the account it found and Now → After. Then write How ownership was verified (and How the previous owner was told, when the window asks for it) and confirm.
Change owner window for an organization's pet in an open transfer: the transfer that closes and what stays with the pet
An organization's pet in its open transfer. The same Change owner… button gives it to an account you verified (Assign now when invitations are on): the window says which transfer closes and what stays with the pet. There is no Revert for it — the way back is Return to organization….

Organizations → Applications

Every admin looks, super-admins decide. A plain admin sees the list and opens an application with View (read-only: the answers, the decision, the history); Verify, Reject, Dismiss and every other action are super-admins'. One review queue for every application form, newest first. Whatever the form, an application asks for the same thing: an organization on Findpet and a company in Shopify (it buys in the shop). Its type adds its own on top:

  • Shop / wholesale — a pet store / retailer or a distributor / wholesaler (the short wholesale form, or the Shopify shop's own form): it registers to buy — nothing more.
  • Organization — a shelter, a rescue, a vet and the like (Apply for Findpet Organization ID): it also gets its account on Findpet — its people manage its pets and see their owners' contacts; an integration (PetPoint, ShelterManager) is set up apart.
  • Free microchip program — Apply to Join Findpet's Free Microchip Program for Nonprofits: all of the above, and it joins the program and orders free chips (letter T2; T9 for an organization already on Findpet).

Under the type, where it came from: the page of the site (/register-organization, /wholesale, /Free-Microchip-Program), Shopify shop form (a company the shop's own application form made — the approval completes it, not a new one), or By Org ID (a program application of an organization already on Findpet).

Google form — Org ID form and Google form — Free microchip program mark the applications of Dan's Google forms (the sheets the team worked from before the site's forms), moved here once. They are worked like the others — the type above the source is the form's own, Verify and Review… are the same windows. Under block 1 of the window (Verify, Review… and View), the block Imported from Google form (row N), read only, shows the sheet's row: its number, the team's columns (Sent, Contacted by, Petfinder ID, Stripe ID, Findpet URL — a link, Activation status, Team comments), Organization created, and As typed — what was typed in the sheet and is not stored as typed (a phone that is no number, Same as above for the public address, a logo that is no link). An approved one is already linked to its organization; the open ones wait for a decision as usual.

  • Type filter — All types (the default) or one of the three, each with its count of the status shown.
  • Status filters — Open (waiting for a decision; the default), Approved, Rejected, Dismissed and All, each with its count. Rejected and dismissed applications leave the main list but are never lost: a decided row says who decided, when and why — a rejection's reason (the one the applicant read), a dismissal's explanation.
  • Search — a piece of the organization's name, an email (any of the form's), the contact's name, a phone typed any way (the digits are compared, the US +1 optional), an Org ID (typed in a program application or given at the approval) or the application's id (the one in the window's header and in the Audit log). The counts on the filters are of the search, so a match in another status or type is seen at once. Every search is in the audit log.
  • Registered · <Org ID> — a program application by an organization already on Findpet (the form's "Already registered?"): Review… opens the same window in its By Org ID form — the registration with its type, the Org ID and email typed, how the email compares; approving adds the organization to the program and creates nothing. The window also says whether the organization has its company in Shopify: if not (or its last link stopped), Link to Shopify… opens the same window as in Organizations — a step of its own, the program's approval doesn't wait for it. The program is closed to stores, distributors, volunteer groups and breeders (since 2026-10-12, the site no longer takes theirs): for such a type the window warns — reject it, or, if the type is wrong (shelter software registers organizations as pet_shop by default), fix it in Organizations → Edit… → Change type… first. A full program application of such a type sent before opens in Verify organization with Add to the program unticked and the same warning (a wrong type: Change type… there, then tick the box).
  • Open rows have Verify organization, Reject… and Dismiss… (see below). A Dismissed row can still be verified or rejected — if it was dismissed by mistake. Hover over any button to see what it does. Reject… and Dismiss… (outlined in red) never act on one click: the next window asks you to tick Yes, reject this application / Yes, dismiss this application, and its red button stays off until you do — Cancel closes it with nothing changed.
  • Approved rows show the organization's org_id with an Edit organization button (opens it in the Organizations tab), and View — a read-only look at the application: its status, who decided and when, the reason, the organization it was linked to, and every answer of the application, grouped like the form.
  • Shop / wholesale from the site — the short wholesale form of a pet store / retailer or a distributor / wholesaler (on /register-organization and /Free-Microchip-Program for these two types, and the /wholesale page — the window's Sent from). Its answers (business phone, monthly purchase volume, products, new products) are in their own Wholesale section. The organization gets no public address or phone: the business address and phone go to the shop location (the shop account part), the account admin becomes the main contact and Location admin; the price group starts as Retailers (store) or Wholesale (distributor).
  • Sample… on every row (FR-276) — a free sample kit (a microchip multipack of 3 or 20) sent from the application with a button, straight from the warehouse (Flexport; later eFulfillment), not through Shopify. A Sample kit asked mark — the form's "Would you like a free Findpet Sample Kit…?" was answered Yes; once a sample is sent the mark shows its status and number. The window shows what the form asked and the applicant's own shipping text; the address is filled from the application (check it against that text: US only, no PO box). Pick the kit, add a note for the warehouse if needed (eFulfillment gets it; Flexport's order has no such field) and the address of letter T11 (English, Spanish, Portuguese or French) — it goes by itself with the tracking once the sample ships. A second sample to the same application asks first.
    • TEST mode (the default, FLEXPORT_MODE=test): Flexport has no test switch, so the order is created at Flexport for real under a number starting with TEST- and cancelled at once — Test passed. Nothing ships, no letter. If the cancel didn't go through — Test order NOT cancelled: press Cancel the test order (the hourly check also retries it) or cancel it in Flexport Seller Portal, or it may ship. While a test order is open the sample can't be sent again or closed. If Flexport ships a test order before it is cancelled, the sample says so in red with the tracking — a real kit goes to the applicant. eFulfillment's test mode only checks the order (Version TEST).
    • Live (only on the user's decision, only with the production database): the sample is At the warehouse → Shipped (tracking, letter T11) → Delivered (Flexport reports it). The status is checked every hour (B2B_PROGRAM_JOBS_ENABLED) and by Check the status. Cancel shipment… — only before it ships.
    • Error — the warehouse refused (its words are shown: fix the address and Retry, or Close without shipping), the answer was lost (Retry looks the order up by its number first — no second box), or the warehouse's own error on a created order (Retry at Flexport when Flexport allows it, or Cancel shipment… and send a new one).
    The kits, each kit's warehouse and its SKU there (Flexport's logisticsSku), and the shipping methods are in Organizations → Samples (super admins); moving the samples to eFulfillment is changing a kit's warehouse and SKU there. Every step is in the audit log.

Click Verify organization on a row. It is one window with one scrolling column of blocks; nothing is written to an organization until you press Confirm & approve. The header of every block says in one line what that block does On Confirm, and follows what you choose:

  • The blocks — 1 Organization (the applicant's answers: name, type, contact, public contacts, website, links, logo, the application's other answers), 1A Found-pet alerts (not for a shop), 2 Address, 3 Shop account, 4 Free microchip program, 5 Shelter software, Changes, and the decision panel at the bottom. View opens the same blocks read-only, with What was done on top: each source — the organization, the alerts, the program, the letters, Shopify, the integration — as it is now, with Retry Shopify where a step stopped.
  • Save changes and the Changes journal — you can correct the applicant's answers in the window (blocks 1, 1A and 2). Save changes writes only the answers you changed, in the form the site wrote them; the applicant's page then shows them. Every save is a row of Changes (who, when, what was before and after) with Revert, which refuses if the field changed since. If the applicant or another agent changed the application while the window was open, nothing is saved: Reload and keep my edits or Discard my edits. Esc or Cancel with unsaved input asks Discard the changes?. The explanation is optional for a super-admin; the buttons are off while a request is on its way.
  • Fields — a phone takes the country and is written as +1…; an e-mail and a web address are checked as you leave the field; the first and last name are two fields; the address is by its parts with Google's suggestions; the logo is uploaded or removed with its own confirmation. A value the application already had is not checked again until you change it. Looks right saves a name split as shown.
  • Which organization — the window searches organizations and shows the candidates. A candidate comes by a strong sign: the same email; the same email domain or website (not a free mail like gmail.com, not a social or listing site like facebook.com or petfinder.com, and not one more than 5 organizations share); the same phone, written any way; the same street address with its ZIP. Each card says Matched by: … and whether the value is public or private. The name only is weak (the same name, or a similar one); such cards come last, under Weak — by the name only. With a strong match you must choose: pick it, or None of these — create a new organization; Confirm & approve stays off until you do. If a strong match appears after you opened the window, Confirm is refused and the window asks you to open the application again. If the search fails, look the organization up in Organizations before you create a new one.
  • Keep / Overwrite — for a picked organization: Keep its data, fill only what it lacks, or Overwrite with the application's. The table shows every field as Organization now, Application and what the organization will have after Confirm; each field has its own switch, and the contact is one switch for the whole person (two people's fields are never mixed). A list (e-mails, phones, social links) is merged without duplicates. Nothing here is written before Confirm.
  • Who gets the letters — when the link changes who receives the organization's letters, found-pet alerts or shop sign-in (a new admin contact, an SMS number, an alert or finder e-mail, a website that makes its addresses trusted, a new address), a window Confirm who gets the letters and alerts of … lists them. Tick Yes, these people get the letters and alerts, then Confirm the recipients. Its private contacts are visible on the site too — check with the organization first. A row that is the organization's own address or website needs no OK. If the rows change before Confirm, the window opens again with the new ones. A new organization needs no such window.
  • Hide listings — switched off for now: the window shows no pets block and hides nothing until the rules of what to hide are agreed. When it is on: if the picked organization already has pets on file, the window counts them by kind: its old imported listings (Petfinder and the like — out of date, with no owner, not touched for a long time) that can be hidden; listings kept in sync by RescueGroups or PetPoint; the organization's other listings (its own, or imported recently); listings in a transfer and listings with an active paid plan; pets of people (adopted or bought, with this organization's ID); other records (lost and found reports, records without a type); and records already hidden, merged or placeholders. Hide the N old imported listings sets only those listings to inactive — everything else is never touched, people's pets and real reports and transfers included. A second window asks you to tick Yes, hide these N old imported listings first, and if the number changed meanwhile Confirm is refused and the numbers are counted again. Each hidden listing keeps its earlier status in its history, under the change id of the approval's row in the Audit log; the Revert of that row (in the application's Changes or in the Audit log) brings them back, together with the rest of the link. Leave as is changes nothing.
  • Found-pet alerts and the consent (block 1A) — the SMS number (its check runs when you save it; an unavailable service is said, with Check again), the alert e-mail, and who receives the finder's e-mails. The consent shows agreed, withdrawn or not agreed, when, where and the words shown to the person. Turn on… is only on the organization's written request: the next step asks for the https link to it. Turn off… ends it (it stays on record as withdrawn). Changing the number ends the consent given for the old one. With Keep, the organization's own alerts stay; with Overwrite the application's go.
  • Shop account (block 3) — the company in Shopify, the price group, the people of the location and the two letters; its address is from the form's address parts when it kept them, else taken apart from its text (the window says which). Find the address fills every part from Google. An empty ZIP is marked: the location can't order without it. A PO box (P.O. Box, Post Office Box, Apartado postal…) in the street or line 2 is refused — the chips go to a street address only; ask the organization for it. The same rule is in Link to Shopify and a chip order's Edit address…. Turning Set up off leaves the shop to the organization's card later.
  • Free microchip program (block 4) — the program's own step (Add to the program) with the letter T9 and the free sample kit (Send samples…; in the list — Sample…). The program is closed to stores, distributors, volunteer groups and breeders (since 2026-10-12): for such a type the box starts unticked with a warning, and ticking it joins the organization without T9. The warning and T9 follow the type picked with Change type…: a closed type sends no T9, an open one does.
  • Shelter software (block 5) — the software the application names; tick to turn ShelterManager or the PetPoint import on with this approval, or leave it for the organization's card.
  • Org type is shown, not typed: a new organization gets the application's type (in the site's words — shelter, pet_shop, volunteer, vet, breeder), a linked one keeps its own. The site gives the organization's members their roles by it, so another type is set only with Change type… (Use this type). A linked organization's type the site doesn't know (one from before FR-241, like rescue) is kept and marked red.
  • Address — the public address goes to the organization's page with its point on the map; when the applicant gave none, the page has no address and no point (the full address is internal: it goes to the shop location and the org_id). A linked organization keeps its own point.
  • Confirm & approve writes the organization (creating or merging it) and does the steps shown in each block, then marks the application approved. Hover over it: it says what it does, and why it is off when it is (a match not chosen, the recipients not confirmed, unsaved input, a shop account problem). The answer is a line per step — the organization, the alerts, the program, the letters, Shopify, the integration; a step that stopped after the organization was written does not undo it — it is said with its error and a way to retry. A newly created organization gets an 8-character org_id. It starts with the two-letter state code — of the full address (its parts when the form kept them) or the public one, e.g. FL7K2M9Q; if no US state code is found, all 8 characters are random. The random characters never use 0/O or 1/I (the state code itself can, e.g. OH…). Dismiss… moves it to Dismissed without touching organizations or writing to anyone — for spam or duplicates; the explanation you give is shown as its reason. Like Reject…, it asks you to tick the “Yes, …” box first.
  • Revert the link — in the window of an approved application (in the organization's row, and in Changes): puts the organization's fields, its alerts and the hidden listings back as they were before the approval; an organization the approval created is removed. The window shows what goes back first. It refuses, with the reason, if the organization or the listings changed since — nothing is half-reverted. The application stays Approved; the Shopify company and letters already sent are not undone. The same Revert is in the Audit log (super-admins).
  • Edit organization — on an approved row; opens the organization in the Organizations tab (see Organizations → Organizations).
  • An old tab — a cs-admin tab opened before an update answers This window is from before an update — reload the page and open the application again; nothing is written. Reload the page.
  • When the Shopify part stops (the window after Confirm says at which step): the organization is saved all the same. Retry Shopify runs the steps again with the same choices — what is already done in Shopify is found, not made twice. Change and retry… opens those choices to change first; the same two buttons are on the organization's card in the Organizations tab. The usual case: the contact's phone is another Shopify customer's — Shopify gives a phone number to one customer only, so a new contact can't have it, and fixing the phone in the organization doesn't reach Shopify. Remove or change the phone in Change and retry…. Put that customer's email as the contact's only if the organization confirms the person is theirs (anyone can sign up in the shop with a phone): that customer then becomes the contact. The window warns about such a phone in advance, under the contact's Phone (Shopify is searched by the application's and the organization's phones), and offers that customer's company as This is it — pick it only if the organization confirms the company is theirs. In Change and retry the company the stopped link has stays its company.

Super-admin only — neither is shown to a plain admin at all (their menu is Queue/Sent/Customer Search/Organizations (Organizations/Shop employees)/Free microchips (Chip orders/Program feedback)/Pet certificate verifications/Audit log/Help). Every verify/dismiss/view/search is in the audit log with a before/after snapshot of the organization fields touched where there's something to compare.

Organizations → Organizations

Every admin looks an organization up — a shelter, a shop, a clinic — by a piece of its org_id, its name, an email (public or the older one) or a phone, typed any way: the digits are compared, and a US number finds the one stored with or without the leading 1. Up to 20 results, an exact org_id first; a short piece like a state code ("FL") lists the first 20 ids that contain it anywhere — not strictly that state's organizations, and not all of them.

Each card shows the organization's contacts:

  • On its page — the email and phone its findpet.com page shows: the first valid public ones (a value stored as text counts, "None" doesn't); the older ones only when the organization has no public contacts at all.
  • Public emails / Public phones — every value. The app and the shelter imports (PetPoint, RescueGroups) put the first ones on the organization's pets.
  • Email (older field) — where the site's emails to the organization go. Empty or not a valid email: the first valid public email instead. They are:
    • the message from its findpet.com page;
    • the copy of a finder's message about a pet that carries the organization, a sold one too (the organization's alert e-mail, once it has one, comes first);
    • only while the organization keeps the pet and the pet's own record has no valid email: the shelter's transfer confirmation, the pet owner notice and the tag scan notice (the tag scan notice goes to the alert e-mail first, once the organization has one).
  • Phone (older field) — where the site uses the organization's number. Empty or not a valid phone: the first valid public phone instead. It is:
    • on the finance admin's invoices (Bill to);
    • only while the organization keeps the pet and the pet's own record has no valid mobile phone: in the pet owner notice texts and the tag scan texts;
    • never in a finder's message.
  • Address — the one line its page shows — and Address parts (street, city, state, ZIP, country): the page's title is built from these parts — or, without parts, from the one-line address read as a US address. At an invoice's Send, the finance admin's invoices (Bill to) take them too, on top of the customer's address in Stripe:
    • without parts — the one-line address read as a US address;
    • a part left empty here stays as Stripe has it;
    • Stripe's suite stays only while the street is the same — with another street here, the old suite is dropped;
    • without a street here, while Stripe has one, Stripe's address is not changed (change it in the Stripe Dashboard).
  • Found-pet alerts — the SMS number, whether the organization agreed to the texts (agreed, withdrawn, not agreed), the alert e-mail, and where the e-mails to a person who found one of its pets go. Every admin reads these; only a super-admin changes them, in Edit….

Edit… — super-admins only (the server refuses anyone else). One window, in blocks: the organization (name, type, logo), the contacts, the public address and the found-pet alerts. Phones take the country and are written as +1…; an e-mail and a web address are checked as you leave the field; the first and last name are two fields; the public e-mails and phones, and the primary contact's e-mails when the organization keeps them as a list, are one field each with + Add; the address is by its parts with Google's suggestions — the point on the public map follows it when you save (a picked address is exact, a typed one approximate). The logo is its own step: Upload… / Replace… / Remove… with its own confirmation. Turn on… / Turn off… of the SMS alerts are also steps of their own (turning on needs the https link to the organization's written request); changing the number ends the consent given for the old one. A number that could not be checked (the service was out of reach) has Check again. Carry over from the application… appears for an organization with no alerts at all. The explanation is optional for a super-admin. A new e-mail, phone or link is checked; a field you didn't change isn't touched — even when someone changed it while your window was open — and saving the window untouched changes nothing. If someone changed a field you changed too, nothing is saved: Reload and keep my edits. The old values stay on the record (<field>_bkp), the change is in the Audit log, and Revert there undoes it — a number comes back, but a consent that ended with it is not opened again. Worth knowing:

  • An organization without public contacts shows the older email and phone on its page; once you add a public email or phone, the page shows only the public ones — the window warns you.
  • The finance admin reads Bill to at an invoice's Send: invoices already sent keep the old address.
  • The organization's adoptable pets synced from PetPoint get its new public contacts and address at the next sync (every 6 hours); other pets keep the contacts they have.

Every search (with the organizations it showed) and every save is in the audit log — a super-admin's. The Applications list also has a quick Edit organization link next to an approved application's org_id — it jumps here and opens the edit form for that organization directly.

Shop (B2B) & free microchips on the card: the Shopify link, the price group, the free microchip program. A link that stopped shows why, with Retry (the same choices again) and Change and retry… (the link window with what was sent, to change — a phone Shopify refused, the contact's email, the address; when the organization's contact is another now, the window shows it with Use it). Super-admins only.

Notifications

Every admin. The journal of the letters and SMS the system sent — or tried to send — to owners, organizations and finders: found-pet alerts, messages to organizations and their copies, scan alerts, transfers completed, accounts deleted in the app. Newest first, times in New York. Contacts are masked; Details shows them in full with the text as the recipient saw it (one-time links and tokens stay masked) — that look is written to the audit log.

  • Send status — Queued, Sent, Send error (the error text is on the badge and in Details) or Not sent (an SMS the plan or an opt-out kept back).
  • Support status — Info (the default), Needs action or Done. Needs action and Done ask for a short reason; Done can be put back to Needs action. Comments do not change the status. Every change is in the audit log. The number on the tab button is the Needs action.
  • Mark as Info — tick rows, then the button above the list. Records are never deleted.
  • Search — Tag ID, microchip, email, phone, a /m/… or /r/… link, an organization. An email or phone search is logged. Records saved before the type was recorded show as Info.

Organizations → Shop employees

Every admin. Requests to let one more person of a business customer order in the shop (shop.findpet.com, Shopify B2B) — any company linked to the shop, whatever form it applied with, not only the Free Microchip Program's. A request alone gives no access: the access is the Shopify role given when it is approved. The open ones (new, or failed at approval) are the number on the tab button.

  • Shop form — sent from the shop's Business pricing page by a signed-in customer who is a Location admin of that location (checked with Shopify, not typed). An Ordering only request is approved by itself when the company is linked to an approved Findpet organization and the requester is still a Location admin there; anything unusual (the email is already a shop customer outside this company, belongs to another company's contact, or the person already has another role here) is left to you, with the reason in the window.
  • From a letter — Add from a letter… types in a request that came by email (the shop's contact form): find the company, pick the location. The requester is what the letter says, so it is never approved by itself.
  • Open shows the request and live hints from Shopify: already a shop customer, a contact of another company, the role the person has here, whether the email domain matches the requester's or the organization's, whether the requester is still a Location admin.
  • Approve — pick the role (the requested one by default). The person becomes a contact of the company (a new shop customer if the email is new) and gets the role on this location only; the role is read back from Shopify, then letter T7 goes to the requester, the employee and dan@findpet.com. Location admin lets the person manage the location — only ever given here, by you. If Shopify fails half-way the request shows Error with the reason: Approve again finishes it without doubles.
  • Reject — with a reason, kept here; nobody is emailed.
  • Revoke access on an approved request takes back that one role on that location; the person stays a shop customer and keeps other locations.

Every action is in the audit log. Without the Shopify keys the tab says so: requests can be read and rejected, approving waits.

Numbers on the tabs. Applications (super-admins: new applications of every form), Shop employees and Chip orders show how many requests wait for an agent, refreshed every 90 seconds and after each action. Organizations and Free microchips in the main menu show the sum of their sections' numbers.

Organizations → Letters

Super-admins only (the server refuses anyone else). The letters Findpet sends organizations, T1–T13, in English, Spanish, Portuguese and French. The list says whom each one is for:

  • All organizations — whatever form the organization applied with: T1 Organization approved (its shop account is ready), T7 Employee added (Shop employees), T10 Application declined, and the one-time letters to organizations already on Findpet: T12 with the Free Microchip Program paragraph, T13 for the types the program is closed to (shops, distributors, volunteer groups, breeders).
  • Free microchip program — only the program's: T2 and T9 (approved for the program), T3–T6 and T8 (chip requests: approved, approved in part, declined, shipped, received).

The texts are our drafts until Dan sends his. Open a letter, pick the language, edit the subject and the text (HTML; a variable chip puts {{name}} where the cursor is), Preview it with sample values, then Save all languages. A saved letter applies to the next one sent; a part left as the draft (or emptied) keeps following the draft. Back to the draft throws the saved text away. Only the letter's own variables can be used — a letter with an unknown one isn't saved. Each save and reset is in the audit log with the text before. The letters were a part of Program settings before.

Pet certificate verifications tab

Not an organization's certificate: an organization's tax certificate is in its application (Organizations → Applications) and on its card (Organizations).

Every admin. Owners order a microchip registration certificate on findpet.com (FR-222). The International one prints the microchip implant date (and the clinic, "Implanted by") and the rabies vaccination date. The owner may upload a vet record (PDF, JPG, PNG or HEIC, up to 3 files) to have a date checked; until then the certificate says Declared by owner. Each upload is a request here; we promise the owner an answer within 72 hours, and requests older than 48 hours are highlighted. hello@findpet.com gets an e-mail with a link to each new request.

Review opens the request: the documents on the left (zoom for images, the browser's viewer for a PDF, or Open in a new tab), the pet, the owner and what is on the pet now on the right. Check that the document shows this microchip number and the date. Take it marks you as the one on it.

  • Approve — put the date as the document shows it (correct it if the owner typed it wrong); for the implant date, tick The clinic is on the document and correct the clinic if needed, or untick it when the document doesn't name the clinic — then only the date is verified. The values become Verified by Findpet for every certificate generated from now on (certificates issued earlier don't change); the owner gets an e-mail. A super-admin can undo an approval with Revert in the Audit log.
  • Reject — choose the reason (it goes into the owner's e-mail in their language) and, if it helps, a comment for the owner. The owner is asked to upload a clear copy again; a new upload comes as a new request. A rejection is not reverted.

Both ask for the justification, like every change of customer data. The documents are personal data: they are shown only here, never by a public link. Payments for certificates are not orders and don't appear on Queue, Sent or Payments.

Stats tab

Super-admin only. The numbers of the weekly growth table (Findpet growth table, tabs Users, Reports, SBP, Helps) for every day of a period. It opens on the last full week, Monday to Sunday; Last week brings it back, or pick From / To and press Show (up to a year at a time). Download CSV saves what's on screen: one line per day, the columns in the order of the table's tabs (without its totals — to fill the table itself, use Write to Google Sheet below). A day with nothing is 0 — no need to fill gaps by hand.

  • Days are UTC days, as the table always had them.
  • USA / Non-USA — by the country of the address (the code US, in any case; US territories such as Puerto Rico are Non-USA, as Google gives them). Most site sign-ups have no address (the form doesn't ask for one): such an account takes the country of its pets — one in the USA makes it USA, only pets abroad make it Non-USA. A report without a country takes its author's. With nothing to tell by, it counts as USA (of the accounts whose country is known, 95–99% are in the USA). So USA + Non-USA is always the Web / Apps number of the day. SBP and API are not split, as in the table.
  • Users — new accounts on the site (Web) and in the app (Apps). Reports — new pet reports, without searches (SBP) and in-shop pets. SBP — new searches by photo. Helps — Similar / Dissimilar votes. Staff and test accounts are left out, as in the old script.
  • Reports API — pet transfers of our API partners that came through the API. The same partners' transfers made from their dashboard on the site are the last column, Partner transfers from the site: the old query counted both, so API + that column is its number. Which partners — the admin's STATS_API_TOKENS; without it these two columns show —.

Every Show is in the audit log (a download is the numbers already on screen, not a new count).

Write to Google Sheet puts the period on screen into the growth table itself (tabs Users, Reports, SBP, Helps; the totals and the weekly / monthly tabs are formulas and stay as they are). The numbers are counted again for the write, and they go only into empty cells: anything already in the table — typed by hand or written before — is kept. Where it differs from the count, the result box lists it (column, date, in the sheet, counted); the table is not changed. A day after the last one in the table gets a new row with the formulas of the row above. Writing the same period again changes nothing, so it is always safe to repeat — for example, after a failure. Only days that are over (before today, UTC) can be written.

  • A tab is not written at all if its headers are not where the admin expects them (a column moved or renamed — for example, the Reports tab's E–G must be headed Non-USA). A day missing in the middle of the table, or one that would leave a gap after its last day, is listed and not written.
  • Every Monday at 09:00 UTC the admin writes the week before by itself, and, if the table stops earlier, the days since its last one; the result goes to Slack. The line under the buttons shows the schedule and the last run.
  • Every write — by the button or on Monday — is in the audit log with what was written, what differs and what was not written.

Ad modal tab

Super-admin only. What visitors do with the partner's modal (Pet Insurance Quotes) that the site shows on a pet's page once the pet is saved or a transfer accepted and a plan chosen: how many times it was opened, closed (the cross or outside it) and clicked through to the partner (the picture or the button), and the CTR — clicked / opened. One row per day of the period, a day with nothing is 0, and a Total row. It opens on the last full week; Last week brings it back, or pick From / To and press Show (up to a year at a time).

  • Events / Pets — every event, or the different pets (a double click, a second visit to the page is one pet). In the Total row a pet of two days is one pet, so the Pets total is not the sum of the days. The events' CTR can pass 100% (a double click is two clicks); for the share of shows that led to a click, look at Pets.
  • By context — why the modal was shown: Transfer accepted, Pet added, Pet edited, Microchip activated, Tag activated; only those that occurred in the period get columns. Other is any other mark — from Aug 26 to Sep 23, 2026 the site wrote the pet's page address there instead. By device — Mobile (a phone or a tablet) and Desktop. All is the same in both.
  • Dashboard page — the same offer is also a page of the customer's dashboard, Pet insurance, and it logs into the same place: Opened is a visit to the page, Clicked a click on its button (no Closed, no pets — shown as —). It is a group of its own at the end, not part of All, so the modal's CTR is the modal's only. It appears when the page had visits in the period.
  • Days are UTC days, as on the Stats tab. Staff and test accounts are left out, as there, and so are the accounts our autotests make on the live site (alex+…@findpet.com).
  • The site records these events from any browser without a login, so the numbers are as good as that. A period with more than 200,000 events is refused — pick a shorter one.
  • Download CSV saves the view on screen (the switches included) with its Total line; the file is named by the moment of the download, yyyymmdd_hhmmss-ms.csv, UTC.

Every Show is in the audit log.

Checkout funnel tab

Only for the users of CHECKOUT_FUNNEL_USERS (super-admins). Every opening of the plan window on findpet.com — the checkout — and how far it got, per day, window v4 against window v5 (Dan's new design). The site splits the accounts between the two: an account always sees the same window. A day is the day the window was opened; what became of that opening is counted on that day, however long it took. Days are UTC (as on Stats) or New York.

  • The steps: Window served (the site sent it) → Window shown (it started in the browser) → Changed a choice (a plan, a product, a colour, the country) → Step 2: checkout → Payment form ready → Address entered (orders with something to ship) → Pressed Pay → Paid → Step 3 shown → Insurance clicked. Paid comes from the server when Stripe took the money — never from the browser; a bank that confirms later (US bank account) is Bank processing until it does.
  • Summary — the funnel of the period for All, v4 and v5 (and the old Payment Links dialog when the site fell back to it): attempts at each step, % of the windows shown and % of the step before; what became of them; revenue per currency, average order, revenue per window shown, the plan mix, orders with gear, promo codes, payment errors and the median time from the window to the money. The coloured line on top is the A/B: paid ÷ shown of v4 and v5 and the p-value — under 0.05, the difference is unlikely to be chance; above it, wait for more windows before deciding. It counts only the accounts the site split by the share: windows forced by a link or QA, pets the site keeps on v4 and days at 0% or 100% stay in the tables but not in the test.
  • Went to pay (bank / wallet) — the page was left while Stripe took the buyer to their bank or wallet; it turns into Paid once the money arrives.
  • By day — every step and number per day for one window (pick All, v4, v5 above the table); a date opens its attempts. v4 vs v5 by day — the key numbers side by side.
  • Attempts — the openings themselves, newest first, for the period or one day, one window, one outcome: the account, the pet, where the window was opened, the device, the country, how far it got, the outcome, the amount, payment errors. A row opens the timeline: every step with its time, the order, the Stripe session (the link searches the Stripe dashboard).
  • Filters — country, device, language, window mode (Free or Basic + SMS buying Premium, a Monthly/Yearly pet changing plan, a Lifetime pet buying gear), where it was opened, the account's age. Staff and test accounts are left out unless Include test accounts is ticked (the autotests' alex+…@findpet.com included).
  • Window v5: N% of accounts — the share of accounts the site shows v5 to, changed here with Change (0–100, no deploy: the site follows it within 10 seconds; a justification as on every write). 0 sends everybody back to v4. A pet on Monthly, Yearly or Lifetime gets v5 only once the site has the plan change of FR-212.
  • Download CSV saves the view on screen (By day, v4 vs v5, the attempts page).

Every Show, every list of attempts and every change of the share is in the audit log.

UKM transfers tab

Only for the users of UKM_RESEND_USERS (god and dan by default), as a super-admin. The transfers of the UKM shops — the shops that register chips through the partner API with one shared token, the finance admin's billing group — that the new owner hasn't accepted yet, by the month the transfer started (New York time). Pick the Year; each month shows how many transfers are not accepted and how many emails and SMS a resend would send.

  • Resend… — tick Email, SMS or both and press it: the window says how many emails and SMS will be queued and asks the reason. Each new owner gets the very same email/SMS as when the transfer started — the same accept link, the same address or number — as Resend link in Customer Search does for one transfer.
  • Not sent: a message the shop chose not to send (automatic sending off, or the box unticked) — neither email nor SMS; a message still waiting in the queue; a transfer resent in the last 30 days — here, by Resend link or by the shop through the API — neither channel; a transfer whose link first went out less than 7 days ago — not yet; an email to an address the validator found dead (email_disabled); an email from before Dec 13, 2022, which the email sender doesn't read.
  • In portions: a portion of transfers every few minutes (the pace is above the table), not all at once: the senders send one email a second and one SMS every two seconds, and the site's own messages must not wait for long. The pace is one for all jobs: several months started go one after another, oldest first (the list says which one a job waits for). The jobs list shows what went and what is left; a job continues after a restart of the panel, and Cancel stops what hasn't gone yet (what was queued stays queued). A transfer that fails three times is skipped (failed 3 times), so it can't hold the month up.
  • Each transfer is checked again right before its turn: one accepted, cancelled, moved to another shop or resent meanwhile is skipped.
  • One job per month at a time. The start (with the reason), every portion, the end and a cancel are in the audit log.

Audit log tab

Every admin reads and searches it (a plain admin — the changes only, see below). Who logged in and when (and failed or locked-out logins), every address edit, every cancel/revert/delete/retry, every step of a Cancel & refund, every Customer Search (who searched for what) and every action on a result card — Unlink, Deactivate tag, Cancel transfer, Resend link (opening the window and every attempt, refused ones too), Merge (opening the window, both records as they were before, the outcome), Cancel subscription — every Applications/Organizations view, search, approval, dismissal and edit, every record action (Change owner, Return to / Change organization, Remove premium, Delete account, Deactivate pet — opening the window, the change, refusals), every user created/disabled/enabled or given a new password, and what the internal sender did with each new-checkout order (sent, held, failed, outcome unknown), every Stats and Ad modal period shown and every write to the growth table in Google Sheets — the full history of actions taken in this panel, by every admin (not just your own). Worth checking whenever something looks off and you need to know who did what. The Justification column shows why a change was made — the explanation and the links (rows from before the three fields show the one reason they had).

  • Search finds any text in a row: the admin, the action, the target (a report id, a tag code, an org_id), the explanation, a helpdesk or escalation link — and, in a super-admin's search, the details. Narrow it by Action, User, From/To (days, UTC — the times shown are your own) and Only changes.
  • A plain admin sees the changes of customers' data — who, when, what, on which record, why, and whether it was reverted — without IPs, and with the details only of support's operations (Return, Surrender, Change owner, Edit registration, photos): what was changed, Before → After, how ownership was verified and how the people were told. Logins, customer searches, what was opened, and the super-admins' tabs (Applications, organization searches and edits, refunds, Users, Stats) are in a super-admin's log only.
  • Revert… undoes a change. Any admin can undo the operations of support's tools — Return to organization, Surrender to a shelter, Edit registration, a photo change — and only those (a Change owner is a super-admin's to undo); super-admins also undo the rest of this list: Mark stolen and Not stolen anymore, Unlink tag or microchip, Deactivate tag (back in use, linked to its pet again), Deactivate pet (shown again, with its tag back as it was), Change owner (a direct give: the new record is taken out of service and the old one comes back), Return to / Change organization, Remove premium, Edit organization, an order's address edit, and Merge (the duplicate comes back as a record of its own, with its tag, microchip and plan). The window shows every field, now and after the revert. If anyone changed one of them since (the owner on the site, another admin, a shop through the partner API), or the pet has had another owner since, the revert is refused and nothing is written. The explanation and the helpdesk link are required for a plain admin, optional for a super-admin. The revert is a change of its own, in the log; the original row then shows Reverted, by whom and when — once only.
  • Not revertable, and the row says why: a transfer cancel (it wrote cancel_transfer to the billing log the finance admin bills shops by — the shop starts the transfer again), an account deletion, anything done in Stripe or Shopify, a resent email or SMS, an application approved or dismissed, an order's place in the queue (its own buttons do that), and changes made before revert existed.

Signing in: two steps

Every sign-in is your password and then a second step: the 6-digit code from the authenticator app on your phone, or a passkey (fingerprint, face or security key) if you added one.

  • The first time (and after a super-admin resets your 2FA) the panel shows a QR code right after the password: scan it in an authenticator app (Google Authenticator, Microsoft Authenticator, 1Password, Authy…), type the code — and save the 10 recovery codes it shows once.
  • A new account or a reset one has a day to do that; after that the sign-in is refused until a super-admin resets 2FA again.
  • Lost your phone? On the code step, choose Use a recovery code. Each code works once. Then open Security (top right) and move to a new phone. Out of codes too — ask a super-admin to reset your 2FA.
  • Security (top right, every admin): move to a new phone, get a new set of recovery codes (the old ones stop working), add or remove passkeys. Anything that adds a way in asks for your password first.
  • A code works once; wrong codes are counted — after too many, sign-in is paused for a while.

Users tab — super-admin only

Add new staff accounts, disable access, reset passwords. The 2FA column shows who has set it up (and their passkeys), who still has to, and whose time to do it ran out. Reset 2FA removes someone's app, recovery codes and passkeys and signs them out: they set it up again at their next sign-in, within a day. Your own 2FA you change in Security, not here.

Edit shipping address

Ownership history

Loading…

    Why this order failed

    show raw error
    
        

    Cancel & refund

    Loading…

    Refund in Stripe

    Resend transfer links

    Counting…

    Resend transfer link

    Loading…

    Merge duplicate records

    Loading…

    New user

    Reset password

    Verification request

    Loading…
    Open in a new tab

    Approve

    Check the document: the microchip number and the date. Correct the date or the clinic if the document says otherwise — every field is confirmed on its own.

    Reject

    Reject application

    Confirm

    Revert

    Loading…

    Change

    Loading…

    Your recovery codes

    If you lose your phone, each of these codes signs you in once instead of the code from the app. Keep them somewhere safe — a password manager, or printed. They are not shown again.

      Security — how you sign in

      Authenticator app

      Recovery codes

      Passkeys

      Sign in with a fingerprint, your face or a security key instead of typing the code. The password is still asked first.

        In the app on the new phone, add an account and scan this code (or enter the key). Your old app keeps working until you finish here.

        QR code for the authenticator app On this phone? Open it in the app

        Now confirm with your fingerprint, face or security key — your browser will ask.