Blog · a series
How we charge
Billing arithmetic, shown: which way every rounding goes, the one rule that stops a unit being priced twice, and the refund button that does not ask why.
5 parts · about 16 minutes to read them all
Part 1 · 4 min read
Ask for your money back, any time, and we will not ask why
If you have paid for time you are not using, there is a button that gives it back. No window, no reason, no email to support. Here is exactly how the number is worked out, and where we round.
Part 2 · 3 min read
Every rounding goes to the customer
Software is full of places where the arithmetic is not exact. Each one is a decision about who absorbs the fraction, and we made that decision once, in advance, for all of them.
Part 3 · 3 min read
One unit, one rater: the rule that stops us billing you twice
When two systems can both price the same thing, eventually both of them do. Here is the single rule we hold to instead, and the one line of SQL that enforces it.
Part 4 · 3 min read
A shop does not pay by the person any more
Per user was the wrong unit for a shop, not the wrong amount: a three-person counter paid three times for one till. Commerce, Inventory and Orders are now bought by the business on the orders it takes, with every member of staff and every register included.
Part 5 · 3 min read
One price list, and no page carries a price
One product was advertised at three different prices depending on which Rutba site you opened, and nothing could tell. Every figure now comes from one record as the page renders, and a test fails the build if anybody types a price into the site.
