GITNUXSOFTWARE ADVICE
Business Process OutsourcingTop 10 Best Cafeteria Software of 2026
Top 10 cafeteria software ranked for school and campus food service, with comparison of SchoolCafé, Nutrislice, and Clover Dining features.
How we ranked these tools
Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.
Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.
Framework: Features 40% · Ease 30% · Value 30%
Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy
SchoolCafé is the best fit when districts need menu transparency plus student-linked preordering across campuses, while Clover Dining works well if you want more tightly aligned day-of-service ordering and POS execution, and Nutrislice is the go-to when nutrition and allergen consistency across channels matters most.
Editor’s top 3 picks
Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.
SchoolCafé
Student account-linked meal preordering that maps selections to individual eligibility during ordering.
Best for: Fits when districts need family-facing menu transparency plus student-linked preordering across multiple campuses.
Clover Dining
Editor pickOrdering window rules connect menu availability to kitchen production tasks without separate manual mapping.
Best for: Fits when schools want controlled preordering plus day-of-service production alignment with reliable account linkage.
Nutrislice
Editor pickItem-level nutrition and allergen display generated from structured menu content for each service day.
Best for: Fits when districts need consistent nutrition labeling across schools and channels during each menu cycle.
Comparison Table
SchoolCafé
vertical specialistSchool meal software supports menus, meal payments, applications, student accounts, and cafeteria administration.
Student account-linked meal preordering that maps selections to individual eligibility during ordering.
SchoolCafé is built around the meal experience for families and the operational workflow for food service teams. Meal preordering flows connect to student account identifiers so orders reflect who is eligible to buy and what they selected. Administrative configuration supports menu cycle management and recurring publish schedules across campuses.
A practical tradeoff is that deep cashless payment integration and full transaction reconciliation depend on district POS or payment stack alignment. SchoolCafé fits best when a district wants a single place for menu transparency and preordering while keeping production workflows tied to existing POS, kitchen, or student-account systems.
- +Menu publishing and preordering use the same customer-facing data workflow
- +Student account-linked meal ordering reduces manual roster checking
- +Allergen and nutrition display supports family meal decisions
- +District controls support multi-campus menu cycle operations
- –Cashless payment and reconciliation depth depends on integration with existing systems
- –Cross-site governance takes configuration discipline for consistent setup
Food service directors
Centralize menus and preorders by campus
Fewer manual service-day changes
School nutrition operations
Reduce roster checks during service
Lower staff workload
Show 2 more scenarios
Parent portal administrators
Communicate allergens and nutrition online
More confident selections
Family-facing content shows ingredient and nutrition details that support dietary restriction planning.
District IT integration teams
Connect ordering to existing student systems
Cleaner eligibility alignment
Integrations map student identifiers so ordering reflects the district’s enrollment data.
Best for: Fits when districts need family-facing menu transparency plus student-linked preordering across multiple campuses.
Clover Dining
SMBPoint-of-sale software supports cafeteria payments, menus, employee management, and restaurant applications.
Ordering window rules connect menu availability to kitchen production tasks without separate manual mapping.
Clover Dining fits districts that want a single ordering workflow that starts with menu decisions and ends with kitchen production steps. Menu cycle management drives available items, while recipe and item setup support consistent production details for day-of-service. The admin surface is built around configuration that controls ordering windows, item availability, and how selections map to production tasks.
A tradeoff appears in integration depth for complex district landscapes, since many deployments depend on point-of-sale integration and student account data feeds to get end-to-end swipe and eligibility behavior. A common usage situation is a school that moves from ad hoc lunch signup sheets to a controlled preordering window with kitchen-ready outputs for batch service preparation.
- +Menu cycle configuration and ordering windows map to kitchen production workflows
- +Item setup supports consistent production details for day-of-service execution
- +District admin controls make item availability changes auditable by time window
- +Ordering workflow reduces mismatch between student selections and kitchen prep
- –End-to-end behavior depends on working point-of-sale integration and student data feeds
- –More complex districts may require careful rollout for eligibility-linked ordering rules
- –Advanced kitchen reporting can require additional operational process alignment
- –Complex menu changes can increase admin workload near ordering cutoffs
Food service directors
Standardize lunch operations across campuses
Fewer missing or mismatched items
School IT integration teams
Connect accounts and cashless POS
Reduced reconciliation effort
Show 2 more scenarios
Campus administrators
Control eligibility-driven menu access
More consistent student access control
Apply rules that govern what students can order during configured windows and production periods.
Kitchen production leads
Turn menus into daily prep lists
Clearer batch prep decisions
Use item setup and production mapping so day-of-service execution follows configured selections.
Best for: Fits when schools want controlled preordering plus day-of-service production alignment with reliable account linkage.
Nutrislice
vertical specialistSchool nutrition software publishes menus, supports meal ordering, and provides nutrition and allergen information.
Item-level nutrition and allergen display generated from structured menu content for each service day.
Nutrislice is built for nutrition content publishing with structured meal data that supports allergen and dietary restriction messaging per item and per service day. Its admin workflows focus on updating menu content for schools and keeping labels aligned to the calendar rather than producing separate static documents. For districts coordinating many buildings, the core advantage is reducing rework by centralizing menu cycle updates that then flow to the student and family experience.
A practical tradeoff is that Nutrislice is primarily a publishing and labeling workflow tool, not a full cafeteria operations suite for production records and inventory. Nutrislice fits best when menu items and nutrition facts need to be visible across a parent portal, kiosks, and mobile surfaces while meal service teams still rely on separate kitchen production and POS systems. Another fit signal is when district staff need repeated updates across many sites during the same menu cycle.
- +Centralized nutrition labeling updates that keep meal info consistent across sites
- +Allergen and dietary messaging tied to published menu items
- +Multi-channel publishing for families and students without recreating documents
- +Workflow focus on menu cycle updates rather than one-off announcements
- –Does not replace core POS, payment, and swipe-driven meal counting workflows
- –Complex district-wide content mapping can require governance discipline
- –Production-sheet and batch record workflows depend on separate systems
- –Customization beyond labeling and publishing can be limited by integration scope
Food service directors
Maintain consistent nutrition labels district-wide
Fewer manual label corrections
School nutrition teams
Reduce daily menu change rework
Faster day-to-day updates
Show 2 more scenarios
District communications staff
Provide dietary messaging across channels
More consistent parent messaging
Comms teams publish allergen and diet information to student and family-facing views from one workflow.
Families and students
Check item-level dietary restrictions before lunch
Quicker meal selection
Students and families view structured labels per menu item instead of scanning printed PDFs.
Best for: Fits when districts need consistent nutrition labeling across schools and channels during each menu cycle.
Toast
SMBRestaurant POS software supports cafeteria ordering, payments, menus, kitchen operations, and reporting.
Toast's POS workflow ties item-level ordering to terminal operations and daily reconciliation without splitting records across separate systems.
Toast is a cafeteria POS and ordering system from Toasttab that routes menu selections from self-service into kitchen prep and payment flows. It is distinct for how strongly it unifies ordering, payment, and reporting around one operational POS surface.
- +Single POS workflow links ordering, payments, and daily reporting
- +Terminal permissions support role-based access for staff workflows
- +Menu item configuration enables consistent pricing and modifiers across locations
- +Operational reports support faster variance checks versus planned production
- –School eligibility and subsidy workflows require external data connections
- –Kitchen workflows can need extra configuration to match production sheet formats
Best for: Fits when schools need a unified cafeteria POS plus ordering-to-production handoff with tight operational reporting.
Oracle MICROS Simphony
enterpriseEnterprise restaurant POS software supports cafeteria transactions, kitchen operations, payments, and centralized reporting.
Service-time transaction execution with device-first controls typical of Oracle MICROS POS deployments.
Oracle MICROS Simphony runs cafeteria service workflows through point-of-sale terminals, kitchen order handling, and back-office management. It is tightly tied to Oracle MICROS retail and hospitality foundations, which helps with POS integration patterns, transaction handling, and operational reporting.
- +Strong POS-centered workflow support for cafeteria transactions at service time
- +Operational reporting aligns to store and device execution models
- +Useful fit when campus dining follows Oracle MICROS deployment practices
- +Extensibility options exist through Oracle MICROS integration components
- –School-specific meal eligibility and subsidy workflows need careful system integration
- –Admin and device governance can be complex in multi-site deployments
- –Kitchen workflow depth may depend on the implementation scope for production screens
- –Automation for student account level processes can require external system orchestration
Best for: Fits when campuses already run Oracle MICROS POS ecosystems and need cafeteria execution plus operational reporting.
Mashgin
API-firstAutonomous checkout kiosks identify packaged food and beverages for unattended cafeteria purchases.
Computer-vision recognition of served meal items that maps directly to POS transaction records for reconciliation.
Mashgin brings computer-vision identification of meals to the cafeteria workflow, linking what gets served to the POS and student purchase records. It focuses on item-level accuracy rather than menu-only forecasting by recognizing packed or plated items as they move through service.
- +Vision-based meal identification improves accuracy of what was served
- +Transaction matching supports tighter reconciliation against student purchase data
- +Service workflow reduces the need for manual count and code entry
- +Designed for high-throughput lunch lines with real-time capture
- –Requires camera placement, lighting control, and operational discipline
- –Works best when stations follow standardized serving formats
Best for: Fits when schools need item-level serving verification to strengthen transaction reconciliation in high-volume lines.
CBORD
enterpriseCampus dining software manages meal plans, point-of-sale transactions, mobile ordering, and foodservice operations.
Campus-wide meal service orchestration that connects provisioning, production workflows, and external systems into one operational sequence.
CBORD is a cafeteria and campus foodservice system focused on high-control meal operations across multiple locations and entities. It supports menu cycle workflows, payment and POS-adjacent integrations, and production planning that connects to kitchen execution.
- +Strong workflow fit for multi-site foodservice operations
- +Menu and production processes designed to align with service execution
- +Integration options for student accounts and point-of-sale environments
- +Extensive configuration controls for dietary and communication requirements
- –Administration complexity rises with multi-entity governance needs
- –Extensibility and API coverage can require system-integration planning
- –Kitchen workflow outcomes depend on configuration of upstream data
- –User experience varies by role and the depth of installed integrations
Best for: Fits when district or university foodservice needs controlled operations across multiple schools with heavy integration coverage.
Square for Restaurants
SMBRestaurant POS software provides ordering, payments, menu management, inventory, and sales reporting.
Payment-first checkout using Square terminals and digital ordering, with receipts tied to the POS order lifecycle.
Square for Restaurants is a restaurant point-of-sale and ordering tool adapted for cafeteria-style service through kiosk and mobile ordering options. It delivers fast card and digital payment processing, modifier-based menu building, and operational receipts that help with transaction reconciliation.
- +Modifier-driven menu setup supports configurable cafeteria items
- +Cashless payment support reduces line friction during high-volume service
- +POS receipts and order history support transaction reconciliation
- +API access supports integration for custom ordering and reporting
- –Eligibility verification and subsidy eligibility workflows are not cafeteria-native
- –Meal swipe management and student account controls require external systems
- –Kitchen production sheets need configuration instead of dedicated school printouts
- –Audit log depth and RBAC granularity depend on configuration choices
Best for: Fits when schools need cashless POS and ordering with light student account requirements.
MealSuite
vertical specialistFoodservice software manages menus, recipes, production, purchasing, and resident meals for senior living communities.
Batch production worksheets generated from configured recipes and ingredient sets for consistent serving-day execution.
MealSuite supports cafeteria teams with menu cycle management, ingredient and recipe setup, and production-facing worksheets. The workflow centers on creating serving plans from recipes and recipes from an ingredient catalog, then translating those plans into batch production records and serving outputs.
- +Clear workflow from recipe and ingredient setup to production worksheets
- +Dietary restriction and allergen handling tied to menu items
- +Production records support batch cooking and serving outputs
- +Menu cycle configuration supports recurring school schedules
- –Limited visibility into cross-campus performance without added process
- –Complex rule sets can require careful configuration discipline
- –POS and student systems integration depends on external connectivity
- –Allergen workflows can feel rigid for frequent ingredient substitutions
Best for: Fits when school cafeterias need recipe-to-production workflow control and allergen-labeled meal planning.
LINQ Nutrition
vertical specialistSchool nutrition software handles meal programs, menus, point of sale, production, and compliance workflows.
Menu planning workflow links nutrition and allergen labeling content directly to the published menu cycle schedule.
LINQ Nutrition serves schools and districts with cafeteria menu planning and student meal ordering workflows tied to nutrition content. Its core capabilities focus on managing menu cycles, recipe and nutrition data, and allergen or dietary restriction communication that staff and families can act on.
- +Menu cycle management keeps nutrition and labeling inputs tied to each serving period
- +Allergen and dietary restriction content is organized for repeatable student-facing display
- +Recipe and nutrition inputs reduce rework when recipes change across the menu cycle
- +Student account integration supports consistent meal eligibility handling during service
- –Workflow coverage can require district-level configuration to match each site’s service model
- –Advanced kitchen production reporting is not as visibly comprehensive as in some large suite products
Best for: Fits when districts want menu cycle governance with nutrition and allergen content tied to ordering and service.
Conclusion
After evaluating 10 cafeteria software, SchoolCafé 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.
How to Choose the Right Cafeteria Software
Cafeteria software is getting evaluated across student-facing ordering, kitchen execution handoffs, and the operational data that ties them together across schools and universities. This guide covers SchoolCafé, Clover Dining, Nutrislice, Toast, Oracle MICROS Simphony, Mashgin, CBORD, Square for Restaurants, MealSuite, and LINQ Nutrition.
The included tools are judged on integration depth with meal counting and payment systems, how each product organizes the menu and service-day data, and how automation and API surface affects district and campus administration. Each individual review focuses on those mechanisms so category fit can be judged by workflow control and governance, not marketing claims.
Cafeteria Software for schools and universities: ordering to production with eligibility-linked operations
Cafeteria software coordinates menu cycle management, meal preordering, and service-day execution so that published menu choices map to eligibility, production steps, and transaction reconciliation. SchoolCafé emphasizes student account-linked meal ordering that carries selections through ordering while matching eligibility during the ordering workflow.
Some tools also specialize in content operations and labeling so nutrition and allergens remain consistent as menus change. Nutrislice generates item-level nutrition and allergen display from structured menu content for each service day, while Toast ties item-level ordering to POS terminal operations and daily reconciliation in a single workflow path.
Cafeteria Software decision criteria for ordering, production, and reconciliation
Cafeteria software must connect menu cycle publishing to what students order and what kitchens execute during each service day. The most reliable systems carry selections through ordering while preserving eligibility checks, then they reconcile transactions against serving outcomes.
These criteria separate tools that coordinate the full ordering-to-production workflow from tools that focus on menu content or labeling. Each criterion below uses concrete mechanisms like eligibility mapping, POS workflow linking, and device or vision execution control.
Student-linked meal preordering with eligibility mapping
SchoolCafé connects student account-linked meal ordering to selections that match eligibility during the ordering workflow. Clover Dining also supports controlled preordering, but it ties ordering window rules to production tasks rather than emphasizing student account-linked eligibility mapping.
Menu publishing data reused in both ordering and kitchen execution
SchoolCafé uses the same customer-facing data workflow for menu publishing and preordering. Clover Dining maps menu cycle configuration and ordering windows to kitchen production workflows, but it requires tighter alignment between menu setup and production execution rules.
POS workflow that keeps ordering, payment, and daily reporting in one chain
Toast keeps ordering, payments, and daily reconciliation inside a unified POS workflow path so terminal operations and transaction reporting stay linked. Oracle MICROS Simphony centers on service-time transaction execution with device-first controls typical of Oracle MICROS POS deployments.
Nutrition and allergen labeling generated from structured menu content
Nutrislice generates item-level nutrition and allergen display from structured menu content for each service day. LINQ Nutrition also links menu planning inputs to nutrition and allergen labeling content tied to the published menu cycle schedule.
Serving verification that reconciles what was served to transaction records
Mashgin uses computer-vision recognition of served meal items and maps results directly to POS transaction records for reconciliation. CBORD connects provisioning and production workflows into one operational sequence, but it does not replace POS-driven meal counting with vision-based serving verification.
Multi-site foodservice orchestration across provisioning and service execution
CBORD orchestrates campus-wide meal service operations that connect provisioning, production workflows, and external systems into a single sequence. SchoolCafé is strong across multiple campuses when governance stays consistent, but cross-site administration is more sensitive to rollout configuration discipline.
How to choose Cafeteria Software by workflow ownership and integration depth
Start by defining which workflow owns the transaction record from ordering through reconciliation. Tools like Toast and Oracle MICROS Simphony stay strongest when the POS workflow is the system of record for cafeteria execution.
Then decide how nutrition and allergen content should be governed. Some tools generate labeling from structured menu inputs, while others depend on external data feeds and content mapping governance across schools.
Pick the system of record for ordering-to-reconciliation
If transaction execution and daily reporting must stay inside one terminal-driven workflow, compare Toast against Oracle MICROS Simphony. Toast ties item-level ordering to terminal operations and daily reconciliation, while Oracle MICROS Simphony emphasizes device-first service-time controls typical of Oracle MICROS POS deployments.
Decide whether student eligibility must be enforced during ordering
Choose SchoolCafé when eligibility-linked ordering must map selections to individual student accounts during the ordering step. Choose Clover Dining when ordering window rules must connect menu availability to kitchen production tasks with reliable account linkage.
Confirm how menu content becomes nutrition and allergen output
If item-level nutrition and allergen display must be generated from structured menu content per service day, prioritize Nutrislice. If menu cycle governance must keep nutrition and allergen inputs tied to each serving period, evaluate LINQ Nutrition.
Select the reconciliation model for high-volume serving lines
If serving accuracy must be verified at item level against POS transactions, compare Mashgin against batch and worksheet-driven execution options like MealSuite. Mashgin focuses on vision-based serving verification, while MealSuite focuses on batch production worksheets generated from configured recipes and ingredient sets.
Validate multi-site governance and orchestration coverage
If the district or university needs one operational sequence spanning provisioning and external integrations, CBORD is designed for campus-wide orchestration. If the priority is family-facing menu transparency plus student-linked preordering across multiple campuses, SchoolCafé fits that workflow but needs configuration discipline for consistent cross-site governance.
Who Cafeteria Software is built for
Cafeteria software fits organizations that need menu cycle management to flow into student ordering, kitchen production steps, and transaction reconciliation. The best fit depends on whether the organization owns eligibility enforcement during ordering and whether nutrition content must be generated from structured menu inputs.
These segments map to how each tool’s workflow emphasis shows up in ordering handoffs, labeling operations, and service-day reconciliation.
District foodservices managing multi-campus eligibility-linked preordering
SchoolCafé supports student account-linked meal preordering that maps selections to eligibility during ordering. Cross-site governance is workable when configuration standards are applied consistently across campuses.
Schools standardizing service-day execution to ordering window rules
Clover Dining connects ordering window rules to kitchen production tasks without separate manual mapping. It targets controlled preordering while aligning day-of-service availability to production execution.
Organizations publishing consistent nutrition and allergen labeling across channels
Nutrislice generates item-level nutrition and allergen display from structured menu content for each service day. LINQ Nutrition also ties nutrition and allergen content to the published menu cycle schedule when menu governance is centralized.
Universities and operators needing POS-centered transaction execution and reporting
Toast keeps ordering, payments, and daily reconciliation inside one POS workflow and supports terminal permissions for staff role-based operations. Oracle MICROS Simphony provides service-time transaction execution with device-first controls common in Oracle MICROS deployments.
High-volume operations requiring serving verification beyond transaction matching
Mashgin uses computer vision recognition of served meal items and maps results to POS transaction records for reconciliation. This supports item-level serving accuracy when serving formats can be standardized across stations.
Common pitfalls when buying Cafeteria Software
Most buying failures happen when eligibility enforcement, reconciliation workflow, or labeling governance is assumed to be native when it depends on external connections and operational setup. Another failure mode is selecting menu-labeling-first tools while expecting them to replace POS and meal swipe workflows.
The mistakes below show where mismatches typically appear in ordering-to-production handoffs and day-of-service reconciliation.
Assuming a nutrition and allergen labeling tool replaces core POS, payment, and meal counting workflows
Nutrislice focuses on item-level nutrition and allergen display generated from structured menu content, and it does not replace core POS, payment, and swipe-driven meal counting workflows. Plan for POS and student account transaction sources separately when selecting labeling-first tools.
Underestimating the integration dependency for eligibility and subsidy workflows
Toast requires external data connections for school eligibility and subsidy workflows, which can affect ordering outcomes even when ordering and reconciliation are unified in POS. Oracle MICROS Simphony also requires careful integration for school-specific meal eligibility and subsidy workflows.
Buying serving verification without validating station layout and serving standardization
Mashgin vision-based recognition depends on camera placement, lighting control, and operational discipline. It works best when stations follow standardized serving formats, so the workflow rollout must include station requirements.
Treating multi-site governance as a one-time configuration instead of an operational control
SchoolCafé requires cross-site governance configuration discipline for consistent setup across campuses. CBORD also adds administration complexity for multi-entity governance, so governance planning must start before rollout.
How We Selected and Ranked These Tools
We evaluated cafeteria software across ordering, kitchen execution handoffs, and reconciliation mechanisms that connect menu cycle management to transaction outcomes. Features accounted for 40% of the score and focused on workflow fit like SchoolCafé student account-linked meal preordering and Toast single POS workflow linking ordering, payments, and daily reconciliation.
Ease and value each contributed 30% and reflected operational friction such as governance complexity in multi-site deployments for SchoolCafé and integration dependency for eligibility workflows in Toast. SchoolCafé placed highest because its menu publishing and preordering use the same customer-facing data workflow and its student account-linked meal ordering reduces manual roster checking during ordering.
Frequently Asked Questions About Cafeteria Software
How does SchoolCafé map meal preorders to individual student eligibility during ordering?
Which tool handles item-level nutrition and allergen labeling for each menu cycle item?
When districts need ordering release rules tied to kitchen production tasks, how do Workflows differ?
What breaks if a campus uses a general restaurant POS approach instead of cafeteria-specific meal account logic?
How does Toast handle reconciliation when orders move from self-service into kitchen prep?
Which option is best for item-level serving verification using computer vision rather than swipe assumptions?
How should districts plan data migration when moving from legacy menu and production spreadsheets into MealSuite?
Which tool supports multi-campus administration with configuration and integration touchpoints in one operational backbone?
When universities already run Oracle MICROS POS ecosystems, how does Oracle MICROS Simphony fit into daily cafeteria execution?
What should be checked before integrating student accounts into LINQ Nutrition ordering and service touchpoints?
Tools reviewed
Primary sources checked during evaluation.
Referenced in the comparison table and product reviews above.
Funding and competing interests
This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.
They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.
Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →
- Top 10 Best Tax Practice Workflow Software of 2026
- Top 10 Best Task Workflow Management Software of 2026
- Top 10 Best Task Management Workflow Software of 2026
- Top 10 Best Task Management System Software of 2026
- Top 10 Best Task Management Template Software of 2026
- Top 10 Best Task List Management Software of 2026
- Top 10 Best Task Management Collaboration Software of 2026
- Top 10 Best Task Based Project Management Software of 2026
- Top 10 Best Task Assign Software of 2026
- Top 10 Best Task Assigning Software of 2026
- Top 10 Best Task Assignment Software of 2026
- Top 10 Best Task And Project Management Software of 2026
- Top 10 Best Task Allocation Software of 2026
- Top 10 Best Sweeper Software of 2026
- Top 10 Best Subscription Billing Management Software of 2026
- Top 10 Best Subcontractors Software of 2026
- Top 10 Best Subcontracting Software of 2026
- Top 10 Best Subcontractor Database Software of 2026
- Top 10 Best Subcontract Software of 2026
- Top 10 Best Sub Contractor Software of 2026
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→In this category
Business Process Outsourcing alternatives
See side-by-side comparisons of business process outsourcing tools and pick the right one for your stack.
Compare business process outsourcing tools→