Buying digital cards for a university or public body
Scaanme is an option for bilingual public business cards and centrally managed team profiles. A Saudi government department, Bahraini bank or Qatari employer should separately establish whether its required hosting, identity integration and purchasing terms are available. An Arabic interface is not evidence of local data residency, supplier registration or a particular tax treatment.
Start by sending the supplier a short list of requirements that would prevent purchase if unmet. Scaanme's published self-service prices can inform an initial budget, but they do not confirm purchase-order acceptance, payment by bank transfer, a local tax registration or a negotiated data processing agreement.
Ask for evidence in the right form
| Requirement | Evidence to request |
|---|---|
| Approved supplier | Contracting entity details and any required registration |
| Hosting location | Written account of storage, backups and relevant subprocessors |
| Single sign-on | Identity-provider documentation and a working test tenant |
| Employee provisioning | Demonstration of adding and removing a user through the directory |
| Invoice requirements | A sample with the entity, currency and fields your finance team requires |
| Data export and exit | A sample export and written cancellation procedure |
Do this before transferring a real employee list or customer records. You can test a public card's layout with clearly labelled sample data while the buying process is still open.
Separate product suitability from procurement eligibility
An institution can like the product and still be unable to buy it under its own rules. A payment button establishes a self-service purchase route. It does not establish that a supplier accepts your purchase order, offers deferred payment or appears on a government supplier register.
For Scaanme, request those answers through the contact page and keep the response with the purchase file. Ask for the legal entity issuing the invoice, the billing currency, the service period and the exact scope. If a document or payment route is mandatory, leave that requirement unresolved until the supplier supplies it.
The same discipline applies to local currency. A price shown in a display selector may differ from the currency used to settle the subscription. Your finance team should review the actual invoice format rather than a converted marketing-page price.
Test identity requirements separately
An administrator who edits every employee's card provides central control. Single sign-on controls how people authenticate, and directory provisioning controls account creation and maintenance. Buying the first does not establish the other two.
Microsoft's provisioning documentation is a useful reference for writing that part of the brief. HiHello publishes identity-management integrations, while Blinq describes its business and enterprise controls. These are vendor statements to verify against the proposed plan and a test account, not substitutes for your acceptance test.
For a Scaanme rollout, treat enterprise SSO and automated HR provisioning as unconfirmed requirements unless you receive explicit current evidence. A demonstration of Google social sign-in does not answer a question about enforcing company identity policies.
Put the hosting question in writing
Ask where account data is stored, where backups are kept, which services process it and what documents govern that processing. An office address, a regional domain name or an Arabic-speaking support team does not answer those questions.
Do not describe Scaanme as locally hosted in Saudi Arabia, Bahrain, Kuwait or Qatar without contractual evidence for the service you are buying. Give the hosting documents to your organization's qualified reviewers, who can decide whether they meet its requirements.
Assign someone to collect the documents and set a reply deadline. If the supplier cannot provide a required assurance, resolve that before preparing hundreds of employee cards. If a mandatory requirement remains unmet, evaluate another supplier before committing to the rollout.
Plan the end of the subscription
Ask what remains accessible after cancellation, which files you can export, who can deactivate public profiles and what happens to QR codes on printed material. Keep account closure separate from deleting copies that recipients have already saved to their phones.
Export a small set of test leads during the pilot. Open the file with the application your team uses, check Arabic names and phone-number prefixes, and see whether the fields are useful for migration. The existence of an export button alone does not prove that your next system can use the result.
Finally, assign an owner for changes after purchase. Someone needs to update titles, approve public details and handle leavers. The team card control guide sets out a practical test, and the card budget guide separates public-card arithmetic from employee-seat quotations.
FAQ
Can a public institution buy through a normal subscription page? Its own purchasing rules determine that. Obtain internal approval for the buying route and confirm the supplier's documents before committing.
Does Scaanme promise a Saudi VAT invoice or BHD invoicing here? No. Request the required invoice format and currency directly. A public software price does not establish either.
Does Arabic support prove local hosting? No. Language, hosting and the contracting entity are different facts and require separate evidence.
What if SSO is mandatory? Ask for the integration documentation and test it on the quoted plan. Leave the requirement unmet until that evidence exists.
