Skip to content

1. Getting Started

[← Index]/00-index/

1. Getting Started

Verified against: sindhu-naturals-site, branch feature/redesign-account, 2026-08-09.


What is Sindhu Naturals?

Sindhu Naturals is an India-focused ecommerce brand selling wood cold-pressed edible oils. Today the catalog has exactly two products, each sold in three sizes:

  • Wood Cold Pressed Groundnut Oil — 250ml / 500ml / 1000ml
  • Wood Cold Pressed Coconut Oil — 250ml / 500ml / 1000ml

INFO: No other products exist in the system today. A 5L variant is referenced in early planning notes but does not exist in the catalog — there is no packaging artwork for it yet.

Purpose of the admin system

The admin system is where staff manage the store day to day: creating and editing products, tracking orders, viewing customers, and generating GST invoices/credit notes. It is Medusa’s built-in admin dashboard (see [Section 2]/02-admin-dashboard/) — no separate custom admin application has been built.

Who should use the admin system

Staff responsible for catalog, order fulfillment, and customer support.

IMPORTANT: As of today, the system has one admin login per environment (one for local development, a separate one for the live testing server). There is no way to give a staff member limited/partial access — anyone with a login can do anything an admin can do. See Admin roles below.

Admin roles

PROPOSED — none of this is configured yet. There is no role or permission system active in this project today; the list below is a suggested future structure, not a real one. Do not tell a new hire “you are an Inventory Manager” — that role does not technically restrict anything today.

IMPORTANT: Medusa’s admin package actually ships real Roles/Policies settings screens, gated behind a feature flag that doesn’t appear to be turned on in this project — see [Section 26]/26-user-roles-and-permissions/#a-real-capability-was-found—correcting-the-premise-of-this-section for the full detail. Enabling that may be less work than building a custom permission system from scratch.

Suggested future roles (to be built, not currently enforced):

  • Super Admin
  • Admin
  • Inventory Manager
  • Order Manager
  • Content Manager
  • Customer Support
  • Read Only

Full detail: [Section 26 — User Roles & Permissions]/26-user-roles-and-permissions/.

Basic terminology

Plain-language definitions, in the context of this specific store.

TermMeaning here
ProductA sellable item, e.g. “Wood Cold Pressed Groundnut Oil.” Holds shared info like description, images, HSN code. Does not by itself have a price or stock count — its variants do.
SKUThe unique code identifying one exact sellable unit, e.g. SINDHU-GRN-500 for 500ml Groundnut Oil. Used to track that specific item in inventory.
VariantOne specific version of a product — in this store, a size (250ml / 500ml / 1000ml). Each variant has its own SKU, price, and stock.
InventoryThe system that tracks how many units of each variant are available to sell, at which location.
StockThe actual quantity on hand for a variant at a given location.
OrderA confirmed purchase made by a customer — created automatically when checkout completes.
CustomerA person who has registered an account or placed an order (guest checkout is also supported).
PaymentThe money transaction for an order, handled through Razorpay (test-mode credentials only today — see [payments status]/02-admin-dashboard/#payments).
ShipmentThe physical delivery of an order. Today this is a single flat-rate nationwide option — see [Section 13]/13-shipping/.
RefundMoney returned to a customer for a cancelled or returned order.
ReturnA customer sending a delivered product back.
CouponA discount code applied at checkout. Planned / Not yet implemented — no coupon has ever been created in this store.
CategoryA grouping of products (e.g. “Oils,” “Gift Sets”). Planned / Not yet implemented — the store currently has only 2 products and no categories have been created.
InvoiceThe GST-compliant tax document generated for an order. This is one of the more built-out parts of the system — see [Section 16]/16-invoicing/ and the note below.

INFO: GST invoicing is real and working — a PDF invoice is automatically generated when an order is placed, and a credit note when an order is cancelled from the admin. See [02-admin-dashboard.md]/02-admin-dashboard/ for where to find these, and the upcoming Invoicing section for the full workflow.

TO BE CONFIRMED: The GSTIN used for invoicing (GST_SELLER_GSTIN) is currently a placeholder value, not the business’s real GST registration number. Any invoice generated today is not a legally valid tax document until this is replaced with the real GSTIN.


[← Index]/00-index/ · [Next: Admin Dashboard →]/02-admin-dashboard/