Brilliance One Point of Sale

Complete the sale. Keep the business connected.

Connect customer transactions, products, inventory, payments, receipts, discounts, taxes, accounting, and operational history inside the same platform that manages the customer relationship.

Brilliance One Point of Sale extends the Business Operating System to the moment revenue is collected, helping retail and service transactions remain connected to CRM, products, inventory, accounting, documents, communications, and specialized industry workflows.

Customers Products Inventory Payments Accounting
Brilliance One point of sale retail payments inventory and customer management software

Connected Commerce

The checkout should not become another disconnected system.

A sale touches the customer, products, inventory, payments, taxes, receipts, financial records, and often the relationship that continues afterward. Brilliance One Point of Sale is designed to keep those pieces closer together.

Sell

Customer Transactions

Create supported retail or service transactions using products, quantities, pricing, discounts, taxes, customer information, and applicable payment details.

Fulfill

Products & Inventory

Connect sales with the products and inventory responsible for the transaction so commerce activity can remain part of the broader operational record.

Account

Payment & Financial Context

Keep supported payment and transaction information connected with customers, products, receipts, accounting workflows, and the financial activity created by the sale.

Beyond Checkout

The payment is one event. The customer relationship is bigger.

Modern payment and POS platforms already make it easy to collect money. Brilliance One is designed around the broader workflow surrounding the transaction.

  • Who is buying?
  • What are they purchasing?
  • Which inventory is affected?
  • What price was used?
  • Were discounts applied?
  • Which taxes apply?
  • How was payment recorded?
  • What receipt or document was created?
  • What financial activity follows?
  • What customer history should remain afterward?

Customer + Commerce + Operations

A completed transaction should make the customer record more valuable.

The customer now has purchase history. Inventory has changed. Revenue has been created. Payment activity exists. Products have been associated with the relationship.

Brilliance One is designed so those events can remain part of the same broader operating environment instead of disappearing into a standalone checkout system.

Point of Sale Capabilities

Ring up the sale. Preserve the context behind it.

Brilliance One Point of Sale combines transaction processing with the customer, product, inventory, financial, document, and operational information surrounding the purchase.

Transactions

Retail & Service Sales

Create supported transactions for products, services, fees, and other configured items sold through the business.

Customers

CRM-Connected Checkout

Associate transactions with an existing customer or appropriate relationship record instead of maintaining an entirely separate POS customer database.

Products

Shared Product Catalog

Use appropriate product and service records throughout sales, inventory, financial, customer, and operational workflows.

Inventory

Inventory Context

Connect supported sales activity with inventory so the transaction reflects the items moving through the operation.

Pricing

Quantity, Price & Discounts

Maintain applicable quantities, pricing, discounts, and transaction-level information as part of the supported checkout workflow.

Taxes

Tax Context

Apply configured tax information where supported and preserve the resulting tax context with the transaction.

Payments

Payment Activity

Associate supported payment methods and transaction information with the sale and the broader customer and financial record.

Receipts

Customer Transaction Records

Provide appropriate transaction documentation and retain the supporting record with the underlying sale.

History

Purchase & Transaction Context

Keep supported transaction history associated with the customer, products, users, payments, and operational records responsible for the sale.

Transaction Workflow

Customer. Cart. Payment. Record.

Keep the checkout experience understandable while preserving the relationships required by downstream business workflows.

1

Build the Sale

Identify the customer where applicable and add the products, services, quantities, prices, discounts, taxes, and other supported transaction details.

2

Complete Payment

Record the supported payment activity required to complete the transaction and preserve the resulting financial information.

3

Continue the Record

Keep the resulting customer, product, inventory, payment, receipt, accounting, and operational context available after checkout.

POS + CRM

Know what they bought. Keep it with who bought it.

Connecting checkout with CRM allows supported purchase activity to become another part of the relationship rather than a transaction known only to the register.

  • Customer identity
  • Contact information
  • Account relationship
  • Purchase activity
  • Products purchased
  • Transaction dates
  • Communication history
  • Follow-up context
  • Documents and receipts
  • Broader customer history

Customer History

The customer existed before checkout. They still exist afterward.

CRM context can help an authorized employee understand the relationship before the transaction, while purchase history can provide useful context for future service, communication, support, sales, and customer-retention activity.

The transaction becomes part of the relationship rather than replacing it.

Products & Services

Sell from the same product foundation.

Products sold at the point of sale can remain connected to the wider product records used throughout supported inventory, purchasing, accounting, customer, and operational workflows.

Products

