Mendcard

Service cards with a customer link

How it works

How cards, visits and the next due work

You keep one card for each boiler, stove, appliance, vehicle, bike or lock. Each visit takes under a minute to add. Your customer opens the card's link or scans its sticker and sees the history and the next service due. The rules below are the ones the server enforces, in the order you meet them.

Last updated 28 October 2026

The rules, in the order you meet them

  1. Signing in. You make an account with a passkey: your device keeps the private half behind your fingerprint, face or screen lock and the server keeps only the public half. There is no password and no username. You get a recovery code once, for a lost device, and can add up to 10 passkeys.
  2. Your business. Before the first card you enter your business name and trade, and the time zone your days are counted in. Phone and website are optional and show on customer cards.
  3. A card. A card has a title the customer sees (for example Kitchen boiler), a make and model, and fields for you only: a customer label, a note, the serial number, an install month and, for vehicles only, a registration plate of up to 10 characters.
  4. Dates. Every date is a calendar day in your time zone, and today is your local date. Changing the time zone never moves a saved date. A visit can be dated today or up to 365 days back, never in the future.
  5. A visit's next due. Each visit chooses one of four: 6, 12 or 24 months after the visit date (31 August plus 6 months is 28 February, the last day of the shorter month), a date you pick, which must be after the visit, no next due, or keep the due as it is.
  6. The card's next due. It comes from the latest visit by date that did not choose keep; two visits on one day go by the one saved later. With no such visit there is no due. Deleting a visit works it out again.
  7. What the customer sees. The visits you marked as shown, newest first, and the next due as a month (Next service due March 2027) or a date (Next service due 12 Mar 2027). Once it has passed it reads Service was due in March 2027. Add to my calendar saves one all-day event: on the date, or on the 1st of the month when the card shows a month.
  8. Visit requests. The customer leaves a phone number of 7 to 15 digits or an email address, and when suits them. One card takes up to 3 requests in 24 hours. Requests are on your dashboard, and emailed to your confirmed address at most once an hour. They are deleted 90 days after they arrive.
  9. A new owner. By default the card stays with the object. Making a new link stops the old link and sticker, which then say the card has moved and on which date, and can show the new owner only visits from a date you choose. The new card says when its link was replaced and from which date visits are shown, and a card you restore after deleting it says so too.
  10. Archive and delete. An archived card stays readable for the customer with Ask for a visit off, and leaves the due list. A deleted card says This card is no longer kept by your engineer, and can be restored for 7 days.
  11. Limits. Up to 25 cards, archived ones included, and 500 visits on each card. You can add up to 120 visits an hour.
  12. When the server is busy. The site runs on a free hosting allowance with daily limits. When one is reached the page says "Saving is paused for now" and what you typed stays on your device.

Worked example

A heating engineer services a kitchen boiler on 15 October 2026 and chooses 12 months: the customer's card shows Next service due October 2027. In December the customer calls about a noisy pump; the repair is added with Keep the due as it is, so the card still says October 2027. Another boiler, serviced on 31 August 2026 with 6 months, falls due on 28 February 2027. In February 2027 that boiler is taken out and the last visit chooses no next due, so its card shows no date. On 10 November 2026 the engineer's due list shows a stove due on 30 October under Overdue and a fire due on 25 November under this month.

What it is not