Olivers

Delivery runs on three named rails rather than one shipping table: same-day inside the Newport postcodes, next-day across South Wales, next-day to the rest of the UK, each with its own cut-off and its own fee. A postcode checker sits on the product page and in the cart, so the answer arrives while the customer is still choosing.

The checkout treats the browser as something to be checked rather than believed. The server prices every line from its own table and ignores whatever price the page sent, recomputes the delivery fee from the postcode, recalculates the total and mints the order reference itself. A total that disagrees with the server's by more than a penny is refused, and the security rules let nothing but the server create an order record in the first place.

Two things were deliberately not built in. MAST did not bolt a card processor onto the shop at the start: Olivers already takes card across the counter, so the online rails are the ones the business was actually using, with a card processor wired in behind a switch to be turned on when card-not-present demand paid for it. The same reasoning ruled out the obvious subscription add-on, which would have tied the shop straight back to the platform it was leaving. Recurring orders were left as a contact-to-arrange page with the online wiring deliberately unbuilt, because at launch the business arranges them in person and paying for rails nobody uses is the mistake the whole rebuild was avoiding.

An AI-assisted operations layer drives product and content changes end to end, so the shop can be updated without a developer on hand.

That layer works to named routines rather than to open-ended instructions. A new bouquet, a price change, a retirement, a product going live, a workshop launch and a marketing pack each have one, and running any of them fans the work out across everything it touches — the catalogue, the photography, the printed pack, the marketing and the live site — because adding a product rarely ends at the product. Each run opens a ledger of what it still owes, the ledger survives a crash, and it does not close until the checks pass.

The checks are the part that makes the rest safe to run. They compare the shop's prices against the server's, the quoted delivery fee against the charged one, whether every product carries an image, whether the live product page actually renders and whether the checkout completes. Alongside them sits a fixed list of surfaces automation does not touch at all: payments, sign-in, the security rules, the legal pages, the checkout and the canonical catalogue. Those move on a person's say-so.