01
Store overview
Understand sales, orders and reporting.
Etteroma
Bringing product, order, and reporting work into one operating dashboard.
Etteroma needed one place to manage the work behind its online store - products, inventory, collections, orders, fulfillment, and sales reporting.
We built a custom operations dashboard that brings those workflows together, so the business can manage day-to-day activity from one connected interface.
31
Products
3
Collections
5
Order states
4
Onboarding steps
9
Operating areas
Stack
Next.jsTypeScriptStripeResendRailway
01
Operational context
The customer sees an order. The business has much more to manage behind it.
The dashboard had to support several different kinds of work without treating them as unrelated admin tasks.
Product administration
Products carry more than a name and price. Collection, options, pricing, stock, availability and organization all matter.
Order administration
Payment and fulfillment answer different operational questions as each order progresses.
Business visibility
Paid sales, paid orders, units sold, recent activity and best sellers need to be visible in the operating environment.
02
What shaped the build
We designed around relationships and workflow, not around a list of screens.
The structure came from how the information connects and how work moves through the business.
Products needed relationships, not isolated records.
A product connects to its collection, available options, current price, stock and status.
Orders needed separate payment and fulfillment states.
Payment answers whether the transaction is complete. Fulfillment answers what happens next operationally.
Guidance needed to be part of the operating experience.
Guided onboarding and contextual help keep key tasks and reporting logic documented inside the product.
03
Store overview
The questions the owner needs answered every day.
The opening dashboard brings the current state of the operation into one view.
How much has been paid?
Paid sales show current commercial activity for the selected period.
How many paid orders are there?
Completed transactions remain distinct from orders still awaiting payment.
What is actually moving?
Units sold and best sellers show which products are generating activity.
What just happened?
Recent orders surface the latest purchases and current status.
04
Catalog administration
Product information changes as the business changes.
Pricing, inventory, options, availability and product groupings evolve over time. The catalog view keeps those operating details together.
Product
Core product record.
Collection
Where it belongs.
Options
Product variations.
Price
Selling price or range.
Stock
Available inventory.
Status
Current availability.
Collections have their own operating structure.
Product groups can be created, reviewed and maintained as the catalog evolves.
05
Order lifecycle
Payment is one moment. The order keeps moving.
Payment and fulfillment remain visible as two connected parts of the same order.
What moves with the order
Payment state
Whether the transaction has been completed.
Fulfillment state
What operational step comes next.
Customer communication
Transactional messages can stay connected to order activity.
01
Awaiting payment
Payment incomplete.
02
Ready to ship
Fulfillment can begin.
03
Shipped
Order in transit.
04
Delivered
Fulfillment complete.
05
Cancelled
Order exits flow.
01
Awaiting payment
Payment incomplete.
02
Ready to ship
Fulfillment can begin.
03
Shipped
Order in transit.
04
Delivered
Fulfillment complete.
05
Cancelled
Order exits flow.
06
Guided handoff
The operating guidance became part of the product.
Guided onboarding introduces the main operating areas, while contextual help keeps task-level instructions available inside the dashboard.
What the handoff covers
Orientation
Where the core operating areas live.
Core tasks
Products, collections, orders and reporting.
Reference
Help & Tutorials remains available inside the dashboard.
02
Manage products
See where catalog administration happens.
03
Organize collections
Understand product grouping.
04
Handle orders
Follow purchases through fulfillment.
Built-in help
Instructions stay close to the work.
The Help & Tutorials area keeps common operating tasks documented inside the dashboard.
Add a product
Upload product photos
Change price or stock
Organize a collection
Review an order
Understand reports
07
Technical foundation
The interface is only the visible layer.
Product records, order state, reporting, payments, users and transactional communication depend on the application layers underneath.
Dashboard interface
Next.js / TypeScript
↓
Application & API layer
Business logic and workflows
↓
Business data
Products, orders, users, reporting
Stripe
Payment processing
Resend
Transactional communication
Dashboard interface
Next.js / TypeScript
Application & API layer
Business logic and workflows
Business data
Products, orders, users, reporting
Stripe
Payment processing
Resend
Transactional communication
08
Outcome
One operating environment for the work behind the business.
Catalog administration
Product information, pricing, inventory, availability and collections.
Order visibility
Payment and fulfillment remain visible through the workflow.
Business visibility
Paid sales, order activity, units and best sellers.
Operating guidance
Onboarding and help remain available inside the dashboard.
Custom dashboards & internal applications
Build around the operation the software needs to support.
Start a conversationNext project
Custom Web Development for Healthcare Staffing