Design stage: there is no released app yet. This site separates what exists in the repository from what is planned. See status

Migrating and buying

Comparisons by category

Non-promotional comparisons of approaches (cash-first vs card-first, offline vs cloud, free acquisition vs subscription)

Status labels: Built in the repository (checked files or tested library code; not a product you can run yet) 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

How risky is “Cash-first versus card-first tools” to get wrong, in particular regarding share of cash sales?

No claim C0277

Two design stances. Card-first systems centre on payment processing; cash-first systems centre on the drawer, credit and manual wallets. Neither is better in general; the right one follows how customers pay. Plan for: share of cash sales; wallet use; provider fees. No claim is made.

Open this answer on its own page

Where does “Offline-first versus cloud-based” fit in Simca, with a focus on connectivity?

No claim C0278

Offline-first keeps working without internet and keeps data on the shop's devices; cloud-based tools give easy multi-site access and remote support. Many shops need a mix. Plan for: connectivity; remote access; data ownership. No claim is made.

Open this answer on its own page

Where does “Free acquisition versus subscription” fit in Simca, thinking about cash flow?

Not decided C0279

Acquisition is free (ADR-0007), so there is no upfront cost; a quarterly fee would apply only above the profit threshold and moves with the published costs and the number of paying members. Pricing is not published. Plan for: cash flow; update needs; long-term cost. It is not decided.

Open this answer on its own page

What should owners check about “Local fiscal tools versus international tools”, thinking about tax rules?

No claim C0280

Local tools know local tax documents; international ones know many markets lightly. Plan for: tax rules; language; support hours. No claim is made.

Open this answer on its own page

Why does “Restaurant POS versus retail POS” matter for a small business, especially around mixed businesses?

No claim C0281

Tables, courses and kitchens versus barcodes, variants and returns. Plan for: mixed businesses; modifiers; receipts. No claim is made.

Open this answer on its own page

What should owners check about “Single store versus multi-store”, considering central pricing?

No claim C0282

Multi-store adds central catalogs, transfers and consolidated reports. Plan for: central pricing; local overrides; sync. No claim is made.

Open this answer on its own page

How does Simca approach “POS versus logistics tools”, thinking about boundaries?

No claim C0283

A POS sells; logistics tools move goods and track drivers. Simca plans an overlay rather than merging them. Plan for: boundaries; data sharing; roles. No claim is made.

Open this answer on its own page

How risky is “Bookkeeping inside a POS versus separate accounting” to get wrong, thinking about chart of accounts?

No claim C0284

Built-in bookkeeping suits tiny shops; separate accounting suits larger or regulated ones. The catalog provides exports. Plan for: chart of accounts; accountant preferences; audits. No claim is made.

Open this answer on its own page

How does Simca approach “Open data formats versus closed”, with a focus on format longevity?

No claim C0285

Open exports mean leaving is easy. Plan for: format longevity; attachments; export completeness. No claim is made.

Open this answer on its own page

What goes wrong with “Open hardware versus proprietary hardware” in a shop, considering support?

No claim C0286

Using common printers and phones versus locked devices. Plan for: support; cost; reliability. No claim is made.

Open this answer on its own page

Is “What to compare, in order” supported today, with a focus on hidden fees?

No claim C0287

A checklist: how customers pay, connectivity, local tax needs, who the staff are, existing hardware and who answers the phone when it breaks. Plan for: hidden fees; switching cost; support language. No claim is made.

Open this answer on its own page

What should owners check about “The three pricing classes: Standard, Free and Not priced”, in particular regarding presets are all standard?

Not decided C0288

Each catalog item carries one of three classes (ADR-0003). Standard is the same pricing for everyone and covers every customer-facing element, Simca Logistics included. Free applies to the launcher only. Not priced covers the packaging engine, the website and policy items that are never part of a customer package. There is no free tier by role. Everyone starts free because acquisition is free; a flat quarterly fee would apply only above a tentative profit threshold. Plan for: presets are all standard; a package is free only if every element in it is free; not-priced elements are ignored. It is not decided.

Open this answer on its own page

What should owners check about “Legacy enterprise POS suites versus the planned Simca scope”, considering which functions you really need?

No claim C0289

Large chains run suites that cover lanes, promotions, loyalty, returns, fuel, clinical or lodging systems and sit on ERP, EDI and warehouse systems. The planned Simca catalog covers the till, stock, cash, simple bookkeeping and an optional supply network, and the legacy Fortune 500 review lists where it stops. Planned and suggested only; nothing is built. Plan for: which functions you really need; what an erp already owns; integration versus building. No claim is made.

Open this answer on its own page

Is “ERP versus POS bookkeeping” supported today, thinking about number of legal entities?

No claim C0290

An ERP consolidates several legal entities, runs intercompany, procurement approvals, budgets and statutory close. POS bookkeeping records sales, purchases, cash and simple statements for one business. Multi-entity consolidation and intercompany are listed as not in the catalog yet. Plan for: number of legal entities; approval chains; audit needs. No claim is made.

Open this answer on its own page

What should I plan for with “Property management system versus POS”, considering charge posting?

No claim C0291

A hotel PMS owns reservations, rooms, folios and night audit; a POS owns the restaurant, bar and shop sales that charge to a folio. The catalog plans room-service notes and credit on account but lists folios and night audit as gaps. Plan for: charge posting; room status; night audit. No claim is made.

Open this answer on its own page

How risky is “Dealer management system versus POS” to get wrong, with a focus on deals and desking?

No claim C0292

A DMS owns vehicle or equipment inventory, deals, finance and insurance, title paperwork and manufacturer warranty claims; a POS owns the parts counter, service lane and receipts. Dealer functions are listed as gaps, and most would be integrations. Plan for: deals and desking; manufacturer claims; parts counter. No claim is made.

Open this answer on its own page

Is “Forecourt control versus convenience-store POS” supported today, thinking about pump authorisation?

No claim C0293

Pump control, tank gauging and fuel pricing signs run on forecourt controllers with their own standards; the shop till sells snacks, tobacco and prepared food. Fuel functions are listed as gaps; a c-store till can be planned without them. Plan for: pump authorisation; wet-stock reconciliation; shop and fuel in one shift. No claim is made.

Open this answer on its own page

How does Simca approach “Enterprise retail media versus local-first loyalty”, considering consent?

No claim C0294

Large chains sell advertising and aggregated insights built on card data from most transactions. A local-first loyalty design keeps customer data on the shop's devices and shares nothing by default. Retail media is listed as a gap and may be left out on purpose. Plan for: consent; data sharing; who benefits. No claim is made.

Open this answer on its own page