# DC Bundles: a short guide
Written for Linh. Open **Apps > DC Bundles** in the Shopify admin. It works on
a laptop and on a phone.
## The pages
In the Shopify admin the app's pages appear in the left sidebar under DC
Bundles. On a phone or outside the admin they appear as tabs at the top.
**Dashboard.** Numbers at a glance (active, draft, out of stock, waiting
for approval, package orders and revenue for the last 30 days), a "Needs
your attention" list with buttons, recent activity and quick actions.
**Program rules.** The rules every package is checked against, in plain
English, straight from the engine.
**Settings.** Who can approve, whether each person's Claude sign-in helper
is running, when the engine last ran, and the app version. Nothing secret.
## The main pages
**New package.** Type what you want in the big box and press **Plan it** (or
Cmd+Enter). The page finds the products, drafts a plan and shows it to you as
tiles: each slot with its main product, price and stock, plus the other
choices a customer can pick. Read the notes under the plan; anything in
yellow is good to know, anything in red must be fixed before you can build.
When it looks right, press **Build this package**.
**Requests.** Everything you asked for, newest first, with a status.
**Packages.** Every package in the store with its Shopify status (Active or
Draft), a stock badge, the price and the items inside. Click a package title
to see each component, its quantity and whether customers can still buy the
package with a swap. Buttons: **View**, **Edit**, **Set to Draft** (hides it
from the store), **Set to Active** (approvers only).
**Sales.** Orders that contained a package, for the last 30 to 360 days,
with a weekly chart and the top packages. Tracking started 2026-08-28.
## Writing a good request
Name the brand and the exact models. Say which items should be a choice.
- "Scubapro Hydros Pro 2 Air2 package with MK25 and MK17 regulator options and a 2-gauge console"
- "Apeks Exotec BCD package with MTX-RC, EVX200 and XTX40 regulator choices plus an octopus"
- "Shearwater Peregrine TX computer with a Swift transmitter and a wrist strap, priced at 899"
Rules the plan follows for you: one brand per package, three or more options
whenever customers get a choice (with only two it becomes a fixed item), new
products only, in-stock products only. The price is the sum of the parts
unless you give a package price.
## What the statuses mean
| You see | It means |
|---|---|
| Planning | The products are being found and the plan written. About a minute. |
| Plan ready | Review the tiles, then Build. |
| Drafting, Checking rules, Researching specs, Publishing, Images and description, Verifying | The package is being built as a hidden draft. This takes 15 to 40 minutes. You can close the page. |
| Waiting for approval | The package is built and hidden. An approver (that may be you) checks it and presses Approve. |
| Approved, going live | Someone approved it and the store is being updated. Under a minute. |
| Live | The package is on the store. Press View in store. |
| Needs attention | Something stopped. The red sentence says what to do next; usually it is "try again" or "ask Jason". |
"Waiting for your Claude sign-in on the build machine" means the part of the
work that runs under your own account on the build Mac has not answered yet.
If it stays longer than ten minutes the request stops with a message asking
Jason to start it.
## Building several packages at once
You can describe a whole family in one request, for example:
- "For every Shearwater computer we carry, build computer + Swift transmitter, then + EVA case"
- "Reg+BCD packages for these five BCDs: Hydros Pro 2, Navigator Lite, Bella, Glide, Level"
- a pasted vendor sheet, one package per line
The plan comes back as a list of packages. Each one is a card you can open
to see its items and prices; ready ones are ticked, ones that need changes
are unticked with the reason on the card. The line at the top says how many
are ready. Press **Build N packages**: they are built one after another
(about 25 to 35 minutes each) and queue behind anything already running,
so you can close the page. On the **Requests** tab the batch shows a
progress bar ("3 of 8 built, 1 waiting for approval") and an **Approve all
in this batch** button once packages are ready.
## Approving packages
When the app is set so that everyone can approve, you can approve your own
builds. Open the package with **Open in admin**, check the title, the
items, the prices and the images, then press **Approve and make it live**.
To approve several at once, open the **Requests** tab: the **Needs
approval** section at the top lists every built package that is waiting.
Tick the ones you checked and press **Approve selected**, or press
**Approve all (N)**. One confirmation asks "Make N packages live in the
store?". Each package goes live on its own, so if one has a problem the
others still finish; you get a message per package.
Every approved package shows "Approved by <name> on <date>" on its card, in
the Requests list and on the Packages tab. Packages still waiting show "Not
approved yet".
## Editing a package
On the Packages tab press **Edit** next to the package, then describe the
change ("swap the console for the compass console", "add the S270 octopus as
a third choice"). This builds a new version and, when an approver approves it,
the old one is taken off the store automatically.
## Hiding or showing a package
**Set to Draft** hides a package from the store right away (nothing is
deleted). **Set to Active** puts it back; only approvers can do that. Both
ask you to confirm first.
## If something goes wrong
Every error is one sentence with what to do next. Two you may see:
- "Your Claude sign-in on the build machine is not set up yet." Ask Jason to
add you.
- "The planner timed out. Try again in a minute."
Nothing goes live until someone presses Approve, so it is safe to
experiment with plans.