Skip to content
cairnscale

Cairnscale working example

Five events. One figure to trust.

A shop sells two items, receives a repeated sale, refunds an order and then tries to sell an item that has run out. Which number belongs in the report?

Follow the money and the stock

The source contains five events. Counting every sale and refund gives £27. Matching event IDs removes a repeated £9. Checking stock holds a second £9 for review. The reconciled total is £9, with three slate pieces and no maps left.

Who needs to act?

One of the five rows needs an operator. The stock owner checks order o3 before fulfilment. The refund returns one slate piece to stock. A repeat run from the same source produces the same total.

Download the editable order ledger (CSV) and the reconciliation script (JavaScript) into the same folder. With Node installed, run node fixture.mjs. The inputs are invented and the check runs locally.

What would implementation cost?

For scoping, an illustrative four hours to map the exports, four to connect them and two for testing and handover gives ten hours. Multiply by the agreed rate, then add any approved provider costs. A real quote follows a timed baseline with the buyer. Five rows inspected by hand versus one flagged row describes this fixture only.

Discuss a similar job

The start and end of one task, who owns it and an invented example of what goes wrong.

We work entirely online. A description is enough to start. Keep records, credentials and attachments for the transfer method we agree.

Start an email enquiry

Build a project brief online

Enquiry privacy · hello@cairnscale.uk