Physical Goods

Sell supported physical products using the same product and inventory context available elsewhere in the platform.

Services

Service Transactions

Add configured service items or other appropriate non-inventory charges to supported transactions.

Catalog

Consistent Product Information

Maintain product naming, pricing, categorization, identifiers, descriptions, and other supported information through the broader product environment.

POS + Inventory

Selling something should affect what you have.

When products are inventory-managed, the point-of-sale transaction should remain connected to the inventory activity created by the sale.

  • Product records
  • Inventory-managed items
  • Quantity context
  • Product identifiers
  • Location context where supported
  • Transaction activity
  • Customer purchase history
  • Operational reporting

Commerce + Inventory

The register should not have a different version of inventory.

Brilliance One is designed so supported POS activity can use the same product and inventory foundation that other operational workflows rely on.

That reduces unnecessary separation between what the business believes it has and what the business is selling.

Payments

Record the payment. Keep it tied to the sale.

Payment activity is most useful when the transaction, customer, products, totals, receipts, and downstream financial records remain connected.

Payment

Supported Payment Methods

Record appropriate payment activity using the payment methods and processing options configured for the organization.

Transaction

Payment + Sale Relationship

Keep payment information associated with the transaction responsible for creating it instead of maintaining an isolated payment record.

Customer

Relationship Context

Associate appropriate payment and transaction history with the customer or account where the sale belongs to an identified relationship.

Receipts & Transaction Records

Complete the transaction. Preserve what happened.

The completed sale can maintain the item, quantity, price, discount, tax, payment, customer, user, and other appropriate information required to understand the transaction later.

  • Transaction identifier
  • Transaction date
  • Customer where applicable
  • Products and services
  • Quantities
  • Prices
  • Discount context
  • Tax context
  • Payment information
  • User context

Transaction History

Today's checkout can become tomorrow's customer-service question.

Preserving the transaction record gives authorized employees context when customers return with questions about what they purchased, when they purchased it, how the transaction was structured, or which supporting records belong to the sale.

POS + Accounting

The sale creates revenue. Keep the financial workflow connected.

A completed transaction may create customer, payment, revenue, tax, product, inventory, and other financial activity that belongs within the broader accounting context.

  • Customer transactions
  • Payment activity
  • Revenue context
  • Tax context
  • Products sold
  • Inventory activity
  • Receipts
  • Financial reporting

Commerce + Finance

The point of sale should not become the end of the financial record.

With Accounting enabled, supported transaction activity can continue into the financial workflows responsible for reporting and managing the business.

Point of Sale records the transaction. Accounting provides the broader financial context.

Connected Revenue

Different customers buy in different ways.

Some transactions begin at a physical checkout. Others begin with a quote, invoice, customer conversation, scheduled service, or another business workflow. Brilliance One is designed to keep these revenue processes on a connected customer and financial foundation.

Retail

Point-of-Sale Transaction

Complete an immediate sale using supported customer, product, inventory, pricing, tax, and payment workflows.

Sales

Quote & Estimate Context

Use appropriate quote or estimate workflows when the customer needs pricing before committing to the transaction.

Billing

Invoice & Payment Context

Use invoicing and accounting workflows when payment occurs later or the transaction requires a broader accounts-receivable process.

POS + Firearms

Sell the product. Keep the serialized firearm connected.

For FFL configurations using the Firearms module, POS can participate in a broader workflow that distinguishes general product information from the specific serialized firearm involved in the transaction.

  • Customer relationship
  • Product record
  • Serialized firearm
  • Inventory context
  • Form 4473 relationship where applicable
  • Bound book disposition where applicable
  • Payment activity
  • Receipt and transaction record
  • Accounting context
  • Supporting documents

Firearms Retail

Product checkout and firearms recordkeeping are related workflows.

A retail system may know that a firearm product was sold. The firearms workflow must also understand which serialized firearm was involved and how the applicable transfer and recordkeeping processes relate to it.

Brilliance One can connect those perspectives rather than forcing the retailer to reconcile two unrelated versions of the transaction.

After the Sale

Checkout ends the transaction. It does not end the relationship.

Purchase activity can become useful context for customer communication, service, marketing, future sales, projects, documentation, scheduling, support, and other supported workflows.

Communications

Customer Follow-Up

Use supported email and SMS workflows for appropriate transaction communication and post-sale follow-up.

Marketing

Purchase Context

Use appropriate customer and purchase information as context for future marketing audiences and customer-retention strategies.

Service

Ongoing Relationship

