Frequently asked questions
Answers before your next step.
Explore product fit, pricing and implementation. Bring your specific requirements to a demo.
Choose your question
Find your next answer.
What would you like to know?
Can I see the working product?
Yes. Watch the complete product walkthrough, or request a personal demo built around your dealer operation.
What does bullionOS do?
bullionOS brings dealer pricing, inventory, customer records and payments into a connected operating workspace. Use a demo to confirm the capabilities and handoffs available for your business.
Is bullionOS only for large dealers?
No. Published plans begin with Pilot Dealer for small dealers and continue through Founding Dealer, bullionOS Pro, and larger white-label deployments.
Does bullionOS work on an iPad?
The workflow walkthrough illustrates tablet workflows for pricing, lookup and dealer operations. Confirm current device support, connectivity requirements and role permissions, then test your intended iPad before counter or show use.
How does live pricing work?
The pricing concept combines market inputs with dealer buy and sell rules. In your demo, confirm the available data source, update behavior, product overrides and terms recorded with each quote.
Does bullionOS charge per seat?
Current published plans are structured around the size and complexity of the dealership, not the number of people using the system.
Are white-label setup and implementation included in the monthly price?
White-label implementation scope and setup are quoted separately. Other custom migration or integration work is identified during the deployment plan and confirmed before work begins.
What can be migrated?
The migration conversation typically covers products, SKUs, barcodes, inventory quantities and locations, client records, open operational records, and relevant starting balances. Exact source quality and scope determine the plan.
How is a rollout validated?
Representative records should be tested through pricing, buys, sells, movements, payments, documents, shipments, and accounting outcomes. Physical inventory and financial totals must be reconciled before the system becomes the operating source of truth.
Do we have to start with perfect data?
No, but the project needs an agreed source of truth, owners for cleanup, and an exception log. Importing unresolved duplicates and unexplained quantities simply moves the problem into a new system.
How should staff access be structured?
Define roles around who may price, approve, receive, move, refund, reconcile, manage users, and change configuration. Administrators should use two-factor authentication, and each employee should use an individual account.
What information should not be submitted through the walkthrough form?
Do not submit passwords, payment card data, API secrets, identity documents, or other sensitive credentials. Secure implementation credentials are handled only after approval through the appropriate process.
How does custody fit into the system?
Locations, movements, cage or vault workflows, and exception states help connect the digital record to the physical item. The dealership remains responsible for its physical security, verification, and chain-of-custody policies.
What happens during onboarding?
The working path is operation mapping, source-data preparation, configuration, controlled migration, workflow validation, role-based training, and launch reconciliation. The exact schedule depends on scope and readiness.
Can bullionOS support coin-show workflows?
Review a show-specific inventory location, counter process and return reconciliation with the team. Confirm current device and connectivity requirements. The website does not promise offline operation.
How do we get a specific support or implementation answer?
Request a private walkthrough and describe the workflow, migration question, or exception you need to resolve. The form goes directly to Hunter at hunter@bullionos.co.