MOCKUP · Sample data only · Not connected to cartdock.shop · Buttons do nothing

Mockup notes

This is a clickable mockup of a redesigned Cartdock, built with Nee's (Distro Invoices) design: same fonts, colors, cards, tables, and buttons. Every number here is sample data except order #6225.
Routes checked101Every page, action, and download
Links checked12584 unique targets
Broken links0The links work. The layout is the problem.
Stylesheets today1946 !important overrides → 1 design system

Top fixes

Priority order
  1. Order page: “Void label” breaks into “Vo id lab el”. A CSS rule lets button text wrap after any letter. Fixed: buttons never wrap, and the label actions sit on their own row. See order →
  2. Items show “Master 186” instead of the flavor. Now each item shows the flavor name, then brand · model and SKU. No shelf field. See checklist →
  3. Raw system text like “Remote pack status packed.” Replaced with one status pill and a progress bar.
  4. Cluttered totals line (“Currency USD · Shipping … · Shipping tax … · Totals ok”). Now it's a clean totals block with a bold order total.
  5. Partner name vs master check. A warning appears when the partner's text names a different flavor than the master ID.
  6. 104 grey hint paragraphs (40 on the order page). Cut to one short note where needed.
  7. No shared header or nav, and Log out moves around. Now there's one sidebar, sign-out at the bottom, and a menu button on phones.
  8. Unclear buttons (“Label + slip PDF”, “Retry clear”, a button that says “Inactive” on an active product, bare Yes/Cancel). Now every button starts with what it does.
  9. Flavors hidden in folds on the product page. Now the flavor table is always visible, with a separate Count page that sends +/− changes.
  10. Orders list and Archive. 20 per page (20/50/100), newest first, last 7 days. Older orders move to the Archive automatically.
  11. SKUs are automatic. Made from brand + model + flavor when a product or flavor is added; read-only everywhere. Add product · Add flavor
  12. Partner plugin + guide. Distro.iM 1.1.30 download and the setup guide in English and 中文 on portal API & docs.
  13. Order lists simplified. “Units” column shows only the unit count; “Ship to” shows city and state. Full name and address stay on the order page and labels.
  14. Brand · model · flavor everywhere. One item-name component on every list, order, packing, pull list, inventory, product, count, report, partner and portal page and on the 4×6 prints. Sample items from GeekBar Pulse X, Lost Mary MT35000 and Fasta Alien 51K show why: four products are all called “Watermelon Ice”.
  15. Printing on 4×6. One order: label then slip · Several orders: label 1, slip 1, label 2, slip 2… · Pull list on 4×6
  16. Simpler label buying. Quotes are sorted cheapest first with a Cheapest badge. Tap one to select it (the others gray out). The selected quote becomes one “Buy label · $3.12” button with “Charges ship123 $3.12” and a 5-second Undo, with no separate confirm page. Void, clear stuck label and cancel keep strong confirms. See it
  17. Automatic box. 1–3 units: small box 8.625 × 5.375 × 1.625 in. 4+ units: big box 8 × 10 × 2 in (5 g). Weight = item weights + box. Custom box is optional. Each quote shows the box it used.
  18. Pause vs. delete. Deactivate (pause), Delete API key only, Delete partner completely, side by side on the Partner settings page. Full API key with Copy on the Partner settings page and the portal. Portal users are read-only in portal Account (managed in zzdistro.com).
  19. Partner settings, complete. Everything the live partner page (now “Partner settings”) has (profile, key Rotate/Turn off/Delete, portal login, prices with search, unpriced filter, CSV import/export, price history, staff audit) plus Approved products, a read-only Portal users list, Deactivate (pause) and Delete partner. Partner · Paused partner
  20. Partner portal (what the partner sees). Sign-in · My products · Orders · API & docs · Account
  21. Shipping, step by step, same as live. Ship an order · Every shipping state and message
  22. Sharing for 200+ partners. On the product page, Share-out means “available to the partner pool”. Each partner's Partner settings has its own on/off per flavor and its own price, plus bulk tools (whole product, one price for all flavors, copy from another partner). See partner →
  23. Sign-in page is left-aligned and prints the username. Now it's the shared zzdistro sign-in (decided 2026-11-19). See sign-in →

