GreenNode

A storefront where every order carries an environmental receipt.

_{Repository-native artwork used by the application.}

Your impact receipt

GreenNode treats sustainability as product data, not a marketing footnote. Shoppers can browse recycled and upcycled goods, see product-level footprint context, collect an order’s impact summary, and follow their activity over time. Administrators get the operational views needed to manage products, orders, users, and the quality of those sustainability signals.

ITEM                         STORE SIGNAL
────────────────────────────────────────────────────────
Sustainable product         footprint + comparison context
Cart                        running environmental total
Completed order             impact summary + history entry
Account                     progress, rewards, achievements
Community                   leaderboard and shared momentum
────────────────────────────────────────────────────────
                            GreenNode

The circular journey

flowchart LR
    A["Discover products"] --> B["Inspect eco context"]
    B --> C["Build a cart"]
    C --> D["Review price + impact"]
    D --> E["Complete checkout"]
    E --> F["Record order history"]
    F --> G["Update profile + rewards"]
    G --> H["Improve recommendations"]
    H --> A

Loading

Storefront ledger

Surface	Responsibility
Catalogue	Sustainable product discovery, filtering, details, and comparisons
Cart & checkout	Quantity management, totals, impact roll-up, and payment integration
Personal profile	Orders, footprint history, achievements, alerts, and exports
Community	Sustainability leaderboard and shared progress
Intelligence services	Activity logging, behavioral profiles, eco-aware recommendations
Admin observability	Product and user administration, system events, and cluster controls

Recommendation engine, without the green fog

The repository includes a behavioral clustering path that turns user activity into normalized profiles and groups similar patterns with K-Means. Recommendations can then combine personal history, cluster affinity, and a product’s eco-impact signal.

flowchart TD
    EVT["User activity"] --> PROF["Behavior profile"]
    PROF --> NORM["Normalized feature vector"]
    NORM --> KM["K-Means grouping"]
    KM --> AFF["Cluster affinity"]
    PROF --> HIST["Personal history"]
    PROD["Product eco score"] --> RANK["Candidate ranking"]
    AFF --> RANK
    HIST --> RANK
    RANK --> REC["Explainable suggestions"]

Loading

This is an application-level recommendation heuristic, not a scientific certification of a product’s environmental benefit. Production data and claims should always retain their source and methodology.

Under the canopy

Layer	Main implementation
Web application	Next.js 15, React 19, JavaScript
Interface	Tailwind CSS, Radix UI, shadcn-style components, Recharts
Forms & validation	React Hook Form, Zod
Identity	NextAuth, bcrypt
Data	MongoDB and Mongoose
Commerce	Stripe client/server packages
Messaging	Nodemailer, in-app smart alerts
Operations	Admin routes, system logs, activity services, database seeding

Grow it locally

git clone https://github.com/QizarBilal/GreenNode.git
cd GreenNode
npm install

Create .env.local with your own database, authentication, email, and payment-provider configuration required by the enabled modules. Do not reuse demo credentials or commit a populated environment file.

npm run seed
npm run dev

Open http://localhost:3000.

Command	Use
npm run dev	Start the Turbopack development server
npm run build	Create a production build
npm run start	Serve the production build
npm run lint	Run the project lint task
npm run seed	Seed application data through scripts/seed-db.js

Repository rings

app/         routes, layouts, API handlers, customer and admin screens
components/  shared visual building blocks
services/    intelligence, recommendation, and activity behavior
extensions/  optional alerts and platform extensions
lib/         database and application utilities
scripts/     database seeding and operational helpers
public/      product and storefront artwork

Before calling an impact “saved”

• Record the source, region, timestamp, and assumptions behind carbon values.
• Distinguish estimates from verified measurements in the interface and exports.
• Keep payment operations server-side and verify provider webhooks.
• Protect admin routes by authorization, not by an unlinked URL.
• Remove seeded or demonstration accounts before deployment and rotate any exposed credential.
• Define how account, order, activity, and recommendation data can be exported or deleted.

Contributing a new branch

Issues should state whether a change affects commerce, sustainability data, personalization, or administration. Include the data assumption behind eco-related changes and visual evidence for interface work. Keep claims testable and language precise.

License

The application source is available under the MIT License. Product imagery, third-party marks, sustainability datasets, and environmental claims may carry separate rights or attribution requirements.

---

Buy less blindly. Measure more honestly.