COA library checklist
COA library checklist is included in the paid service pack so customers can launch, refine, and operate delivery-zone and category pages without chasing outside docs.
Resources
Useful launch notes, playbooks, and configuration shortcuts.
Everything here is organized to help the site stay easy to manage after you put it live.
Delivery page structure
Delivery page structure is included in the paid service pack so customers can launch, refine, and operate delivery-zone and category pages without chasing outside docs.
Repeat-order strategy notes
Repeat-order strategy notes is included in the paid service pack so customers can launch, refine, and operate delivery-zone and category pages without chasing outside docs.
Launch checklist
- Replace the Stripe secret key, publishable key, webhook secret, and plan price IDs in config.php.
- Replace the SMTP host, username, password, and sender values in config.php so outbound mail runs through your real mailbox.
- Publish SPF, DKIM, and DMARC records for the sending domain before testing outbound mail.
- Replace the app secret in config.php with a long random value before going live.
- Confirm the support inbox at hello@hemp2go.online or change it to your preferred address.
- Upload the folder contents to the domain's public_html directory in cPanel.
- Make storage/ and its subfolders writable so leads, orders, deliverables, logs, and private workspaces save correctly.
- Point your Stripe webhook to /webhooks/stripe and subscribe to checkout.session.completed, customer.subscription.updated, customer.subscription.deleted, invoice.paid, and invoice.payment_failed.
- Submit sitemap.xml after launch and test pricing, checkout, activation, login, password reset, and portal flows.
FAQ
The funnel is designed around self-serve pricing, direct payment-link routing, and content blocks that answer common questions before live support is needed.
Stripe checkout can provision the customer instantly, generate an activation link, and open a private workspace with onboarding, saved resources, and a plan-specific execution board.
Yes. Payment links are stored in config.php so you can plug in the Stripe, PayPal, and crypto checkout URLs you already own.
Yes. Each site includes responsive layouts, page metadata, schema markup, robots.txt, sitemap.xml, and extensionless URL support through .htaccess.
Start with coa-forward product pages and one recurring offer so the site can begin compounding with minimal operator time.
Included systems
More than docs. This is the operating stack behind the site.
SEO page stack
Public pages organized to capture demand for local same-day delivery and related searches.
Operator control layer
Admin login, SMTP testing, manual provisioning, and access recovery for live operations.
Fulfillment files
Protected downloads and workspace modules so the paid customer receives usable assets immediately.
Portal packs
Protected files and service assets included after payment.
COA-forward product pages Launch Blueprint
A packaged delivery plan for the first version of delivery-zone and category pages.
COA library checklist Operating Pack
Included operating notes so the purchased service is usable right away after activation.
Education-led storefronts Conversion Pack
Ready-to-use messaging and launch priorities aimed at hemp-derived product retailers, delivery operators, and local CBD shops.