Launch is an evidence-based decision

A store opened because it looks ready discovers its gaps with the first shopper. A readiness checklist connects every visible promise to a real action, test, and owner. A product page is not enough: checkout must place an order, reserve stock, calculate delivery, expose an executable payment method, and issue a secure status capability.

Fix the market before entering money

Choose store country, currency, decimal scale, and timezone before prices and orders exist. After the first financial record, currency cannot be a cosmetic setting. Every order snapshots currency, tax profile, business identity, and locale so a future configuration change never reinterprets history.

Complete business and tax identity

Record legal name, registration state, and identifier when applicable. Decide whether prices are tax inclusive and how shipping and fees are treated. These operating settings require merchant approval and local review; a seeded rate is not a compliance claim. Define whether Shop Tek produces an order receipt or a statutory invoice supported by an approved jurisdiction workflow.

Run a complete catalog journey

Create a real product with imagery, intrinsic dimensions, and useful alt. Exercise a variant, stock, price, discount, category, and collection. Open Arabic and English pages and verify equivalent facts, URL, and search metadata. Export a sample and import it in a test environment so migration columns, currency scale, duplicate SKU behavior, and rollback are understood.

Configure shipping around the local address

Review every region the merchant serves and assign a rate or disable it. Test the complete country address, normalized local phone, optional delivery pin, and store pickup. Do not expose a carrier until the account, contract, failure monitoring, and operating support are live. An own-driver role should see assigned deliveries instead of the full merchant desk.

Exercise payment and refund

Place one COD order and one reviewed-transfer order. Submit a reference or private proof, reject it with a clear correction, resubmit it, and approve only after checking the bank. Record a partial refund with a reference and verify currency and remaining balance. In Jordan, test CliQ as a transfer QR; never treat the QR itself as settlement confirmation.

Review publishing and search

Before indexing, enable SSR and verify that initial HTML contains one title, one H1, canonical, and valid hreflang. Inspect robots and every sitemap child. Preview, account, checkout, and admin URLs remain noindex. Do not activate a country page until its capability matrix and copy review are complete; a truthful noindex page is safer than an indexed sales promise the product cannot fulfill.

Prove operations

Deploy to staging from Git, run owner-role migrations, and test workers, scheduler, SSR, alerts, backups, and isolated restore. Preserve owner, staff, shopper, cart, and guest-order sessions through deploy and code rollback. Probe TLS through a real tenant hostname; a Host header request cannot prove SNI or certificate coverage.

Launch gate

• Market, currency, scale, and timezone fixed.
• Business, tax, and document boundary approved.
• Product, variant, stock, discount, and import tested.
• Shipping regions, address, phone, and pickup tested.
• COD, transfer review, and refund evidence complete.
• Arabic and English facts equivalent.
• SSR, robots, sitemap, redirects, and schema valid.
• RLS denies cross-tenant access.
• Deployment, rollback, sessions, backup, and restore proven.
• Support, monitoring, incident owner, and rollback decision known.

With this evidence, launch becomes a controlled transition into operations instead of a debugging exercise performed on the first shopper.