Go live

Nothing needs switching on — the portal has been live since the rules went in. Going live means telling customers it exists.

Below is the check to run before that, and what to expect afterward.

The checklist

Work down it once. Anything that can't be ticked should be fixed first — each item is something a real customer will hit in the first week.

Your data

• Your store is connected and the most recent orders are showing.
• The product catalogue looks complete.

Your coverage

• Every product is either covered or deliberately excluded. No gaps.
• The coverage shown to a customer has been read for at least three different products, and it says what you'd say out loud.
• Policy documents are attached to the rules they belong to.

Your portal

• Logo and colours are in place.
• It's been viewed in a private window and on a phone.
• What's asked of customers is decided, and it's the shortest version you'd accept.

Your team

• Everyone who'll handle claims has an account and has signed in at least once.
• Claims route somewhere a person is actually watching.
• Somebody is named as the person who receives escalations.
• The team knows internal notes are internal.

Your emails

• Every customer-facing email has been read, including the rejection.
• Internal alerts go to people who'll act on them, and nothing else is switched on.

Your test

• A claim has been walked end to end and reached a decision.
• A claim that gets rejected has been walked too.
• Test data isn't fully removable, so what was created has been noted.

Tell your customers

Do these two first:

Add the link to the order confirmation email. This reaches every customer at the moment they care most. One line: "Register your product for warranty coverage," and the link.

Add it to the site footer, labelled "Warranty."

Then leave it a week. Watch what comes in, check whether registrations look as expected, and fix anything that surprises you while volume is still small.

After that week, add the rest: a card or QR code in the box, replacing whatever's on the existing warranty page, and a macro support can send in one click.

Resist emailing the entire back catalogue on day one. A few thousand registrations arriving in an afternoon means every setup problem arrives at once too. To backfill existing customers, send it in batches a week apart, starting with the most recent purchasers.

What week one actually looks like

Four things come up for most brands. None are broken software.

Customers who can't find their order. They used a different email than they ordered with, or bought through a channel with no order data connected. Decide in advance how to handle these — either allow self-attested registrations, or have a template reply ready.

Registrations for things thought not covered. Somebody registers a spare part or an accessory. This is the coverage audit surfacing something after the fact — add an exclusion and move on.

Claims that arrive with no photos. Even when asked for. The information-request flow handles it, and it's a good early test of whether that round trip works.

Coverage questions rather than claims. People registering just to check whether they're covered. Each of these is a phone call or email that didn't happen.

Watch these three numbers

In the first month, three numbers in admin reporting show whether this is working:

• Active Registrations — how much of what's been sold is actually registered for coverage.
• Open Claims — what's currently in flight across the queues.
• Total Claims — cumulative volume, broken down into approved or resolved versus rejected.

There's no other reporting metric or chart in the admin today. Registrations should climb, then settle — near zero means the portal link isn't where customers are, so revisit placement. Open claims shows whether the queues are keeping up. The split within total claims is the baseline for whether the coverage rules match what's actually being honoured.

If something's wrong

No orders syncing, or the sync stopped. Check the connection in Settings first. If it looks connected but data isn't moving, tell us what you're seeing rather than disconnecting and reconnecting — we'd rather see the failure than have it cleared.

Coverage showing the wrong term. A rule is matching more products than intended, or two rules have priorities that don't reflect what was meant. Open the rule, read its matched-products list, then check your coverage rules.

Emails not arriving. Check spam first. If still not showing up, tell us what you're seeing.

A claim in the wrong place. Routing. Fix it in your workflow settings, and reassign the claim by hand in the meantime.

Something else. Ask us. Setup help is included at no cost, and we'd rather hear about it in week one than in month three.

Next steps, when you're ready

Nothing here is urgent.

• Backfill existing customers, in batches, so coverage records reflect what's already been sold.
• Review rules after six months, when warrantini has enough real claims to suggest adjustments.
• Connect warranty data to other systems — a helpdesk, a CRM, a warehouse system. Ask us when you're ready to look into it.