Custom e-commerce: the business behind the online shop

When I think about an online shop, I think about the person who receives the order. Can they see what was bought, what still needs checking and who is handling it? Or is that information scattered across an inbox and a spreadsheet?

Getting the work behind the shop organised can make the day-to-day job easier for a small New Zealand business. A custom website can connect what the customer does online with what staff need to do next.

Help people choose the right thing

Selling equipment or parts often takes specialist knowledge. A customer may know what they need to do without knowing the name of the product that does it, and a grid of product photos with a search box only takes them part of the way.

Elma New Zealand is a useful example from my own work. Its online shop sells ultrasonic cleaning equipment and related products, supplied in New Zealand by Techspan. Customers can narrow the catalogue by product type, series, application and tank capacity. They can compare products, see prices in New Zealand dollars with GST options, and tell available stock apart from products that need a quote.

Those details help a buyer work through a technical range. Someone looking for a cleaner for a jewellery workshop starts from a different place than someone cleaning automotive parts, and the website can reflect that instead of expecting both people to understand the whole catalogue first.

That is the public buying experience. The admin examples below are possibilities for a custom build, and they don't describe Elma's private systems.

An enquiry, a quote and an order need different handling

An enquiry means someone needs help. A quote request needs someone to check the requirements and prepare an offer. An order is further along, although it may still need a stock check or a delivery arrangement. If all three arrive as the same generic email, staff have to work out which one they're looking at before they can do anything useful.

Take a vehicle-parts supplier as a purely illustrative example. A request could include the vehicle's make, model and year, the part selected and whether fitting is needed. Staff could check compatibility before confirming the order and pass the details to whoever arranges fitting, so the customer doesn't have to explain the vehicle again each time someone picks up the job.

That only works if the product and compatibility information is reliable. A well designed selection form can't make up for an inaccurate catalogue, so who maintains that information belongs in the project brief too.

Give staff an admin screen that fits the work

A custom backend is the part customers never see: the screens staff use to manage products, enquiries and orders. It can use the business's own language and put the next job somewhere obvious.

For a small distributor, that might be an order list showing what needs a stock check, what is waiting on the customer and what is ready to dispatch. Each item could have a person responsible for it and a record of the last update, so if someone is away, a colleague can see where things stand.

Customer history helps with that handoff. Previous orders, the current quote and relevant correspondence can sit against the same customer record, which gives staff a place to start when a repeat customer rings about a replacement or an earlier purchase.

I'd keep that record purposeful. It needs sensible access permissions, clear rules about what belongs in it and a way to correct mistakes. Storing every detail you can think of adds work and responsibility without helping anyone.

A different example from my work is Miss Sparkle Home Services. Its system connects the website with enquiries, quoting, scheduling and the field team's work. It's a service business rather than an online shop, but it shows why the admin needs to follow the job through after the first contact.

A dashboard should tell you what needs doing

I like a dashboard that helps someone get through their day. A sales graph might suit the owner, but the person packing orders probably needs a dispatch list and a clear flag on anything holding an order up.

A salesperson could see quote requests awaiting a response. The owner could see work that has been sitting too long or orders waiting on supply. Each person could have a view with the information their role requires.

The test is whether it answers ordinary questions. Has anyone dealt with this? What are we waiting for? Can this go out today? If a dashboard can't do that, I'd ask why it's there.

Sometimes the existing platform is the right answer

A standard shop platform may already cover what a business needs. If customers can choose products easily and staff can manage the resulting orders without much fuss, I wouldn't recommend replacing it just because I can build something custom.

There's also a middle option: keep the shop that works and add a focused tool or connection where the process gets awkward. What's possible depends on the existing platform, but it deserves a look before anyone commits to a rebuild.

Custom work becomes easier to justify when you can point to a recurring problem, such as staff retyping order details, product selection that needs specialist rules, or quote requests losing their context between people. I've covered the broader choice in custom web apps versus off-the-shelf software.

A custom system also needs ongoing care. Someone has to maintain integrations, check permissions and deal with changes in the business. It won't automatically include every feature of an established shop platform, and it isn't automatically cheaper, so the scope needs to say what you're getting and who looks after it.

Start with one order and follow it through

Before talking about a new dashboard, I'd walk through a recent enquiry or order with the people who handled it. Where did the information arrive? Who checked it? What got copied elsewhere? Where did someone have to stop and ask a question?

That gives a custom project a practical starting point. It might point to a better catalogue, a clearer quote process or one shared order screen, or it might show a process you can tidy up with the tools you already have.

If you'd like me to look at that with you, tell me how your business handles enquiries and orders. Bring the awkward bits, because they usually tell me more than a list of features would.