Preserve purchase history so authorized teams have additional context when the customer returns for support, service, another purchase, or another business interaction.

Users & Permissions

Give employees access based on their responsibilities.

Point-of-sale activity can use the broader Brilliance One user, role, permission, security-group, and administrative foundation.

  • Individual user accounts
  • Role-based permissions
  • Security groups
  • Module access
  • Administrative controls
  • Transaction user context
  • Security-focused access
  • Operational accountability

No Per-User Pricing

Add the employees who need to use the system.

Brilliance One's standard platform pricing is based on Core and the capabilities your organization activates rather than charging another recurring platform subscription for every user.

Access remains permission-controlled even though the pricing model does not depend on seat count.

Transaction Documents

Keep supporting information with the transaction it describes.

Transactions can generate receipts, invoices, supporting files, customer documentation, product records, or industry-specific documentation that belongs with the underlying sale.

Receipts

Maintain appropriate customer transaction records associated with the completed sale.

Invoices

Use connected financial workflows where the transaction requires invoicing rather than immediate payment.

Customer Documents

Associate appropriate supporting customer records with the broader relationship and transaction.

Product Documents

Connect relevant product or item documentation with the records responsible for the transaction.

Industry Records

Associate specialized documentation with industry-specific transactions where additional modules require it.

Historical Context

Keep appropriate documentation available with the sale for authorized review later.

Sales Visibility

Understand what sold. Connect it to who bought it.

Available transaction data can help authorized teams review sales activity alongside products, customers, payments, inventory, employees, and the broader operational context.

Transactions

Review supported transaction activity and the underlying records associated with completed sales.

Products

Understand which products and services participate in supported sales activity.

Customers

Use purchase history as additional context around identified customer relationships.

Payments

Review available payment information associated with the transactions responsible for it.

Users

Maintain appropriate user context around supported transaction activity.

Operations

Connect commerce information with inventory, accounting, customer, and other operational records where supported.

Connected Commerce

Point of sale becomes more useful when the rest of the business can see it.

POS transactions can participate in the same customer, inventory, financial, document, communication, security, reporting, and industry workflows used throughout Brilliance One.

Accounts

Customer Relationships

Associate appropriate transactions and purchase history with customers, contacts, organizations, and broader relationship records.

Products

Product Catalog

Use shared product and service information instead of maintaining another independent catalog solely for checkout.

Inventory

Product Movement

Connect supported sales activity with inventory records and the operational movement created by selling products.

Accounting

Financial Operations

Continue applicable sales, payment, tax, revenue, customer, and product activity into the broader accounting environment.

Firearms

Serialized Retail

Connect appropriate firearms transactions with serialized inventory, bound-book activity, e4473 workflows, customers, documents, and financial context.

Communications

Customer Messaging

Use supported email and SMS for transaction-related communication and appropriate post-sale follow-up.

Marketing

Purchase Context

Use appropriate customer and purchase information as context for future segmentation, campaigns, and retention strategies.

Documents

Transaction Records

Keep appropriate receipts, invoices, supporting documents, and specialized records with the transaction or customer they support.

Insights

Business Context

Use available customer, product, transaction, and operational information to better understand the business around the sale.

Commerce Platform Strategy

Payment platforms complete transactions. Brilliance connects the transaction to operations.

Modern customer platforms increasingly provide product catalogs, payments, invoices, estimates, checkout, subscriptions, mobile payment tools, and other commerce capabilities. Brilliance One extends commerce into a broader CRM + ERP + industry operating environment.

Sell

Products + Customers

Complete supported retail and service transactions using connected product and customer information.

Record

Payment + Inventory

Keep supported payments and inventory activity associated with the transaction responsible for creating them.

Operate

Accounting + Industry Workflows

Continue the transaction into financial, document, customer, reporting, firearms, communication, and other operational processes.

Transaction Security

Commerce data deserves controlled access.

Point-of-sale workflows can include customer, payment, financial, product, employee, and industry-specific information that should be available only to appropriate authorized users.

  • User authentication
  • Role-based permissions
  • Security groups
  • Module access
  • Administrative controls
  • Customer data separation
  • Secure transport
  • Operational logging
  • Transaction user context
  • Security-conscious payment integrations

Payment Responsibility

Payment security is a shared responsibility.

Brilliance One can integrate transaction and payment workflows with supported providers while organizations remain responsible for appropriate payment configuration, access controls, merchant requirements, and applicable PCI or other obligations.

Brilliance should be described as designed to support security-conscious commerce workflows rather than as automatically making an organization compliant.