Mockup pages

Design rules used

  • Nee's Inter font, 14px text, numbers that line up in columns
  • White cards on a light grey page, 10px corners
  • One blue primary button per screen, with red for anything that can't be undone
  • Colored pills for status: blue to pack, purple needs label, green shipped
  • Tables turn into cards on phones (under 700px)
  • Plain words: “To pack”, “Needs label”, “Count kept by”

Jeff’s decisions (Nov 18)

  • Partner portal users move to zzdistro too (Jeff, 2026-11-19 1:30 PM CT). All user management, for staff and Partner portal logins alike, happens only on the zzdistro.com Settings page, and only Jeff manages it. Partner settings shows a read-only Portal users list (username, role, permissions, last sign-in, status) with “Manage in zzdistro.com”; the new-login form, password fields, password generator and per-user login buttons are removed. Portal Account lists the company’s users and permissions read-only (“contact ZZ Distro”); the new-user form, permission checkboxes, per-user buttons and the change-password form are removed. Partner sign-in is “Sign in with zzdistro”. The user-management permission is gone. The “Show partner price in portal” switch stays on Partner settings (it is a partner setting, not a user record).
  • Sign-in and staff users move to zzdistro (decided 2026-11-19). All user management for every zzdistro app lives in zzdistro.com Settings, and Cartdock staff sign in with the shared zzdistro sign-in. Settings now shows a read-only Staff access card (sample users, “Manage in zzdistro.com”); staff user editing and all Cartdock password controls are removed; the sign-in page is “Sign in with zzdistro”. SSO is already live on live Cartdock, with Jeff’s zzdistro account mapped to Cartdock user mj. Partner portal users followed at 1:30 PM CT (see the next decision).
  • One “Partner price”. The price list and partner cost are the same thing: the price ZZ Distro gives the partner. One field, labeled “Partner price” everywhere: per flavor → per product → default $10.00, with history and CSV export/import. The API sends it, reports use it, and the partner sees it read-only on portal My products.
  • Partner portal (main design): My products shows partner price (read only) and stock available per flavor; API & docs shows the full API key with Copy.
  • Names. The staff page for one partner is Partner settings (Partners › Vapicos › Partner settings). What the partner signs in to is the Partner portal. Button: “View as partner portal”.
  • Auto-cancel after 7 days. Orders not shipped within 7 days are cancelled automatically: reservation released in the master catalog, partner sees Cancelled via API and Partner portal. Rows 5–7 days old show “Cancels in N days” and a Cancelling soon filter; order countdown; cancelled order and Archive show “Auto-cancelled: not shipped in 7 days”. Replaces the old “keep unshipped past 7 days” option.
  • One “Pull list” button. The orders toolbar has one Pull list button (replaces “Make pull list” and “Pull list (4×6 PDF)”); it opens the on-screen pull list for the selected orders, which has Print 4×6 (the 4×6 PDF). “Labels + slips (4×6 PDF)” is unchanged.
  • 5-Pack SKUs (decided 2026-11-19). 5-Pack products use the single product’s model code + P (letters only) and the same flavor codes as the single: ZZ-VPP-GGP-WMI, ZZ-GKB-PLXP-WMI, ZZ-LMY-MTP-MMI, ZZ-FST-ALP-PCI, ZZ-ELF-PIP-BRI, ZZ-FOG-SWPP-JPI, ZZ-VNG-MCHP-TRP. Sample Elf Bar Pi9000 5-Pack SKUs now read ZZ-ELF-PIP-…; inventory and product pages show a Galactic Gleam 5-Pack sample. Catalog 5-Pack SKUs (VPP-GG5, GKB-PLX5, LMY-MT355, FST-A515, ELF-PI95, FOG-SWP5, VNG-MCH5) still need renaming in the master catalog.
  • Real catalog names (read-only check of products.distro.a2hosted.com Store API, Nov 18). Samples now use real products and flavors: VapePie Galactic Gleam, GeekBar Pulse X, Lost Mary MT35000, Fasta Alien 51K, Elf Bar Pi9000, Fog Switch Pro Pods, Vapengin Mecha (each also sold as a 5-Pack). Current catalog SKUs don’t follow the new rule yet: no ZZ- prefix, digits in model codes (LMY-MT35, FST-A51, ELF-PI9, VPP-GG5, GKB-PLX5, DST-GUM-1000MG-5PK), 4-letter flavor codes (FOG-SWP-JPIC, FOG-SWP-STWM), and codes that don’t match the flavor (LMY-MT35-WMI = Winter Mint; VPP-GG-BRI = Berry Ice while Blue Razz Ice is VPP-GG-BRZ). 5-Pack products get the single’s model code + P (decided 2026-11-19, see below). Renaming catalog SKUs is a catalog job, not done.
  • Brand names (Jeff). VPP = VapePie, GKB = GeekBar, FST = Fasta, ELF = Elf Bar, FOG = Fog, LMY = Lost Mary. DST: name not known yet, shown as code only.
  • SKU rule (confirmed by Jeff). Every SKU: ZZ-<3-letter brand>-<model code>-<3-letter flavor code>, e.g. ZZ-VPP-GG-WMI. The flavor code is 3 letters taken from the flavor name (Blue Razz Ice → BRI); a 4th letter is added only to break a clash within the product. Letters only: no numbers anywhere in brand, model or flavor codes (e.g. model “BC5000” → BC, “Alien 51K” → AL); a clash is broken with a 4th letter, never a number. Brand codes (from the master catalog): VPP = VapePie, GKB = GeekBar, FST = Fasta, ELF = Elf Bar, FOG = Fog (catalog says “Foger”), LMY = Lost Mary, VNG = Vapengin, DST = code only. 5-Pack products use the single product’s model code + P (letters only) and the same flavor codes as the single: ZZ-VPP-GGP-WMI, ZZ-GKB-PLXP-WMI, ZZ-LMY-MTP-MMI, ZZ-FST-ALP-PCI, ZZ-ELF-PIP-BRI, ZZ-FOG-SWPP-JPI, ZZ-VNG-MCHP-TRP. Generated by the master catalog. Lost Mary added as LMY. All sample SKUs use 3-letter alphabetic flavor codes (no S01 / F01 / 4-letter codes).
  • SKU format (decided by Jeff, 2026-11-18). The live format with a ZZ- prefix. Product SKU ZZ-<BRAND>-<MODEL>, e.g. ZZ-VPP-GG. Flavor SKU adds - and a 3-letter flavor code (4th letter only to break a clash), e.g. ZZ-VPP-GG-WMI. Brand codes (from the master catalog): VPP = VapePie, GKB = GeekBar, FST = Fasta, ELF = Elf Bar, FOG = Fog (catalog says “Foger”), LMY = Lost Mary, VNG = Vapengin, DST = code only. Auto-generated in the master catalog from brand, model and flavor; a clash adds a 4th letter. Every sample SKU in the mockup and the 4×6 PDFs uses this form.
  • Stock lives in the master catalog. Woo site 3 (products.distro.a2hosted.com, _stock) is the source of truth. Cartdock reads it through the catalog API (“Synced from master catalog · updated Xs ago” + Refresh), never edits counts, and has no DB-to-DB link. Receiving, counts, damage, case breakdowns and transfers happen in the inventory app (inventory.zzdistro.com); manual adjustments and uploads in the catalog. Cartdock sends stock events back: reserve on order, decrement on ship, release on cancel / 7-day auto-cancel, return/restock (event log). Columns: On hand, Reserved, Available (= on hand − reserved, what partners see), optional Incoming; pack breakdown is a nice-to-have. SKUs are created in the catalog (read-only in Cartdock; format ZZ-<BRAND>-<MODEL>-<FLAVOR>, set by Jeff). Partner matching uses the master ID.
  • No shelf field. Removed everywhere (item names, packing, pull list, slips, prints, product page). Pull lists and slips group by brand, then model, then flavor.
  • Everything else stays as live by default; proposals show only as labeled options.

