Customer profiles
Each buyer has a profile with their name, contact details and saved addresses, created when they first order or sign up.
Features · Customers
Each buyer has a profile with their addresses and full order history, and can see their own orders when they log in. Subscriptions, segments, loyalty and marketing tools are built or connected for you when you need them.
A moving band of sample orders from Indian cities, with the item, amount, payment method and status. The orders are made up.

The problem
An organic grocery has families who order the same vegetables, milk and atta every week. The owner knows most of them by name, but the details live in her phone: who skips when they travel, who wants the A2 milk, who still owes for last week. When she is away, nobody else can answer a customer properly.
Works on day one
Each buyer has a profile with their name, contact details and saved addresses, created when they first order or sign up.
Every order a customer has placed sits on their profile, so your team can see what they usually buy and whether anything is unpaid.
Buyers can log in to see their orders and track deliveries themselves, which saves your team a phone call.
Customers hear from the store when their order is confirmed, shipped and delivered.
Built or connected for you when needed
Custom work is built by the Code Colonies technology team on 2good.dev terms: you pay after you accept it. See the full list.
How it works
Returns and refunds
Requested, approved against your policy, picked up and checked. Returns workflows are built for you around the policy you publish.
Return #R-218, kurta in L
In progressA size swap: the M goes out once the L is picked up and checked. Exchange rules like this are set up for you.
1/5
Customer: Meera Deshpande
An example
A Pune organic store delivers vegetables, dairy and staples to about two hundred families, most on a fixed weekly order. On ShopenUp every family has a profile with their address and order history, so the delivery team can see last week's order without calling the owner. Weekly subscriptions with a skip button and recurring payment are not part of the standard store, so they ask us to build them. How often to deliver, what happens when a payment fails and how far ahead a family can skip are rules the owner sets. Customer names, phone numbers and addresses are personal data under India's Digital Personal Data Protection Act, 2023, so they also look at how they collect consent and answer deletion requests.
Illustrative example with sample data.
Questions
Not on day one. Subscriptions and recurring billing are built for you as a custom module, with the rules for skipping, pausing and failed payments agreed with you first.
Your customer data is yours. It can be taken out through the API, or our team can help with an export when you ask.
Shopper data is personal data under India's Digital Personal Data Protection Act, 2023. You need a lawful basis such as consent, a clear notice and a way to handle requests. TrustOS, our group's DPDP compliance product at dpdpatrustos.com, can help, and your lawyer should confirm what applies to you.
Keep going
Feature
Every order in one list, from payment to doorstep, with the buyer kept informed.
Learn moreFeature
See what sold, what is left and what to reorder, from the admin.
Learn moreGuide
A platform move is the moment most small stores lose search traffic, and nearly always for avoidable reasons: changed addresses, missing redirects, thin product pages. The work comes down to what to record before the move, what to map, and what to watch in the weeks after.
Learn moreTrades that lean on customers
See the store running with your own products.
Send a few products and your trickiest order. The demo shows them in the admin and on a storefront, with a plain list of native and custom parts.