What is a POS system?

How a POS system supports a sale

A typical sale begins when an employee selects an item or service, scans a barcode, enters a custom amount, or accepts an order from an approved sales channel. The software builds a cart, applies the business's configured prices, taxes, discounts, and order details, then presents the available payment choices. After payment, the system records the result and can produce a printed or digital receipt.

Current Shopify documentation describes creating and modifying a customer cart, accepting a range of payment methods, managing orders, and connecting optional retail hardware. Stripe's current POS guide similarly describes a system made from hardware and software that supports transactions and may also manage inventory, customer data, and reports. These are useful examples of the general workflow, not evidence that every product offers identical controls.

1. Build the cart: Add products, services, quantities, modifiers, or custom amounts needed for the sale.
2. Review the total: Confirm the configured prices, discounts, taxes, and fulfillment details before payment.
3. Take payment: Use a payment method supported by the merchant's approved setup.
4. Record the outcome: Save the order and payment result, then issue the appropriate receipt.
5. Continue operations: Update relevant inventory, order, reporting, or fulfillment records when the selected system supports that workflow.

Software and hardware play different roles

POS software is the application layer employees use to create and manage sales. It may include an item catalog, order controls, receipt settings, employee roles, inventory tools, and reporting. A merchant should separate essential checkout functions from optional operational features so a demonstration stays focused on real requirements.

POS hardware is the physical equipment used around that software. A setup may use a computer, tablet, phone, or dedicated register, along with a payment reader, receipt printer, barcode scanner, cash drawer, scale, customer-facing display, or kitchen display. Not every business needs every device. A service business may use a compact mobile setup, while a retailer or restaurant may need several stations and specialized peripherals.

Hardware should never be selected from a generic feature list alone. The responsible provider must confirm supported devices, operating systems, connections, installation conditions, and payment configuration for the exact POS product. That confirmation is especially important when a merchant plans to reuse existing equipment.

Common POS functions vary by business type

The most useful POS functions follow the work that happens before, during, and after checkout. A retailer may prioritize barcode entry, item variants, inventory by location, returns, and purchase records. A restaurant may care more about modifiers, courses, table or counter service, kitchen routing, tips, and order handoff. Appointment-based businesses may need service selection, staff assignment, and scheduling context.

Capabilities also vary by plan, device, region, and configuration. Shopify's current guidance, for example, documents order and inventory synchronization across retail locations, an online store, and other active sales channels within its own product. That supports evaluating cross-channel recordkeeping as a category, but it does not establish that another POS will synchronize the same data or channels.

• Checkout: Item entry, cart changes, discounts, taxes, tips, receipts, and returns relevant to the business.
• Catalog and inventory: Product variants, stock visibility, counts, transfers, or ingredient-level needs where applicable.
• Orders and fulfillment: Pickup, delivery, shipping, table service, work orders, or scheduled service details.
• Staff controls: Individual access, role permissions, approvals, shift activity, and responsibility for sensitive actions.
• Reporting: Sales, items, locations, tenders, employees, refunds, and other records needed for daily review.
• Connected workflows: Ecommerce, accounting, loyalty, kitchen, scheduling, or other systems only after current support is verified.

Choose a POS from the workflow backward

Begin with a map of how the business sells rather than a list of product names. Document where orders start, who creates or changes them, which payment methods matter, what receipt or fulfillment follows, and which records staff need later. Include peak-volume conditions, multiple locations, mobile selling, and any period when connectivity may be limited.

Turn that map into a short set of demonstrations. Use representative products, modifiers, discounts, returns, employee roles, and end-of-day reports. Ask the provider to show a normal sale and the exceptions that create the most work: a changed order, unavailable item, lost connection, incorrect tender, device failure, or employee who should not have manager access.

A useful comparison distinguishes required functions, optional conveniences, and items that need written verification. Avoid relying on screenshots from another plan or a general claim that a system connects with a particular service. The responsible vendors should confirm the current setup, support boundary, data flow, and ownership of troubleshooting.

A practical POS evaluation checklist

1. List every sales path. Include counter, tableside, mobile, event, pickup, delivery, online, phone, or invoice workflows that actually apply.
2. Define the cart. Note products, services, variants, modifiers, discounts, taxes, tips, deposits, and fulfillment details employees must handle, without assuming a feature exists.
3. Identify the hardware. Map each station, reader, printer, scanner, drawer, display, and network connection to a specific job.
4. Set staff boundaries. Decide who may create discounts, process returns, view reports, change settings, or manage other users.
5. Test realistic exceptions. Demonstrate corrections, canceled items, returns, duplicate entries, connectivity loss, and recovery from a failed device.
6. Review the records. Confirm what receipts, order histories, shift information, inventory changes, and reports are available and who can access them.
7. Verify connected systems. Have the responsible providers confirm the exact data shared, supported versions, update process, and troubleshooting owner.
8. Document support and fallback. Record escalation channels, operating hours, replacement procedures, and the approved process for continuing or pausing sales during an outage.

Protect access and customer information

A POS can expose sales, customer, employee, and operational information, so access should follow each person's job. Shopify's current security guidance supports using individual staff access, appropriate roles and permissions, device auto-lock, and a response process for lost or stolen equipment. Merchants should follow the selected provider's current instructions and their own security policies.

Keep support requests privacy-safe. Do not send cardholder data, full account numbers, security codes, passwords, bank credentials, or secret API keys through screenshots, email, chat, or a general contact form. Share only the minimum non-sensitive details needed to identify the device, location, time, workflow step, and error, then use an approved provider support channel for transaction-specific investigation.

Related POS planning resources

Use the POS systems and integrated payments FAQ hub for broader planning questions. Compare deployment concepts with what a cloud POS system is, learn how a customer-facing display fits the checkout, and review kitchen display system workflows for restaurant operations. The payment processing glossary can help a team align terminology before comparing providers.