Merch Riot — mockups

Every product version in one sheet — 30 columns, identity pinned while the rest scrolls, four saved views, and filters for brand and for what needs a decision. Click any row to open the product record.

Open Catalog Products → catalog-list-v2.html

The eleven formulas, one row per formula at one unit spec. Marine Collagen 500 appears twice, at 90 and 60 capsules, on purpose: weight and dimensions only exist once a count does. Six formulas need a decision.

Open Source Formulas → source-formulas-list.html

The product-type taxonomy — what a product is, as against the Benefits that say what it does. Create, rename, move and retire a node; a node in use, or one with children, cannot be deleted and the control says which before you reach for it. Lives in Settings, not on the main nav.

Also addressable: a node blocked from deletion twice over — in use and with children · five products on one leaf: blocked by use alone · the branch that is not a supplement, and is empty · the one node that deletes — unused and childless · a retired node, still carried by the product nobody re-filed

Open Categories → categories.html

One catalog product: identity, versions, images, benefit tags and Supplement Facts. Where a source formula owns the physical facts they are read-only with an SF-0007 ▸ link back; a product that arrives finished owns them, picks its own label panel, and has its purchase orders and COAs below.

• Arrives finished · supplementCP-0044: Supplement Facts typed here, an incoming v2 to make active
• Arrives finished · topicalCP-0151, a cream: ingredient list, a batch waiting on its COA, research by Category
• Hard goodCP-0152: a Product details panel, POs with QuickBooks columns only, research by Guidance

Also addressable: ShipStation needs you: the run bar shows both systems and every control opens the drawer on that state (MR-385) · the Setup & gaps drawer open on the record; untick the Active marks and its rows follow (MR-386)

Open The product record → catalog-product-edit-v6.html

What the product still owes before it can be listed — and the two automatic jobs, QuickBooks and ShipStation, that create its records. Facts a person owes are a table; the two machines are cards, because each runs a lifecycle (checked · you decided · created · proved) that a table cell cannot hold. It opens as a drawer off the product record, and shows only what is outstanding — settled intake fields fold to one line.

• 1 · Things need youCP-0119: no front image and no weight, four folded away, both machines blocked (MR-389)
• 2 · QuickBooks needs youthe check found possible matches: pick one, or mint; a cost that differs opens the cost conflict (MR-373)
• 3 · Creating the recordsnothing waiting on you: QuickBooks minting, ShipStation queued behind it
• 4 · ShipStation needs youQuickBooks linked; the ShipStation component answered OK and read back at 0 oz (MR-385)
• 5 · All completethe verdict and the two records, each collapsed to a line opening on its proof

Also addressable: the ShipStation component that did not read back: sent against stored, and Send the weight again · the QuickBooks decision in the drawer: three candidates, one refused, and the cost conflict behind FP-0231 · CP-0102 rewound to state 1 — the product record opens it complete (MR-389) · after the decision: linked to FP-0231, keeping our cost · settled after the decision: minted by a person who checked 3 candidates · left unlinked to check, with the note · the settled drawer, opened · the product record carrying the processing banner · the drawer with work outstanding · CP-0044 arrives finished, a supplement: Supplement Facts and its batch are its own rows (MR-353) · CP-0151 topical: a received batch with no COA is a reminder that blocks nothing · CP-0152 hard good: a Product details panel row, and its POs with QuickBooks columns only

Open Setup & gaps → catalog-product-setup.html

The record that owns every physical fact — count, weight, dimensions, bottle, cost, ingredients. Read-only everywhere else; edited through a drawer that opens over whatever screen you are on. Creating one mints its RW SKU in the background.

• A · The recordthe formula, its RW SKU, assets and the four brands wearing it
• B · Createone canvas; Create returns and the RW SKU mint follows on its own
• C · RW settledthe durable record after the RW SKU is linked
• D · Edit drawerthe editor opening over another screen, naming its blast radius

Also addressable: the record mid-mint, with the running banner · the drawer stopped on two RW candidates, waiting on a decision · the setup drawer with optional fields outstanding · the settled drawer, opened on the proof

Open Source formula → source-formula.html

Creation is a readiness checklist, not a wizard: three fields mint the product and Create is live from step 1. Sourcing comes first: a product that arrives finished never has a raw SKU or a formula, so its facts and label panel are asked here. Pressing Create product opens the new product with its Setup & gaps drawer, where the gaps and the QuickBooks item are settled.

• A · Create formstepped, with a third column that accumulates the record so far
• B · Duplicatean exact match is refused outright; a near match only warns

Also addressable: Arrives finished · a supplement: Supplement Facts typed on the create form (MR-356) · Arrives finished · a topical: an ingredient list, research by Category · Arrives finished · a hard good: Product details, research by Guidance · Arrives finished · a real product from ingredientlist.com: 27 Supplement Facts rows, 6 marked Active (MR-368) · step 6 · Ready to create: what is done and what is not (MR-390) · after Create with gaps: the drawer opens on ✓ created, the form keeps a status bar (MR-386, MR-387) · after Create with nothing blocking: the drawer opens on ✓ created and walks to complete (MR-388) · after Create, ShipStation needing you: the form’s status bar, resolved in the drawer (MR-388)

