Virtual Kit Stock Sync

The problem this kills

You sell bundles - "starter kit," "deluxe set," "value pack" - but you don't actually keep those bundles on a shelf. You build them on demand from individual components you already stock. So how many of each bundle can you really sell right now?

It is easy to get this wrong, and getting it wrong is expensive. List 50 of a kit when you only have parts for 12, and you oversell. Worse: the same component often sits inside several different kits. Promise that component to Kit A and Kit B independently and you've double-promised stock you don't have. The result is cancelled orders, refunds, angry customers, and a customer-service queue full of apologies.

Most teams "solve" this with a manual spreadsheet that someone updates by hand once a week. It is slow, it goes stale the moment stock moves, and it quietly double-counts shared parts because no human can track every overlap in their head.

What you'll build

A small internal web app that does the math correctly and safely:

• Import your component on-hand quantities and your kit definitions (which components, and how many of each, go into every bundle).
• Compute each kit's raw buildable quantity as the limiting component - the part you'd run out of first.
• Account for shared components so a single part is never promised to two kits at once - you decide the allocation rules, the tool enforces them.
• Produce a clean virtual availability snapshot, which an ops lead reviews and approves before anything goes live.
• Export an availability CSV in exactly the columns your sales channels expect.

What's inside the Implementation Plan

This is not a generic template. The plan opens by interviewing you about your business - your kit naming, your SKU conventions, how your components are stocked, your sharing rules, your typical and peak volumes, and your messy edge cases. It reflects a short tailored spec back to you for a thumbs-up, then shapes the data model, the math, and every later step around your real situation.

From there it walks you - step by step, in plain language - through building the importer, the availability engine (including the shared-component allocation logic), the review-and-approve screen, the audit trail, and the CSV export. Every build step ends with a ready-to-paste prompt for your AI coding agent. There's a "No API yet?" path so you can ship today using a Google Sheet or CSV as your data source, even with zero integration to your existing system.

The governance it includes (this is the point)

Anyone can paste together a calculator. The reason this tool is safe to put in front of your sales channels is the governance baked in:

• Login so only your team can use it.
• Row-level security so each organization only ever sees its own data.
• A full audit trail - who imported, who computed, who approved, and when.
• A hard human-in-the-loop approval gate - the AI computes the availability snapshot, a person reviews it, and only an approved snapshot can be exported and published.
• Duplicate guards so the same import or snapshot can't be processed twice (dedupe on kit + snapshot).

Who it's for

Ecommerce and ops managers, inventory-control specialists, and customer-service leads who sell build-on-demand bundles and are tired of overselling shared stock. You do not need to be a developer. If you can describe your kits and read a spreadsheet, you can build this.

You've got this - paste the first prompt and let the agent interview you.