Admin Docs Overview

These Admin Docs are for store owners, shop managers, support teams, finance teams, and operations teams who run AweCommerce from WordPress admin.

The Admin Docs explain how to set up, operate, and troubleshoot the store by clicking through WordPress admin and the storefront. They avoid implementation details and focus on what an operator needs to do.

What Admins Can Manage

Admins can manage:

  • Store setup and launch readiness.
  • Store pages and customer navigation.
  • Currency, email sender, seller profile, checkout behavior, agreements, and general settings.
  • Payment gateways and test or live mode.
  • Product catalog.
  • Product categories, galleries, product pages, and purchase buttons.
  • One-time prices and recurring prices.
  • Trials, setup fees, and billing cycles.
  • Taxes.
  • Coupons.
  • Customer records.
  • Orders, refunds, transactions, and invoices.
  • Subscriptions, pauses, resumes, cancellations, and payment recovery.
  • Memberships, protected content, and access grants.
  • Downloadable files.
  • Software licenses, activation limits, activated domains, key reveal, key rotation, and software releases.
  • Customer emails and admin notifications.
  • Reports, exports, Store Health, webhooks, and background tasks.
  • Privacy export and erasure requests.

Admin Area Map

The main AweCommerce menu includes these areas:

  • Dashboard.
  • Reports.
  • Launch Guide.
  • Products.
  • Coupons.
  • Customers.
  • Orders.
  • Subscriptions.
  • Grants.
  • Licenses.
  • Emails.
  • Settings.
  • Store Health or Operations.
  • Help.

Some pages are hidden from the main menu because they are reached from related workflows. Examples include tax settings and software release screens.

Use this setup order for a new store:

1. Activate AweCommerce. 2. Open the Launch Guide. 3. Create or repair store pages. 4. Configure currency. 5. Configure seller profile. 6. Configure email sender. 7. Configure checkout settings. 8. Configure required agreements. 9. Configure at least one payment gateway in test mode. 10. Add taxes if required. 11. Add coupons if needed. 12. Create products. 13. Add prices. 14. Configure downloads, memberships, or licensing if the product uses them. 15. Run a test checkout. 16. Confirm email delivery. 17. Confirm portal access. 18. Confirm reports and Store Health. 19. Switch gateway credentials to live mode only after testing.

Operational Principle

Treat AweCommerce as production billing software. Confirm every money movement, customer access change, and licensing action before launch. Test refunds and subscription failures before customers depend on the store.

Was this documentation helpful?