Skip to content
Coilwise

Case study

A pricing and ordering desk for a steel importer

A steel importer in Thailand buys coil overseas and sells it by the kilo at home. This page covers what we built for them, how it has grown since, and how each release is checked. Their name and their numbers are not on it.

screens
18screensbehind one sign-in
automated tests
386automated testsat the latest release, up from 21 on day one
releases
25+releasesin the first three weeks, each one tested before it went out
languages
2languagesEnglish and Thai, chosen per person

The problem

They order steel coil from overseas mills and sell it by the kilo at home. A shipment takes about two months to arrive, and in that time the coil price, the freight rate and the exchange rate all move.

Three questions kept costing them money. What will this coil really cost once it lands? What will it be worth by then? And is this the week to order, or is next month better?

The answers lived in people's heads and in spreadsheets. Each one took time to work out, and by the time it was worked out the prices had moved again.

What we built

A private web app that answers those three questions every morning, on a desk or a phone. It has eighteen screens behind one sign-in, and ten of them are described here.

Today's briefing
The expected margin on the next shipment, the likely range around it and the chance of a loss, recalculated as they change a figure.
Landed cost
Every cost line from the supplier's price to the warehouse door: freight by the container, insurance, duty, local charges and, if they switch it on, their own operating costs.
When to order
A 52-week view of which order week is expected to leave the most margin, and how much waiting is worth.
Suppliers
Quotes saved against each supplier and compared on what the goods cost landed, not on the quoted price.
Selling prices
Their own price list by product and size, shared across the company so everyone works from the same figures.
Freight
Freight quotes logged by the container, with a market estimate beside them for comparison.
Duties and rules
The import duties and trade measures that apply by origin and exporter, worked out for the date the goods arrive.
Price outlook
Forecast ranges up to 18 months ahead, each tested against history, with a diary of past predictions so the track record can be checked.
Scenarios
What-if tests before committing to a shipment: a weaker currency, dearer freight, a price rise.
People and access
The owner chooses which screens each person sees. Access is enforced on the server, and there is a log of who signed in and what was downloaded.
  • It collects its own data

    Four scheduled jobs bring in prices, freight and trade data, so nobody has to remember to update it.

  • Entries follow the person

    What each person enters is saved to their account, so it is there on the office computer and on their phone.

  • It says when a forecast is weak

    Where a forecast has not beaten “the price stays where it is” in testing, the screen says so in plain words.

  • It works on a phone

    Every screen has been audited at phone width, and the screens a release changes are checked there again, in both languages.

How it has grown

It went from a first version to eighteen screens in twenty-one days, across more than 25 releases. These are the larger ones, with the client's own requests marked.

The first three weeks, a day at a time

  • Asked for by the client
  • Our own next step
  1. Day 1

    First version live

    Sign-in, the first screens (landed cost, when to order, prices, freight, duties) in English and Thai, and the scheduled jobs that keep the data current.

  2. Day 2

    Entries saved to each person's account

    So nothing has to be re-entered on a new device. The owner also gets a log of sign-ins and downloads.

  3. Day 4

    A second product rangeClient request

    Added from the client's feedback and kept visibly separate from the first, so the two are never confused. A security review went out the same day.

  4. Day 5

    Forecasts to a year, and a briefing they can type into

    The order window grows from 12 weeks to 52, and the morning briefing becomes a calculator: change the price, the tonnage or the order week and the answer moves.

  5. Day 12

    A full audit of the numbers

    Every figure on the main screen was recalculated independently, outside the app's own code, and the core sums matched. Rates and rules were checked against official sources. The audit also turned up things to tighten, and those fixes went out the same day.

  6. Day 14

    Freight the way they pay for itClient request

    Switched from a price per tonne to a price per container, at the client's request. Entries already saved were converted and nothing was lost. Every screen was audited on a phone.

  7. Day 15

    Suppliers, operating costs, plainer words

    A new screen to save and compare supplier quotes, an optional switch to count operating costs, and a pass over every screen to replace jargon with plain language.

  8. Day 16

    Security update

    The framework underneath was updated. Every check was run again and the saved data was confirmed untouched.

  9. Day 21

    A freight estimate on the prices screenClient request

    Asked for by the client that week, in the same style as the other prices on the board.

How a release goes out

Seven checks run before and after every release of the client's tool, so that moving quickly doesn't break anything.

  1. 1

    Code checks

    The code is checked for the mistakes a computer can catch, before anything else.

  2. 2

    Automated tests

    386 of them at the latest release. They cover the sums, so a change in one place cannot quietly break a figure in another.

  3. 3

    A full build

    The exact version that will go live is built and run first.

  4. 4

    A look on a desk and on a phone

    The changed screens are opened at both sizes, in both languages.

  5. 5

    Saved data, before and after

    What the client's people have saved is fingerprinted before the release and again after it, to confirm nothing was touched.

  6. 6

    A live check

    Once it is out: every screen still asks for a sign-in, every data link still refuses a stranger.

  7. 7

    A way back

    The previous version is noted with each release, so it can be put back if something is wrong.

Confidentiality

This page describes the software and how it is released. It leaves out the client's name, their prices, their volumes and their suppliers.

Those are theirs. They stay off this site unless the client asks us to add them, and a tool we built for you would be treated the same way.

Have a job like this one?

If part of your business runs on a spreadsheet that only one person understands, that's usually where a tool like this starts.

We reply by email within two working days, wherever you are.

Get an estimate