E-commerce and booking platforms

The short version

Standard checkout assumes a standard business: fixed prices, a box, a courier. Plenty of businesses are not that. If you price by volume or by customer, take a deposit instead of the full amount, book a two-hour window with a travel gap, or fulfill from three locations with different stock, the off-the-shelf platform starts costing you sales quietly, not obviously.

• Start by naming the rule your current platform cannot express. That rule is the whole scope.

• Shopify, Squarespace and the booking apps are good products. If one fits, use it — that is a cheaper answer than we are.

• The usual breaking points are pricing rules, deposits, real capacity, and fulfillment from more than one place.

• A custom storefront or booking system typically runs $15,000 to $40,000 over six to twelve weeks.

• You never hold card numbers. Payments go through Stripe or a similar processor, and that stays true whatever we build.

Where off-the-shelf checkout breaks

Not on the shopping cart. It breaks on the rules that make your business your business — the things a platform designed for the average merchant has no field for.

The five that come up most:

• Pricing that depends on who is buying — wholesale accounts, contract rates, tiered volume breaks, negotiated pricing per customer.

• Money taken in stages — a deposit now, a balance on completion, or a payment plan that has to survive a failed card.

• Capacity that is real — two trucks, not two slots; a technician who can do this job but not that one; travel time between appointments.

• Products configured, not picked — dimensions, materials, options that change the price, and a quote that has to be approved before it is an order.

• Fulfillment from more than one place — locations with different stock, partial shipments, buy-online-pick-up-in-store, and delivery windows that depend on ZIP code.

The tell that you have crossed the line is a spreadsheet next to the platform, or a step in the process that says "then they call us". Both mean the software has stopped modeling your business and started modeling half of it.

Staying on Shopify is often the right call

Very often, yes, and we will say so in the first call, not the third. Hosted platforms handle a colossal amount for a small monthly fee, and rebuilding what they give you for free is a bad use of your money.

The middle row is the one people miss. A hybrid — keep the storefront you have, build the quoting or scheduling engine it lacks, and wire the two together — is regularly a $10,000 answer to what was being quoted as a $40,000 replatform.

What a booking system needs to hold up

Bookings are harder than shopping carts, because a slot is not stock. Two people can want the same Tuesday morning, and only one can have it — while both are still typing.

What has to be right:

• Real capacity, modeled honestly: staff, skills, vehicles, rooms, equipment — whatever the actual constraint is.

• Service windows and buffers, including travel time between jobs and the setup nobody puts in the calendar.

• Holds during checkout, so a slot cannot be double-booked in the ninety seconds someone spends entering a card.

• Deposits and cancellation rules that match your terms, including what happens on a late cancellation.

• Reschedules and no-shows, which are the majority of the messy cases and are usually an afterthought.

• Reminders by email and SMS, because the return on a reminder the day before is the best in the system.

• Time zones and daylight saving, handled properly once, not badly forever.

The last one sounds pedantic until an appointment moves by an hour in November. Booking systems fail on calendar arithmetic more often than on anything else, and it is entirely avoidable.

Inside a custom storefront

The same catalogue and cart everyone has, plus the parts that are actually yours:

• A pricing engine that knows about customer groups, contract rates, volume breaks and promotions — and can explain how it reached a number.

• Product configuration, where choices drive price and availability instead of just appearing on the order.

• Quote-to-order, so a customer can request a price, you approve it, and they check out against it.

• Stock across locations, with backorders and partial fulfillment that do not confuse the customer.

• Wholesale accounts — credit terms, purchase order numbers, approval chains, statements.

• Accounting and shipping integrations, so an order becomes an invoice and a label without anyone retyping it.

Everything is built to work on a phone first, because that is where most of your customers are, and the search is built to be good, because in a real catalogue search is how people actually shop.

What it costs

A full custom storefront or booking platform sits in the same band as other custom web applications: typically $15,000 to $40,000, six to twelve weeks. Narrower pieces cost considerably less.

Before you compare that with a monthly fee, add up what you pay now across the platform, its apps, the transaction percentage and the staff time spent on the workarounds. For a business doing real volume, that annual total is often closer to a build than expected — and unlike the build, it goes up every year.

Payments, PCI, and the URLs you already have

You do not want to hold card numbers, and with us you never will. Card details go directly from your customer's browser to a payment processor — Stripe, Square, PayPal or similar — and your system stores only a token and the outcome. That keeps you in the simplest possible PCI category, and it is not a corner we cut for convenience.

One thing to raise early if you are replatforming rather than starting fresh: your existing URLs are an asset. Product and category pages that rank have taken years to get there, and a migration that quietly changes every address throws that away. Mapping the old URLs to the new ones and redirecting them properly is a small piece of work at the start of a project and an expensive recovery six months after launch, so we do it as part of the build rather than as an afterthought.

The parts that actually need care are the ones after payment: webhooks arriving out of order, a customer closing the tab mid-checkout, refunds and partial refunds, failed renewals, and disputes. Those are handled explicitly and reconciled, because "the payment went through but the order did not appear" is the one failure customers never forgive.

One sentence is usually enough to place you: "we charge wholesale customers differently", "we need a deposit and a balance", "a job takes a truck and two hours plus travel". From that, plus roughly how many orders or bookings a month you handle and what you pay today, it is normally clear whether you need a plugin, a hybrid, or a build.