Ecommerce CRM Software Where The Customer And The Orders Are One Record.
Most CRMs sit next to the store and sync. This one is the store. The purchase history on a customer is the orders themselves, so there is no import to schedule and nothing to drift out of date between two systems.
What Sits On A Customer
One record, and none of it assembled at read time from somewhere else.
Who They Are
Name, email, phone and country, with a verified flag on the email and their own sign-in rather than a row somebody typed for them.
Where They Are
Many addresses per customer, with state as a real relation, which is what makes tax and shipping rules resolve instead of guess.
What They Bought
The order history is not an import. It is the same order records the rest of the dashboard works from.
What You Know
Free-text notes for the things that do not fit a field, and a metadata object for the things your own code needs to keep.
What They Are Worth
Points on the record, a referral secret, who referred them, and the affiliate fields if they sell for you.
What They Agreed To
Marketing consent stored as a timestamp, a source and the IP it came from. Not a checkbox: evidence.
Tags Do The Grouping.
A tag has a name, a color and a description. It can be applied by hand or by an automation, and a tag arriving on a customer is itself an event, so tagging somebody can start the next flow.
That is the whole mechanism, and it is worth being plain about the edge of it: there is no saved-query segment that recalculates itself as people qualify. Tags are applied, by you or by a rule you wrote. For most stores that is the same outcome with less machinery. For a few it is not, and those few should know now.
Consent You Can Actually Show.
Marketing consent is stored as three things: the moment they agreed, the place they agreed, and the address the agreement came from. A single yes-or-no field answers the question. These answer the follow-up question.
Personal fields are encrypted at rest, and phone numbers stay searchable anyway through a blind index. Encryption that breaks lookup gets switched off within the year, so it was built to not break lookup.
The Support Lane
Messages from your contact forms become records, not emails in somebody’s personal inbox. Six statuses, threaded replies, and attachments kept with the message.
newIt arrived and nobody has opened it.
readSomebody has seen it. Distinct from having done anything about it.
in_progressBeing worked on right now, so two people do not answer the same message.
repliedAn answer went out, threaded onto the original.
resolvedFinished, and still there to read.
archivedOut of the way rather than deleted, which is the rule everywhere here.
The Ones Who Bring You More.
Loyalty and referral are fields on the customer rather than a bolted-on app, which means a flow can read them and act on them like anything else on the record.
Points
A balance on the customer, readable and writable by an automation as well as by a person.
Referrals
Each customer carries their own referral secret and a link back to whoever referred them.
Affiliate Tiers
A tier with commission earned to date, and a per-customer override for the deal that was negotiated rather than assigned.
Their Own Login
A verified email, a real session and their own account, rather than a record that only exists on your side of the screen.
It Reads From The Same Records
Flows
Read And Write Back
A tag added is a trigger, and tagging is an action, so automations work both ways.
Questions People Ask
What is ecommerce CRM software?
It is where everything you know about a buyer lives: who they are, what they ordered, what they asked you, what they agreed to receive. On DashForDevs it is not a separate product syncing against your store. The customer record and the order records are in one database, so the purchase history on a customer is the orders themselves rather than a copy that drifted.
Does it do segments?
It does tags, and tags are how grouping works here. A tag has a name, a color and a description, it can be added by hand or by an automation, and a tag being added is itself an event other automations can start from. What there is not is a saved-query segment builder, so if your work depends on defining an audience by a rule and having it recalculate itself, that gap is worth knowing about before you sign up rather than after.
Is there a help desk or shared inbox?
Yes. Messages from your contact forms land as records with six statuses running from new through in progress to resolved and archived, they carry attachments and any custom fields your form collected, and replies thread onto the original. Nothing is deleted, so a conversation from last year is still readable.
How is customer data protected?
Personal fields are encrypted at rest rather than stored in the clear, and the platform reports the encrypted field count against its key-ring every time it boots. Phone numbers stay searchable through a blind index, which is the part most encryption work skips and then quietly reverses six months later when somebody needs to look a customer up.
Can I prove someone opted in?
Consent is three fields, not one: when they agreed, where they agreed, and the IP it came from. A boolean tells you the answer is yes. Those three tell you why the answer is yes, which is the version that survives being asked.
Does the CRM connect to the automations?
Directly. An account being created, an email subscription, a contact being created or updated and a tag being added are all triggers, and tagging a contact, creating one, updating one and opening a task are all actions. So a flow can read the customer record and write back to it in the same run.
Open One Customer And See.
Sign up, place a test order, and watch it appear on the record rather than in a queue waiting to sync.