Most small businesses that sell online don't have a broken shop. They have no shop at all, just stand-ins for one: an order form that sends an email, a direct message, a phone number, a payment app. It works, in that money changes hands. But no one can tell you what sold last month without digging through their inbox.
Here's a quick test. Ask what was ordered on a certain Tuesday and see what happens. If the answer means scrolling, the business doesn't have an ordering system. It has a pile of messages.
The fix isn't a bigger form. It's a setup that understands what you actually sell, with rules the site can enforce instead of just describing them.
The rule your site states but can't enforce
This is the most common problem we find, and it's worth spelling out. Sweet Squares sells a thirty-count box: up to three flavors, in any mix, from a list of forty-four. The old site could say that. It couldn't let a customer actually do it. The form sent three flavor names and a price, and the business had to work out how many of each afterwards.
That gap is where money leaks out. Every rule the page states but the system can't enforce turns into a phone call, a correction, or an order that arrives wrong. On the live site, the pan is the order form: pick a day, pick a size, tap flavors into squares, and watch the count. An uneven split across three flavors is just three taps, two taps and one.
What an ordering system has to know
This isn't a feature list. These are the questions a real business needs its site to answer without anyone stepping in:
- What's actually available today, and what's sold out.
- How much notice this order needs, and which dates the kitchen or workshop can really meet.
- Whether you deliver to this address, what it costs, and what the minimum order is.
- What was promised, at what price, to whom, saved as a record, not a message.
- Where the order is now, so the customer can check without asking.
- What the owner needs to see this morning, on one screen.
Money, stated once
Deposits, payment terms, delivery minimums and refund rules tend to get written in two places, and then the two disagree. On one audit, we found an order page asking for a $15 deposit and a terms page asking for payment in full. Both were published and live, for years.
So your business rules live in settings you control, and every page that mentions them pulls from the same place. Change the notice period once, and the homepage, the product page and the checkout calendar all update with it.
Payments, without the lock-in
We connect payment providers in a way that keeps them separate from the rest of the site. If you switch processors later, it's a small change, not a rebuild. You get card payments, and you can keep the informal payment methods you already take alongside them.
Prices and totals are worked out on the server, not in the customer's browser. A total calculated in the browser and emailed can be changed by anyone who edits the page.
Work that shows it
Common questions
Should I just use Shopify?
Quite possibly, if you sell simple products with simple options, and we'll tell you so. A custom build makes sense when you have rules a template can't handle: a box with a flavor limit, lead times that vary by product, a delivery area with real boundaries, a daily limit on what the kitchen can make. That's where platform fees buy you a fight, not a shortcut.
Can customers still pay by Zelle or Cash App?
Yes, if you want them to. Plenty of local businesses take both, and there's no reason to stop. The difference is that every order is saved as a record either way, so each payment gets matched to something instead of remembered.
How do I handle things selling out?
From the admin, in a couple of taps, without calling anyone. Each item has its own availability, and it updates on the menu, the product page and the box builder at the same time, because they all read from the same place.
What about pickup and delivery windows?
Set up properly: real opening hours, real lead times, real daily limits. The checkout calendar only offers dates you can actually meet. That's the difference between a booking system and a wish.
How long does this take?
Longer than a simple brochure site, because more of it has to be right. Expect the upper end of our usual two to six weeks range, and sometimes longer, depending on how many rules your business has. The first weeks usually go into writing those rules down for the first time.