Open Add a product to the catalog → catalog-product-create.html

Every image the system holds, across the three libraries that own them — browse them, tag them, and administer the two dropdown lists the tags come from. Four structured facets (product, sale, sale type, image type) plus a free keyword pool; the pickers on the product, formula and channel screens still open only the one library that belongs to them.

• 1 · 50 imagesthe sales-channel library at the scale the question was asked about
• 2 · A folder per brandbrand is the folder, product is the group inside it
• 3 · Sale art onlythe sale tag as a cutter — nine images out of fifty
• 4 · Tagging one imagethe drawer, with machine suggestions an operator accepts field by field
• 5 · The two listsimage types and sale types, with an in-use count guarding every delete

Also addressable: the administration tab on its own · the catalog-product bucket

Open Image library → image-library.html

Where a bundle meets a box: the package table with its tares, the USPS tier × zone rate matrix, Bundle Mapping (source formula — or the product, where it has none — × pack size) and Combo Mapping (one row per mixed-product box), and the ShipStation automations generated from all of it. A row is Tested, Estimated or Pending, and one switch decides whether an estimate is allowed to name a box to ShipStation. An Estimated row opens How this was estimated: every pack size’s calculation side by side, and a Tested row — or combo — opens the same view as the estimate against the warehouse’s choice.

• 1 · Configuredthe package table, the rates and both mapping grids
• 2 · What we don’t knowtwo unweighed tares block their rules
• 3 · Resolving a combopromoting a repeat combo by hand — the resolver never promotes one itself
• 4 · Adding a packagethe tare is required, so a package with no weight cannot be created
• 5 · How an estimate was madeone Estimated row, every pack size’s calculation side by side

Also addressable: a Tested row: the estimate against the warehouse, 4 of 6 matched

Open Shipment Packaging → packaging.html

The four Channel Accounts, one row each. Two status columns, not one: active is your switch, connection is a system fact — and the row that matters is the one that is both active and broken. Promoted out of SCREENS.md’s SKIP because it owns the margin floor, the channel fee and the ad rate, which nothing else could set.

• 1 · All four accountsCA-03 is active with a dead credential — the only tinted row
• 2 · Filtered to what needs youthe same list, narrowed to the two that are not connected
• 3 · Adding an accountfour fields; creating does not connect it

Open Sales channel accounts → sales-channel-accounts-list.html

One account screen for every channel (MR-395). A shared top — identity, the connection card, margin floor, sales channel fee, Compliance and its listings — then the tabs its channel has: eBay’s listing defaults and ladder models; Shopify’s New job defaults, Money and Store behaviour. The connection runs a lifecycle — checked · authorised · scopes · proved — in five states, one set of nodes.

• 1 · Connectedall four beats green, nothing owing
• 2 · Expiringstill working; 11 days left on the grant
• 3 · Scope gapvalid token, one required scope missing — partly working
• 4 · Connection lostactive and unreachable, with what it stops right now
• 5 · Never connectedjust created; Connect starts the handoff

Also addressable: CA-01 Vital Depot (Shopify) — New job defaults · CA-01 — Money: the gateway pair and CheckoutChamp’s rates, with a worked order · CA-01 — Store behaviour: measured facts, not settings · CA-02 eBay — the ladder model library · arriving from the list on the broken account · the alarming state on its own

Open Sales channel account → sales-channel-account.html

Every listing on a channel, one tab per channel. The two grains differ and that is why they are two tabs: an eBay row is a listing, a Shopify row is a product that opens into its variants. Carries MR-027’s bookkeeping columns — qty · listed · by · sold · views — which were declared a year of decisions ago and never drawn. The Shopify tab carries two views — grouped by product, or flat by variant.

• 1 · eBay29 listings across two seller accounts, with lineage and the bookkeeping columns
• 2 · Shopifyfour products; status and published are two columns, never one
• 3 · A product openedthe variant sub-table — SKU, pack, price, compare-at, CheckoutChamp id
• 4 · Not purchasablea variant with no metafield is not in the cart and nothing errors
• 5 · Every variantthe second Shopify view — flat, one row per purchasable unit, grouped by a Product column
• 6 · Stale accountCA-03 is live and its figures froze when the token expired
• 7 · One listingthe whole built listing — content, images and their provenance, product, pricing, lineage, bookkeeping
• 8 · Previewthe listing as the marketplace draws it — and, on Shopify, one chip per variant
• 9 · Marketing anglesthe listing jobs’ own angle list, administered beside every channel (MR-379)

Also addressable: the ended predecessor, reached from its relist · a combo that was built and never listed — two of nine aspects filled, each blank with its reason · the storefront preview: a complete, buyable-looking page for a variant that is not in the cart · a Shopify product that is active, syncing and published nowhere

Open Sales channel listings → sales-channel-listings.html

