Before we moved the business to a new ordering system, online orders were not really “online” in the way people imagine.
Customers placed their orders through the website.
But behind the scenes, someone still had to manually copy those orders into a Google Sheet.
Pickup date.
Pickup time.
Cake size.
Flavor.
Custom request.
Lettering.
Customer information.
Order changes.
Everything depended on a person moving information from one place to another.
And because it was manual, mistakes happened.
A custom request would be copied incorrectly.
A lettering message would be written wrong.
A pickup date or time would not be updated.
Sometimes an order would be missed completely.
But the person who made the mistake was rarely the person who had to deal with the customer.
That usually fell on the manager at the store.
The customer would arrive expecting a cake.
The team would check the sheet.
The order would not be there.
Then the manager would have to apologize, investigate, call the owner, search the website admin, check emails, figure out what happened, and somehow find a solution while the store was still running.
One time, a customer came in for pickup at the confirmed time.
The cake was not ready.
According to the internal Google Sheet, the order was for the following week. But the customer had already confirmed a pickup date change by email. The website order had been updated, but the internal sheet had not.
From the customer’s point of view, they did everything right.
They placed the order.
They confirmed the change.
They arrived at the correct time.
From the store’s point of view, the order did not exist for that day.
That is the kind of problem that damages trust immediately.
Another time, a last-minute order was placed close to the pickup date. At that time, the shop normally required orders to be placed at least seven days in advance, so the production sheets were usually printed several days ahead.
The order existed in the website admin.
But it was not properly communicated to the production team.
On pickup day, the customer arrived and the cake was not there.
The staff did not know.
The manager did not know.
The owner did not know until the order was checked directly inside the website system.
The customer was upset, and they had every reason to be.
At that point, the issue was no longer just about making a cake.
It became customer service recovery.
It became reputation management.
It became refund decisions.
It became delivery coordination.
It became staff stress.
It became disruption inside the store.
One missed order became everyone’s problem.
That is what a weak system does.
It does not just create mistakes.
It pushes the cost of those mistakes onto the people closest to the customer.
For a long time, the solution was simply to “check more carefully.”
Check the website.
Check the sheet.
Check the email.
Compare the order list every morning.
Manually update changes.
Manually catch mistakes before they reached the customer.
But that is not really a system.
That is labor.
And labor does not scale well when the same problems keep repeating.
The issue was not that people were careless.
The issue was that the workflow required people to be perfect.
Eventually, I realized that the website did not just need to look better.
It needed to operate better.
The ordering system had to do more than accept payment.
It had to create clean production information.
It had to reduce phone calls.
It had to make pickup dates and times clearer.
It had to make custom requests easier to track.
It had to help the team see what needed to be made, when it needed to be ready, and what details mattered.
After moving from the old website workflow to a Shopify-based ordering system, the difference was immediate.
In the first month after the transition:
Total sales increased from $12,669 to $23,669.
Total orders increased from 151 to 257.
Conversion rate increased from 1.80% to 3.09%.
Average order value increased from $83.90 to $92.10.
Revenue per session increased from $1.51 to $2.85.
But the numbers only tell part of the story.
The bigger change was operational.
Customers had an easier time placing orders.
Staff spent less time handling long phone orders.
Production information became clearer.
Order mistakes decreased.
The team had less back-and-forth.
The store became easier to run.
That is what good systems are supposed to do.
They are not just there to make a business look more modern.
They are there to protect the people inside the business from repeated preventable problems.
Because when a system fails, it is rarely the system that has to apologize.
It is the person standing in front of the customer.
And after you have been that person enough times, you stop seeing systems as a nice upgrade.
You start seeing them as necessary.
Leave a Reply