Point of Sale Pricing

Add Point of Sale to the same platform running the business.

Point of Sale participates in Brilliance One's modular pricing model. Start with Core, add POS, and combine it with Accounting, Firearms, Scheduling, Marketing, or other modules according to the way your organization operates.

  • Brilliance One Core required
  • Point of Sale available as a business module
  • No per-user platform pricing
  • Connected customer and product context
  • Inventory-aware commerce workflows
  • Accounting integration within Brilliance One
  • CMS included with qualifying configurations
  • Founders 400 alternative available

Standard Configuration

Core + Point of Sale. Add the operation around it.

Under current standard pricing, Brilliance One Core starts at $147 per month and Point of Sale is $135 per month before applicable module-volume adjustments, payment-processing costs, and other usage-based services.

Use the pricing estimator to combine POS with Accounting, Firearms, Scheduling, Marketing, or the other capabilities your business needs.

Build the Commerce Stack

Start with checkout. Add the workflows around it.

Different businesses need different combinations of customer, retail, inventory, financial, scheduling, and industry functionality.

Retail

Core + Point of Sale

Connect customers, communications, users, security, products, supported transactions, payments, and purchase history.

Retail + Finance

Add Accounting

Extend sales into invoices, payments, expenses, vendors, banking, ledger activity, reporting, and broader financial workflows.

Firearms Retail

Add Firearms

Connect POS with serialized firearms, bound-book records, e4473 workflows, customers, inventory, payments, and specialized FFL operations.

Business Modules

Add the capabilities you need. Keep the platform connected.

Expand Brilliance One with connected modules for financial operations, content, compliance, training, industry workflows, workforce management, reporting, marketing, commerce, projects, scheduling, and technology operations.

Financial Operations

Accounting

Manage quotes, invoices, payments, expenses, vendors, banking activity, journals, and financial reporting while keeping the numbers connected to the customers, projects, products, and business activity behind them.

Explore Accounting

Websites & Content

CMS

Build and manage websites, pages, forms, landing pages, blogs, digital assets, public experiences, and lead capture while connecting the digital experience directly to business operations.

Explore CMS

Governance & Controls

Compliance

Support compliance-conscious operations with identity controls, permissions, logging, security protections, data governance, administrative oversight, and specialized operational workflows.

Explore Compliance & Security

Training & Learning

Courses

Manage courses, curriculum, lessons, assessments, instructors, participants, completion, certifications, renewal requirements, and training history in one connected system.

Explore Courses

Testing Program Operations

Drug Testing

Manage testing pools, random selections, collections, specimens, chain of custody, laboratory workflows, results, documents, and testing-program history.

Explore Drug Testing

FFL Operations

Firearms

Manage serialized firearms, acquisitions, dispositions, bound book records, e4473 workflows, inventory, customers, documents, point of sale, and connected firearms operations.

Explore Firearms

Workforce Operations

Human Resources

Manage employees, onboarding, documents, attendance, leave, training, certifications, reviews, workforce history, responsibilities, and the operational context surrounding your people.

Explore Human Resources

Reporting & Visibility

Insights

Turn customer, marketing, financial, workforce, scheduling, project, and operational information into connected reporting and clearer business visibility.

Explore Insights

Growth & Engagement

Marketing

Manage campaigns, audiences, lead sources, referrals, reputation, local visibility, communications, attribution, and customer acquisition while keeping marketing connected to CRM and operations.

Explore Marketing

Connected Commerce

Point of Sale

Connect customers, products, inventory, transactions, payments, receipts, accounting, purchase history, and specialized retail workflows through the same business platform.

Explore Point of Sale

Work & Delivery

Projects

Manage projects, phases, milestones, tasks, employees, time, documents, costs, customer relationships, communication, and delivery history from one connected operational record.

Explore Projects

Appointments & Resources

Scheduling

Manage appointments, services, attendees, employees, availability, locations, resources, capacity, customers, and the operational workflows surrounding scheduled work.

Explore Scheduling

Assets & Infrastructure

Technology

Manage technology assets, equipment, vehicles, software, subscriptions, assignments, maintenance, warranties, vendors, documents, lifecycle history, and supported monitoring.

Explore Technology

Brilliance One Point of Sale

Complete the sale. Keep the business connected.

Connect customers, products, inventory, transactions, payments, receipts, accounting, communications, documents, reporting, firearms workflows, and ongoing customer history inside the broader Brilliance One Business Operating System.

Brilliance One • Point of Sale • Products + Inventory + CRM + Accounting