RFID Smartzoom Console

New system

Business name

What the customer calls themselves. Their first warehouse is named after it.

System ID

Suggested from the name, and yours to overrule. They type this at every sign-in, so it should be short and theirs. It cannot be changed afterwards.

Database Create it hereDerived from the System ID on this server. Nothing to type. Point at an existing oneA cloud cluster, a replica set, or the customer's own server.

Channels: what they bought

Modules: what is switched on

Exactly these are on for the customer: they have no switch of their own, and only grant them per user. core is always included.

First administrator Username or email Display name

A one-time password is generated. They must replace it before they can use anything.

Licence

Customer Business name Label

A note for you, kept from before plans existed. It changes nothing the customer can do: what they have is under Licence below.

Notes

Domains

The three Dokploy entries that route this system's address: the dashboard at /, the API at /api and live updates at /socket.io. Added when the system is created; repair adds only what is missing and never touches another system.

Licence A catalogue planModules, channels and limits come from the plan and its add-ons, and follow any change to them. Custom termsSet by hand below, as every system from before plans was. Add-ons need a plan.

Licence term No end dateThe licence runs until you change it. Ends on a dateWorks through the end of that day (UTC), then for the grace days, then can only be read for the read-only days, then locks (Plans, Licence defaults). Moving the date forward opens it again on its next request.

Limits: blank is no limit

Lowering a limit below what they already have deletes nothing. Only the next one is refused. Handhelds are counted as signed-in handheld sessions; signing one out frees its seat.

Channels: what they bought

Modules: what is switched on

The only place modules are turned on or off for this system: the customer's dashboard has no Modules page. A module added to the product later starts off here until you tick it. Takes effect on their next request, with no sign-out and no redeploy. Anything withdrawn stops answering; nothing they recorded is deleted, and it all comes back if the module is restored.

Features

The system's own switches, applied at once (not with Save). Off takes the feature away: its pages, routes, permissions and jobs. Nothing is deleted, and on brings it back. A feature the terms do not include has no switch.

EPC scheme

Set here only: the customer's Settings page no longer shows it. The company prefix is the first two hex digits of every tag this system encodes from now on. Tags already written keep theirs and still work. The rest of the layout is fixed.

Reading…

Company prefix

Integrations

API keys for other systems to read this one, and webhooks that push its events out. Managed only from here: the customer's dashboard has no Integrations page. Every change is written to the customer's audit log as the supplier and takes effect on their next request. Stored secrets are never shown again; replace them instead.

Handheld app

Developer sign-in

Signs this system's developer account in, in a new tab, for an hour. Only for what that account alone can do: everyday support work goes through support access on the customer's ticket (Support page), which the customer can see and which ends with the ticket. The customer's audit log shows the sign-in with your reason.

Reason (the customer reads it)

Demo This is a demo systemLets you save a snapshot of it and reset it to that snapshot after a showing. Never tick this for a real customer: a reset replaces all of their data.

Delete system

Permanently deletes all of this client's data: stock, users, history and images. This cannot be undone. Suspending is the way to stop a client without losing anything.

Type the SystemID to confirm

New plan

Code

Lowercase letters, digits and dashes. Every system on the plan names it, so it cannot be changed afterwards.

Name Name in Arabic Description Description in Arabic

The customer reads these on their Plan and add-ons page, in their language.

Billing PaidCounted in the monthly revenue on Home. FreeNo price.

Demo planFor showroom systems. Free only, and never offered to customers.

Limits: blank is no limit

Features included

Ticked is included. A feature the product gains later is included unless you untick it here. An add-on can grant one the plan leaves out.

Archive ArchivedNo longer offered: not on customers' Plan pages, and no system can be put on it. The systems already on it keep it.

New add-on

Code

Lowercase letters, digits and dashes. Cannot be changed afterwards.

Name Name in Arabic Description Description in Arabic

What it adds Kind

Feature

Per unit

Added to the limit for each unit a system carries, only where the plan sets a limit.

Price

Archive ArchivedNo longer offered. The systems already carrying it keep what it grants.

Handheld app (generic)

Served to every system that has no handheld app of its own. A system's own pre-configured app, built with scripts/build-client-apk.ps1, is uploaded from that system's Manage sheet and wins over this one.

Site PC package

The Windows reader service, built by GitHub Actions. Every client's admin downloads it from Admin, Install on their dashboard.

Quote requests

Sent from the quote form on rfid.smartzoom.tech by people who are not customers yet. Nothing goes back to them on its own: call or write, then mark the request handled.

Show

Export requests

Approval, for every system Auto-approve export requestsA request nobody has decided is approved by the server after the delay below. Off: every request waits for you.

Delay (days)

Customers ask for their data export from their Settings page. Approving opens a download for 7 days; denying tells them your reason. Every decision is written to the customer's audit log as the supplier and reaches their page at once.

Show

Users

Locking signs the person out everywhere at their next request and refuses every sign-in, on the dashboard and the handheld. It is the same switch as the customer's own "deactivate", so either side can see and undo it: the customer's administrator can reactivate somebody you locked. Unlocking takes a user seat back, so it is refused while the system is at its users limit. Every action here is written to the customer's audit log as the supplier.

User	Role	Status	Last sign-in	Actions

System created

Shown once. These are stored only as hashes and cannot be retrieved. If this closes before you have them, the only way back is to reset them.

I have saved these and handed them over.

Sign in

Create the first owner

Set up your sign-in

Home