How can we help?

We start with a discovery call to understand your store workflows, staff roles, and inventory structure. We then configure the system, import your data, and validate sales and transfer flows before go-live. Most stores are operational within a few days.

No. Orosphinx is a cloud-hosted platform that runs entirely in your browser — Chrome, Safari, Edge, or Firefox. The optional desktop companion app is only needed for direct receipt printing and encrypted local backups.

Orosphinx works on any modern browser across desktop, tablet, and mobile. We recommend Chrome or Safari for the best experience. The POS is optimized for desktop and tablet form factors.

Yes. We support CSV imports with column mapping for items, variants, images, and pricing. Our team can also assist with data migration from legacy systems during onboarding.

Yes. Orosphinx includes offline-resilient workflows that queue operations locally and sync them safely when connectivity returns. You can continue making sales and managing inventory during temporary outages.

Staff open a shift at the start of their work period. All sales, returns, and payment totals are tracked per shift. When the shift closes, a Z-report summary is generated and can be exported as CSV or printed. Cloud backups are also triggered automatically on shift close.

Roles control exactly what each user sees. Sales staff can process transactions without viewing financial summaries, cost prices, or other sensitive fields. All permissions are enforced server-side.

Yes. Multi-location support includes location-scoped access, inter-location transfers with traceable events, and consolidated reporting across all branches.

All data is stored in Google Cloud (Firebase) with tenant isolation enforced via JWT claims. Every API call validates the tenant context server-side. No client-side Firestore writes are allowed — all mutations go through Cloud Functions with full RBAC checks.

Cloud backups are created automatically after every shift close. Optionally, you can also save AES-256-GCM encrypted local copies to the store PC via the desktop companion. Retention policies clean up old local files automatically.

Every expensive operation (exports, uploads, backups) is protected by per-tenant rate limits at minute and hour granularity, daily caps, and emergency kill switches. This prevents denial-of-wallet attacks and keeps operational costs predictable.

Yes. The desktop companion binds to the local network interface only, uses strict CORS, constant-time API key comparison, and enforces request size limits. No customer PII is included in print payloads. It is an optional component — the platform works fully without it.

Yes. You can export your full catalog with images into a Shopify-compatible CSV format. Image URLs are signed with a TTL and hard limits prevent cost abuse during large exports.

Customers are attached to sales, and points are calculated server-side based on configurable rules. Points can be earned and redeemed at checkout. A full ledger history provides auditability for every point transaction.

Yes. You can start with counter operations and inventory, then activate manufacturing, repairs, compliance, and advanced reporting as your team is ready.

Yes. Orosphinx supports karat-aware workflows and operational controls aligned with day-to-day gold retail realities.

Teams can follow a controlled intake flow, including pre/post-burn process checkpoints and clear payout tracking.

Yes. Shift, inventory, and approval controls are scoped by location so each branch can be reviewed independently.

Yes. Bullion and commitment flows are part of the broader domain roadmap and are being integrated with strict accounting safety.

Yes. The product and onboarding approach are built for Arabic and English operations.