cowelltactical.com · design handoff v2

Screens for Peter

This set replaces the earlier direction. Pages are object-first: photographs and a specification table carry the product, with no marketing sections, no numbered process steps and no competitor comparison. Dashed boxes are photography or facts we are still waiting on from Matt. These files are design references in HTML, not production code.

Khand / BarlowCrimson #C8102E on #EDF0F2, white cards, ink #15171AZero radiusMobile nav is the developer's call

Read this first: two purchase paths

Carriers and loadbearing vests Configured in the Loadout Designer, quoted, then invoiced through Xero when the work is done. Never paid at checkout. Specs change during a sixteen-week build, so invoicing happens at the end. Owner's instruction: do not unify this with checkout.
Everything else Panels, identification vests, air medic vests, pouches and accessories are ordered and paid on the site. Checkout offers card, purchase order, or a quote request for departments that need one to get a PO approved.
Lead timesCarriers ~16 weeks · ID and air medic vests 4–6 weeks · pouches and accessories within 2 weeks · panels batched weekly, ship Wednesdays Sales taxIdaho orders only RepairArmor carriers only, $50/hour, quoted first. Not vests, panels or pouches One sign inThe store and the Loadout Designer share one customer identity — email plus a confirmation code, no password. Customer records live in Xero, or are pushed to it, so a returning department is the same customer in both systems. "Sign in" is a single door that routes by what the customer has: store orders, carrier quotes, or both Owned by LoadoutArmor tracings, measurements, reorders, saved department specs, and the patch/panel configurator

Screens

Home Portrait photo beside one statement, then the product list with prices, the shop paragraph, and in-service-with. No stat band, no testimonial trio. Open → Products index Catalog rows grouped by the two purchase paths. Wear-test block at the foot. Open → Armor carrier Sticky photo column, specification table, construction notes with labeled heads, in-service-with, ordering instruction. The template for loadbearing vests. Open → MOLLE pouches All 35 SKUs in nine categories with a jump nav, one global color, per-item quantity, live cart. Real SKUs; prices outstanding. Open → Identification vests Model, color, size and ID fields on one page, with a compare row. Clone this for air medic vests. Open → Cart, checkout, confirmation One page. Card / purchase order / request a quote as equal choices; tax line reacts to the state field; confirmation copy differs per route. Quotes are issued by Xero. Open → Wear a carrier first Runs like a lending library: samples listed with armor, size range and status, each row expanding to its check-out log. Program terms, an evaluation checklist that ships in the box, and program questions. Needs the shop's real samples and the damage policy. Open → Vendor information W-9 download, DUNS, CAGE, SAM, billing paths. Answers three of the five most common phone calls. Link it from Xero invoices and quotes, not just the site. Open → Questions and answers Expandable rows in four groups. Carries the owner-approved repair terms verbatim. Build the rest from Matt's phone log. Open → About Company history, how we work, owners, in-service-with. Copy is draft and the owner is rewriting it. Open → Contact Details as a table, two shortcut cards for people who should not use the form, topic picker that changes the message prompt. Open →

Not designed yet

Air medic vestsClone identification vests. Blocked on models and prices AccessoriesClone MOLLE pouches. Blocked on what is in the line Loadbearing vestsClone the carrier page, its own configurator entry Sign in, order statusPasswordless: email plus a confirmation code. With the developer Panel configuratorPrototyped separately by the developer Policy pagesTerms, privacy, shipping and returns

Waiting on the owner

Every dashed box in these files is one of these. Nothing here is a design decision.

All copy in these files is draft. The owner is rewriting it, so build copy as swappable content rather than hard-coded strings.