Settings › Users & access — the part Cloudflare Zero Trust cannot do: a user row the app can write on a record, an API credential an agent can act through as a person, and an audit log with a definition and somewhere to read it. The API credential is a Cloudflare service token, minted here or in the dashboard and then assigned; the local row is authoritative, so disabling someone puts them out at once and the three Cloudflare calls that follow are a repair — which is why one of them failing reads not yet in sync (2 of 3) and not error.

• 1 · The usersthree people, their roles, tokens and last login — plus the Cloudflare token nobody has assigned
• 2 · One userrole, the status switch with its consequence, the token table, and the Cloudflare repair card
• 3 · Audit logwho did what, when and through which door — facets, keyset paging, and a row that opens onto its effects

Also addressable: Paul — the admin, two live tokens, nothing owing · one person’s history, the way a History link arrives · a record’s history — the &entity= form

Open Users & access → settings-users.html

Settings › Compliance rules — the house rules every listing on every sales channel follows, written out in one Markdown editor and saved. Every content generation and compliance check reads them together with the account’s own Compliance text; a channel can only add. No rule lists, no word patterns, no approval, no history.

Open Compliance rules → settings-compliance.html

Settings › Integrations — one grid of every connection to Shopify, eBay, QuickBooks, ShipStation and CheckoutChamp, one row each, worst first. Check cells are only ✓, ✗ or —; click a row for the reasons, what it is connected to, where its credentials live, Check now, Sign in again or Reconnect, and its last ten checks. A red banner while anything is failing.

• Two failingan eBay seller whose login expired, and CheckoutChamp refusing the website sign-in
• A login expiringeBay — main expires in 11 days: amber, no banner
• All workingno banner; two rows still not connected

Also addressable: CheckoutChamp’s drawer: the allowlist reason, and Sign in again that fails again · eBay — outlet’s drawer: Reconnect turns it working · an operator on the QuickBooks production row: Connect is for admins

Open Integrations → settings-integrations.html

One listing job end to end for an eBay account — products, packages, the SKU plan, brief, generated drafts, images, the ShipStation mirror, and a final review. Stage 3 is the package rule stack (was its own screen until MR-077): you type the one-bottle price and the ladder derives every bundle and combo from it.

• 1 · Accountthe channel account, and the defaults frozen onto the job
• 2 · Productsthe products in this job — search the catalog to add another; each name links back to its record
• 3 · Packagesthe rule stack — pool, shape, gifts, base prices, ladder — and the listings it makes
• 4 · SKU Planone row per listing — its recipe, its channel SKU and the two-system duplicate check, all settled before a word is written
• 5 · Briefsale type, guidance, benefits from the products and marketing angles, both searches open (MR-380)
• 6 · Draftsgenerated titles and descriptions, the claim gate, and the hand-off to an outside agent
• 7 · Imagesa lane per listing, a column per template slot, and the library beside it
• 8 · Buildone ShipStation bundle product per listing — the only record minted here
• 9 · Final reviewtwo views on the batch — walk one listing, or read all four in a grid

Its sibling: the Shopify builder

Also addressable: the final review as a grid — every listing about to be published on one page · the job before its first generation — Generate drafts is the only control · the agent pushed some listings and not others · Template 1 failed twice; the job can still go to the agent

Open Listing builder — eBay → listing-builder.html

One listing job end to end for a Shopify store — a sibling of the eBay builder, not a switch inside it. Tabs 1–6 write nothing outside the app; tabs 7 and 8 are execution, either side of the one human gate, and they share a display whose columns are the artifacts that now exist rather than the process steps. The CheckoutChamp sync has no progress to show and says so.

• 1 · Accountthe store, and the destination token, collection and campaign it brings onto the job
• 2 · Productsfive catalog products, one Shopify product each — no fan-out
• 3 · Packagesthe per-unit price at each tier; the pack price and the compare-at follow
• 4 · SKU Planthe SKU plan, its approval gate, the three-system duplicate check, and a Packages column saying what each SKU actually is
• 5 · Draftstitle, body, SEO and the advisory handle pre-flight — with the run bar reporting the research and generation that ran to get here, and the prompt readable beside the drafts
• 6 · Imagesa lane per product, six gallery slots, pushed before the sync
• 7 · Buildthe run finished, with one lane halted after the sync — and honest about what already exists
• 8 · Review & publishthe finished state at the gate; one product blocked, four ready

Its sibling: the eBay builder

Also addressable: handed to the outside agent — the export copied, nothing pushed back yet · the agent pushed some products and not others, and says which · the agent rewrote and pushed back — one approved in its harness · generation failed on the tab 4 approval; the gate reports it rather than claiming to be clear · the agent refreshed after the build — every product marked content drifted, with one repair · four already published and holding superseded copy — the drift is read before the publish state · mid-run — four lanes building, Eroluve halted on a handle collision · the hard stop before the sync, with the unresolved lane blocking it · during the sync — elapsed time, no progress bar, the CRM session · a row expanded onto its eleven steps with real ids · every variant, one row each · the storefront preview — one chip per variant, and the one a shopper cannot buy · four published and one outstanding — the job stays open

Open Listing builder — Shopify → listing-builder-shopify.html