Status labels: ■ Built in the repository (checked files or developer tooling, not an app feature) ◧ Designed in a document, no code yet ○ Planned: listed in the catalog, not built ? Not decided △ Not in the catalog yet (a gap) – No claim made
What is missing in Simca's plan for full-service restaurants, including no hosted online-reservation widget or marketplace?
△ Gap C0607
Honest gaps for full-service restaurants: no hosted online-reservation widget or marketplace; no handheld-order-taker hardware list beyond generic phones and tablets; no payroll tip-compliance engine. Fit rating: close fit. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in full-service restaurants, including split a check five ways with different items?
○ Planned C0608
In full-service restaurants watch for: split a check five ways with different items; item voided after being cooked; table moved mid-meal; kitchen printer offline. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
What integrations do full-service restaurants depend on, for example kitchen display and ticket printers?
○ Planned C0609
Integrations full-service restaurants typically need: kitchen display and ticket printers; reservation list; accountant; delivery apps via CSV. In Simca's plan most are files or optional adapters rather than cloud APIs; marketplace and ERP connectors are gaps.
Open this answer on its own page
Which payment types do full-service restaurants usually see, such as cash?
○ Planned C0610
Typical tenders in full-service restaurants: cash; cards via external terminal or phone Tap to Pay; mobile wallets recorded manually; vouchers; house account. Simca's stance is cash first, wallets like Yape and Plin recorded by hand, and cards only through the phone's Tap to Pay. All planned.
Open this answer on its own page
Who works in full-service restaurants and what do they need, for example host?
○ Planned C0611
Typical roles in full-service restaurants: host; server; bartender; line cook; expediter; manager. The business is characterised by table and seat management; courses and modifiers; kitchen and bar stations. The planned catalog serves these through permissions, shifts and reports.
Open this answer on its own page
What is missing in Simca's plan for quick-service and fast casual, including no drive-through lane timing hardware?
△ Gap C0612
Honest gaps for quick-service and fast casual: no drive-through lane timing hardware; no native delivery-marketplace API; no franchisor royalty engine. Fit rating: close fit. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in quick-service and fast casual, including combo substitution?
○ Planned C0613
In quick-service and fast casual watch for: combo substitution; drive-through order changes; order number rolls over; delivery app tablet offline. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
What integrations do quick-service and fast casual depend on, for example kitchen display?
○ Planned C0614
Integrations quick-service and fast casual typically need: kitchen display; kiosk; delivery marketplaces (manual or CSV); franchisor reports. In Simca's plan most are files or optional adapters rather than cloud APIs; marketplace and ERP connectors are gaps.
Open this answer on its own page
Which payment types do quick-service and fast casual usually see, such as cash?
○ Planned C0615
Typical tenders in quick-service and fast casual: cash; cards; phone Tap to Pay; mobile wallets recorded manually; vouchers. Simca's stance is cash first, wallets like Yape and Plin recorded by hand, and cards only through the phone's Tap to Pay. All planned.
Open this answer on its own page
Who works in quick-service and fast casual and what do they need, for example cashier?
○ Planned C0616
Typical roles in quick-service and fast casual: cashier; cook; expediter; shift lead; manager; franchisee. The business is characterised by counter ordering; combos and upsells; drive-through. The planned catalog serves these through permissions, shifts and reports.
Open this answer on its own page
What is missing in Simca's plan for cafes, coffee shops and bakeries, such as no production scheduling for ovens?
△ Gap C0617
Honest gaps for cafes, coffee shops and bakeries: no production scheduling for ovens; no allergen matrix generator. Fit rating: close fit. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in cafes, coffee shops and bakeries, such as batch bake that fails?
○ Planned C0618
In cafes, coffee shops and bakeries watch for: batch bake that fails; recipe change; loyalty card lost; wholesale order short. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
What rules should cafes, coffee shops and bakeries check locally, including food-safety and allergen labelling?
○ Planned C0619
Themes to verify for cafes, coffee shops and bakeries: food-safety and allergen labelling; tax on takeaway versus dine-in; labelling for baked goods (themes to verify). These are themes, not advice, and Simca claims no compliance with any of them.
Open this answer on its own page
Which reports matter most in cafes, coffee shops and bakeries, including sales by hour?
○ Planned C0620
Reports commonly wanted in cafes, coffee shops and bakeries: sales by hour; waste; recipe cost; loyalty redemptions; wholesale invoices. Stock and assets to track: ingredients; finished goods with a short shelf life; packaging; recipe yields. The RPT module lists planned reports; nothing is built.
Open this answer on its own page
How do cafes, coffee shops and bakeries businesses take a drink order and customise, for example sell baked goods by piece or weight?
○ Planned C0621
Take a drink order and customise is one of the usual flows in cafes, coffee shops and bakeries. Others: sell baked goods by piece or weight; bake from a recipe; produce wholesale orders. The planned catalog touches this through modules SALE, TKT, TBL, MENU, KDS, BILL; fit rating: close fit. Planned only; nothing is built.
Open this answer on its own page
What is missing in Simca's plan for bars, pubs and nightlife, think of no id-scanner integration?
△ Gap C0622
Honest gaps for bars, pubs and nightlife: no ID-scanner integration; no pour-meter hardware integration; no door-capacity counter. Fit rating: close fit. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in bars, pubs and nightlife, think of tab left open at closing?
○ Planned C0623
In bars, pubs and nightlife watch for: tab left open at closing; comped drinks; price change at 21:00 mid-round. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
Which reports matter most in bars, pubs and nightlife, for example pour cost?
○ Planned C0624
Reports commonly wanted in bars, pubs and nightlife: pour cost; sales by bartender; comps and voids; happy-hour mix. Stock and assets to track: bar pours; bottles opened; spill and comp tracking; kegs. The RPT module lists planned reports; nothing is built.
Open this answer on its own page
How do bars, pubs and nightlife businesses open a tab with a card or ID as security, including add drinks by round?
○ Planned C0625
Open a tab with a card or ID as security is one of the usual flows in bars, pubs and nightlife. Others: add drinks by round; apply happy-hour price rules; split tabs. The planned catalog touches this through modules SALE, TKT, TBL, MENU, KDS, BILL; fit rating: close fit. Planned only; nothing is built.
Open this answer on its own page
What rules should bars, pubs and nightlife check locally, for example alcohol licensing and hours?
○ Planned C0626
Themes to verify for bars, pubs and nightlife: alcohol licensing and hours; age checks; over-service rules; entertainment licences (themes to verify). These are themes, not advice, and Simca claims no compliance with any of them.
Open this answer on its own page
What is missing in Simca's plan for food trucks and street food, including no map or location-based reporting beyond a free-text location?
△ Gap C0627
Honest gaps for food trucks and street food: no map or location-based reporting beyond a free-text location field; no event-vendor settlement. Fit rating: good fit, some gaps. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in food trucks and street food, including no signal at an event?
○ Planned C0628
In food trucks and street food watch for: no signal at an event; a sudden sell-out; device battery low; lost phone. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
Who works in food trucks and street food and what do they need, for example owner-operator?
○ Planned C0629
Typical roles in food trucks and street food: owner-operator; cook; helper. The business is characterised by tiny crew; limited stock carried each day; cash-heavy. The planned catalog serves these through permissions, shifts and reports.
Open this answer on its own page
What integrations do food trucks and street food depend on, for example phone only?
○ Planned C0630
Integrations food trucks and street food typically need: phone only; accountant export. In Simca's plan most are files or optional adapters rather than cloud APIs; marketplace and ERP connectors are gaps.
Open this answer on its own page
Which payment types do food trucks and street food usually see, such as cash?
○ Planned C0631
Typical tenders in food trucks and street food: cash; phone Tap to Pay when online; mobile wallets recorded manually. Simca's stance is cash first, wallets like Yape and Plin recorded by hand, and cards only through the phone's Tap to Pay. All planned.
Open this answer on its own page
What is missing in Simca's plan for contract catering and food-service management, including no per-cover contract-billing module?
△ Gap C0632
Honest gaps for contract catering and food-service management: no per-cover contract-billing module; no menu-cycle nutrition analysis; no payroll-deduction integration. Fit rating: close fit. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in contract catering and food-service management, including client changes headcount on short notice?
○ Planned C0633
In contract catering and food-service management watch for: client changes headcount on short notice; allergen incident; site closed for a holiday. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
Which payment types do contract catering and food-service management usually see, such as client invoicing?
○ Planned C0634
Typical tenders in contract catering and food-service management: client invoicing; employee payroll deduction; cash at some sites; cards. Simca's stance is cash first, wallets like Yape and Plin recorded by hand, and cards only through the phone's Tap to Pay. All planned.
Open this answer on its own page
Who works in contract catering and food-service management and what do they need, for example site manager?
○ Planned C0635
Typical roles in contract catering and food-service management: site manager; chef; kitchen porter; district manager; client liaison; buyer. The business is characterised by many client sites; per-head or per-meal billing; staff canteens. The planned catalog serves these through permissions, shifts and reports.
Open this answer on its own page
What integrations do contract catering and food-service management depend on, for example client hr (payroll deduction?
○ Planned C0636
Integrations contract catering and food-service management typically need: client HR (payroll deduction); accountant; purchasing. In Simca's plan most are files or optional adapters rather than cloud APIs; marketplace and ERP connectors are gaps.
Open this answer on its own page
What is missing in Simca's plan for hotels, hostels and lodging, including the catalog has a hotel/hostal preset and reservation items?
△ Gap C0637
Honest gaps for hotels, hostels and lodging: the catalog has a hotel/hostal preset and reservation items but no full property-management system: no channel manager, no room rack, no housekeeping board, no door-lock integration, no night-audit module. Fit rating: close fit. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in hotels, hostels and lodging, including guest disputes a charge?
○ Planned C0638
In hotels, hostels and lodging watch for: guest disputes a charge; early departure; currency exchange; room move. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
What integrations do hotels, hostels and lodging depend on, for example channel managers and booking sites?
○ Planned C0639
Integrations hotels, hostels and lodging typically need: channel managers and booking sites; door-lock systems; accountants. In Simca's plan most are files or optional adapters rather than cloud APIs; marketplace and ERP connectors are gaps.
Open this answer on its own page
Which payment types do hotels, hostels and lodging usually see, such as cash?
○ Planned C0640
Typical tenders in hotels, hostels and lodging: cash; cards; transfers; city ledger; deposits; foreign currency recorded manually. Simca's stance is cash first, wallets like Yape and Plin recorded by hand, and cards only through the phone's Tap to Pay. All planned.
Open this answer on its own page
Who works in hotels, hostels and lodging and what do they need, for example front-desk agent?
○ Planned C0641
Typical roles in hotels, hostels and lodging: front-desk agent; housekeeper; night auditor; revenue manager; outlet staff; general manager. The business is characterised by rooms and rates; guest folios; restaurant, bar and spa outlets. The planned catalog serves these through permissions, shifts and reports.
Open this answer on its own page
What is missing in Simca's plan for casinos, gaming and resorts, such as gaming-floor, slot and table systems, cage, chip, aml and?
△ Gap C0642
Honest gaps for casinos, gaming and resorts: gaming-floor, slot and table systems, cage, chip, AML and surveillance are out of scope; at most the restaurant, bar and retail outlets could use the POS modules. Fit rating: good fit, some gaps. The planned catalog is not a shipped product.
Open this answer on its own page
What edge cases trip up point-of-sale systems in casinos, gaming and resorts, such as large cash transactions?
○ Planned C0643
In casinos, gaming and resorts watch for: large cash transactions; regulator audit; chip count variance. A system that cannot handle these will frustrate the business; the catalog's failsafe items address some generic cases.
Open this answer on its own page
What rules should casinos, gaming and resorts check locally, including gaming-regulator rules?
○ Planned C0644
Themes to verify for casinos, gaming and resorts: gaming-regulator rules; anti-money-laundering reporting; surveillance and audit requirements (themes to verify; Simca does not address these). These are themes, not advice, and Simca claims no compliance with any of them.
Open this answer on its own page
Which reports matter most in casinos, gaming and resorts, including outlet sales?
○ Planned C0645
Reports commonly wanted in casinos, gaming and resorts: outlet sales; cage reconciliation; loyalty; compliance reports. Stock and assets to track: outlet stock; retail; chips and tokens are a separate regulated system. The RPT module lists planned reports; nothing is built.
Open this answer on its own page
How do casinos, gaming and resorts businesses sell chips or credits at a cage, for example reconcile the cage?
○ Planned C0646
Sell chips or credits at a cage is one of the usual flows in casinos, gaming and resorts. Others: reconcile the cage; run outlets (restaurants, bars, shops) with a POS; reward loyalty. The planned catalog touches this through modules SALE, TKT, TBL, MENU, KDS, BILL; fit rating: good fit, some gaps. Planned only; nothing is built.
Open this answer on its own page