Lost and damaged parcel claims tracker for shops
Lost and damaged parcel claims tracker for shops is a SaaS idea for online shops shipping their own orders with several carriers, priced to test at $19 a month per shop. When a parcel is lost or arrives broken, the shop sends a replacement and means to claim later. With it, online shops log every lost or damaged parcel, keep the photos and proof, and file carrier claims before the deadline passes.
. A starting point we wrote, not market research: run the 7-day test before you build.
What problem does it solve?
When a parcel is lost or arrives broken, the shop sends a replacement and means to claim later. Claim windows close, the proof sits in an inbox, and the money is never recovered.
Why now: Small shops now ship with several carriers to save money, and each carrier has its own claim rules and deadlines.
What do they use today?
Shop owners handle each lost parcel as it comes, looking up that carrier’s rules online and keeping photos in a phone gallery or an email thread. A few note deadlines on a calendar.
How does it work?
When a customer reports a missing or broken parcel, the shop owner logs it with the order, the carrier and any photos. The log shows the carrier’s claim deadline and a checklist of the proof that carrier asks for, and emails a reminder as the date nears. The owner marks the claim as filed, then paid or refused, and reads a monthly report of money claimed and recovered.
What goes in the first version?
- Log a problem parcel with order, carrier and photos
- Claim deadline per carrier with email reminders
- Checklist of the proof each carrier asks for
- Status from filed to paid or refused
- Monthly report of money claimed and recovered
Who pays, and how much?
- Who pays
- Online shops shipping their own orders with several carriers
- Price to test
- $19 a month per shop
Each shop ships from one place with its own mix of carriers, so one flat monthly price per shop is easy to follow. It stays the same however many claims are filed.
How to test it in 7 days
- 1Ask ten shop owners how many claims they skipped last quarter because of the hassle.
- 2Collect one shop’s lost parcels from the last three months and list which were still claimable.
- 3Read each main carrier’s claim rules and check they can be turned into a checklist.
Where to find the first customers
- Small-business ecommerce subreddits
- Online shop owner groups on Facebook
- Bookkeepers who work with small online shops
What are the risks?
- Shipping insurance add-ons handle some claims, so focus on uninsured everyday parcels.
- Carriers change claim rules, so the checklists need regular updates.
How to build it on shipanysaas
4 of the parts it needs are already in the kit. Get the kit, open it in Claude Code, Codex or Cursor, and paste the starting prompt.
- Already in the kit
- Teams and roles
- Billing
- Emails
- In-app notifications
- You build
- Parcel problem log with photos
- Carrier rules, deadlines and reminders
- Money recovered report
See the starting prompt
You are in a fresh copy of the shipanysaas starter kit, a pnpm and Turborepo monorepo: the Next.js web app is in apps/web and the Supabase database, with its migrations, in apps/web/supabase. Help me build the first version of Lost and damaged parcel claims tracker for shops. Read AGENTS.md first, then the AGENTS.md in every folder you work in: the kit's rules there win over your defaults. When a skill in .agents/skills (also in .claude/skills and .cursor/skills) matches a task, use it. ## The product - What it does: Online shops log every lost or damaged parcel, keep the photos and proof, and file carrier claims before the deadline passes. - Who pays: Online shops shipping their own orders with several carriers - Their problem: When a parcel is lost or arrives broken, the shop sends a replacement and means to claim later. Claim windows close, the proof sits in an inbox, and the money is never recovered. - Price to test: $19 a month per shop (a plan in apps/web/config/billing.config.ts) ## Build only this first version 1. Log a problem parcel with order, carrier and photos 2. Claim deadline per carrier with email reminders 3. Checklist of the proof each carrier asks for 4. Status from filed to paid or refused 5. Monthly report of money claimed and recovered ## Already in the kit: reuse it, never rebuild it - Teams and roles: team accounts with members, roles and invitations - Billing: Stripe or Lemon Squeezy subscriptions, per seat or usage-based, and one-off payments - Emails: transactional email through Resend or Nodemailer - In-app notifications: a notifications bell in the web app ## New code it needs - Parcel problem log with photos - Carrier rules, deadlines and reminders - Money recovered report ## How to work 1. Plan first: list the database tables (with row-level security, so each team only sees its own rows), the pages and the server actions for the first feature. Then stop and wait for my OK. 2. Build one feature at a time with the kit's own UI and form components, with a migration for every schema change and user-facing text in the translation files. 3. After each feature, run the verification steps in AGENTS.md, fix what they find, and tell me what you built and what comes next. ## Rules - Ask me before you add a dependency, delete a file, or change sign-in, billing or the admin panel. - Leave the parts of the kit this product doesn't use as they are. Done when every first-version feature works for a signed-in team and the AGENTS.md checks pass.
Guides for the parts it uses
Want ideas for your own skills?
The free generator writes three while you watch, each with a plan and a starting prompt. Or paste this idea into it for two sharper versions.
More ideas: Online shops
Product photo tracker and shot lists for shops
Shops see which products lack photos, build a shot list for the photo day, and share it with their photographer.
Product gifting tracker for small brands
Small brands track which creators got free products, when they shipped, whether they posted, and which gifts led to sales.
Returns requests and tracking for small online shops
Customers start a return from a link with their order number, reason and photos, and the shop approves it in one place.