Orders & receipts
Signed-in purchases can become persistent order history, giving customers somewhere to return to previous transactions and receipts.
Turn an order
into a customer
relationship.
One customer. One account. More useful every time they return.
A little more familiar, every time8:40
An account opened at Drip & Bake, in a name and an email.
Someone orders a coffee today.
They come back next week. They earn points. They find an old receipt. They subscribe to their usual order. They buy a ticket to an event. They visit another one of your locations.
Customers get an account directly inside your storefront where they can manage their profile and return to the orders, receipts, loyalty points, subscriptions, tickets and other services connected to your business.
For the business, those same accounts turn otherwise separate transactions into recognizable customer relationships.
Drip & Bake Customer Accounts give all of those interactions one place to belong.
01 / A place to belong
What customers get.
Customer Accounts are built directly into every Drip & Bake storefront.
A signed-in customer can use their account as their home within your business.
Depending on the services you offer through Drip & Bake, that can include:
- 01profile and account information
- 02order history
- 03digital receipts
- 04loyalty points
- 05subscriptions
- 06stored value
- 07event tickets
- 08community activity
They don't need separate accounts for loyalty, subscriptions, events or community.
Those services can belong to the customer account they already use to order.
02 / The next visit matters
Start as a customer.
Become a regular.
The first order doesn't tell you much about a relationship.
The fifth might.
Because activity can remain connected to the same customer, Drip & Bake can understand that today's order wasn't necessarily made by a stranger.
The account isn't required to begin the relationship. It gives the relationship somewhere to continue.
The relationship continues
01
Their previous orders can still exist.
02
Their points can still exist.
03
Their receipts can still exist.
04
Their subscriptions and tickets can still belong to them.
For the merchant, customer activity stops disappearing at the end of every transaction.
For the customer, returning doesn't mean starting over.
03 / One identity, throughout
Customer Accounts connect to the rest of Drip & Bake.
This is where the system becomes more useful.
We didn't build separate customer identities for every feature.
Ordering, Loyalty, Subscriptions, Community, Ticketing and other customer-facing systems can work with the same underlying customer account.
Loyalty
Purchases can contribute to the customer's loyalty relationship while Drip & Bake continues to understand where that activity occurred.
Subscriptions
Recurring purchases belong to an existing customer rather than becoming a disconnected subscription record.
Tickets
When customers participate in merchant events, their tickets can live in the same account they already use with the business.
Community
A person reading, liking or participating in a merchant's community does not need to become a different user when they decide to order.
Stored value
Balances can be associated with the customer while remaining financially separated by the appropriate business.
The result is not a collection of features that happen to have login buttons.
It is one customer relationship being used throughout the platform.
04 / Familiar, wherever they visit
One customer across your locations.
If you operate multiple connected locations, we don't think your regular customer should become a new person every time they visit another shop.
Drip & Bake's Linked Mode allows customer identity to work across participating locations within the same business relationship.
But we don't simply throw everything into one shared bucket.
Drip & Bake separates two ideas:
JWho the customer is.One customer identity
Your first locationOrders · Points · Records
Your next locationOrders · Points · Records
Where their activity belongs.
That means a customer can be recognized across linked locations while the system continues to preserve the location behind individual activity.
Loyalty can understand where points were earned.
Orders still belong to the location that received them.
Business-specific stored value can remain with the appropriate business.
This distinction is intentional.
Identity can travel. Money and operational records still need boundaries.
Prepared by a person.
Remembered by a regular.
Remembered by a regular.
On both sides of the counter
Useful on both sides of the counter.
Customer Accounts aren't only useful when someone opens their account page.
They also give other parts of Drip & Bake a customer to work with.
For authorized merchants and staff, that can provide appropriate customer context through systems such as the customer register and customer recognition.
For customers, completed orders can retain useful information from the other side of the transaction too. Features such as Prepared By can connect an order with the person who fulfilled it.
The business can recognize the customer.
The customer can recognize the people serving them.
That matters because cafés and bakeries aren't anonymous warehouses.
Hospitality is built around people returning.
Thought through, underneath
One relationship.
Carefully connected.
The principles behind the account.
Shared identity does not mean shared access.
The more useful a customer account becomes, the more carefully its boundaries need to be handled.
Drip & Bake distinguishes between customer access, employee access and authorized management access.
A customer should not be able to inspect another customer's information.
An employee should not automatically receive management-level customer access.
And a financial balance belonging to one business should not become available somewhere simply because the same customer can be recognized there.
We designed Customer Accounts around that distinction:
Connect what should be connected. Keep separate what should remain separate.
Why we built one customer system.
There was an easier way to build this.
Orders could have customers.
Loyalty could have members.
Community could have users.
Subscriptions could have subscribers.
Ticketing could have attendees.
Each feature could maintain its own version of essentially the same person.
We chose not to build Drip & Bake that way.
Eventually every one of those systems asks the same question:
Who is this customer?
Customer Accounts give Drip & Bake one answer.
That means when another part of the platform needs customer identity, we can connect it to something the platform already knows instead of creating another disconnected customer database.
It is why we think of Customer Accounts as infrastructure rather than another checkbox on a feature list.
Nothing extra to install.
Customer Accounts are part of the Drip & Bake storefront.
There isn't a separate customer portal for the merchant to deploy or another customer database they need to manually keep synchronized.
Customers create or access their account from the storefront they already use to browse and order.
The account experience follows the storefront rather than sending them into an unrelated application.
For the merchant, the relevant customer relationship becomes available throughout Drip & Bake where the business actually needs it.
Storefront for the customer. Operational context for the business. One underlying relationship.
Built to become more useful.
Know the customer once.
Let the relationship grow from there.
Customer Accounts weren't designed around a fixed list of account-page features.
They were designed to give Drip & Bake a persistent customer foundation.
As we expand what merchants can offer their customers, new services can build on the identity, history and relationships that already exist—with the appropriate permissions and boundaries around them.
That means the account can become more useful without repeatedly asking the customer or merchant to start again.