Import, export and entries without a connection
Getting data into an application is work. Getting it back out should not be.
Import: the preview first, the writing second
You paste a spreadsheet and the application tells you, row by row, what it would make of it, without creating anything. Only the second button writes.
An import that creates immediately leaves you, after one misunderstanding, with thirty items nobody meant. What the preview waves through, the run creates; what it stops, the run skips. That is why the preview also checks the patterns of identifiers, otherwise it would promise a row that is then rejected.
Which columns exist comes from the module. Both the key and its translation are recognised, regardless of case, so an export from this application can be read straight back in without renaming anything.
An unknown column does not vanish quietly, it appears in the preview.
Export: a link, not a request
You pull your whole inventory out yourself, complete as JSON or per kind as a table. No request and no form are needed; it is an address you can remember (Art. 20 GDPR).
The CSV columns are written out explicitly in the code, not taken from the keys of the first row. A new column in the data model should not silently change the format somebody built a macro against.
It is written to RFC 4180: comma, UTF-8 with BOM, CRLF. Without the separator hint line that would make a German Excel open it happily on a double click. That line is not part of the format, and every other reader would see it as a row of data. The note about "Data, then From Text/CSV" is on the page instead.
Anything that starts like a formula gets an apostrophe in front of it. A hyperlink formula in a "where" field is text when it is typed in and an executed formula when the file is opened. In a shared setting, one member types it and another opens it.
A calendar instead of one integration per provider
Deadlines are available as an ICS feed. Apple, Google, Thunderbird and Outlook all subscribe to an address: no account, no OAuth, no permission granted to a third party. End the subscription and nothing is left here.
Because the calendar asks without signing in, the address carries the proof — a long key you can revoke. The feed says little: title, item, date. No amount, no counter reading, no identifier, because a calendar entry sits on other people's servers as soon as somebody syncs a phone.
The entries are all-day. A roadworthiness test is due on a day, not at 9:13 in the morning.
Without a connection
The application installs and keeps working when the network goes. Whatever you submit in the meantime goes into a queue and is caught up later.
Every form carries a key with it, and the same key only ever writes once. Without that the queue could not run at all: a repeated submission would create the cost entry a second time.
If an entry really cannot be delivered any more, it does not disappear silently. Open windows get a message. An entry that vanishes without a word would be worse than one that was never sent.
Handing over means copying
When you sell something, a new item with a new identifier appears at the buyer; yours stays with you and goes to "sold". Your cost receipts therefore stay yours and keep pointing at a row you are allowed to read.
There is a sales sheet to go with it, holding what belongs to the item. Costs only if you want them, no working material, nothing expired. The route to a PDF is your browser's print dialogue.
More: costs · inspection dates