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
How risky is “Sales reports” to get wrong, in particular regarding timezone and trading-day cut-offs?
○ Planned C0164
Totals by hour, product, category, staff and tender. Plan for: timezone and trading-day cut-offs; returns netted or not; taxes inclusive or not. In the catalog it is a plan and nothing is built.
Open this answer on its own page
How risky is “Cash and finance reports” to get wrong, in particular regarding multi-register consolidation?
○ Planned C0165
Drawer sessions, over and short, deposits and paid-outs. Plan for: multi-register consolidation; sessions open across midnight; corrections. In the catalog it is a plan and nothing is built.
Open this answer on its own page
Where does “Inventory reports” fit in Simca, in particular regarding valuation method?
○ Planned C0166
Stock on hand, valuation, movements, expiry, slow movers. Plan for: valuation method; negative stock; lot-level detail. In the catalog it is a plan and nothing is built.
Open this answer on its own page
Where does “People and operations reports” fit in Simca, considering privacy of staff data?
○ Planned C0167
Hours, sales per person, voids and discounts, tasks. Plan for: privacy of staff data; overtime; shared logins. In the catalog it is a plan and nothing is built.
Open this answer on its own page
What goes wrong with “Dashboards” in a shop, thinking about offline refresh?
○ Planned C0168
A single view of the day's sales and cash. Plan for: offline refresh; many stores; colour-only signals. In the catalog it is a plan and nothing is built.
Open this answer on its own page
How does Simca approach “Report engine”, especially around large exports?
○ Planned C0169
Filters, grouping, scheduling and export in one engine instead of one-off reports. Plan for: large exports; saved filters; export formats. In the catalog it is a plan and nothing is built.
Open this answer on its own page
Is “Local analytics” supported today, in particular regarding small data?
○ Planned C0170
Smart assistance computed on the device without sending data out. Plan for: small data; explanations; wrong suggestions. In the catalog it is a plan and nothing is built.
Open this answer on its own page
How risky is “Bookkeeping reports” to get wrong, in particular regarding cash versus accrual?
○ Planned C0171
Ledger, books and statements for small businesses. Plan for: cash versus accrual; chart of accounts; period locks. In the catalog it is a plan and nothing is built.
Open this answer on its own page
What should I plan for with “Tax reports”, considering rate changes mid-period?
○ Planned C0172
Reports that support tax filing; they never replace professional review. Plan for: rate changes mid-period; exempt sales; corrections. In the catalog it is a plan and nothing is built.
Open this answer on its own page
Is “Logistics and route reports” supported today, with a focus on missed stops?
○ Planned C0173
Deliveries, driver cash and route performance. Plan for: missed stops; backhaul; disputes. In the catalog it is a plan and nothing is built.
Open this answer on its own page
What should I plan for with “Multi-store consolidation”, especially around different tax settings?
○ Planned C0174
Combining numbers from several stores. Plan for: different tax settings; sync gaps; currency. In the catalog it is a plan and nothing is built.
Open this answer on its own page
What is the plan for “Exception reports”, thinking about thresholds?
○ Planned C0175
Voids, discounts, no-sales, price overrides and edits after the fact. Plan for: thresholds; alert fatigue; staff privacy. In the catalog it is a plan and nothing is built.
Open this answer on its own page