Unfinished work, moving a shop, exporting a shop
Some jobs need a person. The panel lists them in plain sentences. A shop can also move to another partner, or leave with all its files.
The unfinished-work list
Section titled “The unfinished-work list”The panel’s “To do” tab lists, across the shops you can see, the real jobs that need a person. A partner sees only their own shops. Examples:
- A deposit was received but there is no confirmed booking.
- A refund is waiting for the owner, or its outcome is unknown.
- An answer from the owner has waited too long (12 hours by default).
Each item is one sentence in your language, with the time it began:
Deposit of ₹200 received, booking b-3 is missing: review recoveryAn item shows only the buttons that fit it: check the payment again, try to confirm the booking again, ask the owner again, check the refund again. A button only looks again or asks again. It goes through Guard and the same limits as everything else, and it never sends a refund a second time.
The list is read from the record the deployer exports every quarter of an hour. After you press a button, the shop’s agent acts within a minute or two, and the list changes after the next export. The page says “Read from the record of” a time. A shop with no export yet says so, instead of saying “nothing to do”.
Moving a shop to another partner
Section titled “Moving a shop to another partner”Example: a partner stops serving a shop and hands it to Divya.
- On the shop’s page, choose “Move this shop”. Type the new person’s sign-in name and the reason: they stopped paying, they stopped serving, or the owner asked.
- The panel shows a one-use code once. It runs out in 72 hours.
- Ask the owner to send
move CODEfrom their own phone to the shop’s WhatsApp number. The shop must be running to receive it. - When the message arrives, the new person serves the shop. This can take a quarter of an hour.
What moves: who can see and change the shop, and the name on the owner’s monthly report. What stays: the shop’s own WhatsApp number, payment account and calendar. No key is carried across, so whoever serves the shop next enters them again.
A shop can go to another partner or builder. It cannot go to Geometer. The reason is kept with the move and never sent to Geometer.
A move is within one server. Moving between two servers is an export and a new shop add there, with the keys entered again. There is no import yet.
Taking a shop’s files out
Section titled “Taking a shop’s files out”node bundle/geometer.ts export glow-salon --out ./glow-salon-exportnode bundle/export/check.ts ./glow-salon-exportThe panel’s shop page has the same download. You get open files, as a folder and a .tar.gz:
- the settings and the limits, with their history,
- the record, as JSON lines,
- the reports and certificates,
- a manifest with each file’s sha256, and a README.
No key or secret is in it. Customers’ numbers are short codes. It reads files only, so it works for a stopped shop and for a lapsed plan.
The second command re-hashes every file against the manifest, finds missing or extra files, and checks every signed paper. A changed byte fails it.