Needs new backend work (not in the live code today)

  • Full API key display · keys are stored only as hashes; needs encrypted key storage.
  • Pause / resume key · today “Turn off” can’t be undone (no un-revoke route).
  • Deactivate partner and Delete partner completely · no routes today; only key delete exists.
  • Portal permissions per user · See partner prices (Owner always), See stock, See orders, See API key, Enter ad spend (no user-management permission: users are managed only in zzdistro.com). Users without “See partner prices” see “Price hidden for your access” (sample). Partner settings shows each user’s permissions read-only. Needs backend work.
  • Master switch “Show partner price in portal” per partner (Partner settings). Off overrides every user’s “See partner prices”; the box shows greyed out with “Turned off by ZZ Distro” (permissions, My products). Needs backend work.
  • Profit split per partner (Partner settings, default in Settings, history kept) and Profit + ZZ share / Partner share in Reports. Proposed formula (confirm with Jeff): Profit = Item sales (excl. tax, after discounts) + Shipping charged − Partner price × units − Label cost − Ad spend (spread per day), then split by that partner’s %. Tax collected is pass-through, not profit. Selling data comes from the partner’s WP/Woo site via the API order push, which already stores line price/subtotal/subtotal_tax/total/total_tax/unit_price and order subtotal, discount_total, total_tax, shipping_total, shipping_tax, total, tax_lines, prices_include_tax. Reports don’t use these yet, and profit split is new: backend work.
  • Ad spend · new Partner portal page (Ad spend): Day / Week / Date range, amount, optional platform and note, list with edit/delete, totals, overlap warning; per-user permission “Enter ad spend”. Staff see and correct entries on Partner settings. Reports subtract ad spend before the split; week/range spend is spread evenly per day for daily reports. New backend.
  • Auto-cancel job · daily/hourly job cancels paid orders not shipped within 7 days (Central time), runs the cancel stock move, records reason “auto_7d” (system), and reports Cancelled to the partner API/portal. Needs a countdown field on the orders list. New backend; the live code only hides orders after 7 days.
  • Partner sale data in reports · use the Woo order fields the API already receives (item sales after discounts, tax collected as pass-through, shipping charged) for Profit; today reports ignore them.
  • Master catalog: read API + stock-event write endpoint (reserve / decrement / release / restock) · the write endpoint is not built yet; Cartdock’s manual count save and CSV stock upload are removed from v2. None of this plan is built yet.
  • Multi-user portal logins with roles, managed in zzdistro.com · the Partner portal has one login per partner today.
  • Box rule · code uses the small box for 1–4 units and blocks 5+; Jeff’s rule (1–3 small, 4+ 8×10×2 in big box, custom optional) needs a change.
  • SKUs · auto-generated by the master catalog in the format ZZ-<BRAND>-<MODEL>-<FLAVOR> (set by Jeff); the catalog needs the generator and the ZZ- prefix. Cartdock shows SKUs read-only.
  • Portal shows partner price (read only), stock available per flavor, and the full API key · Jeff’s decision, main design. The live portal shows only the masked key and no prices or stock today, so this needs backend work (feed resolved partner price + available stock to the Partner portal; store keys so they can be shown).
  • One-click buy with Undo · replaces the preview + confirm step; the price re-check stays.
  • Archive page and paging on orders by date.
  • Retire the PartnerPrices store (Cartdock SQLite table partner_price: product default / per flavor, “Price on request”, price history, price CSV). Jeff decided: one Partner price (stored as the partner cost overlays). Its existing rows need a one-time review (compare with partner prices, carry over anything still wanted) before the table is removed. History and CSV move onto partner price.
  • New brand from Cartdock · needs the master to accept a new brand + 3-letter prefix.

All live functions now in the mockup

Needs attention · Import orders · Order money detail · Partner item changes · Price changed · Older/test orders · Full product page · Full add product · Inventory CSV upload · Settings · Daily report · Orders by date · New key · Partner price history + CSV · Error screens