# Box contents and packing lists for subscription boxes

Box contents and packing lists for subscription boxes is a SaaS idea for small subscription box businesses packing a few hundred boxes a month, priced to test at $49 a month per box business. Subscribers have sizes, allergies and items they already received, all tracked in a spreadsheet. With it, subscription box businesses plan each month’s contents, respect subscriber preferences and print packing lists that say exactly what goes in each box.

_Published 19 Oct 2026. A starting point we wrote, not market research: run the 7-day test before you build._

## What problem does it solve?

Subscribers have sizes, allergies and items they already received, all tracked in a spreadsheet. On packing day the team guesses, boxes go out wrong, and the swaps and refunds eat the margin.

**Why now:** Subscribers expect boxes tailored to their tastes, and generic boxes are easy to cancel.

## What do they use today?

Box owners usually keep one large spreadsheet with a column for each preference, then print it as a checklist for the packing table. Late changes are written on the printout by hand.

## How does it work?

The owner imports subscribers with their sizes, allergies and preferences, then each month builds the item plan with stock counts. Rules skip anything a subscriber has already received, so nobody gets a repeat, and the plan warns of any shortage before packing day. On packing day the team prints a packing list and a label for every box.

## What goes in the first version?

- Subscriber import with sizes, allergies and preferences
- Monthly item plan with stock counts
- Rules that skip items a subscriber already got
- Packing list and label for every box
- Shortage warnings before packing day

## Who pays, and how much?

- **Who pays:** Small subscription box businesses packing a few hundred boxes a month
- **Price to test:** $49 a month per box business

A box business runs on a monthly cycle, so one flat price per business fits how owners plan their costs. It stays the same whether a month brings a few more boxes or a few fewer.

## How to test it in 7 days

1. Ask five box owners to walk you through their last packing day and where it went wrong.
2. Turn one owner’s subscriber spreadsheet into packing lists by hand and ask if it saves time.
3. Post a mock packing list in subscription box owner groups and count replies asking for access.

## Where to find the first customers

- Subscription box owner groups on Facebook
- Ecommerce and subscription business subreddits
- Fulfilment warehouses that pack boxes for small brands

## What are the risks?

- Subscription billing apps add basic box planning; preferences and packing must be clearly better.
- Small box businesses often close or pause, so expect churn and keep onboarding short.

## 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, Admin panel, Emails

**You build:**

- Subscriber import with preferences
- Monthly item plan with matching rules
- Packing lists and labels to print

[Get the kit](https://shipanysaas-demo.vercel.app/pricing)

### The starting prompt

```text
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 Box contents and packing lists for subscription boxes.

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: Subscription box businesses plan each month’s contents, respect subscriber preferences and print packing lists that say exactly what goes in each box.
- Who pays: Small subscription box businesses packing a few hundred boxes a month
- Their problem: Subscribers have sizes, allergies and items they already received, all tracked in a spreadsheet. On packing day the team guesses, boxes go out wrong, and the swaps and refunds eat the margin.
- Price to test: $49 a month per box business (a plan in apps/web/config/billing.config.ts)

## Build only this first version
1. Subscriber import with sizes, allergies and preferences
2. Monthly item plan with stock counts
3. Rules that skip items a subscriber already got
4. Packing list and label for every box
5. Shortage warnings before packing day

## 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
- Admin panel: a super-admin panel that needs two-step sign-in
- Emails: transactional email through Resend or Nodemailer

## New code it needs
- Subscriber import with preferences
- Monthly item plan with matching rules
- Packing lists and labels to print

## 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

- [How to add Stripe embedded checkout to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-stripe-embedded-checkout)
- [Multi-tenant SaaS architecture: teams, roles and invitations done right](https://shipanysaas-demo.vercel.app/blog/multi-tenant-saas-teams-roles-invitations)
- [How to add Resend email to a Next.js + Supabase app](https://shipanysaas-demo.vercel.app/blog/nextjs-supabase-resend-email)

## More ideas: Online shops

- [Materials stock and reorder alerts for makers](https://shipanysaas-demo.vercel.app/saas-ideas/maker-materials-reorder-alerts): Makers list what goes into each product, sales count down their materials, and they get a warning before anything runs out.
- [Lost and damaged parcel claims tracker for shops](https://shipanysaas-demo.vercel.app/saas-ideas/lost-parcel-claims-tracker): Online shops log every lost or damaged parcel, keep the photos and proof, and file carrier claims before the deadline passes.
- [Product photo tracker and shot lists for shops](https://shipanysaas-demo.vercel.app/saas-ideas/product-photo-shot-lists): Shops see which products lack photos, build a shot list for the photo day, and share it with their photographer.

- [All SaaS ideas](https://shipanysaas-demo.vercel.app/saas-ideas)
- [Try the free generator](https://shipanysaas-demo.vercel.app/saas-ideas#generator)