Store launch and payment readiness¶

Status: planned; development remains fictional checkout only. Updated: 2026-09-19

Launch gates and assigned work¶

Kanboard owns status and assignments. All new tasks are Backlog, assigned to Angel as department triage owner; default review2026-10-19 is not a launch date. Existing payment-account task#23, shipping task#25, exemption task#52 and contracts task#138 are dependencies, not duplicated. Social login remains store-social-login, tasks266–271.

#272 Accept and reconcile store card payments through Stripe ¶

Depends on existing #23 payment-account setup. Use installed official Woo Stripe gateway; validate sandbox first, then approved live connection. Preserve test and live credentials separately; no raw card storage. Test successful/declined/3DS payments, signed duplicate/out-of-order webhooks, refunds, disputes, fees, payouts and ERP reporting. Never release fulfillment on an unconfirmed payment.

Deliverables: Gateway configuration and test evidence; reconciliation and failure-recovery SOP; approved live activation record.

#273 Handle store check and wire orders without premature shipment ¶

Depends on #23 banking details and credit/deposit policy. Native check/wire orders stay on hold; finance records clearance and reconciles by order reference. Define partial payments, timeout/cancellation, overpayments and refunds; do not confuse order receipt with settlement.

Deliverables: Approved instructions and clearance roles; offline payment acceptance tests; reconciliation procedure.

#274 Reserve ERP stock and synchronize every released store SKU ¶

Before real sales, validate SKU identity and unit mappings for all listings, available-to-promise stock, atomic reservation, concurrent checkout, release on cancellation/expiry, refunds/restock and retry reconciliation. Ten added test catalog items are not mapped in the order worker yet; mixed carts must not silently create partial ERP orders. ERP remains inventory authority.

Deliverables: Catalog mapping register; concurrency and retry evidence; production promotion and rollback record.

#275 Quote eligible shipping and verify label-to-pack fulfillment ¶

Depends on existing #25 shipping accounts/packaging. Configure measured parcels, rates, destinations, split shipments and customs; standalone battery requires its own transport documents and allowed services. Verify paid-and-allocated gate, one label per request, printer retry, tracking updates and exception handling; no automatic re-buy on ambiguous timeout.

Deliverables: Eligible shipping/rate matrix; test label and printer evidence; shipment tracking and exception SOP.

#276 Approve store taxes and customer-facing sales policies ¶

Use qualified finance review for US and international tax obligations and B2B exemptions. Link existing #138 contracts/policies and #52 exemption evidence; define sales/returns/warranty, privacy/deletion, contact identity and shipping disclosures before launch. Do not enable worldwide checkout by default.

Deliverables: Approved tax/destination configuration; published policy pages; exemption and order-total test evidence.

#277 Finish catalog presentation and customer checkout acceptance ¶

Finish actual images/specifications, approved retail prices and quantity breaks, search/filter/category organization, persistent Products navigation, breadcrumbs and pagination (recently viewed removed). Test mobile/accessibility, cart changes, guest/account checkout and My orders. Benchmark representative thousand-item catalog separately. Social login tracks #266–271; define any accepted staged deferral.

Deliverables: Listing release checklist; link/mobile/accessibility report; catalog load and customer journey evidence.

#278 Verify store email delivery and abandoned-cart reminders ¶

Prepare production transactional email with authenticated sender, order/receipt/shipping templates and delivery monitoring. Validate opt-in where required, unsubscribe, completed-purchase and unavailable-stock suppression for recovery reminders. Keep sandbox external email blocked and use captured messages for tests.

Deliverables: Email authentication and delivery evidence; reminder suppression/consent tests; support and notification SOP.

#279 Approve store launch after backup, security and order rehearsal ¶

Depends on all store-launch gates in linked plan. Prove database/media recovery, monitoring, secret handling, updates and rollback. Rehearse order-to-ERP-to-shipment/refund with approved credentials; review B2B access and payment isolation. Replace marketing coming-soon link only when actual launch accepted; keep unfinished features explicit.

Deliverables: Restore and security evidence; signed-off launch checklist and staged activation record; support/rollback ownership.

Release order¶

Finish account/policy decisions first, then payment/offline clearance, stock mapping and reservation, and eligible shipping. Customer journeys, email, restoration and security acceptance must pass before live activation. Social login and tracking maps may be staged only with an explicit scope decision; no provider or map is represented as connected. Processor transaction fees and postage remain business costs even with free software.

2026-09-19: Task277 incorporates navigation redesign; task280 adds documentation inventory and a wiki/forum decision. Existing Engineering Notes and real shop help pages are the initial support routes.

2026-09-19: Basic customer-facing Terms of Sale, Privacy, Shipping, Returns and Refunds, and Warranty/Product Use pages were published to the gated development store and linked from the footer. WooCommerce terms/privacy destinations now point to them while the development warning remains. Source/native checks and 52 browser checks at 375/1440 passed. Professional/legal review, tax/destination approval and production checkout wording remain task276 gates. Shipping configuration procedure: SOP-038 Store Shipping Setup.