GITNUXSOFTWARE ADVICE
Top 10 Best Point Of Sale Restaurant Software of 2026
Top 10 ranking of point of sale restaurant software for restaurants, with feature and pricing comparisons of Clover, Lavu, Oracle MICROS.
How we ranked these tools
Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.
Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.
AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.
Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.
Score: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
Clover is the best pick for restaurants that want a general POS with restaurant-specific integrations and permission-controlled operations, while Lavu is the cheaper entry point for iPad teams managing menus and stations without rewrites, and TouchBistro fits if tableside ticket and floor workflows matter most.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
Clover
Clover’s API and app integration surface supports transaction and receipt-centric automation tied to the POS data model.
Built for fits when restaurants need API-driven integrations and RBAC-controlled POS operations..
Lavu
Editor pickConfigurable menu, modifier, and pricing data model that drives consistent ordering across stations and integrations.
Built for fits when multi-station restaurants need governed menu data and integration-driven automation without custom POS rewrites..
Oracle MICROS
Editor pickAPI and enterprise integration patterns that exchange structured POS order and operational data with back-office systems.
Built for fits when multi-site restaurants need enterprise integration control and governed configuration via API..
Related reading
Comparison Table
This comparison table maps restaurant POS tools such as Clover, Lavu, Oracle MICROS, Toast, TouchBistro, and others against integration depth, data model design, and the automation and API surface used for back-office workflows. It also highlights admin and governance controls, including RBAC, provisioning paths, and audit log coverage, so teams can assess extensibility and configuration for day-to-day throughput.
Clover
SMBGeneral POS with restaurant-specific app ecosystem and integrated payment hardware.
Clover’s API and app integration surface supports transaction and receipt-centric automation tied to the POS data model.
Clover fits restaurant operations that need tight integration between ordering, payments, and back-office reporting. Its data model ties orders and payments to tickets, menu configuration, and tender types in a way that supports consistent reconciliation. Automation and extensibility map to that same structure through APIs and app integrations that can react to order and transaction events. Governance features support role-based permissions and operational controls for multi-station shifts.
A key tradeoff is that deeper custom workflows depend on the available integration points rather than free-form logic inside the POS UI. Clover works best when integration requirements align with documented app events and payment or receipt lifecycle hooks. A practical usage situation is a multi-location restaurant that provisions standardized menu schemas and access roles across stores while routing reporting data to finance.
- +Transaction-linked data model connecting orders, tenders, and receipts
- +Extensibility through documented apps and APIs for automation
- +RBAC controls for shift access and workstation restrictions
- +Operational reporting aligned to POS entities and menu configuration
- –Custom automation can be limited by event and API coverage
- –Integration setup requires careful schema mapping across systems
- –Multi-store governance adds admin overhead for provisioning
IT and systems integrators
Build order-triggered automations
Reduced manual reconciliation
Restaurant operations managers
Control access by station roles
Lower shrink risk
Show 2 more scenarios
Finance and accounting teams
Standardize receipt and tender reporting
Faster close process
Use structured transaction data for consistent reconciliation across shifts and locations.
Multi-location restaurant teams
Provision consistent menu configuration
Fewer setup errors
Keep menu schema and operational permissions aligned across stores.
Best for: Fits when restaurants need API-driven integrations and RBAC-controlled POS operations.
More related reading
Lavu
SMBiPad restaurant POS with inventory tracking, employee management, and menu customization.
Configurable menu, modifier, and pricing data model that drives consistent ordering across stations and integrations.
Lavu’s core data model centers on menu entities, modifiers, pricing rules, and order lifecycle states that map cleanly to kitchen display and station workflows. Configuration supports provisioning of stations and devices, plus structured user roles that reduce permission sprawl for managers, cashiers, and supervisors. Automation and API surface are geared toward syncing orders, items, and operational events into connected systems, which helps teams maintain consistent menu state across channels.
A practical tradeoff is that deeper custom automation can require schema-aligned implementation to avoid mismatches between POS configuration and external systems. Lavu fits best when multiple ordering devices must follow the same service rules, and when governance needs include RBAC boundaries and audit-friendly operational logs for staff actions.
- +Menu and modifier schema maps to station and kitchen workflows
- +RBAC-style user roles support controlled access for staff groups
- +Automation and API surface supports order and data integration
- +Store and device configuration supports consistent multi-station behavior
- –Advanced automation can require careful data model alignment
- –Complex multi-location setups need disciplined configuration management
Franchise operations teams
Standardize menus across multiple sites
Fewer menu drift incidents
Integration engineers
Sync orders to external systems
Lower manual reconciliation
Show 2 more scenarios
Restaurant managers
Control staff actions by role
Reduced policy violations
Apply RBAC-style permissions to POS actions and limit what staff can change.
Multi-location IT admins
Provision devices and station behavior
Consistent throughput
Manage station configuration so every terminal follows the same service flow and UI setup.
Best for: Fits when multi-station restaurants need governed menu data and integration-driven automation without custom POS rewrites.
Oracle MICROS
enterpriseEnterprise restaurant POS platform with global deployment and hospitality integrations.
API and enterprise integration patterns that exchange structured POS order and operational data with back-office systems.
Oracle MICROS fits teams that need a well-defined data model for orders, payments, modifiers, and operational states across many store locations. Administrative controls focus on role-based access patterns, operational configuration, and consistent provisioning so changes do not drift by site. Automation and integration are where it differentiates, since external systems can exchange structured data and trigger POS workflows through an API surface and integration tooling. Audit and governance capabilities are designed for operational traceability, including tracking changes tied to back-office processes.
A tradeoff shows up in implementation effort, since enterprise integration and schema alignment require more upfront configuration than simpler POS options. Oracle MICROS works best when inventory, procurement, loyalty, and reporting systems already follow an enterprise integration approach. It is less ideal for teams that only need basic POS with minimal back-office connectivity. In high-throughput service environments, consistent order processing and controlled configuration reduce workflow variance during peak periods.
The automation layer typically supports event-driven patterns like sending structured order status to external services and updating item, pricing, or operational configuration. The resulting integration breadth depends on how stores are provisioned and how external systems map to the POS data model and schema conventions. Where that mapping is already in place, Oracle MICROS reduces reconciliation effort during audits. Where it is not, integration mapping becomes a primary project task.
- +Enterprise-grade integration patterns for menu, pricing, and operational states
- +Role-based access and governance controls for multi-site administration
- +Automation through API-driven workflows and external system data exchange
- +Consistent data model to reduce store-level configuration drift
- –Heavier integration and provisioning effort than lightweight POS deployments
- –Workflow customization requires careful schema and device mapping
- –Change management can slow rapid menu testing without structured rollout
IT integration teams
Automate POS workflow triggers
Reduced manual reconciliation work
Multi-site operations managers
Govern configuration across stores
Lower configuration drift
Show 2 more scenarios
Finance and audit teams
Trace payment and workflow changes
Faster audit evidence gathering
Rely on audit-ready operational records tied to administrative actions and POS transactions.
Restaurant analytics teams
Standardize reporting schemas
More reliable performance reporting
Align reporting feeds to a consistent data model for orders, items, and modifiers across sites.
Best for: Fits when multi-site restaurants need enterprise integration control and governed configuration via API.
Toast
SMBCloud-based restaurant POS platform with integrated payments, online ordering, and inventory management.
Role-based access with audit log coverage for management actions across locations and terminals.
Toast pairs POS, payments, and restaurant operations into one data model that reduces handoffs across stations. Its integration depth shows up in hardware provisioning, menu and modifier schemas, and management of order routing through configurable workflows.
Toast also provides an API and automation hooks that support extensibility around ordering events, reporting extraction, and operational integrations. Admin controls center on role-based access, location-level configuration, and audit visibility for operational changes.
- +Unified menu and order data model across POS and reporting
- +Extensible API surface for integrations tied to ordering and operations
- +Location and configuration controls support multi-outlet governance
- +RBAC supports role separation across admin and floor workflows
- –Automation breadth depends on the specific event and object model
- –Complex custom workflows can increase setup time and change risk
- –Hardware provisioning and workflow configuration can require careful rollout
- –Some advanced analytics require export or external BI rather than native automation
Best for: Fits when multi-location restaurants need tight POS-to-operations integration with an API and strong admin governance.
TouchBistro
SMBiPad-based POS designed specifically for restaurants with tableside ordering and floor plan management.
Table-side ticket management with modifier and tax accuracy across splits, transfers, and settlement.
TouchBistro runs in-store POS workflows for menu items, tables, modifiers, and payments while handling restaurant operations end to end. Integration depth centers on exportable reporting, third-party add-ons, and payment hardware support that reduces custom wiring.
The data model supports ordering, tickets, tickets-to-invoices, and item-level tax and modifier calculations that keep reconciliation consistent. Automation and admin controls focus on role-based access, permissioned settings, and operational task sequencing for faster staff execution.
- +Strong table service workflow with ticketing, split, and modifiers
- +Role-based permissions for menus, pricing, and operational settings
- +Multiple hardware and payment integrations reduce custom glue code
- +Reporting uses operational data like items, taxes, and payments
- –API automation surface is limited compared with more developer-first POS
- –Multi-location governance needs careful setup to prevent config drift
- –Some back office adjustments require admin review instead of self-serve
- –Complex promotions and edge cases can require manual procedure work
Best for: Fits when restaurant teams need reliable table and ticket workflows with controlled admin permissions.
HungerRush
SMBRestaurant POS with built-in delivery management, loyalty, and online ordering.
Role-based terminal access for order handling and admin actions with operational permission boundaries.
HungerRush is a restaurant point of sale system focused on operations that require tight order flow and staff execution control. The product’s core capabilities center on menu and ordering screens, ticket management, and back-office reporting tied to a POS data model.
Integration depth matters most for operators that need API-driven workflows, store provisioning, and automation hooks across kitchen, payments, and fulfillment steps. Governance control is evaluated through role-based permissions, configuration management, and operational auditability across terminals and locations.
- +Menu, modifiers, and ticket flow model matches common restaurant workflows
- +Terminal operations are structured around order states and role-based screens
- +Back-office reporting ties outcomes to POS transactions and time windows
- +Configuration supports multi-location operations with consistent menu mapping
- –API surface and automation hooks are less transparent than top integration-led POS
- –Data schema breadth for custom fields and events appears limited for deep extensibility
- –Audit and audit log controls need clearer separation across admin roles
- –Extending order routing logic may require workarounds when rules get complex
Best for: Fits when restaurant groups need reliable POS ticket flow with controlled staff permissions and light automation.
Aldelo
SMBRestaurant POS with offline capability, table management, and online ordering integration.
API-backed data exchange that supports integrating orders, menu, and loyalty workflows into external systems with governed access controls.
Aldelo differentiates itself for restaurants that need deep back-office integration through a documented POS and workflow model. Aldelo supports station-based ordering, kitchen ticketing, and table or counter order management that map directly to restaurant service flows.
Aldelo also provides a customization and extensibility surface through its API and configuration options, which can support integrations for loyalty, accounting, and third-party systems. Admin controls focus on role-based access and operational governance so staff actions remain traceable through audit-friendly patterns.
- +Station and ticket workflow aligns with kitchen throughput
- +Integration depth through POS data exposure and extensibility options
- +Role-based access supports separation of duties
- +Automation and operational configuration reduce manual re-entry
- –API and integration work requires schema and mapping effort
- –Multi-location governance needs deliberate setup
- –Extensibility depends on integration design choices
- –Workflow configuration can add admin overhead during menu changes
Best for: Fits when restaurant groups need POS ordering mapped to kitchen and accounting integrations with controlled staff access.
Restroworks
enterpriseCloud restaurant POS with multi-brand management, supply chain, and analytics.
REST API plus event-driven automation hooks that map orders, menus, and service status changes to external systems.
Restroworks is restaurant point of sale software built around restaurant-specific operations and kitchen flow. The distinct focus is integration depth via an automation and API surface that supports order, menu, and operational data exchange.
Core capabilities center on POS order capture, modifier and menu data modeling, and operational reporting tied to service workflows. Admin and governance controls target role-based access and auditability across staff and management actions.
- +API surface supports operational automation across POS and systems
- +Role-based access controls map to kitchen, floor, and manager duties
- +Menu and modifier data model supports consistent ticket construction
- +Audit logging supports traceability for order and admin actions
- –Complex integrations require schema alignment across connected systems
- –Advanced automation configuration can take time for administrators
- –Governance settings need careful rollout to avoid staff friction
- –Reporting depth depends on how events are mapped in integrations
Best for: Fits when restaurants need POS order capture plus API-driven integrations with controlled access and audit trails.
Epos Now
SMBCloud POS with restaurant mode offering table management, course ordering, and stock control.
Epos Now kitchen ticket routing driven by the shared order data model across tills.
Epos Now runs restaurant point of sale workflows with order capture, payment handling, and kitchen-ready ticketing tied to menus and stock. It offers a defined retail data model across items, modifiers, orders, and customers that drives reporting and operational views.
Integration depth centers on configuration extensibility, exports, and an automation surface for connecting external services through an API. Admin and governance controls cover user permissions, operational auditability, and centralized configuration needed to coordinate multiple tills and locations.
- +Restaurant POS workflows connect orders to kitchen ticketing
- +Item and modifier schema supports consistent menu configuration
- +Automation and API surface supports system integration
- +Role-based access supports multi-till operational governance
- –API automation breadth can be limited for advanced edge cases
- –Complex modifier rules may require careful configuration
- –Multi-location setup needs strong change control to avoid drift
- –Reporting exports can require additional tooling for data modeling
Best for: Fits when restaurant teams need POS order processing tied to menu data plus API integration and RBAC controls.
Sapaad
SMBCloud restaurant POS with inventory, online ordering, and multi-branch management.
API and automation surface tied to the POS order and payments data model for external system syncing.
Sapaad is a restaurant point of sale system designed for operators who need more than local billing screens. It centers on a POS data model for menus, orders, payments, and day-end reporting with role-based administration and configurable settings.
The automation and integration depth comes from its support for system-level workflows and external connectivity through an API and event-style behaviors. Governance shows up in how administrators control access, maintain configuration consistency, and preserve operational auditability across daily sales cycles.
- +Restaurant-focused data model for items, orders, and payments
- +Administration controls support controlled access by role
- +Automation-friendly workflow design for daily operational routines
- +API-oriented extensibility for integrations and provisioning
- –Integration depth depends on the available API surface for each use case
- –Governance controls may require deliberate setup to match internal RBAC
- –Reporting configuration can take effort across menu and modifier structures
- –Operational throughput tuning requires careful POS terminal configuration
Best for: Fits when multi-role restaurant teams need POS governance plus API-driven integration and automation.
How to Choose the Right point of sale restaurant software
This buyer’s guide compares Clover, Lavu, Oracle MICROS, Toast, TouchBistro, HungerRush, Aldelo, Restroworks, Epos Now, and Sapaad on integration depth, the POS data model, automation and API surface, and admin and governance controls.
It focuses on what teams need to connect POS events to kitchen, payments, online ordering, and back office systems while keeping menu configuration consistent across terminals and locations.
Evaluation criteria focused on data model control, integration depth, and governance
Integration depth determines how much of the restaurant workflow can be automated without fragile exports and manual re-entry. A tool’s data model and schema design determine how cleanly orders, tenders, receipts, taxes, and modifiers map into downstream systems.
Automation and API surface determine which events can trigger actions across ordering, kitchen routing, loyalty, accounting, and fulfillment. Admin and governance controls determine how access is separated across roles, locations, and terminals, and whether changes remain traceable through audit log coverage.
Transaction-linked POS data model for orders, tenders, and receipts
Clover ties orders, tenders, and receipts into a transaction-centric data model so automation can be anchored to the POS objects teams care about at settlement time. Toast similarly maintains a unified menu and order data model that reduces handoffs across stations and reporting.
Configurable menu, modifier, and pricing schema for station and kitchen consistency
Lavu uses a configurable menu, modifier, and pricing data model to drive consistent ordering across stations and integrations. TouchBistro keeps modifier and tax accuracy across splits, transfers, and settlement, which reduces reconciliation gaps when tables change.
Documented API and automation hooks tied to ordering events
Restroworks provides a REST API plus event-driven automation hooks that map orders, menus, and service status changes to external systems. Clover emphasizes transaction and receipt-centric automation tied to the POS data model, which is the basis for receipt-linked workflows in integrations.
Enterprise-style provisioning and API-driven workflow exchange
Oracle MICROS fits teams that need enterprise connectivity patterns for menu, pricing, and operational states with API-driven workflows and external system data exchange. This reduces store-level configuration drift when multi-site governance is enforced through the same administrative patterns.
RBAC and audit visibility for operational changes across terminals and locations
Toast provides role-based access with audit log coverage for management actions across locations and terminals. Clover also includes role-based access and operational audit visibility for governing daily workstation actions.
Table and ticket workflow modeling with accurate modifier and tax handling
TouchBistro’s table-side ticket management keeps modifier and tax calculations consistent across split, transfers, and settlement. Aldelo aligns station and ticket workflow to kitchen throughput while using role-based access to keep operational traces clear for integrations with loyalty and accounting.
Decision framework for selecting a restaurant POS tool by integration, schema, and control
Start with the integration contracts that actually exist in the workflow. Pick tools like Restroworks, Clover, or Oracle MICROS when the target systems require structured order, menu, and operational state exchange through an API.
Then validate the POS data model that will feed those integrations. Lavu and Toast help when station ordering and menu consistency must stay aligned because their menu and modifier schema drives both ordering and routing behaviors.
Map each automation target to a POS object and event
For receipt-driven automation and settlement workflows, anchor to Clover’s transaction-linked orders, tenders, and receipts model. For service-status and operational routing triggers, align workflows to Restroworks event-driven automation hooks that map orders and service status changes.
Test menu, modifier, and tax accuracy across the service patterns that break systems
If split bills, transfers, or table-side modifier edits are routine, validate TouchBistro’s ticket management with modifier and tax accuracy across those flows. For multi-station consistency, validate Lavu’s configurable menu, modifier, and pricing schema against the station routing rules.
Check whether governance is enforced through RBAC and audit log coverage
If multiple locations and management roles are active at the same time, require Toast’s role-based access with audit log coverage for management actions across locations and terminals. For workstation-level operational governance, verify Clover’s role-based access and operational audit visibility for daily workstation actions.
Confirm provisioning and configuration strategy for multi-store deployments
For enterprise-style multi-site control that reduces configuration drift, validate Oracle MICROS with API-driven workflow exchange and governance patterns used across the enterprise. For smaller groups that still need multi-location control, verify Lavu’s store and device configuration and controlled multi-device ordering with role-based permissions.
Assess how custom workflow logic will be configured or extended
When custom automation must cover many ordering edge cases, confirm Clover’s documented app and API coverage and identify which events are supported before committing. For operator-driven automation with defined order handling boundaries, validate HungerRush’s role-based terminal access and configuration to ensure routing logic stays within supported operational rules.
Plan schema alignment work for integrations that depend on custom fields and event mapping
For tools where integrations require careful schema mapping, run a schema-mapping dry run for Aldelo and Clover to estimate effort for menu, orders, and loyalty fields. For deeper operational integrations, validate Restroworks and Oracle MICROS event mappings so external systems consume the same order and service status model across stores.
Restaurant teams by workflow and governance needs
Different restaurant models stress different parts of a POS platform. Table-first operators need ticket correctness under splits and modifier changes. Multi-store groups need configuration consistency plus RBAC and auditability.
Integration-led operators need an API and automation surface that can carry structured menu and order objects into external systems without re-keying data.
Multi-station restaurants that must keep menu and modifier schema consistent across stations
Lavu fits when governed menu, modifier, and pricing schema must drive consistent ordering behavior across stations and devices. Clover also fits when station workflows must remain tied to transaction and receipt-centric POS objects that integrations can consume reliably.
Multi-location operators that require audit visibility and role separation across staff, managers, and terminals
Toast is a fit when role-based access and audit log coverage are required across locations and terminals. Clover fits groups that also need role-based workstation restrictions plus operational audit visibility for daily actions.
Enterprise multi-site teams that need enterprise governance and API-driven operational state exchange
Oracle MICROS fits deployments where menu, pricing, and operational states must be provisioned through enterprise patterns and exchanged via documented APIs. It also reduces store-level configuration drift through consistent governance controls.
Operators focused on table-side service workflows and accurate modifier and tax handling
TouchBistro fits when table-side ticket management must stay accurate across splits, transfers, and settlement. HungerRush fits when staff need controlled order handling through role-based terminal access with operational permission boundaries for order states.
Integration-first restaurant groups that must sync orders and service status to external systems
Restroworks fits when a REST API plus event-driven automation hooks must map orders, menus, and service status changes into external systems with audit trails. Aldelo and Sapaad also fit integration-centric teams because both expose POS workflows and data model elements for orders, payments, menu, and loyalty or external syncing.
Pitfalls that show up when selecting restaurant POS tools
Many failures come from treating POS like a simple billing terminal instead of a governed data system. Another common failure comes from integrating without validating how the POS data model represents menu, modifiers, taxes, and ticket splits.
Governance mistakes also appear when RBAC is not aligned to actual operational roles and when audit log coverage does not meet compliance and training needs.
Assuming automation can cover edge cases without validating event and API coverage
Clover and Restroworks support automation tied to POS objects and events, but custom automation can be limited where event coverage does not match the desired workflow. Run a workflow coverage check for the specific triggers needed for ordering, routing, and receipt outcomes.
Skipping schema-mapping validation between POS objects and downstream systems
Clover and Aldelo both require careful schema mapping effort for integrations, which can affect timeline when menu, modifier, and receipt objects must match external schemas. Validate the schema contract early for item, modifier, tax, and tender objects.
Allowing configuration drift across multi-location or multi-device setups
Lavu and Toast support store-level configuration and multi-device ordering, but complex multi-location setups still require disciplined configuration management. Use a rollout plan that enforces consistent menu and modifier schema behavior across devices and terminals.
Underestimating governance gaps in auditability and admin role separation
HungerRush and Sapaad can need clearer separation across admin roles or more deliberate governance setup, especially as teams grow across terminals and locations. Require RBAC behavior and audit log coverage to match real admin and staff boundaries.
Choosing a POS without validating table-side ticket and modifier accuracy for real service flows
TouchBistro is built around table-side ticket management and modifier and tax accuracy across splits and transfers, which is critical when the service model breaks order assumptions. If splits and transfers are common, validate those flows before committing to a POS configuration.
How We Selected and Ranked These Tools
We evaluated Clover, Lavu, Oracle MICROS, Toast, TouchBistro, HungerRush, Aldelo, Restroworks, Epos Now, and Sapaad using a weighted scoring model across features, ease of use, and value, with features carrying the largest weight at forty percent. Ease of use and value each counted for thirty percent, while we kept the scoring grounded in the documented capabilities in each tool’s operational workflow, integration surface, and governance controls.
Clover separated from lower-ranked tools because its transaction-linked POS data model connects orders, tenders, and receipts and it pairs that with a documented API and app integration surface for receipt-centric automation tied to POS objects. That combination lifted the features score since integration depth and automation mapping depend on a consistent schema and clear event anchors.
Frequently Asked Questions About point of sale restaurant software
How do Clover and Toast differ in POS-to-operations integration design?
Which tools offer the most explicit integration surface for external systems via API?
How do multi-location restaurants evaluate RBAC and audit log coverage?
What data migration approach matters when moving from spreadsheets or legacy POS to a schema-driven POS?
Which POS products map best to table service workflows with ticket and settlement accuracy?
How do TouchBistro and Clover handle offline or store resilience during order capture?
What technical requirements differ for kitchen ticketing and item-level calculations?
Which tools support extensibility for automation tied to menu and modifier configuration changes?
How should admins control configuration consistency across terminals and locations to avoid operational drift?
Conclusion
After evaluating 10 tools, Clover stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.
Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Keep exploring
Comparing two specific tools?
Software Alternatives
See head-to-head software comparisons with feature breakdowns, pricing, and our recommendation for each use case.
Explore software alternatives→Need a personal recommendation?
Software Advisory Service
Skip months of vendor evaluation. Our analysts recommend the right tool for your business in 2–4 weeks.
Talk to an analyst →