Project

General

Profile

Edit Copy Actions

Feature #10356

open

wroking on ecom and admin panel implementation for nexshop

Added by Teja Sriram Sangani about 1 month ago. Updated about 1 month ago.

Status:
In Progress
Priority:
Normal
Target version:
-
Start date:
08/13/2026
Due date:
% Done:

80%

Estimated time:
Spent time:

Add

Subtasks


Add

Related issues

Updated by Teja Sriram Sangani about 1 month ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 60
  • Implemented Accounts availability check in the main FE landing Login flow.
  • Added fallback to the main FE login (`localhost:5173/login`) when Accounts is unavailable.
  • Kept the existing redirect to Accounts (`accounts.localhost:5180/login`) when Accounts is running.
  • Updated Login behavior for desktop, mobile, footer, and “Login to Workspace” entry points.
  • Added `__accounts-ping` in `vite.config.js` to perform a real Accounts health check.
  • Updated `accountsHost.ts` and `EvergreenLandingPage.tsx` to integrate the new login/fallback logic.
  • Tested the scenario by stopping Accounts and verifying that Login opens the local FE login screen instead of `ERR_CONNECTION_REFUSED`.

Updated by Teja Sriram Sangani about 1 month ago

  • % Done changed from 60 to 80

• Completed the architecture feasibility study for the NexZenTek product-first model and confirmed that the existing stack can support the new architecture without a backend rewrite.

• Finalized the tenant architecture plan, implementation task breakdown, and feasibility analysis for the required architecture decisions.

• Fixed the session-expiry flow so users are redirected to the global Accounts login instead of the tenant-specific login URL.

• Implemented the PLAN_EXPIRED handling to prevent expired or suspended plans from proceeding and to show the appropriate message on the login screen.

• Clarified the hosting structure: nexzentek.com is used for the Gallery, while product domains such as pos. and landscaping. are used for the Staff application, login, and dashboard.

• Completed the Staff FE signup flow so the selected plan and billing cycle are passed from the landing/pricing page to registration and then into the company registration step.

• Finalized the overall signup flow: Landing → Select Plan → Company Registration → Account/Payment.

Edit Copy Actions

Also available in: Atom PDF