How can we help?

We start with a scoping call, migrate your items and rates together, and run a pilot at your counter before you commit. Your shop sets the pace.

No. Orosphinx runs in your browser — Chrome, Safari, Edge, or Firefox. The optional desktop agent is only required for direct receipt printing and encrypted local backups on the store PC.

Any modern browser on desktop, tablet, and mobile. POS is optimized for desktop and tablet. Chrome and Safari give the best results.

Yes. CSV imports with column mapping for items, variants, images, and pricing. Our team helps with migration from legacy systems during onboarding.

Yes. The counter queues sales, returns, and transfers locally and replays them with idempotency keys when connectivity returns.

Each branch opens and closes shifts with a counted drawer. The close records expected vs counted cash and keeps a variance history per branch — the numbers the owner actually argues about.

Only if their role allows it. Permissions are enforced server-side, so a cashier role cannot see cost prices, margin, or financial statements.

Yes. Branch-scoped roles, inter-branch transfers with custody, per-branch cash positions, and consolidated reporting across the group.

Tenant data sits behind Postgres row-level security. Every mutation is server-enforced and audit-logged. The application database role does not have BYPASSRLS. Webhooks are signed with HMAC v1 carrying timestamp and nonce.

Continuous Postgres point-in-time recovery in the cloud, plus a logical backup on every shift close. Optionally, the store agent writes AES-256-GCM encrypted backups to the local PC, with retention policies.

Per-tenant per-minute and per-hour rate limits, daily caps, and emergency kill switches. Rate limiting is always on in production.

Yes. It binds to the local network only, uses constant-time API key comparison, and enforces strict request size limits. No customer PII is sent to print jobs. It is optional — the platform works without it.

Yes. Export the full catalog with images into a Shopify-compatible CSV. Image URLs are signed with a TTL and hard size limits prevent runaway cost on large exports.

Customers attach to sales. Points are calculated server-side from configurable rules and can be earned or redeemed at checkout. A full ledger gives you auditability per transaction.

Fawry, InstaPay, and Paymob integrations are built in for card and wallet payments, alongside cash. Trade-in intake and assessment is a separate module.

Yes. Start with counter operations, then add the workshop module and financial statements generated from the ledger as your team is ready.

Pre-burn weighing, post-burn settlement, and payout computed from your live buy price per karat.

Yes. Shift, cash, inventory, and approvals are scoped per branch, so each branch can be reviewed and reconciled independently.

Bullion bars have their own lifecycle: registered, committed, released — with custody recorded at each step.

Yes. The product is bilingual and RTL-correct. Onboarding, training, and support all run in Arabic.