Skip to main content
MilGadgetCivilian field utility

Launch status · Evidence-gated

MilGadget is built for demand before checkout.

The storefront code supports catalog, cart and Shopify-hosted checkout, but a configured connection is not proof of product readiness. Live supplier candidates, samples and evidence remain UNKNOWN in this view. Checkout remains off until every product passes current authoritative approval and the global launch gates.

View catalog stateQA methodSupplier path

Current evidence boundary

This page does not infer products, samples, sales or revenue from configured integrations. The live candidate count is UNKNOWN and the authoritative approved count is treated as zero until runtime evidence binding is implemented and verified.

Deployment

Connections reported
  • ·milgadget.com, Lovable, GitHub and Supabase connections are reported
  • ·Production values and runtime health still require launch verification

Storefront

Code ready for staging
  • ·Server-rendered catalog, product and cart paths
  • ·Human-review and checkout gates
  • ·Policies remain launch-gated pending factual and legal verification

SEO structure

In progress
  • ·Guide hub
  • ·Checklist lead magnet
  • ·Safe candidate schema
  • ·Kit page schema
  • ·Breadcrumbs
  • ·Sellability-gated product sitemap

Suppliers

Readiness UNKNOWN
  • ·Hertwill connection exists
  • ·Syncee connection exists
  • ·AppScenic connection exists
  • ·Live access, product candidates and evidence have not been verified here

Shopify

Checkout blocked
  • ·Secure Storefront API implementation is present
  • ·Approved product count is treated as zero until authoritative evidence is bound
  • ·Checkout stays off until all global and per-product gates pass

Automation

Not measured here
  • ·Operational workflow status is outside this storefront view
  • ·No automation run, approval or fulfilment claim is inferred from a connection

Launch product depth

Template slots

130 planning/template slots exist; they are not supplier products.

Live candidates

UNKNOWN until connected supplier feeds are queried and evidence is stored.

Authoritatively approved

Treated as 0 until the storefront proves current Postgres evidence.

Samples or test orders

UNKNOWN; no result is claimed without dated evidence.

First sales gates

What must pass before any product is sold.

Supplier evidence

Open

Confirm wholesale cost, stock, image rights, returns, delivery days, and safe claim wording for each launch candidate.

Contribution math

Open

Check price against product cost, shipping, expected returns, payment fees, and first marketing tests.

Sample or test order

Later

Use sample evidence before stronger product claims, stronger photography, or paid traffic.

Checkout approval

Blocked

Checkout stays off until global readiness, Shopify state and exact authoritative Postgres approval/evidence binding all pass.

Next build priorities

What moves the store toward first revenue.

  1. 1. Verify read access and current feed health for Hertwill, Syncee and AppScenic; then record dated supplier evidence for each proposed product.
  2. 2. Reconcile every Shopify item to one supplier candidate and one immutable evidence digest; do not count template slots as products.
  3. 3. Select launch products only after market-specific shipping, returns, image rights, claims and contribution evidence is complete.
  4. 4. Deploy and privilege-test the authoritative Postgres parity contract, then verify the complete server-side gate before enabling Shopify checkout.
  5. 5. Record staging smoke evidence, legal/payment sign-off, deployment approval and a rollback identifier before launch.

Follow launch progress

Join the MilGadget waitlist

Get product QA updates and first access when approved kits go live.