Case study: online ordering built over a supplier's systems with no API

Three systems that never met. One front door now.

Sector: building products, composite doors · Client: a UK door retailer · Delivered by the engineering practice behind Better Systems Co. · Published 11 November 2026, updated 17 November 2026

In short: a retailer of composite doors ordered from a supplier that ran three separate systems, added over the years. One tracked orders. One was a trade-ordering plug-in from another company, with no API. Every order still had to be filled in again by hand. We built the retailer its own ordering website and connected it to the supplier's side, using a method the supplier had permitted. Orders now reach the supplier without re-keying.

This one is real. We have left out names and figures the client has not agreed to publish, and added nothing.

What was the problem?

A customer rings a door retailer. They want a composite front door. They describe it: the size, the style, the colour, the glass, the handle, which way it opens. Someone in the office writes it all down, works out which options go together, and gives a price.

When the customer says yes, the same person signs in to the supplier's trade ordering and builds the door again, screen by screen. Then the order has to be filled in once more, by hand, before the supplier will make it. The retailer sold doors from a single manufacturer, and this was the only way to place an order with them.

Two things went wrong regularly. A detail was misheard on the phone or mistyped on the second or third entry, and a wrong door is an expensive door. And the business could only take an order when somebody was free to answer the call, which put a ceiling on how many it could sell.

How did it get like that?

Nobody designed it. On the supplier's side there were three separate pieces of software, each with its own login, and none of them passed information to the others.

  1. Trade ordering. A plug-in made by another company, where a trade account builds and prices a door. It was built for a person to use in a web browser. It had no API, which is the usual way for one program to pass information to another, and no file import.
  2. Order entry. An order that had been through the plug-in still had to be filled in again by hand before it went into production.
  3. Order tracking. A third system, separate again, for seeing where an order had got to.

Each piece did its own job. It looked as though each had been added when it was needed, which is how most firms' software grows. The retailer's staff were the link between all three. The usual answer in that position is "it cannot be connected", which is why the double typing had carried on for years.

What did we build?

  1. A website where customers build and order their own door. They choose every option, the site stops combinations that cannot be made, shows the price and takes the order. The options, rules and prices match what the supplier's trade ordering offers the retailer, so what a customer can order is exactly what can be made. The screens are the retailer's own, laid out for a homeowner choosing a door, not for a trade clerk entering one.
  2. A controlled link into the supplier's ordering. With the supplier's permission for the approach, a service takes each confirmed order and enters it on the supplier's side in the form and order its screens expect. It then reads back what was recorded and compares it with what the customer ordered.
  3. Safeguards. Every order is recorded with exactly what was sent and what the supplier confirmed. If a step fails it tries again, then stops and tells a person. It never guesses, and nothing is sent twice.
  4. A look before it goes. The retailer sees each order before it reaches the supplier, and can hold it or change it.

Nothing on the supplier's side was replaced or changed. The three systems are all still there, doing what they did before.

What changed?

  • Customers order at any hour, including when the office is shut, and the door they describe is checked by rules, not by ear.
  • Nobody builds a door in the trade plug-in or fills an order in by hand any more. The staff spend that time on customers' questions and on the few orders the site holds for a second look.
  • Every order has a record of what was ordered, what was sent and what the supplier confirmed.

We are not publishing volumes or savings for this project, because nobody measured how long the old way took before the work started. We would do that differently today. Every Better Systems Co. project now starts by counting, so that the result can be given in the client's own numbers.

What we left out, and would add next

The third system, order tracking, was not part of this job. The same approach would bring it onto the same screen, so that the retailer and its customers could follow a door from order to delivery without signing in anywhere else. That is the work we now call one screen for all your systems.

What we would do the same, and differently

The same. Ask the system's owner first. Record everything. Read back and compare. Stop when in doubt. Differently. Count the hours and the mistakes before building, so the result is a number and not a description. That is now a fixed part of how we work.

Is this relevant to you?

If your business runs on software that was added a piece at a time, and your people are the link between the pieces, the same approach usually applies. That includes a supplier's or a customer's system that "cannot be connected", and an old system of your own with no API. It needs the owner's written approval, and we use a supported route wherever one exists. See trade and customer ordering portals, one screen for all your systems, connecting existing systems and the guide to integrating a legacy system that has no API.

Questions people ask

Did the supplier commission or endorse this work?

No. The customer was the door retailer. The supplier permitted the integration approach used to reach its system. We do not present this as work commissioned or endorsed by the supplier, and we would not connect to any system without the owner's approval.

Would you do the same for a system that forbids this kind of access?

No. If the system owner does not approve a route, we do not use it. In that case the options are a supported export or import, a request to the vendor, or accepting that the step stays manual.

Is a screen-level integration reliable enough for orders?

It can be, with safeguards: every order is confirmed against what the supplier system actually recorded, failures retry and then stop rather than guess, and a person is alerted. Where a supported API or import exists we use that first, because it is simpler to maintain.

Find out what the typing is costing you

A 20-minute call. You tell us about your Sandra, your Dave or your Phil, and how the job gets done today. We tell you honestly whether automating it would pay, and what it would cost.