Receipt Wallet — User & Admin Guide

What this app does

Receipt Wallet turns a phone camera into a proof-of-purchase tool. Your customers can photograph a receipt, the product's serial number, and any other supporting evidence, and the app keeps it safely stored against the product they bought.

It works in two ways depending on how the customer arrives:

• Claim ownership — they scanned a generic product code and want to register that they own this specific item (using receipt + serial number as proof).
• Attach to an existing item — they scanned an item that already has a digital identity (a "proof") and want to add their receipt for warranty / support purposes.

It's designed for brands who want to:

• Offer hassle-free warranty registration.
• Capture verified ownership without manual paperwork.
• Have a single, searchable inbox of every customer's proof of purchase.

AI does the heavy lifting — reading the receipt, extracting vendor / date / total / serial number, and scoring how legitimate the submission looks. Anything the AI is confident about is auto-verified; anything borderline is queued for you to review.

Getting started — first-time setup

1. Open your collection's admin console and select Receipt Wallet.
2. You'll land on the admin with three tabs: Submissions, Settings, and Evidence.
3. Open Settings first and configure the app for your brand (see the table below).
4. Click Save settings. The app is now live for shoppers.
5. (Optional) Open a specific product, then go to Evidence to customise what proof shoppers must upload for that product.

Admin Configuration — Settings tab

The Settings tab applies to your whole collection.

Click Save settings after any change. Updates are live immediately.

Admin Configuration — Evidence tab (per product)

Open the admin from a specific product and use the Evidence tab to control what shoppers must submit for that product.

Default evidence slots

Out of the box, every product asks for:

• Receipt — required. The shopper uploads a photo or PDF of their receipt.
• Serial number — optional. A photo of the serial number on the product itself.

You can add, rename, or remove slots freely. Common additions:

• Box label — for branded packaging proof.
• Warranty card — if you ship a paper card.
• Product photo — to show condition at registration.

For each slot:

• Label — what the shopper sees as the section heading.
• Required toggle — if on, the shopper can't submit until they've added at least one file in this slot.
• Hint — small help text shown under the label (e.g. "Make sure the total and date are clearly visible").

Click Save evidence schema when done.

Note: the evidence schema is per-product. To configure it, you must open the admin from inside a product's context.

Day-to-day usage — what the shopper sees

The shopper's flow is the same on phone or desktop.

1. They land on the app — usually after scanning a QR code or tapping a link on the product page. The app figures out automatically whether they're claiming ownership or attaching a receipt to an existing item.
2. They see the upload form — one card per evidence slot you configured. Each slot has two buttons: Take photo (opens the rear camera on a phone) and Upload file (for choosing existing photos or PDFs).
3. They add evidence. Each file is shown as a thumbnail; a small × removes it. Files over 10MB are rejected.
4. AI parses the receipt. As soon as a receipt photo is added, the AI reads it in the background and pre-fills:
   • Vendor (shop name)
   • Purchase date
   • Total
   • Currency
   • Serial number (when claiming ownership)
5. They review and edit. All AI-extracted fields are editable — anything they change wins over the AI guess.
6. They tap Submit. A progress bar shows upload status.
7. They see a confirmation screen with:
   • Status: Verified, Pending review, or Conflict.
   • The warranty expiry date.
   • A claim ID for their records.
   • A "Submit another" button.
   • The support email if you configured one.

The whole flow is mobile-first and takes most shoppers under a minute.

Managing submissions — Submissions tab

This is your inbox. Every submission your customers make appears here.

Filters & search

• Status filters at the top: all, pending, verified, rejected, conflict.
• Search box matches anywhere in the submission (vendor, serial number, product, etc).
• Export CSV downloads the current list as a spreadsheet.

Status meanings

Each submission card shows

• Status badge and flow type (claim or attach).
• When it was submitted.
• The product (and proof, if attaching).
• Vendor, purchase date, total, currency.
• Serial number, if provided.
• AI score (as a percentage) and the AI's short reasoning.
• A grid of evidence thumbnails — click any to open the original file.

Actions on each submission

• Verify — approves the submission. Status flips to Verified.
• Reject — you'll be prompted for a reason; it's saved with the record.

Both actions are immediate and update the customer's record.

Exporting

The Export CSV button gives you a spreadsheet with: id, status, flow, productId, proofId, vendor, purchaseDate, total, currency, warrantyUntil, aiScore, submittedAt — useful for support reporting or integration with your CRM.

Widget — adding Receipt Wallet to product pages

The ReceiptWalletWidget can be embedded on any product page in the SmartLinks platform. It shows the latest receipt and warranty status for whichever item is being viewed.

It comes in three sizes:

If no claim exists yet, the widget shows a friendly empty state with an Add receipt button that takes the shopper into the upload flow.

The widget configures itself — no extra setup beyond the initial app configuration.

Bulk import — per-product evidence requirements

If you have a large catalogue, you can import evidence requirements and warranty overrides per product using a CSV.

CSV template

productId,warrantyMonths,evidenceSlots
prod_001,24,"Receipt,Serial number"
prod_002,60,"Receipt,Serial number,Box label"
prod_003,12,"Receipt"

Field reference

Rows with a productId that doesn't match any product in your collection are skipped — you'll see a summary at the end of the import.

FAQ & troubleshooting

Q: A shopper says they can't tap Submit. A: The Submit button stays disabled until every required evidence slot has at least one file. Check your Evidence tab — you may have more required slots than they realised. Reduce required slots or improve the hint text.

Q: The AI got the vendor / date / total wrong. A: That's expected occasionally with poor photos. The shopper can edit any field before submitting — their edits always win over the AI guess. If a particular brand of receipt is consistently mis-read, contact support.

Q: Submissions are sitting in "Pending" — none get auto-verified. A: Your AI auto-verify threshold is probably too high. Lower it from 0.75 toward 0.6 to auto-approve more, or temporarily turn on Auto-approve everything for testing.

Q: Why was a submission marked "Conflict"? A: Two different shoppers claimed the same serial number. Open the submission to see both, then either Verify the legitimate one and Reject the other, or contact both customers for clarification. If you don't want to allow this at all, turn off Allow multiple claims per serial.

Q: A file upload failed. A: Files over 10 MB are rejected at the picker. Ask the shopper to take a slightly smaller photo (most phones have a "low" or "medium" quality option) or scan to PDF.

Q: My CSV import skipped rows. A: Check that every productId matches an existing product in this collection. Misspelled or non-existent IDs are skipped. The Import summary lists each skipped row.

Q: The Evidence tab says "open this from a product context". A: Evidence requirements are configured per product. Open the admin from inside a specific product (so the URL has a productId), then the Evidence tab will be editable.

Q: Can I change settings after launch? A: Yes — every Setting and Evidence field is editable at any time. Changes apply to all future submissions. Existing submissions keep the warranty length and evidence schema they were submitted with.

Q: Where do warranty dates come from? A: Warranty expiry = purchase date (from the receipt) + warranty months. The product's override is used if set; otherwise the collection default. If the AI can't read a purchase date, the shopper enters it manually.

Q: A shopper didn't get a confirmation email. A: The app shows a confirmation screen but doesn't send email itself. Make sure your Support email is set so they have somewhere to reach you. Email notifications can be added on top of the platform's broadcast tools.